-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: API Gateway IAM (AWS_IAM) Authorizers #781
Labels
contributors/good-first-issue
Good first issue for a contributor
Comments
I don't get what this part means: Auth:
Authorizer: null
InvokeRole: null Is that showing how to override auth for a specific path using function events? |
Closed
@jlhood that's correct. I will update with clarification. |
8 tasks
@brettstack Ok. Would also be good to add a Path/Method? Otherwise it looks incomplete to me. Also a yaml comment to explain what this is demonstrating. |
We'll begin implementation based on this spec. |
3 tasks
Released with SAM v1.11.0! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an RFC for enabling IAM (AWS_IAM) auth type on APIs.
SAM Template:
CloudFormation/Swagger Output:
sigv4
security scheme to Swaggersigv4
to list ofsecurity
for each resource+method using AWS_IAMcredentials
tox-amazon-apigateway-integration
for each resource+method using AWS_IAMInvoking APIs with IAM auth requires requests to be signed using Signature Version 4 https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html (derived from an AWS secret access key). The generated API Gateway SDK performs Signature Version 4 signing for you. Alternatively, libraries such as https://github.com/mhart/aws4 exist to make signing requests simpler.
Resources:
The text was updated successfully, but these errors were encountered: