You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Companion to the tutorial [Provision containers on AWS](https://www.pulumi.com/docs/tutorials/aws/ecs-fargate/).
6
6
7
7
## Prerequisites
8
8
9
-
To run this example, make sure [Docker](https://docs.docker.com/engine/installation/) is installed and running.
9
+
To run this example, make sure [Docker Engine - Community](https://docs.docker.com/engine/installation/) is installed and running.
10
10
11
-
## Running the App
11
+
## Deploy the App
12
12
13
13
Note: some values in this example will be different from run to run. These values are indicated
14
14
with `***`.
15
15
16
-
1. Create a new stack:
16
+
### Step 1: Create a new stack
17
17
18
18
```
19
19
$ pulumi stack init containers-dev
20
20
```
21
21
22
-
1. Configure Pulumi to use an AWS region that supports Fargate. This is currently only available in `us-east-1`, `us-east-2`, `us-west-2`, and `eu-west-1`:
22
+
### Step 2: Configure AWS region for Pulumi
23
+
24
+
For this example, you need to set an AWS region that supports Fargate. Refer to the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) for product availability.
23
25
24
26
```
25
27
$ pulumi config set aws:region us-west-2
26
28
```
27
29
28
-
1. Restore NPM modules via `npm install` or `yarn install`.
30
+
### Step 3: Restore NPM modules
31
+
32
+
You can do this via `npm install` or `yarn install`.
33
+
34
+
### Step 4:. Preview and deploy the app
29
35
30
-
1. Preview and deploy the app via `pulumi up`. The preview will take a few minutes, as it builds a Docker container. A total of 19 resources are created.
36
+
Run the following command:
31
37
32
38
```
33
39
$ pulumi up
34
40
```
41
+
The preview will take a few minutes, as it builds a Docker container. A total of 19 resources are created.
35
42
36
-
1. View the endpoint URL, and run curl:
43
+
### Step 5: View the endpoint URL
44
+
45
+
Run [`pulumi stack output`](https://www.pulumi.com/docs/reference/cli/pulumi_stack_output/) to view your stack's output properties, and then `curl` the command to view the resulting page. `$(pulumi stack output url)` evaluates to the load balancer’s URL.
37
46
38
47
```bash
39
48
$ pulumi stack output
@@ -51,15 +60,17 @@ with `***`.
51
60
</body></html>
52
61
```
53
62
54
-
1. To view the runtime logs from the container, use the `pulumi logs` command. To get a log stream, use `pulumi logs --follow`.
63
+
### Step 6: View runtime logs from the container
64
+
65
+
Use the [`pulumi logs`](https://www.pulumi.com/docs/reference/cli/pulumi_logs/) command. To get a log stream, use `pulumi logs --follow`.
55
66
56
67
```
57
68
$ pulumi logs --follow
58
69
Collecting logs for stack container-quickstart-dev since 2018-05-22T14:25:46.000-07:00.
To clean up resources, run `pulumi destroy` and answer the confirmation question at the prompt.
75
+
To clean up resources, run [`pulumi destroy`](https://www.pulumi.com/docs/reference/cli/pulumi_destroy/) to avoid incurring any costs. Select `yes` on the confirmation prompt so Pulumi will remove all of the resources that you've created. To delete the stack itself, run [`pulumi stack rm`](https://www.pulumi.com/docs/reference/cli/pulumi_stack_rm/). Note that this command deletes all deployment history from the Pulumi Console, unless you've explicitly [chosen a different backend](https://www.pulumi.com/docs/intro/concepts/state/) for storing your infrastructure state.
Deploy an EC2 instance using `@pulumi/aws`, using a common module for creating an instance. A function `createInstance` is defined in [webserver.js](webserver.js)which is then used in main program.
5
+
Deploy an EC2 instance with the `@pulumi/aws` package, using a common module for creating an instance. We define a function,`createInstance`, in [webserver.js](webserver.js)and use it in the main program, [index.js](index.js).
6
6
7
-
For a walkthrough of the main example, [Infrastructure on AWS](https://www.pulumi.com/docs/tutorials/aws/ec2-webserver/).
7
+
For a walkthrough of the main example, see [Simple Web Server Using Amazon EC2](https://www.pulumi.com/docs/tutorials/aws/ec2-webserver/).
A simple REST API that counts the number of times a route has been hit. For a detailed walkthrough of this example, see the article [Create a Serverless REST API](https://www.pulumi.com/docs/tutorials/aws/rest-api/).
This example shows how to setup a basic GraphQL endpoint in AWS AppSync. The endpoint contains one query and one mutation that get and put items to a Dynamo DB table.
5
+
This example shows how to set up a basic GraphQL endpoint in AWS AppSync. The endpoint contains one query and one mutation that get and put items to a Dynamo DB table.
This example deploys an EKS Kubernetes cluster with an EBS-backed StorageClass, and deploys a Kubernetes Namespace and Deployment of NGINX
6
-
into the cluster.
5
+
This example deploys an EKS Kubernetes cluster with an EBS-backed StorageClass, and deploys a Kubernetes Namespace and Deployment of NGINX into the cluster.
7
6
8
7
## Deploying the App
9
8
@@ -215,7 +214,7 @@ After cloning this repo, from this working directory, run these commands:
215
214
the NGINX app, and a LoadBalancer `Service` to publicly access NGINX.
216
215
217
216
Pulumi understands which changes to a given cloud resource can be made
218
-
in-place, and which require replacement, and computes
217
+
inplace, and which require replacement, and computes
219
218
the minimally disruptive change to achieve the desired state.
220
219
221
220
>**Note:** Pulumi auto-generates a suffix for all objects.
@@ -230,12 +229,12 @@ After cloning this repo, from this working directory, run these commands:
230
229
>```
231
230
232
231
If you visit the FQDN listed in`serviceHostname` you should land on the
233
-
NGINX welcome page. Note, that it may take a minute or so for the
232
+
NGINX welcome page. Note that it may take a minute or so for the
234
233
LoadBalancer to become active on AWS.
235
234
236
235
1. Access the Kubernetes Cluster using `kubectl`
237
236
238
-
To access your new Kubernetes cluster using `kubectl`, we need to setup the
237
+
To access your new Kubernetes cluster using `kubectl`, we need to set up the
239
238
`kubeconfig` file and download `kubectl`. We can leverage the Pulumi
240
239
stack output in the CLI, as Pulumi faciliates exporting these objects for us.
241
240
@@ -265,12 +264,11 @@ After cloning this repo, from this working directory, run these commands:
265
264
$ kubectl delete deployment my-nginx
266
265
```
267
266
268
-
By deploying this nginx image in this way, it is outside of Pulumi's control. But this is simply to show that we can
269
-
control our cluster via the CLI as well.
267
+
By deploying the NGINX image in this way, it is outside of Pulumi's control. But this is simply to show that we can control our cluster via the CLI as well.
270
268
271
269
1. Experimentation
272
270
273
-
From here on, feel free to experiment. Simply making edits and running `pulumi up` afterwards, will incrementally update your stack.
271
+
From here on, feel free to experiment. Make edits and run `pulumi up` afterwards to incrementally update your stack.
# Slackbot for Posting Slack Mention Notifications
4
4
5
-
A simple Slackbot (called '@mentionbot') that sends a message to specific channel to notifiy you any time you're @mentioned anywhere. Very helpful if you want a time-ordered list of @mentions to go through at a later point.
5
+
A simple Slackbot (called '@mentionbot') that sends a message to specific channel to notify you any time you're @mentioned anywhere. This bot is useful for when you need a time-ordered list of @mentions to go through at a later point.
6
6
7
7
Slack users can subscribe/unsubscribe from notifications easily. Simply add `@mentionbot` to a channel you want to be notified in. Then send any message to `@mentionbot` to subscribe. To stop getting messages send a message to `@mentionbot` containing the word `unsubscribe`.
A simple voting app that uses Redis for a data store and a Python Flask app for the frontend. The example has been ported from https://github.com/Azure-Samples/azure-voting-app-redis.
# Azure Kubernetes Service (AKS) cluster and Azure Functions with KEDA
3
+
# Azure Kubernetes Service (AKS) Cluster and Azure Functions with KEDA
4
4
5
5
This example demonstrates creating an Azure Kubernetes Service (AKS) Cluster, and deploying an Azure Function App with Kubernetes-based Event Driven Autoscaling (KEDA) into it, all in one Pulumi program. Please see https://docs.microsoft.com/en-us/azure/aks/ for more information about AKS and https://docs.microsoft.com/en-us/azure/azure-functions/functions-kubernetes-keda for more information about KEDA.
# A Todo App on Azure App Service with SQL Database and Application Insights and deploys it to Azure DevOps
3
+
# Todo App Using Azure App Service with SQL Database and Integrated with Azure DevOps
4
4
5
5
A Todo List application from Azure Samples GitHub: [.NET Core MVC sample for Azure App Service](https://github.com/azure-samples/dotnetcore-sqldb-tutorial), a web app built with ASP.NET Core, Entity Framework Core and a SQL database.
Copy file name to clipboardexpand all lines: azure-ts-appservice-springboot/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Deploy a Spring Boot App using Jenkins and Pulumi
1
+
# Spring Boot App on Azure App Service Using Jenkins
2
2
3
3
This example shows how you can deploy a Spring Boot app to an Azure App Service instance using Pulumi in a Jenkins Pipeline. The Spring Boot app is packaged into a container image that is conveniently built as part of the Pulumi app. The container image is pushed up to a private Azure Container Registry and then used as the source for an App Service instance.
0 commit comments