Access container applications privately on Amazon ECS by using AWS Fargate, AWS PrivateLink, and a Network Load Balancer - AWS Prescriptive Guidance
SummaryPrerequisites and limitationsArchitectureToolsEpicsRelated resources

Access container applications privately on Amazon ECS by using AWS Fargate, AWS PrivateLink, and a Network Load Balancer

Created by Kirankumar Chandrashekar (AWS)

Environment: Production

Technologies: Containers & microservices; Networking; Security, identity, compliance; Web & mobile apps

Workload: All other workloads

AWS services: Amazon EC2 Container Registry; Amazon ECS; Amazon EFS; Amazon RDS; Amazon VPC; Elastic Load Balancing (ELB); AWS Lambda

This pattern describes how to privately host a Docker container application on the Amazon Web Services (AWS) Cloud by using Amazon Elastic Container Service (Amazon ECS) with an AWS Fargate launch type, behind a Network Load Balancer, and access the application by using AWS PrivateLink. Amazon Relational Database Service (Amazon RDS) hosts the relational database for the application running on Amazon ECS with high availability (HA). You can use Amazon Elastic File System (Amazon EFS) if the application requires persistent storage.

This pattern uses a Fargate launch type for the Amazon ECS service running the Docker applications, with a Network Load Balancer at the front end. It can then be associated with a virtual private cloud (VPC) endpoint for access through AWS PrivateLink. This VPC endpoint service can then be shared with other VPCs by using their VPC endpoints.

You can use Fargate with Amazon ECS to run containers without having to manage servers or clusters of Amazon Elastic Compute Cloud (Amazon EC2) instances. You can also use an Amazon EC2 Auto Scaling group instead of Fargate. For more information, see Access container applications privately on Amazon ECS by using AWS PrivateLink and a Network Load Balancer.

Prerequisites

Using PrivateLink to access a container app on Amazon ECS with an AWS Fargate launch type.

Technology stack

  • Amazon CloudWatch

  • Amazon Elastic Container Registry (Amazon ECR)

  • Amazon ECS

  • Amazon EFS

  • Amazon RDS

  • Amazon Simple Storage Service (Amazon S3)

  • AWS Fargate

  • AWS Lambda

  • AWS PrivateLink

  • AWS Secrets Manager

  • Application Load Balancer

  • Network Load Balancer

  • VPC

Automation and scale

  • Amazon ECS – Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service that makes it easy to run, stop, and manage containers on a cluster.

  • Amazon ECR – Amazon Elastic Container Registry (Amazon ECR) is a managed AWS container image registry service that is secure, scalable, and reliable.

  • Amazon EFS – Amazon Elastic File System (Amazon EFS) provides a simple, scalable, fully managed elastic NFS file system for use with AWS Cloud services and on-premises resources.

  • AWS Fargate – AWS Fargate is a technology that you can use with Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances.

  • AWS Lambda – Lambda is a compute service that lets you run code without provisioning or managing servers.

  • Amazon RDS – Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the AWS Cloud.

  • Amazon S3 – Amazon Simple Storage Service (Amazon S3) is storage for the internet. It is designed to make web-scale computing easier for developers.

  • AWS Secrets Manager – Secrets Manager helps you replace hardcoded credentials in your code, including passwords, with an API call to Secrets Manager to retrieve the secret programmatically.

  • Amazon VPC – Amazon Virtual Private Cloud (Amazon VPC) helps you launch AWS resources into a virtual network that you've defined.

  • Elastic Load Balancing – Elastic Load Balancing (ELB) distributes incoming application or network traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in multiple Availability Zones.

  • Docker – Docker helps developers to easily pack, ship, and run any application as a lightweight, portable, and self-sufficient container.

TaskDescriptionSkills required

Create a VPC.

  1. Sign in to the AWS Management Console, and open the Amazon VPC console. Choose Create VPC, and choose VPC and more. 

  2. Enter a name for your VPC, and choose an appropriate CIDR block range.

  3. Specify two Availability Zones, two public subnets, four private subnets. Two private subnets are for Amazon ECS tasks, and two private subnets are for Amazon RDS databases.

  4. Specify one NAT gateway for each Availability Zone.

  5. Choose Create VPC.

Cloud administrator
TaskDescriptionSkills required

Create a Network Load Balancer.

  1. Open the Amazon EC2 console, and choose the AWS Region that contains your VPC. 

  2. Under Load balancing, choose Load balancers, and choose Create load balancer. 

  3. Choose Network Load Balancer, and choose Create. 

  4. On the Configure load balancer page, configure your Network Load Balancer and listener. Important: Make sure you choose your Network Load Balancer's scheme as Internal. 

  5. Choose the applicable security settings, configure a security group and a target group. Choose IP as the Target type in the Configure routing section. Make sure you do not register a target. 

  6. When you have configured all the settings, choose Next: Review, and then choose Create.

For help with this and other stories, see the Related resources section.

Cloud administrator

Create an Application Load Balancer.

  1. On the Amazon EC2 console, choose the same Region that contains your VPC. 

  2. Under Load balancing, choose Load balancers, and choose Create load balancer. 

  3. Choose Application Load Balancer, and choose Create. 

  4. Configure your Application Load Balancer and its listener. Important: Make sure you choose your Application Load Balancer's scheme as Internal. 

  5. Choose the applicable security settings, configure a security group and a target group. Choose IP as the Target type in the Configure routing section. Make sure you do not register a target. 

  6. When you have configured all the settings, choose Next: Review, and then choose Create.

