Difference between revisions of "Terraform resource: aws iam access key"
Jump to navigation
Jump to search
↑ https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_access_key#secret
| Line 11: | Line 11: | ||
secret<ref>https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_access_key#secret</ref> = XXX | secret<ref>https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_access_key#secret</ref> = XXX | ||
} | } | ||
| + | |||
| + | |||
| + | secret | ||
| + | Secret access key. This attribute is not available for imported resources. Note that this will be written to the state file. If you use this, please protect your backend state file judiciously. Alternatively, you may supply a pgp_key instead, which will prevent the secret from being stored in plaintext, at the cost of preventing the use of the secret key in automation. | ||
| + | |||
== See also == | == See also == | ||
Revision as of 12:32, 4 March 2022
Examples:
resource "aws_iam_access_key" "your_lb" {
user = aws_iam_user.lb.name
pgp_key = "keybase:some_person_that_exists"
}
resource "aws_iam_access_key" "your_lb" {
user = aws_iam_user.lb.name
secret[1] = XXX
}
secret Secret access key. This attribute is not available for imported resources. Note that this will be written to the state file. If you use this, please protect your backend state file judiciously. Alternatively, you may supply a pgp_key instead, which will prevent the secret from being stored in plaintext, at the cost of preventing the use of the secret key in automation.
See also
- Terraform IAM resources:
aws_iam_user, aws_iam_group, aws_iam_role, aws_iam_role_policy_attachment,aws_iam_policy,aws_iam_role_policy, aws_iam_user_policy, aws_iam_user_policy_attachment,aws_iam_access_key, aws_iam_group_policy, aws_iam_group_policy_attachment, aws_iam_openid_connect_provider
Advertising:
