Deploy stages to different regions
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
I'm wondering what is the best way to achieve this. I've seen a couple of closed issues around the same topic, but none seem to provide a clear and final answer.
The best I found suggests using different profiles and then setting an AWS_PROFILE env var in the stage, but then the lambda that gets deployed cannot find such profile and crashes.
What are people using to accomplish this that is not just changing the profile before running chalice --deploy or having to specify a --profile?
Contributor guide
Research direction
Start by reviewing the closed issues about deploying Chalice stages to different regions and the existing profile behavior. Compare using AWS_PROFILE in a stage with changing the profile before chalice --deploy or passing --profile, then define a supported workflow that lets each stage deploy to its region without the deployed Lambda depending on a local profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100