Containers on ECS "Fargate"

In this tutorial, we’ll build and publish a Docker container image to a private Elastic Container Registry (ECR), and spin up a load balanced Amazon Elastic Container Service (ECS) “Fargate” service, all in a handful of lines of code, using Pulumi Crosswalk for AWS.


  1. Install Docker Desktop
  2. Install Pulumi
  3. Configure Pulumi to use your AWS account

Deploying the App and Infrastructure

To get started, we will create a project, initialize it, then run pulumi up:

  1. Run pulumi new to create a new project:

    $ mkdir hello-fargate && cd hello-fargate
    $ pulumi new aws-typescript
  2. Create a subfolder app containing our sample Dockerized application:

    • Add the following file as Dockerfile:

      FROM nginx
      COPY index.html /usr/share/nginx/html
    • Add the following file as index.html:

          <title>Hello Fargate</title>
            <p>Hello AWS Fargate!</p>
            <p>Made with ❤️ with <a href="">Pulumi</a></p>
  3. Replace the contents of index.ts with the following:

    import * as awsx from "@pulumi/awsx";
    // Create a load balancer to listen for requests and route them to the container.
    let lb = new"nginx", { port: 80 });
    // Define the service, building and publishing our "./app/Dockerfile", and using the load balancer.
    let service = new awsx.ecs.FargateService("nginx", {
        desiredCount: 2,
        taskDefinitionArgs: {
            containers: {
                nginx: {
                    image: awsx.ecs.Image.fromPath("nginx", "./app"),
                    memory: 512,
                    portMappings: [ lb ],
    // Export the URL so we can easily access it.
    export const url = lb.endpoint.hostname;

    This example creates an automatic cluster in the default AWS VPC to run our “Fargate” service.

  4. Ensure you have the following directory structure:

  5. Configure the AWS region you would like to use:

    $ pulumi config set aws:region us-east-1
  6. Preview and deploy changes via pulumi up. This will take a few minutes. Pulumi automatically builds and provisions an ECR container registry, builds the Docker container, and pushed the image into the repository. This all happens automatically and does not require manual configuration on your part:

    $ pulumi up
    Previewing changes:
        global: global
        info: Building container image 'pulum-164fa748-container': context=./app
    Do you want to perform this update? yes
    Updating stack 'container-quickstart-dev'
    url: ""
    info: 19 changes performed:
        + 19 resources created
    Update duration: 3m53.44141303s
  7. Test the resulting load balancer URL to see that our service is working!

    $ curl http://$(pulumi stack output url)
            <title>Hello Fargate</title>
            <p>Hello, containers!</p>
            <p>Made with ❤️ with <a href="">Pulumi</a></p>
  8. (Optional) To view the runtime logs from the container, use the pulumi logs command. To get a log stream, use pulumi logs --follow.

    $ pulumi logs --follow
    Collecting logs for stack container-quickstart-dev since 2018-05-22T14:25:46.000-07:00.
    2018-05-22T15:33:22.057-07:00[                  pulumi-nginx] - - [22/May/2018:22:33:22 +0000]
        "GET / HTTP/1.1" 200 189 "-" "curl/7.54.0" "-"

Clean Up

Let's remove the cloud resources that have been provisioned.

  1. Run pulumi destroy to tear down all resources.
  2. To delete the stack itself, run pulumi stack rm. Note that this command deletes all deployment history from the Pulumi Console.

Next Steps

For more information about containerized applications on AWS, please read these User Guides:

For an end-to-end application also includes serverless functions, see the Serverless plus Containers Thumbnailer tutorial.

For an example application that connects two containers, see the Voting App sample.

The code for this tutorial is available on GitHub.