Cloud administrator
TaskDescriptionSkills required

Create an Amazon EFS file system.

  1. Open the Amazon EFS console, and choose Create file system. 

  2. In the Create file system dialog box, enter a name for your file system, and choose your VPC. 

  3. Choose Create to create the file system. 

  4. Set up and configure your Amazon EFS file system.

Cloud administrator

Mount targets for the subnets.

  1. Return to the Amazon EFS console, and choose File systems. The File systems page shows the Amazon EFS file systems in your account. 

  2. Choose the file system that you created, and choose Manage to display the Availability Zone. 

  3. To add a mount target, choose Add mount target, and add the four private subnets that you created.

Cloud administrator

Verify that the subnets are mounted as targets.

  1. On the Amazon EFS console, choose File systems. 

  2. Choose Network to display the list of existing mount targets. Make sure that these include the four subnets that you created.

Cloud administrator
TaskDescriptionSkills required

Create an S3 bucket.

Open the Amazon S3 console and create an S3 bucket to store your application’s static assets, if required.

Cloud administrator
TaskDescriptionSkills required

Create an AWS KMS key to encrypt the Secrets Manager secret.

Open the AWS Key Management Service (AWS KMS) console and create a KMS key.

Cloud administrator

Create a Secrets Manager secret to store the Amazon RDS password.

  1. Open the AWS Secrets Manager console, and create a new secret by choosing Store a new secret. 

  2. Choose the KMS key that you created, and store your new secret.

Cloud administrator
TaskDescriptionSkills required

Create a DB subnet group.

  1. Open the Amazon RDS console, and choose Subnet groups. 

  2. Choose Create DB subnet group, and enter a name and description for your DB subnet group. 

  3. Choose the VPC that you created earlier, and choose the Availability Zones and subnets. Then choose Create.

Cloud administrator

Create an Amazon RDS instance.

Create and configure an Amazon RDS instance within the private subnets. Make sure that Multi-AZ is turned on for high availability (HA).

Cloud administrator

Load data to the Amazon RDS instance.

Load the relational data required by your application into your Amazon RDS instance. This process will vary depending on your application's needs, as well as how your database schema is defined and designed.

DBA
TaskDescriptionSkills required

Create an ECS cluster.

  1. Open the Amazon ECS console, and choose Clusters. 

  2. Choose Create clusters, and set up an ECS cluster according to your required specifications.

Cloud administrator

Create the Docker images.

Create the Docker images by following the instructions in the AWS documentation.

Cloud administrator

Create an Amazon ECR repository.

  1. Open the Amazon ECR console, and choose Repositories. 

  2. Choose Create repository, and enter a unique name for your repository. 

  3. Configure the repository according to your specifications, including AWS KMS encryption if required.

Cloud administrator, DevOps engineer

Push the Docker images to the Amazon ECR repository.

  1. Identify the Docker image you want to push, and run the docker images command in AWS CLI. 

  2. Tag your image with the Amazon ECR registry, repository, and optional image tag name combination. 

  3. Push the Docker image by running the docker push command. 

  4. Repeat these steps for all required images.

Cloud administrator

Create an Amazon ECS task definition.

A task definition is required to run Docker containers in Amazon ECS. 

  1. Return to the Amazon ECS console, choose Task definitions, and then choose Create new task definition. 

  2. On the Select compatibilities page, select the launch type that your task should use, and choose Next step.

For help with setting up your task definition, see “Creating a task definition” in the Related resources section. Important: Make sure you provide the Docker images that you pushed to Amazon ECR.

Cloud administrator

Create an ECS service and choose Fargate as the launch type.

  1. Create an Amazon ECS service by using the ECS cluster you created earlier. Make sure you choose Fargate as the launch type.

  2. Choose the task definition created in the previous step, and choose the target group of the Application Load Balancer.

Cloud administrator
TaskDescriptionSkills required

Set up the AWS PrivateLink endpoint.

  1. Open the Amazon VPC console, and create an AWS PrivateLink endpoint. 

  2. Associate this endpoint with the Network Load Balancer, which makes the application hosted on Amazon ECS available privately to customers. 

Cloud administrator
TaskDescriptionSkills required

Create a VPC endpoint.

Create a VPC endpoint for the AWS PrivateLink endpoint that you created earlier. The VPC endpoint Fully Qualified Domain Name (FQDN) will point to the AWS PrivateLink endpoint FQDN. This creates an elastic network interface to the VPC endpoint service that the Domain Name Service endpoints can access.

Cloud administrator
TaskDescriptionSkills required

Create the Lambda function.

Open the Lambda console and create a Lambda function to update the Application Load Balancer IP addresses as targets for the Network Load Balancer. For more information on this, see the Using AWS Lambda to enable static IP addresses for Application Load Balancers blog post.

App developer

Create the load balancers:

Create an Amazon EFS file system:

Create a Secrets Manager secret:

Create an Amazon RDS instance:

Create the Amazon ECS components

Other resources: