Docs
PackagesTry AWS Native preview for resources not in the classic version.
NGINX on AWS ECS Fargate using Python
Try AWS Native preview for resources not in the classic version.
This example shows authoring Infrastructure as Code in Python. It provisions a full Amazon Elastic Container Service (ECS) “Fargate” cluster and related infrastructure, running a load-balanced NGINX web server accessible over the Internet on port 80. This example is inspired by Docker’s Getting Started Tutorial.
Prerequisites
- Install Pulumi
- Configure Pulumi to Use AWS (if your AWS CLI is configured, no further changes are required)
Running the Example
Clone the examples repo and cd into it.
Next, to deploy the application and its infrastructure, follow these steps:
Create a new stack, which is an isolated deployment target for this example:
$ pulumi stack init devSet your desired AWS region:
$ pulumi config set aws:region us-east-1 # any valid AWS region will workDeploy everything with a single
pulumi upcommand. This will show you a preview of changes first, which includes all of the required AWS resources (clusters, services, and the like). Don’t worry if it’s more than you expected – this is one of the benefits of Pulumi, it configures everything so that so you don’t need to!$ pulumi upAfter being prompted and selecting “yes”, your deployment will begin. It’ll complete in a few minutes:
Updating (dev): Type Name Status + pulumi:pulumi:Stack aws-py-fargate-dev created + ├─ aws:ecs:Cluster cluster created + ├─ aws:ec2:SecurityGroup web-secgrp created + ├─ aws:iam:Role task-exec-role created + ├─ aws:lb:TargetGroup app-tg created + ├─ aws:ecs:TaskDefinition app-task created + ├─ aws:iam:RolePolicyAttachment task-exec-policy created + ├─ aws:lb:LoadBalancer app-lb created + ├─ aws:lb:Listener web created + └─ aws:ecs:Service app-svc created Outputs: url: "app-lb-ad43707-1433933240.us-west-2.elb.amazonaws.com" Resources: + 10 created Duration: 2m56s Permalink: https://app.pulumi.com/acmecorp/aws-python-fargate/dev/updates/1Notice that the automatically assigned load-balancer URL is printed as a stack output.
At this point, your app is running – let’s curl it. The CLI makes it easy to grab the URL:
$ curl http://$(pulumi stack output url) <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/">nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/">nginx.com</a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html>
Please Note: It may take a few minutes for the app to start up. Until that point, you may receive a 503 error response code.
Try making some changes, and rerunning
pulumi up. For example, let’s scale up to 3 instances:Running
pulumi upwill show you the delta and then, after confirming, will deploy just those changes:$ pulumi upNotice that
pulumi upredeploys just the parts of the application/infrastructure that you’ve edited.Updating (dev): Type Name Status Info pulumi:pulumi:Stack aws-py-fargate-dev ~ └─ aws:ecs:Service app-svc updated [diff: ~desiredCount] Outputs: url: "app-lb-ad43707-1433933240.us-west-2.elb.amazonaws.com" Resources: ~ 1 updated 9 unchanged Duration: 14s Permalink: https://app.pulumi.com/acmecorp/aws-python-fargate/dev/updates/2Once you are done, you can destroy all of the resources, and the stack:
$ pulumi destroy $ pulumi stack rm
Try AWS Native preview for resources not in the classic version.