End of support notice: Amazon DevOpsĀ Guru will stop accepting new customers on October 29, 2026. Current customers will not be impacted and can continue using Amazon DevOpsĀ Guru until September 30, 2027. After September 30, 2027 you will no longer be able to access Amazon DevOpsĀ Guru. For more information, see Amazon DevOpsĀ Guru end of support.
Using service-linked roles for DevOpsĀ Guru
Amazon DevOpsĀ Guru 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 DevOpsĀ Guru. Service-linked roles are predefined by DevOpsĀ Guru and include all the permissions that the service requires to call AWS CloudTrail, Amazon CloudWatch, AWS CodeDeploy, AWS X-Ray, and AWS Organizations on your behalf.
A service-linked role makes setting up DevOpsĀ Guru easier because you donāt have to manually add the necessary permissions. DevOpsĀ Guru defines the permissions of its service-linked roles, and unless defined otherwise, only DevOpsĀ Guru 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 its related resources. This protects your DevOpsĀ Guru resources because you can't inadvertently remove permission to access the resources.
Service-linked role permissions for DevOpsĀ Guru
DevOpsĀ Guru uses the service-linked role named
AWSServiceRoleForDevOpsGuru. This is an AWS managed policy
with scoped permissions that DevOpsĀ Guru needs to run in your account.
The AWSServiceRoleForDevOpsGuru service-linked role trusts
the following service to assume the role:
-
devops-guru.amazonaws.com
The role permissions policy, AmazonDevOpsGuruServiceRolePolicy allows DevOpsĀ Guru to complete the following actions on the
specified resources.
Creating a service-linked role for DevOpsĀ Guru
You don't need to manually create a service-linked role. When you create an insight in the AWS Management Console, the AWS CLI, or the AWS API, DevOpsĀ Guru 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; for example, it can appear if you added DevOpsĀ Guru to a repository from AWS CodeCommit.
Editing a service-linked role for DevOpsĀ Guru
DevOpsĀ Guru does not allow you to edit the AWSServiceRoleForDevOpsGuru 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 DevOpsĀ Guru
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 disassociate from all repositories before you can manually delete it.
Note
If the DevOpsĀ Guru service is using the role when you try to delete the resources, the deletion might fail. If that happens, wait for a few minutes and try the operation again.
To manually delete the service-linked role using IAM
Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForDevOpsGuru
service-linked role. For more information, see Deleting a Service-Linked Role in the IAM User Guide.
