Book Image

Running Windows Containers on AWS

By : Marcio Morales
Book Image

Running Windows Containers on AWS

By: Marcio Morales

Overview of this book

Windows applications are everywhere, from basic intranet applications to high-traffic public APIs. Their prevalence underscores the importance of combining the same tools and experience for managing a modern containerized application with existing critical Windows applications to reduce costs, achieve outstanding operational excellence, and modernize quickly. This comprehensive guide to running and managing Windows containers on AWS looks at the best practices from years of customer interactions to help you stay ahead of the curve. Starting with Windows containers basics, you’ll learn about the architecture design that powers Amazon ECS, EKS, and AWS Fargate for Windows containers. With the help of examples and best practices, you’ll explore in depth how to successfully run and manage Amazon ECS, EKS, and AWS Fargate clusters with Windows containers support. Next, the book covers day 2 operations in detail, from logging and monitoring to using ancillary AWS tools that fully containerize existing legacy .NET Framework applications into containers without any code changes. The book also covers the most common Windows container operations, such as image lifecycle and working with ephemeral hosts. By the end of this book, you’ll have mastered how to run Windows containers on AWS and be ready to start your modernization journey confidently.
Table of Contents (22 chapters)
1
Part 1: Why Windows Containers on Amazon Web Services (AWS)?
4
Part 2: Windows Containers on Amazon Elastic Container Service (ECS)
9
Part 3: Windows Containers on Amazon Elastic Kubernetes Service (EKS)
14
Part 4: Operationalizing Windows Containers on AWS

Deploying Windows containers with AWS Copilot

AWS Copilot is an open source command-line interface that allows developers to build, release, and operate containerized applications on AWS App Runner, Amazon ECS, and AWS Fargate.

AWS Copilot abstracts all the network and cluster configurations from the developer and offers an intuitive command line, based on a set of questions that build and deploy your containerized application.

In the following figure, we have an example of how AWS Copilot works once the copilot init command is executed:

Figure 15.3 – AWS Copilot init

Figure 15.3 – AWS Copilot init

Then, you need to answer four basic questions:

  1. What would you like to name your application?
  2. Which service type best represents your service’s architecture?
  3. What do you want to name this load-balanced web service?
  4. Which Dockerfile would you like to use for the frontend?

Once you want Dockerfile to build your Windows container image, AWS Copilot...