AWS Secrets Manager support to specify sensitive information
You can now reference sensitive information in AWS Secrets Manager when using AWS Fargate PV 1.3. This means you can store sensitive information in either AWS Secrets manager or AWS Systems Manager Parameter Store. You can learn more about about it here: Specifying sensitive information to containers .
As you build applications, you need to reference sensitive information such as database credentials, tokens, configuration variables or SSH keys. Previously, you had to directly reference this sensitive information in the task definition or manage your own run-time secrets with custom solutions to decouple secrets from core application logic stored in container images. AWS Fargate now supports task definition conventions for accessing sensitive information stored in either AWS Secrets Manager and AWS Systems Manager Parameter Store.