AWS Elastic Beanstalk supports Database Decoupling in an Elastic Beanstalk Environment
AWS Elastic Beanstalk now supports decoupling a database running in an Elastic Beanstalk environment. Previously, a database instance created by Elastic Beanstalk was tied to the lifecycle of the environment. With this launch, the lifecycle of your database instance will not be tied to your application’s environment lifecycle, and you can decouple a database managed by Elastic Beanstalk from a Beanstalk environment. The environment’s health is not affected by the decoupling operation and you can keep the database operational as an external database, available for multiple environments to connect to it. You also have the option to terminate an Elastic Beanstalk environment while leaving the database operational.
AWS Elastic Beanstalk now supports decoupling a database running in an Elastic Beanstalk environment. Previously, a database instance created by Elastic Beanstalk was tied to the lifecycle of the environment. With this launch, the lifecycle of your database instance will not be tied to your application’s environment lifecycle, and you can decouple a database managed by Elastic Beanstalk from a Beanstalk environment. The environment’s health is not affected by the decoupling operation and you can keep the database operational as an external database, available for multiple environments to connect to it. You also have the option to terminate an Elastic Beanstalk environment while leaving the database operational.
You can configure the database lifecycle using the Elastic Beanstalk Console or with HasCoupledDatabase and DBDeletionPolicy options in the aws:rds:dbinstance namespace. For more information, see Adding a database to your Elastic Beanstalk environment in the AWS Elastic Beanstalk Developer Guide.