Skip to main content

PERN Stack Voting App

Voting app that uses containers

This example lives in the pulumi/examples repository. Check out just this directory to use it:

Get started with this example
git clone --filter=blob:none --sparse https://github.com/pulumi/examples pulumi-examples
git -C pulumi-examples sparse-checkout set aws-ts-pern-voting-app
cd pulumi-examples/aws-ts-pern-voting-app

A simple voting app that uses React, Express, PostgreSQL, and NodeJS.

The example shows how easy it is to deploy containers into production and to connect them to one another. Since the example defines a custom container, Pulumi does the following:

  • Builds the Docker image
  • Provisions AWS Container Registry (ECR) instance
  • Pushes the image to the ECR instance
  • Creates a new ECS task definition, pointing to the ECR image definition

Prerequisites#

  1. Install Pulumi
  2. Configure Pulumi for AWS
  3. Configure Pulumi for TypeScript
  4. Install Docker

Deploying and running the program#

  1. Create a new stack:

    Terminal window
    pulumi stack init aws-ts-pern-voting-app
  2. Set the AWS region and the usernames and passwords for a set of accounts the project uses:

    Terminal window
    pulumi config set aws:region us-west-2
    pulumi config set sql-admin-name <NAME>
    pulumi config set sql-admin-password <PASSWORD> --secret
    pulumi config set sql-user-name <NAME>
    pulumi config set sql-user-password <PASSWORD> --secret

    The user names must be valid PostgreSQL identifiers, and the passwords must satisfy the RDS master password rules (8-128 printable ASCII characters, excluding /, ", @, and spaces).

  3. Restore NPM modules via npm install or yarn install.

  4. Run pulumi up -y to deploy changes:

    Terminal window
    Updating (aws-ts-pern-voting-app):
    Type Name Status Info
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + ├─ awsx:x:ecs:FargateTaskDefinition server-side-service created
    + ├─ awsx:x:ecs:FargateTaskDefinition server-side-service created
    + ├─ aws:iam:Role server-side-service-execution created
    + ├─ awsx:x:ecs:FargateTaskDefinition server-side-service created
    + ├─ aws:cloudwatch:LogGroup server-side-service created
    + ├─ aws:iam:RolePolicyAttachment server-side-service-task-fd1a00e5 created
    + ├─ awsx:x:ecs:FargateTaskDefinition server-side-service created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + pulumi:pulumi:Stack voting-app-aws-ts-pern-voting-app created
    + ├─ aws:iam:Role client-side-service-execution created
    + ├─ aws:iam:Role client-side-service-execution created
    + ├─ aws:iam:Role client-side-service-execution created
    + ├─ aws:ecr:LifecyclePolicy client-side-service created
    + ├─ aws:iam:RolePolicyAttachment client-side-service-task-fd1a00e5 created
    + ├─ aws:iam:RolePolicyAttachment client-side-service-task-32be53a2 created
    + ├─ aws:iam:RolePolicyAttachment client-side-service-execution-9a42f520 created
    + └─ aws:ecs:TaskDefinition client-side-service created
    + ├─ awsx:lb:NetworkLoadBalancer client-side-listener created
    + ├─ awsx:lb:NetworkTargetGroup client-side-listener created
    + └─ aws:lb:TargetGroup client-side-listener created
    + ├─ awsx:lb:NetworkListener client-side-listener created
    + └─ aws:lb:Listener client-side-listener created
    + └─ aws:lb:LoadBalancer client-side-listener created
    + ├─ awsx:lb:NetworkLoadBalancer server-side-listener created
    + ├─ awsx:lb:NetworkTargetGroup server-side-listener created
    + └─ aws:lb:TargetGroup server-side-listener created
    + ├─ awsx:lb:NetworkListener server-side-listener created
    + └─ aws:lb:Listener server-side-listener created
    + └─ aws:lb:LoadBalancer server-side-listener created
    + ├─ awsx:x:ecs:FargateService client-side-service created
    + └─ aws:ecs:Service client-side-service created
    + ├─ awsx:x:ecs:Cluster default-cluster created
    + ├─ awsx:x:ec2:SecurityGroup default-cluster created
    + ├─ awsx:x:ec2:EgressSecurityGroupRule default-cluster-egress created
    + └─ aws:ec2:SecurityGroupRule default-cluster-egress created
    + ├─ awsx:x:ec2:IngressSecurityGroupRule default-cluster-ssh created
    + └─ aws:ec2:SecurityGroupRule default-cluster-ssh created
    + ├─ awsx:x:ec2:IngressSecurityGroupRule default-cluster-containers created
    + └─ aws:ec2:SecurityGroupRule default-cluster-containers created
    + └─ aws:ec2:SecurityGroup default-cluster created
    + └─ aws:ecs:Cluster default-cluster created
    + ├─ aws:ec2:Vpc app-vpc created
    + ├─ awsx:x:ec2:Vpc default-vpc created
    + ├─ awsx:x:ec2:Subnet default-vpc-public-1 created
    + └─ awsx:x:ec2:Subnet default-vpc-public-0 created
    + ├─ aws:ec2:Subnet second-rds-subnet created
    + ├─ aws:ec2:Subnet first-rds-subnet created
    + ├─ aws:ec2:InternetGateway app-gateway created
    + ├─ aws:ec2:SecurityGroup rds-security-group created
    + ├─ aws:rds:SubnetGroup rds-subnet-group created
    + ├─ aws:ec2:RouteTable app-routetable created
    + ├─ aws:ec2:MainRouteTableAssociation app-routetable-association created
    + ├─ aws:rds:Instance postgresql-rds-server created
    + ├─ pulumi:providers:postgresql postgresql-provider created
    + ├─ postgresql:index:Database postgresql-database created
    + ├─ postgresql:index:Role postgres-standard-role created
    + └─ pulumi-nodejs:dynamic:Resource postgresql-votes-schema created
    Outputs:
    URL: "client-side-listener-086d27d-bb5f264d141c31b7.elb.us-west-2.amazonaws.com"
    Resources:
    + 63 created
    Duration: 4m2s
  5. View the DNS address of the instance via pulumi stack output:

    Terminal window
    pulumi stack output
    Current stack outputs (1):
    OUTPUT VALUE
    URL client-side-listener-086d27d-bb5f264d141c31b7.elb.us-west-2.amazonaws.com
  6. Verify that the ECS instance exists by connecting to it in a browser window.

Clean up#

To clean up resources, run pulumi destroy and answer the confirmation question at the prompt.

Related

The infrastructure as code platform for any cloud.