AWSCompromisedKeyQuarantine

Summary

Denies access to certain actions, applied by the AWS team in the event that an IAM user's credentials have been compromised or exposed publicly. Do NOT remove this policy. Instead, please follow the instructions specified in the email sent to you regarding this event.

Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.

Identity

ARN

arn:aws:iam::aws:policy/AWSCompromisedKeyQuarantineCopy ARN

Default version

v1

Created

2020-08-11

Last edited

2020-08-11

Services

None

Control-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

• ec2:RequestSpotInstances (deny, statement 0): 1 matching actions
• ec2:RunInstances (deny, statement 0): 1 matching actions
• ec2:StartInstances (deny, statement 0): 1 matching actions
• iam:AttachGroupPolicy (deny, statement 0): 1 matching actions
• iam:AttachRolePolicy (deny, statement 0): 1 matching actions
• iam:AttachUserPolicy (deny, statement 0): 1 matching actions
• iam:ChangePassword (deny, statement 0): 1 matching actions
• iam:CreateAccessKey (deny, statement 0): 1 matching actions
• iam:CreateInstanceProfile (deny, statement 0): 1 matching actions
• iam:CreateLoginProfile (deny, statement 0): 1 matching actions
• iam:CreateRole (deny, statement 0): 1 matching actions
• iam:CreateUser (deny, statement 0): 1 matching actions
• iam:DetachUserPolicy (deny, statement 0): 1 matching actions
• iam:PutUserPermissionsBoundary (deny, statement 0): 1 matching actions
• iam:PutUserPolicy (deny, statement 0): 1 matching actions
• iam:UpdateAccessKey (deny, statement 0): 1 matching actions
• iam:UpdateAccountPasswordPolicy (deny, statement 0): 1 matching actions
• iam:UpdateUser (deny, statement 0): 1 matching actions
• lambda:CreateFunction (deny, statement 0): 1 matching actions
• lightsail:Create* (deny, statement 0): 24 matching actions
• lightsail:Delete* (deny, statement 0): 21 matching actions
• lightsail:DownloadDefaultKeyPair (deny, statement 0): 1 matching actions
• lightsail:GetInstanceAccessDetails (deny, statement 0): 1 matching actions
• lightsail:Start* (deny, statement 0): 3 matching actions
• lightsail:Update* (deny, statement 0): 10 matching actions
• organizations:CreateAccount (deny, statement 0): 1 matching actions
• organizations:CreateOrganization (deny, statement 0): 1 matching actions
• organizations:InviteAccountToOrganization (deny, statement 0): 1 matching actions

Resource scope and attachment

Resource scope across granted actions: none.

Can be attached: Yes, to users, groups and roles.

Why this tier

• Grants no permissions: the effective allow set is empty.

Guidance

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Related policies

Same domain

• AccessAnalyzerServiceRolePolicy
• AccountManagementFromVercel
• AlexaForBusinessNetworkProfileServicePolicy
• AmazonAppStreamPCAAccess
• AmazonBioDiscoveryFullAccess
• AmazonBioDiscoveryInAppFullAccess
• AmazonChimeServiceRolePolicy
• AmazonCloudDirectoryFullAccess

Frequently asked questions

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": [
        "iam:AttachGroupPolicy",
        "iam:AttachRolePolicy",
        "iam:AttachUserPolicy",
        "iam:ChangePassword",
        "iam:CreateAccessKey",
        "iam:CreateInstanceProfile",
        "iam:CreateLoginProfile",
        "iam:CreateRole",
        "iam:CreateUser",
        "iam:DetachUserPolicy",
        "iam:PutUserPermissionsBoundary",
        "iam:PutUserPolicy",
        "iam:UpdateAccessKey",
        "iam:UpdateAccountPasswordPolicy",
        "iam:UpdateUser",
        "ec2:RequestSpotInstances",
        "ec2:RunInstances",
        "ec2:StartInstances",
        "organizations:CreateAccount",
        "organizations:CreateOrganization",
        "organizations:InviteAccountToOrganization",
        "lambda:CreateFunction",
        "lightsail:Create*",
        "lightsail:Start*",
        "lightsail:Delete*",
        "lightsail:Update*",
        "lightsail:GetInstanceAccessDetails",
        "lightsail:DownloadDefaultKeyPair"
      ],
      "Resource": [
        "*"
      ]
    }
  ]
}

Version history

Current version v1, edited by AWS on 2020-08-11. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AWSCompromisedKeyQuarantine
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSCompromisedKeyQuarantine
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSCompromisedKeyQuarantine

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AWSCompromisedKeyQuarantine

resource "aws_iam_role_policy_attachment" "awscompromisedkeyquarantine" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AWSCompromisedKeyQuarantine"
}

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AWSCompromisedKeyQuarantine"),
);

Sources

Pending editorial review. No editorial sources are listed yet.

• Official AWS reference for AWSCompromisedKeyQuarantine
• Report a data issue