AWS Certified Developer - Associate
Get started today
Ultimate access to all questions.
In your current setup, the application is automatically deployed using AWS Elastic Beanstalk, and its YAML configuration files are stored in the .ebextensions folder. These configuration files are frequently added or updated. The DevOps team prefers not to redeploy the entire application whenever there are configuration changes. They want to handle the configurations externally and securely, ensuring that they are dynamically loaded into the application at runtime.
Which solution allows you to achieve this?
In your current setup, the application is automatically deployed using AWS Elastic Beanstalk, and its YAML configuration files are stored in the .ebextensions folder. These configuration files are frequently added or updated. The DevOps team prefers not to redeploy the entire application whenever there are configuration changes. They want to handle the configurations externally and securely, ensuring that they are dynamically loaded into the application at runtime.
Which solution allows you to achieve this?
Explanation:
Use SSM Parameter Store
AWS Systems Manager Parameter Store provides secure, hierarchical storage for configuration data management and secrets management. You can store data such as passwords, database strings, and license codes as parameter values. For the given use-case, as the DevOps team does not want to re-deploy the application every time there are configuration changes, so they can use the SSM Parameter Store to store the configuration externally.
Incorrect options:
Use Environment variables - Environment variables provide another way to specify configuration options and credentials, and can be useful for scripting or temporarily setting a named profile as the default. Your application is not running AWS CLI. Since the use-case requires the configuration to be stored securely, so using Environment variables is ruled out, as these are not encrypted at rest and these are visible in clear text in the AWS Console as well as in the response of some actions of the Elastic BeanStalk API.
Use Stage Variables - You can use stage variables for managing multiple release stages for API Gateway, this is not what you are looking for here.
Use S3 - S3 offers the same benefit as the SSM Parameter Store where there are no servers to manage. With S3 you have to set encryption and choose other security options and there are more chances of misconfiguring security if you share your S3 bucket with other objects. You would have to create a custom setup to come close to the parameter store. Use Parameter Store and let AWS handle the rest.