Posted On: Dec 17, 2018
As customers build applications, they need to reference sensitive information such as database credentials, tokens, configuration variables or SSH keys. Previously, customers 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.
Now, you have new task definition conventions for accessing sensitive information stored in AWS Systems Manager Parameter Store . You can still set, get, update and delete secrets via existing AWS Systems Manager Parameter Store APIs. However, task definitions can now be used to designate which of those secrets should be exposed to what containers.
You can learn more about the feature in ECS documentation. Also, please review the Fargate documentation to understand potential impact to tasks in cases of certain security updates to the underlying infrastructure.
Platform version 1.3* is available in all regions that AWS Fargate is available. See the global region table for more information on AWS regions and services.
Note: This feature is available via CLI/SDK and will be available in console for all Fargate regions by Friday, December 21, 2018. Additionally, if you are launching your tasks or services before this date, please use version 1.3 directly instead of the LATEST label.