-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support secret for ecs fargate task definition #1478
Comments
It will be at some point, but as you correctly noted it isn't right now. You can use the CloudFormation layer override mechanism to access CloudFormation capabilities that aren't exposed in our classes right now. |
I looked into this, but it appear the So there's nothing that can be done via CDK until that's available? |
Oh in that case, yes, it needs to be available in CloudFormation first. |
The request to support secrets from CloudFormation is being tracked on the containers roadmap: aws/containers-roadmap#97 |
CloudFormation added support for |
Add a union class to treat environment variable values whether they are given as clear text, from a SSM parameter or a secret. Closes aws#1478 BREAKING CHANGE: `environment` in `ecs.ContainerDefinition` now takes an object whose values are of `ecs.EnvironmentValue` type.
* added secrets array to ContainerDefinitionOptions * added secrets to renderContainerDefinition method
* added secrets array to ContainerDefinitionOptions * added secrets to renderContainerDefinition method
ECS container definition can be configured with secrets as per cloud formation specification
Add support for runtime secrets in containers by adding a union class to treat secret environment variable values whether they are pulled from a SSM parameter or a AWS Secrets secret. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html Closes #1478
I couldn't find a way to specify secret for task definition like this:
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html
Will this be supported?
Thanks,
Andy
The text was updated successfully, but these errors were encountered: