Skip to content
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

Update CloudFormation template example and documentation to enable externally managed VPC and DNS #341

Merged
merged 12 commits into from
Oct 1, 2024

Conversation

ag-adampike
Copy link
Member

@ag-adampike ag-adampike commented Sep 20, 2024

A stack that is created using our current CloudFormation template example includes a VPC with public subnets and associated resources and DNS records using Route 53. This PR includes changes to enhance the template, enabling customers to:

  • select an existing VPC and public subnets
  • exclude the DNS records from the stack

Documentation has been updated accordingly, and includes additional changes to align with our other deployment examples.

Additional enhancements:

  • updated TLS policy to enforce TLS 1.3
  • refactored and simplified Redis configuration
  • stripped redundant policy actions
  • specified ARM64 platform to reduce expected cost
  • stores unencoded values in AWS secrets
  • writes secrets to volume instead of env var values
  • reconfigured for zero-downtime rolling updates

Testing criteria:

  • update an existing stack deployed using the existing template and no other changes
  • create a new stack, specifying an existing VPC and subnets
  • create a new stack without specifying a Route 53 hosted zone

@ag-adampike ag-adampike requested a review from a team September 20, 2024 15:55
@ag-adampike ag-adampike force-pushed the solutions/rond/cfn-vpc-selector branch 3 times, most recently from 91c83fd to 6ca9d02 Compare September 23, 2024 16:09
ag-rdoucette and others added 12 commits September 23, 2024 15:15
…S validation and manual CNAME validation with external DNS providers.

Signed-off-by: Adam Pike <[email protected]>
…xibility in resource creation during deployment.

Signed-off-by: Adam Pike <[email protected]>
- revert object ordering to align with current template
- refactor DNS name references
- collpase subnet parameters to single field to simplify and allow arbitrary number
- refactor Redis config into startup command parameters
- remove redundant init containers from task definition
- specify ARM64 platform for reduced cost

Signed-off-by: Adam Pike <[email protected]>
- rework to conform to other deployment examples
- remove CLI instructions for brevity and clarity
- include instructions for creating DNS records when necessary
- include instructions for new parameters

Signed-off-by: Adam Pike <[email protected]>
- introduce volume for mounting secrets
- introduce sidecar (init) container with AWS CLI to mount secrets in volume
- refactor secret creation to store unencoded values
- moved secret read policy to task role from task execution role (task is now directly resonsible for reading secrets)
- restored default service deployment configuration to allow rolling updates
- removed redundant configuration entries including default values
- removed redundant quotation marks
@black-bryan
Copy link
Collaborator

Looks good so far. I have tested the first two criteria.

  1. update an existing stack deployed using the existing template and no other changes
  2. create a new stack, specifying an existing VPC and subnets

Copy link
Collaborator

@black-bryan black-bryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🎉
Tested criteria 3 as well.
Approved.

@ag-adampike
Copy link
Member Author

Thanks for the review, @black-bryan! 😊

@ag-adampike ag-adampike merged commit 1b856f3 into main Oct 1, 2024
@ag-adampike ag-adampike deleted the solutions/rond/cfn-vpc-selector branch October 1, 2024 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants