chore: add docs and example for multi region stacks #303
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
resources cannot be cleaned-up in CI. Updating README with TOC and multi-stack section
corymhall
force-pushed
the
corymhall/multi-region-example
branch
from
c715e35 to
69ba148
Compare
corymhall
changed the title
flostadler
approved these changes
Jan 2, 2025
| @@ -91,6 +91,28 @@ Try the workshop at https://apprunnerworkshop.com | |||
| Read the docs at https://docs.aws.amazon.com/apprunner | |||
| ``` | |||
|
|
|||
| ## Table of Contents | |||
There was a problem hiding this comment.
GitHub shows a ToC by default. I'm worried that the manually created one goes out of sync eventually
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 adds some docs on multi stack setup. The only scenario where you maybe should use multiple stacks is when you are deploying to multiple regions since stack is the most granular level you can configure the environment.
As part of this PR i've also added an example test that uses CloudFront and Lambda@Edge since that is a common scenario where users would need to deploy resources to multiple regions. The test is skipped because Lambda@Edge resources cannot be easily cleaned up (they are removed from all AWS regions in the background).