Book Image

Docker on Amazon Web Services

By : Justin Menga
Book Image

Docker on Amazon Web Services

By: Justin Menga

Overview of this book

Over the last few years, Docker has been the gold standard for building and distributing container applications. Amazon Web Services (AWS) is a leader in public cloud computing, and was the first to offer a managed container platform in the form of the Elastic Container Service (ECS). Docker on Amazon Web Services starts with the basics of containers, Docker, and AWS, before teaching you how to install Docker on your local machine and establish access to your AWS account. You'll then dig deeper into the ECS, a native container management platform provided by AWS that simplifies management and operation of your Docker clusters and applications for no additional cost. Once you have got to grips with the basics, you'll solve key operational challenges, including secrets management and auto-scaling your infrastructure and applications. You'll explore alternative strategies for deploying and running your Docker applications on AWS, including Fargate and ECS Service Discovery, Elastic Beanstalk, Docker Swarm and Elastic Kubernetes Service (EKS). In addition to this, there will be a strong focus on adopting an Infrastructure as Code (IaC) approach using AWS CloudFormation. By the end of this book, you'll not only understand how to run Docker on AWS, but also be able to build real-world, secure, and scalable container platforms in the cloud.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Creating IAM users, groups, and roles


After securing your root account using MFA, you should next immediately create identity access and management (IAM) users, groups, and roles in your account for day-to-day access. IAM is the recommended approach for day-to-day administration and access to your AWS account and you should restrict root account access for billing or emergency purposes only. Before you can continue, you will need to know your AWS account ID, which you can see in the previous screenshot, in the serial number of your MFA device (note that this will be a different number than that which is shown). Write this account number down, as it will be required as you configure various IAM resources.

Creating IAM roles

The standard practice for creating IAM resources is to create roles that a given user can assume, which grants the user elevated privileges for a limited period of time (typically up to 1 hour). At a minimum, you need to create one IAM role by default:

  • admin: This role grants...