Fork me on GitHub

Tutorial: Containers on ECS Fargate

In this tutorial, we’ll use JavaScript to build and deploy a simple container to AWS Fargate. The code for this tutorial is available on GitHub.


  1. Install Pulumi
  2. Configure the AWS CLI

Serve an HTML file in an NGINX container

  1. Make sure Docker is installed and running.

  2. Run pulumi new:

    $ pulumi new aws-javascript --dir container-quickstart
    $ cd container-quickstart
  3. Replace the contents of index.js with the following:

    const cloud = require("@pulumi/cloud-aws");
    let service = new cloud.Service("pulumi-nginx", {
        containers: {
            nginx: {
                build: "./app",
                memory: 128,
                ports: [{ port: 80 }],
        replicas: 2,
    // export just the hostname property of the container frontend
    exports.url = service.defaultEndpoint.apply(e => `http://${e.hostname}`);

    This example uses cloud.Service, which is a high-level, convenient interface for building containers and provisioning an AWS container service.

  4. Create a subfolder app with the following files:

    • Add the following file as Dockerfile:
      FROM nginx
      COPY index.html /usr/share/nginx/html
    • Add the following file as index.html:
        <head><title>Hello World</title><meta charset="UTF-8"></head>
      <body><p>Hello containers!</p><p>Made with ❤️ with <a href="">Pulumi</a></p></body>
  5. Ensure you have the following directory structure:

  6. Install the @pulumi/cloud-aws NPM package:

    $ npm install --save @pulumi/cloud-aws @pulumi/cloud
  7. Configure Pulumi to use AWS Fargate. (Note: Fargate is currently available only in us-east-1, us-east-2, us-west-2, and eu-west-1).

    $ pulumi config set cloud-aws:useFargate true
  8. Preview and deploy changes via pulumi update. This will take a few minutes. Pulumi automatically builds and provisions an AWS container repository in ECR, builds the Docker container, and places the image in the repository. This all happens automatically and does not require manual configuration on your part.

    $ pulumi update
    Previewing update of stack 'container-quickstart-dev'
    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
  9. View the endpoint URL and run curl:

    $ pulumi stack output
    Current stack outputs (1)  
        OUTPUT                  VALUE
    $ curl $(pulumi stack output url)
        <title>Hello world</title><meta charset="UTF-8">
    <body><p>Hello, containers!</p><p>Made with ❤️ with <a href="">Pulumi</a></p>
  10. 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 an end-to-end application also includes serverless functions, see the Serverless and Container Thumbnailer tutorial.

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