Skip to content

Latest commit

 

History

History
132 lines (87 loc) · 3.66 KB

03-provisioning-infrastructure.md

File metadata and controls

132 lines (87 loc) · 3.66 KB

Provisioning Infrastructure

Now that you have a project configured to use AWS, you'll create some basic infrastructure in it. We will start with a simple S3 bucket.

Step 1 — Declare a New Bucket

Add the following to your __main__.py file:

...
bucket = aws.s3.Bucket("my-bucket")

✅ After this change, your __main__.py should look like this.

Step 2 — Preview Your Changes

Now preview your changes:

pulumi up

This command evaluates your program, determines the resource updates to make, and shows you an outline of these changes:

Previewing update (dev):

     Type                 Name              Plan
 +   pulumi:pulumi:Stack  iac-workshop-dev  create
 +   └─ aws:s3:Bucket     my-bucket         create

Resources:
    + 2 to create

Do you want to perform this update?
  yes
> no
  details

This is a summary view. Select details to view the full set of properties:

+ pulumi:pulumi:Stack: (create)
    [urn=urn:pulumi:dev::iac-workshop::pulumi:pulumi:Stack::iac-workshop-dev]
    + aws:s3/bucket:Bucket: (create)
        [urn=urn:pulumi:dev::iac-workshop::aws:s3/bucket:Bucket::my-bucket]
        [provider=urn:pulumi:dev::iac-workshop::pulumi:providers:aws::default_1_7_0::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
        acl         : "private"
        bucket      : "my-bucket-3939366"
        forceDestroy: false

Do you want to perform this update?
  yes
> no
  details

The stack resource is a synthetic resource that all resources your program creates are parented to.

Step 3 — Deploy Your Changes

Now that we've seen the full set of changes, let's deploy them. Select yes:

Updating (dev):

     Type                 Name              Status
 +   pulumi:pulumi:Stack  iac-workshop-dev  created
 +   └─ aws:s3:Bucket     my-bucket         created

Resources:
    + 2 created

Duration: 8s

Permalink: https://app.pulumi.com/joeduffy/iac-workshop/dev/updates/1

Now our S3 bucket has been created in our AWS account. Feel free to click the Permalink URL and explore; this will take you to the Pulumi Console, which records your deployment history.

Step 4 — Export Your New Bucket Name

To inspect your new bucket, you will need its physical AWS name. Pulumi records a logical name, my-bucket, however the resulting AWS name will be different.

Programs can export variables which will be shown in the CLI and recorded for each deployment. Export your bucket's name by adding this line to __main__.py:

...
pulumi.export('bucket_name', bucket.bucket)

✅ After this change, your __main__.py should look like this.

Now deploy the changes:

pulumi up

Notice a new Outputs section is included in the output containing the bucket's name:

...

Outputs:
  + bucket_name: "my-bucket-8257ac5"

Resources:
    2 unchanged

Duration: 3s

Permalink: https://app.pulumi.com/joeduffy/iac-workshop/dev/updates/2

The difference between logical and physical names is in part due to "auto-naming" which Pulumi does to ensure side-by-side projects and zero-downtime upgrades work seamlessly. It can be disabled if you wish; read more about auto-naming here.

Step 5 — Inspect Your New Bucket

Now run the aws CLI to list the objects in this new bucket:

aws s3 ls $(pulumi stack output bucket_name)

Note that the bucket is currently empty.

Next Steps