Top / Amazon Web Service / AWS IAM / User Policy Attachment

AWS IAM User Policy Attachment

This page shows how to write Terraform and CloudFormation for IAM User Policy Attachment and write them securely.

terraform-logo

Review your .tf file for AWS best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

aws_iam_user_policy_attachment (Terraform)

The User Policy Attachment in IAM can be configured in Terraform with the resource name aws_iam_user_policy_attachment. The following sections describe 2 examples of how to use the resource and its parameters.

Example Usage from GitHub

iam.tf#L36
resource "aws_iam_user_policy_attachment" "github_ci_dynamodb" {
  user       = aws_iam_user.github_actions_ci.name
  policy_arn = data.aws_iam_policy.dynamodb_full_access.arn
}

resource "aws_iam_user_policy_attachment" "github_ci_s3" {
main.tf#L51
resource "aws_iam_user_policy_attachment" "iam-full-access" {
  provider   = aws.iam
  policy_arn = data.aws_iam_policy.IAMFullAccess.arn
  user       = aws_iam_user.iam-manager.name
}

Review your Terraform file for AWS best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

>> from Terraform Registry

Explanation in Terraform Registry

Attaches a Managed IAM Policy to an IAM user

NOTE: The usage of this resource conflicts with the aws_iam_policy_attachment resource and will permanently show a difference if both are defined.

>> from Terraform Registry

Tips: Best Practices for The Other AWS IAM Resources

In addition to the aws_iam_account_password_policy, AWS IAM has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

risk-label

aws_iam_account_password_policy

Ensure AWS IAM account password policies requires long passwords

It's better to enforce the use of long and complex passwords to reduce the risk of bruteforce attacks.

Review your AWS IAM settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

AWS::IAM::User (CloudFormation)

The User in IAM can be configured in CloudFormation with the resource name AWS::IAM::User. The following sections describe 10 examples of how to use the resource and its parameters.

Example Usage from GitHub

training-prime.yml#L3
    Type: "AWS::IAM::User"
    Properties:
      Groups:
        - Devusers
        - Produsers
        - PrimeUsers
training-prime.yml#L3
    Type: "AWS::IAM::User"
    Properties:
      Groups:
        - DevUsers
        - ProdUsers
        - PrimeUsers
training-prime.yml#L3
    Type: "AWS::IAM::User"
    Properties:
      Groups:
        - DevUsers
        - ProdUsers
        - PrimeUsers
training-prime.yml#L3
    Type: "AWS::IAM::User"
    Properties:
      Groups:
        - Devusers
        - Produsers
        - PrimeUsers
training-prime.yml#L3
    Type: "AWS::IAM::User"
    Properties:
      Groups:
        - DevUsers
        - ProdUsers
        - PrimeUsers
Identity-CustomUsers.json#L73
      "Type" : "AWS::IAM::User",
      "Properties" : {
        "UserName" : "applicationadministrator",
        "Path" : "/",
        "Groups" : [
          { "Fn::ImportValue" : { "Fn::Sub" : "${CustomGroupsStackName}-ApplicationAdministratorsGroup" }}
Identity-CustomUsers.json#L73
      "Type" : "AWS::IAM::User",
      "Properties" : {
        "UserName" : "applicationadministrator",
        "Path" : "/",
        "Groups" : [
          { "Fn::ImportValue" : { "Fn::Sub" : "${CustomGroupsStackName}-ApplicationAdministratorsGroup" }}
Scout2-Master-004-IAMUsers-Global-Wait.json#L6
            "Type": "AWS::IAM::User",
            "Properties": {
                "UserName": "Scout2User001",
                "Groups": [
                    "BlockedUsers"
                ]
cf-example-100.json#L6
            "Type": "AWS::IAM::User",
            "Properties": {
                "UserName": "TestUser1",
                "Path": "/"
            }
        },
Identity-CustomUsers.json#L46
      "Type" : "AWS::IAM::User",
      "Properties" : {
        "UserName" : "mcrawford",
        "Path" : "/",
        "Groups" : [{ "Fn::ImportValue" : { "Fn::Sub" : "${StandardGroupsStackName}-AdministratorsGroup" }}]
      }

Parameters

>> from AWS CloudFormation Documentation

Explanation in CloudFormation Registry

Creates a new IAM user for your AWS account. For information about quotas for the number of IAM users you can create, see IAM and AWS STS quotas in the IAM User Guide.

>> from AWS CloudFormation Documentation

The Other Related AWS IAM Resources

Frequently asked questions

What is AWS IAM User Policy Attachment?

AWS IAM User Policy Attachment is a resource for IAM of Amazon Web Service. Settings can be wrote in Terraform and CloudFormation.

Where can I find the example code for the AWS IAM User Policy Attachment?

For Terraform, the jasongwartz/fitbit-friends and stilist/drjohndee.net source code examples are useful. See the Terraform Example section for further details.

For CloudFormation, the ServerlessOpsIO/infrastructure, ServerlessOpsIO/infrastructure and ServerlessOpsIO/infrastructure source code examples are useful. See the CloudFormation Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.

Table of Contents