How can I use a Terraform resource's generated ID as input?

In Terraform, a resource's generated ID is often needed as input for other resources. This is achieved using resource references within the Terraform configuration. Here's how you can do it:

1. Using Resource References:

- When a resource is created in Terraform, it generates a unique ID. To use this ID as input for another resource, you'll refer to the first resource within the configuration of the second resource using the syntax: resource_type.resource_name.attribute. For IDs specifically, you typically use the id attribute.

2. Example Scenario:

- Let’s say you create an AWS S3 bucket and need the generated bucket ID to configure a policy. The code would be structured as follows:

resource "aws_s3_bucket" "example_bucket" {
  bucket = "my-unique-bucket-name"
  acl = "private"
}

resource "aws_s3_bucket_policy" "example_policy" {
  bucket = aws_s3_bucket.example_bucket.id
  policy = <<POLICY
{     "Version": "2012-10-17",
  "Statement": [
    {
      "Action": "s3:",
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::my-unique-bucket-name/",
      "Principal": ""
    }
  ]
}
POLICY
}

In the above example:

- aws_s3_bucket.example_bucket refers to the created S3 bucket.

- .id accesses the generated ID of the S3 bucket.

- This ID is then assigned to the bucket attribute of the aws_s3_bucket_policy resource, establishing the dependency.

3. Implicit Dependency:

- Terraform automatically recognizes this dependency. The aws_s3_bucket_policy resource won't be created until the aws_s3_bucket resource has been successfully provisioned and its ID generated.

4. Using Other Attributes:

- You're not limited to just the id. You can also reference other attributes exposed by the resource such as ARN, Name etc.

5. Importance:

- This mechanism is vital because most resources in cloud environments rely on identifiers for proper functioning and relationships between components. Using references makes it dynamic, you don’t have to hardcode values.

6. Best Practices:

- Ensure clear naming conventions for your resources to easily reference them later. Use consistent naming patterns to avoid confusion and make your configuration more readable.

By utilizing this reference mechanism, you ensure that your Terraform configurations are both robust and dynamic, adapting to the unique identifiers generated by the cloud provider.

Learn more about this