AlexaForBusinessFullAccess

AdminAWS managedActivePermissions reviewedShow on map Compare

Summary

Grants full access to AlexaForBusiness resources and access to related AWS services

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

Identity

ARN: arn:aws:iam::aws:policy/AlexaForBusinessFullAccess
Default version: v5
Created: 2017-11-30
Last edited: 2020-07-01
Services: a4b, iam, kms, secretsmanager

Control-plane actions (104)

By access level: 17 List, 19 Read, 2 Tagging, 66 Write.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
Alexa for Business	All 96 actions (see the Alexa for Business page)	17 List, 16 Read, 2 Tagging, 61 Write; 0 restricted, 0 conditional	a4b:*
IAM	3 of 190	1 Read, 2 Write; 3 restricted, 1 conditional	iam:CreateServiceLinkedRole, iam:DeleteServiceLinkedRole, iam:GetServiceLinkedRoleDeletionStatus
KMS	1 of 58	1 Read; 0 restricted, 0 conditional	kms:DescribeKey
Secrets Manager	4 of 27	1 Read, 3 Write; 4 restricted, 1 conditional	secretsmanager:CreateSecret, secretsmanager:DeleteSecret, secretsmanager:GetSecretValue, secretsmanager:UpdateSecret

IAM: 3 actions

iam:CreateServiceLinkedRole (Write)
iam:DeleteServiceLinkedRole (Write)
iam:GetServiceLinkedRoleDeletionStatus (Read)

KMS: 1 actions

kms:DescribeKey (Read)

Secrets Manager: 4 actions

secretsmanager:CreateSecret (Write)
secretsmanager:DeleteSecret (Write)
secretsmanager:GetSecretValue (Read)
secretsmanager:UpdateSecret (Write)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: mixed.

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

Why this tier

Grants at least 80% of the write and permissions-management actions of: a4b (61 of 61).

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.

Same service

Same domain

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": "Allow",
      "Action": [
        "a4b:*",
        "kms:DescribeKey"
      ],
      "Resource": "*"
    },
    {
      "Action": [
        "iam:CreateServiceLinkedRole"
      ],
      "Effect": "Allow",
      "Resource": "*",
      "Condition": {
        "StringLike": {
          "iam:AWSServiceName": [
            "*a4b.amazonaws.com"
          ]
        }
      }
    },
    {
      "Effect": "Allow",
      "Action": [
        "iam:DeleteServiceLinkedRole",
        "iam:GetServiceLinkedRoleDeletionStatus"
      ],
      "Resource": "arn:aws:iam::*:role/aws-service-role/*a4b.amazonaws.com/AWSServiceRoleForAlexaForBusiness*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "secretsmanager:GetSecretValue",
        "secretsmanager:DeleteSecret",
        "secretsmanager:UpdateSecret"
      ],
      "Resource": "arn:aws:secretsmanager:*:*:secret:A4B*"
    },
    {
      "Effect": "Allow",
      "Action": "secretsmanager:CreateSecret",
      "Resource": "*",
      "Condition": {
        "StringLike": {
          "secretsmanager:Name": "A4B*"
        }
      }
    }
  ]
}

Version history

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

Attach snippets

AWS CLI

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

CloudFormation

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

Terraform

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

CDK (TypeScript)

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

Sources

Pending editorial review. No editorial sources are listed yet.