Skip to content

Latest commit

 

History

History

iam_one_active_key_per_user

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

AWS IAM Users With Multiple Active Access Keys

What It Does

This policy template reports all IAM users in an AWS account that have more than the user-specified number of access keys. Optionally, this report can be emailed.

Input Parameters

  • Email Addresses - Email addresses of the recipients you wish to notify.
  • Account Number - The Account number for use with the AWS STS Cross Account Role. Leave blank when using AWS IAM Access key and secret. It only needs to be passed when the desired AWS account is different than the one associated with the Flexera One credential. More information is available in our documentation.
  • Maximum Permitted Access Keys - Number of access keys users are permitted to have. Users with more than this will be included in the report.

Policy Actions

  • Sends an email notification.

Prerequisites

This Policy Template uses Credentials for authenticating to datasources -- in order to apply this policy you must have a Credential registered in the system that is compatible with this policy. If there are no Credentials listed when you apply the policy, please contact your Flexera Org Admin and ask them to register a Credential that is compatible with this policy. The information below should be consulted when creating the credential(s).

  • AWS Credential (provider=aws) which has the following permissions:

    • sts:GetCallerIdentity
    • iam:ListUsers
    • iam:ListAccessKeys

    Example IAM Permission Policy:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "sts:GetCallerIdentity",
                    "iam:ListUsers",
                    "iam:ListAccessKeys"
                ],
                "Resource": "*"
            }
        ]
    }
  • Flexera Credential (provider=flexera) which has the following roles:

    • billing_center_viewer

The Provider-Specific Credentials page in the docs has detailed instructions for setting up Credentials for the most common providers.

Supported Clouds

  • AWS

Cost

This policy template does not incur any cloud costs.