Container Service on AWS
The AWS Container Service template scaffolds a Pulumi project that deploys a containerized service to AWS. The architecture includes an Amazon ECS cluster for orchestration, AWS Fargate for serverless compute, an Application Load Balancer for internet ingress, and an Amazon Elastic Container Registry (ECR) repository for the container image. The template ships with an Nginx Dockerfile so the project deploys end to end out of the box.
Using this template#
To use this template to deploy an ECS cluster running your container service, make sure you’ve installed Pulumi and configured your AWS credentials, then create a new project using the template in the language of your choice:
TypeScript
Python
Go
C#
YAML
HCLmkdir my-container-service && cd my-container-servicepulumi new container-aws-typescriptAlternatively, you can create and configure a new project with this template (container-aws-typescript) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-aws-pythonAlternatively, you can create and configure a new project with this template (container-aws-python) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-aws-goAlternatively, you can create and configure a new project with this template (container-aws-go) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-aws-csharpAlternatively, you can create and configure a new project with this template (container-aws-csharp) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-aws-yamlAlternatively, you can create and configure a new project with this template (container-aws-yaml) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-aws-hclAlternatively, you can create and configure a new project with this template (container-aws-hcl) in Pulumi Cloud.
Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a complete Pulumi project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in index.tsindex.js__main__.pymain.goProgram.csProgram.fsProgram.vbApp.javaPulumi.yaml for a closer look.
Deploying the project#
The template requires no additional configuration. Once the new project is created, you can deploy it immediately with pulumi up:
pulumi upWhen the deployment completes, Pulumi exports the following stack output values:
- url
The HTTP URL for the container’s endpoint.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed url, for example, can be used from the command line to open the newly deployed container service in your favorite web browser:
open $(pulumi stack output url)Customizing the project#
Projects created with the Container Service template expose the following configuration settings:
- container_port
Specifies the port mapping for the container. Defaults to port 80.
- cpu
Specifies the amount of CPU to use with each task or each container within a task. Defaults to 512.
- memory
Specifies the amount of memory to use with each task or each container within a task. Defaults to 128.
- image
Specifies the location of the Dockerfile used to build the container image that is run. Defaults to the Dockerfile in the
appfolder.
- container_port
Specifies the port mapping for the container. Defaults to port 80.
- cpu
Specifies the amount of CPU to use with each task or each container within a task. Defaults to 512.
- memory
Specifies the amount of memory to use with each task or each container within a task. Defaults to 128.
- image
Specifies the location of the Dockerfile used to build the container image that is run. Defaults to the Dockerfile in the
appfolder.
- container_port
Specifies the port mapping for the container. Defaults to port 80.
- cpu
Specifies the amount of CPU to use with each task or each container within a task. Defaults to 512.
- memory
Specifies the amount of memory to use with each task or each container within a task. Defaults to 128.
- image
Specifies the location of the Dockerfile used to build the container image that is run. Defaults to the Dockerfile in the
appfolder.
- container_port
Specifies the port mapping for the container. Defaults to port 80.
- cpu
Specifies the amount of CPU to use with each task or each container within a task. Defaults to 512.
- memory
Specifies the amount of memory to use with each task or each container within a task. Defaults to 128.
- image
Specifies the location of the Dockerfile used to build the container image that is run. Defaults to the Dockerfile in the
appfolder.
- container_port
Specifies the port mapping for the container. Defaults to port 80.
- cpu
Specifies the amount of CPU to use with each task or each container within a task. Defaults to 512.
- memory
Specifies the amount of memory to use with each task or each container within a task. Defaults to 128.
- image
Specifies the location of the Dockerfile used to build the container image that is run. Defaults to the Dockerfile in the
appfolder.
- container_port
Specifies the port mapping for the container. Defaults to port 80.
- cpu
Specifies the amount of CPU to use with each task or each container within a task. Defaults to 512.
- memory
Specifies the amount of memory to use with each task or each container within a task. Defaults to 128.
All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with pulumi config set:
Using your own container image#
If you already have a container image you’d like to build your container service with, you can do so either by replacing the Dockerfile in the app folder or by configuring the stack to point to another folder on your computer with the image setting:
pulumi config set image ../my-existing-imagepulumi upIf you already have a container image you’d like to build your container service with, you can do so either by replacing the Dockerfile in the app folder or by configuring the stack to point to another folder on your computer with the image setting:
pulumi config set image ../my-existing-imagepulumi upIf you already have a container image you’d like to build your container service with, you can do so either by replacing the Dockerfile in the app folder or by configuring the stack to point to another folder on your computer with the image setting:
pulumi config set image ../my-existing-imagepulumi upIf you already have a container image you’d like to build your container service with, you can do so either by replacing the Dockerfile in the app folder or by configuring the stack to point to another folder on your computer with the image setting:
pulumi config set image ../my-existing-imagepulumi upIf you already have a container image you’d like to build your container service with, you can do so either by replacing the Dockerfile in the app folder or by configuring the stack to point to another folder on your computer with the image setting:
pulumi config set image ../my-existing-imagepulumi upIf you already have a container image you’d like to build your container service with, you can do so by replacing the Dockerfile and application code in the app folder, then redeploying with pulumi up.
Cleaning up#
You can cleanly destroy the stack and all of its infrastructure with pulumi destroy:
pulumi destroyLearn more#
- Browse other architecture templates in the Templates gallery.
- Explore the AWS and AWSx provider API docs in the Pulumi Registry.
- Walk through Pulumi from the ground up in Pulumi Tutorials.
- Read the latest container posts on the Pulumi blog.