Compute - Listing Instances - Terraform

Aim

In this demo, we'll be creating some access keys. They are the preferred way to authenticate to Piranha using client software.

Terraform

$ cd terraform/

$ terraform plan

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.access-create-accesskeys.aws_iam_access_key.demoaccesskeys will be created
  + resource "aws_iam_access_key" "demoaccesskeys" {
      + create_date                    = (known after apply)
      + encrypted_secret               = (known after apply)
      + encrypted_ses_smtp_password_v4 = (known after apply)
      + id                             = (known after apply)
      + key_fingerprint                = (known after apply)
      + secret                         = (sensitive value)
      + ses_smtp_password_v4           = (sensitive value)
      + status                         = "Active"
      + user                           = "demoaccesskeys"
    }

  # module.access-create-accesskeys.aws_iam_user.demoaccesskeys will be created
  + resource "aws_iam_user" "demoaccesskeys" {
      + arn           = (known after apply)
      + force_destroy = false
      + id            = (known after apply)
      + name          = "demoaccesskeys"
      + path          = "/"
      + tags_all      = (known after apply)
      + unique_id     = (known after apply)
    }

Plan: 2 to add, 0 to change, 0 to destroy.

───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.




$ terraform apply