@sapessi Anyone actively working on that? Any help needed?

@ericofusco I am not aware of anyone working on this currently. Contributions are always welcome. :)

Calling the cloud function could difficult currently. SAM CLI does not yet resolve Fn:Sub intrinsic functions. We may be able to extract the function name and assume we are in the account and region specified but full ARNs won't be possible to support yet. This issue was originally created before SAM supported Custom Authorizers, so it's worth considering starting from local execution first and then expand to the cloud if needed.

The best place to start would be to do a quick write up, full design isn't probably needed. This will help orient/align us before getting deep into code. Happy to talk more on the #samdev channel as well.

Thanks @jfuss. I'll reach out on #samdev to get this started.

So is it currently impossible to execute an API Gateway locally with authorizer and lambda proxy integration?

So is it currently impossible to execute an API Gateway locally with authorizer and lambda proxy integration?

My testing seems to bear this out. As far as I can tell using the sam local start-api command simply ignores the existence of custom authorizers and passes the request straight to the API backing lambda functions.

SAM doesn't support custom authorizers when you run locally now (SAM version 0.48). So you can't test it by using "sam local start-api".

But it supports in SAM YAML template and you can use SAM CLI to build and deploy custom authorizers to you AWS cloud Api Gateway. It can work well if your YAML setup is correct.

This is a duplicate of #137.

Closing

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.