amazon web services - With AWS API Gateway and Lambda, i'm seeing the paths all prefixed with $default

Question

I'm using AWS API Gateway and Lambda

Configuration is as follows:

API Gateway: Protocol is HTTP, route is '$default', integration is to my lambda function, payload format is 1.0, and permissions are correctly configured, stage name is $default. Everything else is vanilla.

Lambda: Runtime is 'custom runtime' (not linux 2), with an executable called 'bootstrap'. It's actually written in Rust using Rocket + rocket_lamb but that shouldn't make much difference.

What i'm finding is that when you browse to the API Gateway Invoke URL, the lambda is called with path = '$default/' instead of '/' - eg it literally includes '$default'.

Am i missing something here? Where is this $default coming from? I thought using '$default' in the route was the wildcard?

Thanks

question from:https://stackoverflow.com/questions/66055623/with-aws-api-gateway-and-lambda-im-seeing-the-paths-all-prefixed-with-default

Answer 1

Stages help keep different versions of api active, typically used to maintain multiple environments. we can have stages like dev, qa, prod, etc.

Any changes we make to API will not be effective until we deploy to a particular stage.(unless auto-deploy is enabled)

Finally the route will be

https://${apidId}.execute-api.us-east-1.amazonaws.com/${stage}/${route}

Example 1: For /staff route, $default stage , abcdefgh api

https://abcdefgh.execute-api.us-east-1.amazonaws.com/staff

Example 2: for /staff route, dev stage , abcdefgh api

https://abcdefgh.execute-api.us-east-1.amazonaws.com/dev/staff

Example 3: for / route, $default stage , abcdefgh api https://abcdefgh.execute-api.us-east-1.amazonaws.com/

So, the $default path you are using in lambda function is because you are using $default stage.

For HTTP Api , When defining a new api, we can set the stage, which by default is $default

or we can add stages after it is created.