Using AWS single sign-on within your Docker containers

If you deploy applications to Amazon AWS EC2 instances, you probably make a lot of use of Amazon-specific features. In my case, I happen to use Amazon’s Systems Manager to store configuration parameters for my applications. When developing code locally I would also like to be able to run these programs locally in Docker containers. Although you could have two separate sets of configuration files, one for local and one for deployment, we might as well put all our configuration files into AWS parameter store. Let’s walk through how we can make this work. <img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*JIiLMbtop4ZrEYZciGxwsw.png" style="height:467px; width:700px" /> Leverage AWS security within your local Docker stack just like in production (<a href="https://www.rawpixel.com/image/5921739/photo-image-background-public-domain-free" rel="noopener ugc nofollow" target="_blank">rawpixel</a>) <h2>Understanding an AWS single sign-on session</h2> The <a href="https://aws.amazon.com/cli/" rel="noopener ugc nofollow" target="_blank">Amazon AWS system provides a command-line interface program, AWSCLI</a>. With this program, we can log on to an AWS session and link ourselves to our AWS account: <a href="https://tedspence.com/using-aws-single-sign-on-within-your-docker-containers-eb95d0cc377a">Learn More</a>