AWS App Studio is in preview and is subject to change.

Service-linked roles for App Studio

App Studio 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 App Studio. Service-linked roles are predefined by App Studio and include all the permissions that the service requires to call other AWS services on your behalf.

A service-linked role makes setting up App Studio easier because you don’t have to manually add the necessary permissions. App Studio defines the permissions of its service-linked roles, and unless defined otherwise, only App Studio 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 App Studio resources because you can't inadvertently remove permission to access the resources.

Service-linked role permissions for App Studio

App Studio uses the service-linked role named AWSServiceRoleForAppStudio. It's a service-linked role required for App Studio to persistently manage AWS services, to maintain the application building experience.

The AWSServiceRoleForAppStudio service-linked role uses the following trust policy, which only trusts the appstudio-service.amazonaws.com service:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "appstudio-service.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

For permissions, the AWSServiceRoleForAppStudio service-linked role provides permissions to the following services:

Specifically, the permissions granted with AWSServiceRoleForAppStudio are defined by the attached AppStudioServiceRolePolicy managed policy. For more information about the managed policy, including the permissions it includes, see AWS managed policy: AppStudioServiceRolePolicy.

Creating a service-linked role for App Studio

You don't need to manually create a service-linked role. When you create an App Studio instance, App Studio creates the service-linked role for you.

If you delete this service-linked role, it is recommended to create an App Studio instance to have another one automatically created for you.

While not neccesary, you can also use the IAM console or AWS CLI to create service-linked roles by creating a service-linked role with the appstudio-service.amazonaws.com service name, as in the trust policy snippet shown earlier. For more information, see Creating a service-linked role in the IAM User Guide.

Editing a service-linked role for App Studio

App Studio doesn't allow you to edit the AWSServiceRoleForAppStudio 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 by using IAM. For more information, see Editing a service-linked role in the IAM User Guide.

Deleting a service-linked role for App Studio

You don't need to delete the AWSServiceRoleForAppStudio role. When you delete the App Studio instance, App Studio cleans up the resources and deletes the service-linked role automatically.

While not recommended, you can use the IAM console or the AWS CLI to delete the service-linked role. To do this, you must first clean up the resources for your service-linked role and then you can delete it.