Introduce AWS CloudFormation with API Gateway deployment example #351
Conversation
This file contains 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
Signed-off-by: Adam Pike <[email protected]>
- improved wording in some descriptive text - use `1password` as DNS namespace Signed-off-by: Adam Pike <[email protected]>
Signed-off-by: Adam Pike <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a new beta deployment example for AWS using CloudFormation.
This repository already includes examples for AWS that also use Amazon Elastic Container Service; this example uses API Gateway to provide a TLS endpoint instead of a discrete load balancer for a faster time-to-deploy, fewer managed components, and much lower cost.
ECS services are integrated with AWS Cloud Map for service discovery. A VPC with at least two public subnets is required and optionally created and managed by the stack. Credentials are stored in and provided by AWS Secrets Manager. Minimal IAM roles, policy, and security group resources are included for access control and principle of least privilege.