chore: add policy for cicd deployment to api gateway and lambda #22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Used for Serverless deployments. Adapted from https://serverless-stack.com/chapters/customize-the-serverless-iam-policy.html To use, replace <region>, <account_no> and <service_name> with specific project details.
liangyuanruo
suggested changes
Oct 12, 2021
liangyuanruo
left a comment
liangyuanruo
left a comment
There was a problem hiding this comment.
Realised that this PR was dangling, so I'm going to request changes on it
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Used for CI/CD Serverless deployments to ApiGateway and Lambda .
To use, replace
<region>,<account_no>and<service_name>with specific project details.Problem
We don't have a reference for IAM permissions necessary to deploy to ApiGateway and Lambda.
Solution
Added reference IAM policy that limits access only to the project that is being deployed. Policy has been tested on Isomer site-creation-backend repo.
Policy is adapted from https://serverless-stack.com/chapters/customize-the-serverless-iam-policy.html