The latest articles on DEV Community by Farrukh Naeem (@farrukhnaeem14). https://dev.to/farrukhnaeem14 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F193779%2F5c26f793-37ae-4545-a7d9-298fdc3e6293.jpg https://dev.to/farrukhnaeem14 en Farrukh Naeem Thu, 11 Jul 2019 15:55:34 +0000 https://dev.to/farrukhnaeem14/ecs-fargate-secrets-management-with-aws-parameter-store-3oij https://dev.to/farrukhnaeem14/ecs-fargate-secrets-management-with-aws-parameter-store-3oij <p>I've got a node.js application which obviously has some secrets/configurations to be managed in a config file. I am considering the AWS Parameter Store option for passing the configuration to my Fargate Task Definitions as very nicely explained by <a class="comment-mentioned-user" href="https://dev.to/sagarjauhari">@sagarjauhari</a> in his third method of secret management in this post: <a href="https://dev.to/sagarjauhari/3-ways-to-handle-secrets-in-aws-ecs-tasks-2olb">https://dev.to/sagarjauhari/3-ways-to-handle-secrets-in-aws-ecs-tasks-2olb</a></p> <p>I am just not able to grasp the idea that how would my application running inside the container would get these secrets like db passwords etc.</p> <p>Does passing the SSM secrets to the Task Definition automatically makes these secrets available inside the container? If yes, where are these and how to access them within my application?</p> devops docker aws