2.4 KiB
2.4 KiB
layout | page_title | sidebar_current | description |
---|---|---|---|
aws | AWS: aws_iam_role | docs-aws-resource-iam-role | Provides an IAM role. |
aws_iam_role
Provides an IAM role.
Example Usage
resource "aws_iam_role" "test_role" {
name = "test_role"
assume_role_policy = <<EOF
{
"Version": "2012-10-17",
"Statement": [
{
"Action": "sts:AssumeRole",
"Principal": {
"Service": "ec2.amazonaws.com"
},
"Effect": "Allow",
"Sid": ""
}
]
}
EOF
}
Argument Reference
The following arguments are supported:
name
- (Optional, Forces new resource) The name of the role. If omitted, Terraform will assign a random, unique name.name_prefix
- (Optional, Forces new resource) Creates a unique name beginning with the specified prefix. Conflicts withname
.assume_role_policy
- (Required) The policy that grants an entity permission to assume the role.
~> NOTE: This assume_role_policy
is very similar but slightly different than just a standard IAM policy and cannot use an aws_iam_policy
resource. It can however, use an aws_iam_policy_document
data source, see example below for how this could work.
path
- (Optional) The path to the role. See IAM Identifiers for more information.description
- (Optional) The description of the role.
Attributes Reference
The following attributes are exported:
arn
- The Amazon Resource Name (ARN) specifying the role.create_date
- The creation date of the IAM role.unique_id
- The stable and unique string identifying the role.name
- The name of the role.description
- The description of the role.
Example of Using Data Source for Assume Role Policy
data "aws_iam_policy_document" "instance-assume-role-policy" {
statement {
actions = ["sts:AssumeRole"]
principals {
type = "Service"
identifiers = ["ec2.amazonaws.com"]
}
}
}
resource "aws_iam_role" "instance" {
name = "instance_role"
path = "/system/"
assume_role_policy = "${data.aws_iam_policy_document.instance-assume-role-policy.json}"
}
Import
IAM Roles can be imported using the name
, e.g.
$ terraform import aws_iam_role.developer developer_name