This website uses cookies to ensure you get the best experience.
Learn more.
An Elastic Beanstalk application has a tested replacement environment. The team wants a controlled environment cutover while retaining the old environment for recovery. Which supported mechanism should it evaluate?
Published
- Rename a local ZIP file without deploying it to the replacement environment.
- Swap environment CNAMEs after validation and account for connection and DNS behavior.
- Assume creating the environment automatically migrates every stateful dependency.
- Delete the old environment before verifying the new one serves requests.
Comments — 0
Sign in to comment