AWS Secrets should not be passed as container environment variables
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Description
This assessment verifies whether the environment parameter in container definitions includes key values such as AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, or ECS_ENGINE_AUTH_DATA. This evaluation does not extend to environmental variables sourced from external locations like Amazon S3. It is focused solely on the latest active revision of an Amazon ECS task definition.
Utilizing AWS Systems Manager Parameter Store can enhance the security posture of your organization. We recommend leveraging the Parameter Store to securely store secrets and credentials instead of directly embedding them in container instances or hardcoding them in your code.
From the console
To create parameters using SSM, see Creating Systems Manager parameters in the AWS Systems Manager User Guide. For more information about creating a task definition that specifies a secret, see Specifying sensitive data using Secrets Manager in the Amazon Elastic Container Service Developer Guide.
