Answer - A and C.
The AWS documentation mentions that you should ensure the Retention field is marked as "Create Snapshot" for saving a snapshot before the termination of the environment.
This will ensure that we can create a database from the snapshot that is created.
AWS Elastic Beanstalk provides support for running RDS instances in your Elastic Beanstalk environment.
This works great for development and testing environments.
However, it isn't ideal for a production environment because it ties the lifecycle of the database instance to the lifecycle of your application's environment.
Option B is incorrect since it is not necessary that the engine type only has to be MySQL.
Option D is incorrect since the option should be “Create Snapshot”.
For more information on managing a database in Elastic Beanstalk, please refer to the below URL-
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.db.html
Note:
For a production environment, AWS recommends launching a database instance outside of your environment and configure your application to connect to it outside of the functionality provided by Elastic Beanstalk.
Using a database instance that is external to your environment requires additional security groups and connection string configuration.
However, it also lets you connect to the database from multiple environments, use database types not supported with integrated databases, perform blue/green deployments, and tear down your environment without affecting the database instance.
To achieve the requirements of provisioning an RDS instance as part of the Elastic Beanstalk setup and preserving the database even after the environment is torn down, we can follow the below steps:
- Ensure the database is created as part of the Elastic Beanstalk development or testing environment:
We can create an RDS instance and attach it to the Elastic Beanstalk environment using the AWS Management Console or Elastic Beanstalk CLI. This ensures that the database is part of the environment and can be easily managed and scaled along with the application. When the environment is terminated, the RDS instance associated with the environment will also be terminated.
- Ensure that the retention for the database is marked as “Create Snapshot”:
By selecting the “Create Snapshot” retention option, we can preserve the database data even after the environment is torn down. When the RDS instance is terminated, a final snapshot of the database is created, which can be used to restore the database later. We can also specify a retention period for snapshots, which will automatically delete snapshots older than the specified period.
- Ensure that you only choose the MySQL engine type:
This option is not relevant to the requirements mentioned in the question. Elastic Beanstalk supports multiple database engines, including MySQL, PostgreSQL, and SQL Server. We can choose the database engine that best suits our application's requirements.
- Ensure that the retention for the database is marked as “Automated Backup”:
While this option can be used to preserve the database, it does not satisfy the requirement of preserving the database even after the environment is torn down. Automated backups are incremental backups taken daily, which can be used to restore the database to a specific point in time. However, these backups are stored in the same region as the RDS instance and will be deleted if the RDS instance is terminated.
In conclusion, options A and C are the correct answers to achieve the requirements of provisioning an RDS instance as part of the Elastic Beanstalk setup and preserving the database even after the environment is torn down.
