Using Service-Linked Roles for Honeycode

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

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

You can delete a service-linked role only after first deleting their related resources. This protects your Honeycode resources because you can't inadvertently remove permission to access the resources.

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 Role column. Choose a Yes with a link to view the service-linked role documentation for that service.

Service-Linked Role Permissions for Honeycode

Honeycode uses the service-linked role named AWSServiceRoleForAmazonHoneycode – required for Amazon Honeycode to access your resources.

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

• honeycode.amazonaws.com

The role permissions policy allows Honeycode to complete the following actions on the specified resources:

• Action: sso:GetManagedApplicationInstance on all AWS resources

You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-Linked Role Permissions in the IAM User Guide.

Creating a Service-Linked Role for Honeycode

You don't need to manually create a service-linked role. When you set up Honeycode integration with AWS SSO in the AWS Management Console, the AWS CLI, or the AWS API, Honeycode creates the service-linked role for you.

Important

This service-linked role can appear in your account if you completed an action in another service that uses the features supported by this role. Also, if you were using the Honeycode service before November 18, 2020, when it began supporting service-linked roles, then Honeycode created the AWSServiceRoleForAmazonHoneycode role in your account. To learn more, see A New Role Appeared in My IAM Account.

Creating a Service-Linked Role in Honeycode (Console)

You can use the Honeycode console to create a service-linked role.

Follow the Single Sign-On section of this guide to create the service-linked role.

You can also use the IAM console to create a service-linked role with the Honeycode use case. In the AWS CLI or the AWS API, create a service-linked role with the honeycode.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.

If you delete this service-linked role, you can use the same IAM process to create the role again.

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 set up Honeycode integration with AWS SSO, Honeycode creates the service-linked role for you again.

Editing a Service-Linked Role for Honeycode

Honeycode does not allow you to edit the AWSServiceRoleForAmazonHoneycode service-linked role. After you create a service-linked role, you cannot 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 Honeycode

If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up your service-linked role before you can manually delete it.

Cleaning Up a Service-Linked Role

Before you can use IAM to delete a service-linked role, you must first delete any resources used by the role.

To ensure that Honeycode is not using any resources in your account, open an AWS Support Case and request deletion of the service-linked role.

Manually Delete the Service-Linked Role

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

Supported Regions for Honeycode Service-Linked Roles

Honeycode supports using service-linked roles in all of the regions where the service is available. For more information, see AWS Regions and Endpoints.