AlexaForBusinessDeviceSetup

OperatorAWS managedActivePermissions reviewedShow on map Compare

Summary

Provide device setup access to AlexaForBusiness services

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

Identity

ARN: arn:aws:iam::aws:policy/AlexaForBusinessDeviceSetup
Default version: v2
Created: 2017-11-30
Last edited: 2019-05-20
Services: a4b, secretsmanager

Control-plane actions (7)

By access level: 2 List, 2 Read, 3 Write.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
Alexa for Business	6 of 96	2 List, 1 Read, 3 Write; 0 restricted, 0 conditional	a4b:CompleteRegistration, a4b:GetNetworkProfile, a4b:PutDeviceSetupEvents, a4b:RegisterDevice, a4b:SearchDevices, a4b:SearchNetworkProfiles
Secrets Manager	1 of 27	1 Read; 1 restricted, 0 conditional	secretsmanager:GetSecretValue

Alexa for Business: 6 actions

a4b:CompleteRegistration (Write)
a4b:GetNetworkProfile (Read)
a4b:PutDeviceSetupEvents (Write)
a4b:RegisterDevice (Write)
a4b:SearchDevices (List)
a4b:SearchNetworkProfiles (List)

Secrets Manager: 1 actions

secretsmanager:GetSecretValue (Read)

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 3 write, tagging or permissions-management actions, short of full control of any service.

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:RegisterDevice",
        "a4b:CompleteRegistration",
        "a4b:SearchDevices",
        "a4b:SearchNetworkProfiles",
        "a4b:GetNetworkProfile",
        "a4b:PutDeviceSetupEvents"
      ],
      "Resource": "*"
    },
    {
      "Sid": "A4bDeviceSetupAccess",
      "Effect": "Allow",
      "Action": [
        "secretsmanager:GetSecretValue"
      ],
      "Resource": "arn:aws:secretsmanager:*:*:secret:A4BNetworkProfile*"
    }
  ]
}

Version history

Current version v2, edited by AWS on 2019-05-20. 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/AlexaForBusinessDeviceSetup
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AlexaForBusinessDeviceSetup
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AlexaForBusinessDeviceSetup

CloudFormation

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

Terraform

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

CDK (TypeScript)

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

Sources

Pending editorial review. No editorial sources are listed yet.