Using service-linked roles for re:Post Private

AWS re:Post Private uses AWS Identity and Access Management (IAM) service-linked roles. A service-linked role is a unique type of IAM role that's linked directly to re:Post Private. Service-linked roles are predefined by re:Post Private and include all the permissions that the service requires to call other AWS services on your behalf.

A service-linked role makes setting up re:Post Private easier because you don’t have to manually add the necessary permissions. re:Post Private defines the permissions of its service-linked roles, and unless defined otherwise, only re:Post Private can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy can't be attached to any other IAM entity.

For information about other services that support service-linked roles, see AWS services that work with IAM and look for the services that have Yes in the Service-linked roles column. Choose a Yes with a link to view the service-linked role documentation for that service.

Service-linked role permissions for re:Post Private

re:Post Private uses the service-linked role named AWSServiceRoleForrePostPrivate. re:Post Private uses this service-linked role to publish data to CloudWatch.

The AWSServiceRoleForrePostPrivate service-linked role trusts the following services to assume the role:

The role permissions policy named AWSrePostPrivateCloudWatchAccess allows re:Post Private to complete the following actions on the specified resources:

You must configure permissions to allow your users, groups, or roles to create, edit, or delete a service-linked role. For more information, see Service-linked role permissions in the IAM User Guide.

For more information, see AWSrePostPrivateCloudWatchAccess.

Creating a service-linked role for re:Post Private

You don't need to manually create a service-linked role. When you create your first private re:Post in the AWS Management Console, the AWS CLI, or the AWS API, re:Post Private creates the service-linked role for you.

If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create your first private re:Post, re:Post Private creates the service-linked role for you again.

In the AWS CLI or the AWS API, create a service-linked role with the repostspace.amazonaws.com service name. For more information, see Creating a service-linked role in the IAM User Guide. If you delete this service-linked role, you can use this same process to create the role again.

Editing a service-linked role for re:Post Private

re:Post Private doesn't allow you to edit the AWSServiceRoleForrePostPrivate service-linked role. After you create a service-linked role, you can't change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a service-linked role in the IAM User Guide.

Deleting a service-linked role for re:Post Private

You don't need to manually delete the AWSServiceRoleForrePostPrivate role. When you delete your private re:Post in the AWS Management Console, the AWS CLI, or the AWS API, re:Post Private deletes the service-linked role for you.

You can also use the IAM console, the AWS CLI, or the AWS API to manually delete the service-linked role.

To manually delete the service-linked role using IAM

Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForrePostPrivate service-linked role. For more information, see Deleting a service-linked role in the IAM User Guide.

Supported Regions for re:Post Private service-linked roles

re:Post Private supports using service-linked roles in the AWS Regions where the service is available.