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

Chapter 3, Getting Started with AWS


  1. True.
  2. False – you should set up an administrative IAM user to perform administrative actions on your account.  The root account should only be used for billing or emergency access.
  3. False – the AWS best practice is to create IAM roles that define a set of IAM permissions that apply to one or more resources.  You should then grant IAM users/groups the ability to assume a given role or set of roles as applicable to your use cases.
  4. AdministratorAccess.
  5. pip install awscli --user
  6. False – you must store an access key ID and a secret access key.
  7. In the ~/.aws/credentials file.
  8. You need to add the mfa_serial parameter to the profile and specify the ARN of the MFA device for the user.
  9. True.
  10. True.
  11. No – CloudFormation always attempts to create any new resources successfully before removing old resources.  In this scenario, because you have defined a fixed Name value, CloudFormation will not be able to create a new resource with the same name.