# Identity and Access Management for Amazon DevOps Guru
AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use DevOps Guru resources. IAM is an AWS service that you can use with no additional charge.
**Topics**
+ [
## Audience
](#security_iam_audience)
+ [
## Authenticating with identities
](#security_iam_authentication)
+ [
## Managing access using policies
](#security_iam_access-manage)
+ [
## DevOps Guru updates to AWS managed policies and service-linked role
](#security-iam-awsmanpol-updates)
+ [
# How Amazon DevOps Guru works with IAM
](security_iam_service-with-iam.md)
+ [
# Identity-based policies for Amazon DevOps Guru
](security_iam_id-based-policy-examples.md)
+ [
# Using service-linked roles for DevOps Guru
](using-service-linked-roles.md)
+ [
# Amazon DevOps Guru permissions reference
](auth-and-access-control-permissions-reference.md)
+ [
# Permissions for Amazon SNS topics
](sns-required-permissions.md)
+ [
# Permissions for AWS KMS–encrypted Amazon SNS topics
](sns-kms-permissions.md)
+ [
# Troubleshooting Amazon DevOps Guru identity and access
](security_iam_troubleshoot.md)
## Audience
How you use AWS Identity and Access Management (IAM) differs based on your role:
+ **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting Amazon DevOps Guru identity and access](security_iam_troubleshoot.md))
+ **Service administrator** - determine user access and submit permission requests (see [How Amazon DevOps Guru works with IAM](security_iam_service-with-iam.md))
+ **IAM administrator** - write policies to manage access (see [Identity-based policies for Amazon DevOps Guru](security_iam_id-based-policy-examples.md))
## Authenticating with identities
Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role.
You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*.
For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*.
### AWS account root user
When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*.
### Federated identity
As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials.
A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials.
For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*.
### IAM users and groups
An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*.
An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*.
### IAM roles
An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.
IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Managing access using policies
You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*.
Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**.
By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation.
### Identity-based policies
Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*.
### Resource-based policies
Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.
Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy.
### Other policy types
AWS supports additional policy types that can set the maximum permissions granted by more common policy types:
+ **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*.
+ **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*.
+ **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*.
+ **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*.
### Multiple policy types
When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*.
## DevOps Guru updates to AWS managed policies and service-linked role
View details about updates to AWS managed policies and service-linked role for DevOps Guru since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the DevOps Guru [Amazon DevOps Guru document history](doc-history.md).
| Change | Description | Date |
| --- | --- | --- |
| [AmazonDevOpsGuruConsoleFullAccess](security_iam_id-based-policy-examples.md#managed-full-console-access) – Update to an existing policy. | The AmazonDevOpsGuruFullAccess managed policy now supports Amazon SNS subscriptions. | August 9, 2023 |
| [AmazonDevOpsGuruReadOnlyAccess](security_iam_id-based-policy-examples.md#managed-read-only-access) – Update to an existing policy | The AmazonDevOpsGuruReadOnlyAccess managed policy now supports read-only access to Amazon SNS subscription lists. | August 9, 2023 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The AWSServiceRoleForDevOpsGuru service-linked role now supports access to API Gateway GET actions on REST APIs. | January 11, 2023 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The AWSServiceRoleForDevOpsGuru service-linked role now supports several Amazon Simple Storage Service and Service Quotas actions. | October 19, 2022 |
| [AmazonDevOpsGuruFullAccess](security_iam_id-based-policy-examples.md#managed-full-access) – Update to an existing policy | The AmazonDevOpsGuruFullAccess managed policy now supports access to the CloudWatch `FilterLogEvents` action. | August 30, 2022 |
| [AmazonDevOpsGuruConsoleFullAccess](security_iam_id-based-policy-examples.md#managed-full-console-access) – Update to an existing policy | The `AmazonDevOpsGuruConsoleFullAccess` managed policy now supports access to the CloudWatch `FilterLogEvents` action. | August 30, 2022 |
| [AmazonDevOpsGuruReadOnlyAccess](security_iam_id-based-policy-examples.md#managed-read-only-access) – Update to an existing policy | The AmazonDevOpsGuruReadOnlyAccess managed policy now supports read-only access to the CloudWatch FilterLogEvents action. | August 30, 2022 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The `AWSServiceRoleForDevOpsGuru` service-linked role now supports the CloudWatch logs actions `FilterLogEvents`, `DescribeLogGroups`, and `DescribeLogStreams`. | July 12, 2022 |
| [Identity-based policies for DevOps Guru](https://docs.aws.amazon.com/devops-guru/latest/userguide/security_iam_id-based-policy-examples.html#managed-full-access) – New managed policy. | The `AmazonDevOpsGuruConsoleFullAccess` policy has been added. | December 16, 2021 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The `AWSServiceRoleForDevOpsGuru` service-linked role now supports Performance Insights `DescribeMetricsKeys`, and Amazon RDS `DescribeDBInstances` actions. | December 1, 2021 |
| [AmazonDevOpsGuruReadOnlyAccess](security_iam_id-based-policy-examples.md#managed-read-only-access) – Update to an existing policy | The `AmazonDevOpsGuruReadOnlyAccess` managed policy now supports read-only access to Amazon RDS `DescribeDBInstances` actions. | December 1, 2021 |
| [AmazonDevOpsGuruFullAccess](security_iam_id-based-policy-examples.md#managed-full-access) – Update to an existing policy | The `AmazonDevOpsGuruFullAccess` managed policy now supports access to Amazon RDS `DescribeDBInstances` actions. | December 1, 2021 |
| [Identity-based policies for Amazon DevOps Guru](security_iam_id-based-policy-examples.md) – New policy added. | The `AWSServiceRoleForDevOpsGuru` service-linked role now supports access to Amazon RDS `DescribeDBInstances` and Performance Insights `GetResourceMetrics` actions. The `AmazonDevOpsGuruOrganizationsAccess` managed policy provides access to DevOps Guru within an organization. | November 16, 2021 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The `AWSServiceRoleForDevOpsGuru` service-linked role now supports AWS Organizations. | November 4, 2021 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The `AWSServiceRoleForDevOpsGuru` service-linked role now contains new conditions on the `ssm:CreateOpsItem` and `ssm:AddTagsToResource` actions. | October 11, 2021 |
| [Service-linked role permissions for DevOps Guru](using-service-linked-roles.md#slr-permissions) – Update to an existing policy. | The `AWSServiceRoleForDevOpsGuru` service-linked role now contains new conditions on the `ssm:CreateOpsItem` and `ssm:AddTagsToResource` actions. | June 14, 2021 |
| [AmazonDevOpsGuruReadOnlyAccess](security_iam_id-based-policy-examples.md#managed-read-only-access) – Update to an existing policy | The `AmazonDevOpsGuruReadOnlyAccess` managed policy now allows read-only access to the AWS Identity and Access Management `GetRole` and the DevOps Guru `DescribeFeedback` actions. | June 14, 2021 |
| [AmazonDevOpsGuruReadOnlyAccess](security_iam_id-based-policy-examples.md#managed-read-only-access) – Update to an existing policy | The `AmazonDevOpsGuruReadOnlyAccess` managed policy now allows read-only access to the DevOps Guru `GetCostEstimation` and `StartCostEstimation` actions. | April 27, 2021 |
| [AmazonDevOpsGuruServiceRolePolicy](https://docs.aws.amazon.com/devops-guru/latest/userguide/using-service-linked-roles.html#slr-permissions) – Update to an existing policy. | The `AWSServiceRoleForDevOpsGuru` role now allows access to the AWS Systems Manager `AddTagsToResource` and Amazon EC2 Auto Scaling `DescribeAutoScalingGroups` actions. | April 27, 2021 |
| DevOps Guru started tracking changes | DevOps Guru started tracking changes for its AWS managed policies. | December 10, 2020 |
# How Amazon DevOps Guru works with IAM
Before you use IAM to manage access to DevOps Guru, learn what IAM features are available to use with DevOps Guru.
**IAM features you can use with Amazon DevOps Guru**
| IAM feature | DevOps Guru support |
| --- | --- |
| [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes |
| [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No |
| [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes |
| [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes |
| [Policy condition keys](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes |
| [ACLs](#security_iam_service-with-iam-acls) | No |
| [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | No |
| [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes |
| [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes |
| [Service roles](#security_iam_service-with-iam-roles-service) | No |
| [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | Yes |
To get a high-level view of how DevOps Guru and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Identity-based policies for DevOps Guru
**Supports identity-based policies:** Yes
Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*.
### Identity-based policy examples for DevOps Guru
To view examples of DevOps Guru identity-based policies, see [Identity-based policies for Amazon DevOps Guru](security_iam_id-based-policy-examples.md).
## Resource-based policies within DevOps Guru
**Supports resource-based policies:** No
Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.
To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Policy actions for DevOps Guru
**Supports policy actions:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation.
To see a list of DevOps Guru actions, see [Actions defined by Amazon DevOps Guru](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazondevopsguru.html#amazondevopsguru-actions-as-permissions) in the *Service Authorization Reference*.
Policy actions in DevOps Guru use the following prefix before the action:
```
aws
```
To specify multiple actions in a single statement, separate them with commas.
```
"Action": [
"aws:action1",
"aws:action2"
]
```
To view examples of DevOps Guru identity-based policies, see [Identity-based policies for Amazon DevOps Guru](security_iam_id-based-policy-examples.md).
## Policy resources for DevOps Guru
**Supports policy resources:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources.
```
"Resource": "*"
```
To see a list of DevOps Guru resource types and their ARNs, see [Resources defined by Amazon DevOps Guru](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazondevopsguru.html#amazondevopsguru-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions you can specify the ARN of each resource, see [Actions defined by Amazon DevOps Guru](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazondevopsguru.html#amazondevopsguru-actions-as-permissions).
To view examples of DevOps Guru identity-based policies, see [Identity-based policies for Amazon DevOps Guru](security_iam_id-based-policy-examples.md).
## Policy condition keys for DevOps Guru
**Supports service-specific policy condition keys:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*.
To see a list of DevOps Guru condition keys, see [Condition keys for Amazon DevOps Guru](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazondevopsguru.html#amazondevopsguru-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions defined by Amazon DevOps Guru](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazondevopsguru.html#amazondevopsguru-actions-as-permissions).
To view examples of DevOps Guru identity-based policies, see [Identity-based policies for Amazon DevOps Guru](security_iam_id-based-policy-examples.md).
## Access control lists (ACLs) in DevOps Guru
**Supports ACLs:** No
Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.
## Attribute-based access control (ABAC) with DevOps Guru
**Supports ABAC (tags in policies):** No
Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.
To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys.
If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**.
For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*.
## Using Temporary credentials with DevOps Guru
**Supports temporary credentials:** Yes
Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Cross-service principal permissions for DevOps Guru
**Supports forward access sessions (FAS):** Yes
Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html).
## Service roles for DevOps Guru
**Supports service roles:** No
A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*.
**Warning**
Changing the permissions for a service role might break DevOps Guru functionality. Edit service roles only when DevOps Guru provides guidance to do so.
## Service-linked roles for DevOps Guru
**Supports service-linked roles:** Yes
A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.
For details about creating or managing service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). Find a service in the table that includes a `Yes` in the **Service-linked role** column. Choose the **Yes** link to view the service-linked role documentation for that service.
# Identity-based policies for Amazon DevOps Guru
By default, users and roles don't have permission to create or modify DevOps Guru resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.
To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*.
For details about actions and resource types defined by DevOps Guru, including the format of the ARNs for each of the resource types, see [Actions, resources, and condition keys for Amazon DevOps Guru](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awskeymanagementservice.html) in the *Service Authorization Reference*.
**Topics**
+ [
## Policy best practices
](#security_iam_service-with-iam-policy-best-practices)
+ [
## Using the DevOps Guru console
](#security_iam_id-based-policy-examples-console)
+ [
## Allow users to view their own permissions
](#security_iam_id-based-policy-examples-view-own-permissions)
+ [
## AWS managed (predefined) policies for DevOps Guru
](#managed-policies)
## Policy best practices
Identity-based policies determine whether someone can create, access, or delete DevOps Guru resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:
+ **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*.
+ **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.
+ **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*.
+ **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*.
+ **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*.
For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.
## Using the DevOps Guru console
To access the Amazon DevOps Guru console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the DevOps Guru resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy.
You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform.
To ensure that users and roles can still use the DevOps Guru console, also attach the DevOps Guru `AmazonDevOpsGuruReadOnlyAccess` or `AmazonDevOpsGuruFullAccess` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*.
## Allow users to view their own permissions
This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ViewOwnUserInfo",
"Effect": "Allow",
"Action": [
"iam:GetUserPolicy",
"iam:ListGroupsForUser",
"iam:ListAttachedUserPolicies",
"iam:ListUserPolicies",
"iam:GetUser"
],
"Resource": ["arn:aws:iam::*:user/${aws:username}"]
},
{
"Sid": "NavigateInConsole",
"Effect": "Allow",
"Action": [
"iam:GetGroupPolicy",
"iam:GetPolicyVersion",
"iam:GetPolicy",
"iam:ListAttachedGroupPolicies",
"iam:ListGroupPolicies",
"iam:ListPolicyVersions",
"iam:ListPolicies",
"iam:ListUsers"
],
"Resource": "*"
}
]
}
```
## AWS managed (predefined) policies for DevOps Guru
AWS addresses many common use cases by providing standalone IAM policies that are created and administered by AWS. These AWS-managed policies grant necessary permissions for common use cases so you can avoid having to investigate what permissions are needed. For more information, see [AWS Managed Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*.
To create and manage DevOps Guru service roles, you must also attach the AWS-managed policy named `IAMFullAccess`.
You can also create your own custom IAM policies to allow permissions for DevOps Guru actions and resources. You can attach these custom policies to the users or groups that require those permissions.
The following AWS-managed policies, which you can attach to users in your account, are specific to DevOps Guru.
**Topics**
+ [
### AmazonDevOpsGuruFullAccess
](#managed-full-access)
+ [
### AmazonDevOpsGuruConsoleFullAccess
](#managed-full-console-access)
+ [
### AmazonDevOpsGuruReadOnlyAccess
](#managed-read-only-access)
+ [
### AmazonDevOpsGuruOrganizationsAccess
](#organizations-policy)
### AmazonDevOpsGuruFullAccess
`AmazonDevOpsGuruFullAccess` – Provides full access to DevOps Guru, including permissions to create Amazon SNS topics, access Amazon CloudWatch metrics, and access AWS CloudFormation stacks. Apply this only to administrative-level users to whom you want to grant full control over DevOps Guru.
The `AmazonDevOpsGuruFullAccess` policy contains the following statement.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "DevOpsGuruFullAccess",
"Effect": "Allow",
"Action": [
"devops-guru:*"
],
"Resource": "*"
},
{
"Sid": "CloudFormationListStacksAccess",
"Effect": "Allow",
"Action": [
"cloudformation:DescribeStacks",
"cloudformation:ListStacks"
],
"Resource": "*"
},
{
"Sid": "CloudWatchGetMetricDataAccess",
"Effect": "Allow",
"Action": [
"cloudwatch:GetMetricData"
],
"Resource": "*"
},
{
"Sid": "SnsListTopicsAccess",
"Effect": "Allow",
"Action": [
"sns:ListTopics",
"sns:ListSubscriptionsByTopic"
],
"Resource": "*"
},
{
"Sid": "SnsTopicOperations",
"Effect": "Allow",
"Action": [
"sns:CreateTopic",
"sns:GetTopicAttributes",
"sns:SetTopicAttributes",
"sns:Subscribe",
"sns:Publish"
],
"Resource": "arn:aws:sns:*:*:DevOps-Guru-*"
},
{
"Sid": "DevOpsGuruSlrCreation",
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "arn:aws:iam::*:role/aws-service-role/devops-guru.amazonaws.com/AWSServiceRoleForDevOpsGuru",
"Condition": {
"StringLike": {
"iam:AWSServiceName": "devops-guru.amazonaws.com"
}
}
},
{
"Sid": "DevOpsGuruSlrDeletion",
"Effect": "Allow",
"Action": [
"iam:DeleteServiceLinkedRole",
"iam:GetServiceLinkedRoleDeletionStatus"
],
"Resource": "arn:aws:iam::*:role/aws-service-role/devops-guru.amazonaws.com/AWSServiceRoleForDevOpsGuru"
},
{
"Sid": "RDSDescribeDBInstancesAccess",
"Effect": "Allow",
"Action": [
"rds:DescribeDBInstances"
],
"Resource": "*"
},
{
"Sid": "CloudWatchLogsFilterLogEventsAccess",
"Effect": "Allow",
"Action": [
"logs:FilterLogEvents"
],
"Resource": "arn:aws:logs:*:*:log-group:*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/DevOps-Guru-Analysis": "true"
}
}
}
]
}
```
------
### AmazonDevOpsGuruConsoleFullAccess
`AmazonDevOpsGuruConsoleFullAccess` – Provides full access to DevOps Guru, including permissions to create Amazon SNS topics, access Amazon CloudWatch metrics, and access AWS CloudFormation stacks. This policy has additional performance insights permissions so you can view detailed analysis related to anomalous Amazon RDS Aurora DB instances in the console. Apply this only to administrative-level users to whom you want to grant full control over DevOps Guru.
The `AmazonDevOpsGuruConsoleFullAccess` policy contains the following statement.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "DevOpsGuruFullAccess",
"Effect": "Allow",
"Action": [
"devops-guru:*"
],
"Resource": "*"
},
{
"Sid": "CloudFormationListStacksAccess",
"Effect": "Allow",
"Action": [
"cloudformation:DescribeStacks",
"cloudformation:ListStacks"
],
"Resource": "*"
},
{
"Sid": "CloudWatchGetMetricDataAccess",
"Effect": "Allow",
"Action": [
"cloudwatch:GetMetricData"
],
"Resource": "*"
},
{
"Sid": "SnsListTopicsAccess",
"Effect": "Allow",
"Action": [
"sns:ListTopics",
"sns:ListSubscriptionsByTopic"
],
"Resource": "*"
},
{
"Sid": "SnsTopicOperations",
"Effect": "Allow",
"Action": [
"sns:CreateTopic",
"sns:GetTopicAttributes",
"sns:SetTopicAttributes",
"sns:Subscribe",
"sns:Publish"
],
"Resource": "arn:aws:sns:*:*:DevOps-Guru-*"
},
{
"Sid": "DevOpsGuruSlrCreation",
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "arn:aws:iam::*:role/aws-service-role/devops-guru.amazonaws.com/AWSServiceRoleForDevOpsGuru",
"Condition": {
"StringLike": {
"iam:AWSServiceName": "devops-guru.amazonaws.com"
}
}
},
{
"Sid": "DevOpsGuruSlrDeletion",
"Effect": "Allow",
"Action": [
"iam:DeleteServiceLinkedRole",
"iam:GetServiceLinkedRoleDeletionStatus"
],
"Resource": "arn:aws:iam::*:role/aws-service-role/devops-guru.amazonaws.com/AWSServiceRoleForDevOpsGuru"
},
{
"Sid": "RDSDescribeDBInstancesAccess",
"Effect": "Allow",
"Action": [
"rds:DescribeDBInstances"
],
"Resource": "*"
},
{
"Sid": "PerformanceInsightsMetricsDataAccess",
"Effect": "Allow",
"Action": [
"pi:GetResourceMetrics",
"pi:DescribeDimensionKeys"
],
"Resource": "*"
},
{
"Sid": "CloudWatchLogsFilterLogEventsAccess",
"Effect": "Allow",
"Action": [
"logs:FilterLogEvents"
],
"Resource": "arn:aws:logs:*:*:log-group:*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/DevOps-Guru-Analysis": "true"
}
}
}
]
}
```
------
### AmazonDevOpsGuruReadOnlyAccess
`AmazonDevOpsGuruReadOnlyAccess` – Grants read-only access to DevOps Guru and related resources in other AWS services. Apply this policy to users to whom you want to grant the ability to view insights, but not to make any updates to DevOps Guru's analysis coverage boundary, Amazon SNS topics, or Systems Manager OpsCenter integration.
The `AmazonDevOpsGuruReadOnlyAccess` policy contains the following statement.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "DevOpsGuruReadOnlyAccess",
"Effect": "Allow",
"Action": [
"devops-guru:DescribeAccountHealth",
"devops-guru:DescribeAccountOverview",
"devops-guru:DescribeAnomaly",
"devops-guru:DescribeEventSourcesConfig",
"devops-guru:DescribeFeedback",
"devops-guru:DescribeInsight",
"devops-guru:DescribeResourceCollectionHealth",
"devops-guru:DescribeServiceIntegration",
"devops-guru:GetCostEstimation",
"devops-guru:GetResourceCollection",
"devops-guru:ListAnomaliesForInsight",
"devops-guru:ListEvents",
"devops-guru:ListInsights",
"devops-guru:ListAnomalousLogGroups",
"devops-guru:ListMonitoredResources",
"devops-guru:ListNotificationChannels",
"devops-guru:ListRecommendations",
"devops-guru:SearchInsights",
"devops-guru:StartCostEstimation"
],
"Resource": "*"
},
{
"Sid": "CloudFormationListStacksAccess",
"Effect": "Allow",
"Action": [
"cloudformation:DescribeStacks",
"cloudformation:ListStacks"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"iam:GetRole"
],
"Resource": "arn:aws:iam::*:role/aws-service-role/devops-guru.amazonaws.com/AWSServiceRoleForDevOpsGuru"
},
{
"Sid": "CloudWatchGetMetricDataAccess",
"Effect": "Allow",
"Action": [
"cloudwatch:GetMetricData"
],
"Resource": "*"
},
{
"Sid": "RDSDescribeDBInstancesAccess",
"Effect": "Allow",
"Action": [
"rds:DescribeDBInstances"
],
"Resource": "*"
},
{
"Sid": "SnsListTopicsAccess",
"Effect": "Allow",
"Action": [
"sns:ListTopics",
"sns:ListSubscriptionsByTopic"
],
"Resource": "*"
},
{
"Sid": "CloudWatchLogsFilterLogEventsAccess",
"Effect": "Allow",
"Action": [
"logs:FilterLogEvents"
],
"Resource": "arn:aws:logs:*:*:log-group:*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/DevOps-Guru-Analysis": "true"
}
}
}
]
}
```
------
### AmazonDevOpsGuruOrganizationsAccess
` AmazonDevOpsGuruOrganizationsAccess` – Provides Organizations administrators access to the DevOps Guru multi-account view within an organization. Apply this policy to your organization's administrator-level users for whom you want to grant full access to DevOps Guru within an organization. You can apply this policy in your organization's management account and delegated administrator account for DevOps Guru. You can apply `AmazonDevOpsGuruReadOnlyAccess` or `AmazonDevOpsGuruFullAccess` in addition to this policy to provide read-only or full access to DevOps Guru.
The `AmazonDevOpsGuruOrganizationsAccess` policy contains the following statement.
# Using service-linked roles for DevOps Guru
Amazon DevOps Guru uses AWS Identity and Access Management (IAM)[ service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). 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.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"autoscaling:DescribeAutoScalingGroups",
"cloudtrail:LookupEvents",
"cloudwatch:GetMetricData",
"cloudwatch:ListMetrics",
"cloudwatch:DescribeAnomalyDetectors",
"cloudwatch:DescribeAlarms",
"cloudwatch:ListDashboards",
"cloudwatch:GetDashboard",
"cloudformation:GetTemplate",
"cloudformation:ListStacks",
"cloudformation:ListStackResources",
"cloudformation:DescribeStacks",
"cloudformation:ListImports",
"codedeploy:BatchGetDeployments",
"codedeploy:GetDeploymentGroup",
"codedeploy:ListDeployments",
"config:DescribeConfigurationRecorderStatus",
"config:GetResourceConfigHistory",
"events:ListRuleNamesByTarget",
"xray:GetServiceGraph",
"organizations:ListRoots",
"organizations:ListChildren",
"organizations:ListDelegatedAdministrators",
"pi:GetResourceMetrics",
"tag:GetResources",
"lambda:GetFunction",
"lambda:GetFunctionConcurrency",
"lambda:GetAccountSettings",
"lambda:ListProvisionedConcurrencyConfigs",
"lambda:ListAliases",
"lambda:ListEventSourceMappings",
"lambda:GetPolicy",
"ec2:DescribeSubnets",
"application-autoscaling:DescribeScalableTargets",
"application-autoscaling:DescribeScalingPolicies",
"sqs:GetQueueAttributes",
"kinesis:DescribeStream",
"kinesis:DescribeLimits",
"dynamodb:DescribeTable",
"dynamodb:DescribeLimits",
"dynamodb:DescribeContinuousBackups",
"dynamodb:DescribeStream",
"dynamodb:ListStreams",
"elasticloadbalancing:DescribeLoadBalancers",
"elasticloadbalancing:DescribeLoadBalancerAttributes",
"rds:DescribeDBInstances",
"rds:DescribeDBClusters",
"rds:DescribeOptionGroups",
"rds:DescribeDBClusterParameters",
"rds:DescribeDBInstanceAutomatedBackups",
"rds:DescribeAccountAttributes",
"logs:DescribeLogGroups",
"logs:DescribeLogStreams",
"s3:GetBucketNotification",
"s3:GetBucketPolicy",
"s3:GetBucketPublicAccessBlock",
"s3:GetBucketTagging",
"s3:GetBucketWebsite",
"s3:GetIntelligentTieringConfiguration",
"s3:GetLifecycleConfiguration",
"s3:GetReplicationConfiguration",
"s3:ListAllMyBuckets",
"s3:ListStorageLensConfigurations",
"servicequotas:GetServiceQuota",
"servicequotas:ListRequestedServiceQuotaChangeHistory",
"servicequotas:ListServiceQuotas"
],
"Resource": "*"
},
{
"Sid": "AllowPutTargetsOnASpecificRule",
"Effect": "Allow",
"Action": [
"events:PutTargets",
"events:PutRule"
],
"Resource": "arn:aws:events:*:*:rule/DevOps-Guru-managed-*"
},
{
"Sid": "AllowCreateOpsItem",
"Effect": "Allow",
"Action": [
"ssm:CreateOpsItem"
],
"Resource": "*"
},
{
"Sid": "AllowAddTagsToOpsItem",
"Effect": "Allow",
"Action": [
"ssm:AddTagsToResource"
],
"Resource": "arn:aws:ssm:*:*:opsitem/*"
},
{
"Sid": "AllowAccessOpsItem",
"Effect": "Allow",
"Action": [
"ssm:GetOpsItem",
"ssm:UpdateOpsItem"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/DevOps-GuruInsightSsmOpsItemRelated": "true"
}
}
},
{
"Sid": "AllowCreateManagedRule",
"Effect": "Allow",
"Action": "events:PutRule",
"Resource": "arn:aws:events:*:*:rule/DevOpsGuruManagedRule*"
},
{
"Sid": "AllowAccessManagedRule",
"Effect": "Allow",
"Action": [
"events:DescribeRule",
"events:ListTargetsByRule"
],
"Resource": "arn:aws:events:*:*:rule/DevOpsGuruManagedRule*"
},
{
"Sid": "AllowOtherOperationsOnManagedRule",
"Effect": "Allow",
"Action": [
"events:DeleteRule",
"events:EnableRule",
"events:DisableRule",
"events:PutTargets",
"events:RemoveTargets"
],
"Resource": "arn:aws:events:*:*:rule/DevOpsGuruManagedRule*",
"Condition": {
"StringEquals": {
"events:ManagedBy": "devops-guru.amazonaws.com"
}
}
},
{
"Sid": "AllowTagBasedFilterLogEvents",
"Effect": "Allow",
"Action": [
"logs:FilterLogEvents"
],
"Resource": "arn:aws:logs:*:*:log-group:*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/DevOps-Guru-Analysis": "true"
}
}
},
{
"Sid": "AllowAPIGatewayGetIntegrations",
"Effect": "Allow",
"Action": "apigateway:GET",
"Resource": [
"arn:aws:apigateway:*::/restapis/??????????",
"arn:aws:apigateway:*::/restapis/*/resources",
"arn:aws:apigateway:*::/restapis/*/resources/*/methods/*/integration"
]
}
]
}
```
------
## 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-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](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*.
# Amazon DevOps Guru permissions reference
You can use AWS-wide condition keys in your DevOps Guru policies to express conditions. For a list, see [IAM JSON Policy Elements Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#AvailableKeys) in the *IAM User Guide*.
You specify the actions in the policy's `Action` field. To specify an action, use the `devops-guru:` prefix followed by the API operation name (for example, `devops-guru:SearchInsights` and `devops-guru:ListAnomalies`). To specify multiple actions in a single statement, separate them with commas (for example, `"Action": [ "devops-guru:SearchInsights", "devops-guru:ListAnomalies" ]`).
**Using wildcard characters**
You specify an Amazon Resource Name (ARN), with or without a wildcard character (\$1), as the resource value in the policy's `Resource` field. You can use a wildcard to specify multiple actions or resources. For example, `devops-guru:*` specifies all DevOps Guru actions and `devops-guru:List*` specifies all DevOps Guru actions that begin with the word `List`. The following example refers to all insights with a universally unique identifier (UUID) that begins with `12345`.
```
arn:aws:devops-guru:us-east-2:123456789012:insight:12345*
```
You can use the following table as a reference when you are setting up [Authenticating with identities](security-iam.md#security_iam_authentication) and writing permissions policies that you can attach to an IAM identity (identity-based policies).
**DevOps Guru API operations and required permissions for actions**
| DevOps Guru API operations | Required permissions (API actions) | Resources |
| --- | --- | --- |
| AddNotificationChannel | `devops-guru:AddNotificationChannel` Required to add a notification channel from DevOps Guru. A notification channel is used to notify you when DevOps Guru generates an insight that contains information about how to improve your operations. | `*` |
| RemoveNotificationChannel | `devops-guru:RemoveNotificationChannel` Required to remove a notification channel from DevOps Guru. A notification channel is used to notify you when DevOps Guru generates an insight that contains information about how to improve your operations. | `*` |
| ListNotificationChannels | `devops-guru:ListNotificationChannels` Required to return a list of notification channels configured for DevOps Guru. Each notification channel is used to notify you when DevOps Guru generates an insight that contains information about how to improve your operations. The one notification type supported is Amazon Simple Notification Service. | `*` |
| UpdateResourceCollectionFilter | `devops-guru:UpdateResourceCollectionFilter` Required to update the list of CloudFormation stacks that are used to specify which AWS resources in your account are analyzed by DevOps Guru. The analysis generates insights that include recommendations, operational metrics, and operational events that you can use to improve the performance of your operations. This method also creates the IAM roles required for you to use CodeGuru OpsAdvisor. | `*` |
| GetResourceCollectionFilter | `devops-guru:GetResourceCollectionFilter` Required to return the list of AWS CloudFormation stacks that are used to specify which AWS resources in your account are analyzed by DevOps Guru. The analysis generates insights that include recommendations, operational metrics, and operational events that you can use to improve the performance of your operations. | `*` |
| ListInsights | `devops-guru:ListInsights` Required to return a list of insights in your AWS account. You can specify which insights are returned by their start time, status (`ongoing` or `any`), and type (`reactive` or `predictive`). | `*` |
| DescribeInsight | `devops-guru:DescribeInsight` Required to return details about an insight that you specify using its ID. | `*` |
| SearchInsights | `devops-guru:SearchInsights` Required to return a list of insights in your AWS account. You can specify which insights are returned by their start time, filters, and type (`reactive` or `predictive`). | `*` |
| ListAnomalies | `devops-guru:ListAnomalies` Required to return a list of the anomalies that belong to an insight that you specify using its ID. | `*` |
| DescribeAnomaly | `devops-guru:DescribeAnomaly` Required to return details about an anomaly that you specify using its ID. | `*` |
| ListEvents | `devops-guru:ListEvents` Required to return a list of the events emitted by the resources that are evaluated by DevOps Guru. You can use filters to specify which events are returned. | `*` |
| `ListAnomalousLogs` | devops-guru:`ListAnomalousLogs` Required to return a list of Amazon CloudWatch log groups that contain log anomalies. These are used to generate insights in DevOps Guru. Administrators should ensure that only users with permissions to view CloudWatch logs have permissions to view anomalous CloudWatch logs. We recommend that you use IAM policies to allow or deny access to the `ListAnomalousLogs` operation. | \$1 |
| ListRecommendations | `devops-guru:ListRecommendations` Required to return a list of a specified insight's recommendations. Each recommendation includes a list of metrics and a list of events that are related to the recommendations. | `*` |
| DescribeAccountHealth | `devops-guru:DescribeAccountHealth` Required to return the number of open reactive insights, the number of open proactive insights, and the number of metrics analyzed in your AWS account. Use these numbers to gauge the health of operations in your AWS account. | `*` |
| DescribeAccountOverview | `devops-guru:DescribeAccountOverview` Required to return the following that happened during a time range: the number of open reactive insights that were created, the number of open predictive insights that were created, and the mean time to recover (MTTR) for all reactive insights that were closed. | `*` |
| DescribeResourceCollectionHealthOverview | `devops-guru:DescribeResourceCollectionHealthOverview` Required to return the number of open predictive insights, open reactive insights, and mean time to recover (MTTR) for all insights for each CloudFormation stack specified in DevOps Guru. | `*` |
| DescribeIntegratedService | `devops-guru:DescribeIntegratedService` Required to return the integration status of services that can be integrated with DevOps Guru. The one service that can be integrated with DevOps Guru is AWS Systems Manager, which can be used to create an OpsItem for each generated insight. | `*` |
| UpdateIntegratedServiceConfig | `devops-guru:UpdateIntegratedServiceConfig` Required to enable or disable integration with a service that can be integrated with DevOps Guru. The one service that can be integrated with DevOps Guru is Systems Manager, which can be used to create an OpsItem for each generated insight. | `*` |
# Permissions for Amazon SNS topics
Use the information in this topic only if you want to configure Amazon DevOps Guru to deliver notifications to Amazon SNS topics owned by another AWS account.
For DevOps Guru to deliver notifications to an Amazon SNS topic owned by a different account, you must attach a policy to the Amazon SNS topic that grants DevOps Guru permissions to send notifications to it. If you configure DevOps Guru to deliver notifications to Amazon SNS topics owned by the same account you use for DevOps Guru, then DevOps Guru adds a policy to the topics for you.
After you attach a policy to configure permissions for an Amazon SNS topic in another account, you can add the Amazon SNS topic in DevOps Guru. You can also update your Amazon SNS policy with a notification channel to make it more secure.
**Note**
DevOps Guru currently only supports cross-account access in the same Region.
**Topics**
+ [
## Configuring permissions for an Amazon SNS topic in another account
](#sns-permissions-attach-policy)
+ [
## Adding an Amazon SNS topic from another account
](#sns-permissions-add-sns-topic)
+ [
## Updating your Amazon SNS policy with a notification channel (recommended)
](#sns-permissions-policy-notification-channel)
## Configuring permissions for an Amazon SNS topic in another account
### Adding permissions as an IAM role
To use an Amazon SNS topic from another account after logging in with an IAM role, you must attach a policy to the Amazon SNS topic you want to use. To attach a policy to an Amazon SNS topic from another account while using an IAM role, you need to have the following permissions for that account resource as part of your IAM role:
+ sns:CreateTopic
+ sns:GetTopicAttributes
+ sns:SetTopicAttributes
+ sns:Publish
Attach the following policy to the Amazon SNS topic you want to use. For the `Resource` key, *topic-owner-account-id* is the account ID of the topic owner, *topic-sender-account-id* is the account ID of the user who set up DevOps Guru, and *devops-guru-role* is the IAM role of the individual user involved. You must substitute appropriate values for *region-id* (for example, `us-west-2`), and *my-topic-name*.
### Adding permissions as an IAM user
To use an Amazon SNS topic from another account as an IAM user, attach the following policy to the Amazon SNS topic you want to use. For the `Resource` key, *topic-owner-account-id* is the account ID of the topic owner, *topic-sender-account-id* is the account ID of the user who set up DevOps Guru, and *devops-guru-user-name* is the individual IAM user involved. You must substitute appropriate values for *region-id* (for example, `us-west-2`) and *my-topic-name*.
**Note**
Where possible, we recommend relying on temporary credentials instead of creating IAM users who have long-term credentials such as passwords and access keys. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.
## Adding an Amazon SNS topic from another account
After you configure permissions for an Amazon SNS topic in another account, you can add that Amazon SNS topic to your DevOps Guru notification settings. You can add the Amazon SNS topic using the AWS CLI or the DevOps Guru console.
+ When you use the console, you must select the option **Use an SNS topic ARN to specify an existing topic** in order to use a topic from another account.
+ When you use the AWS CLI operation [add-notification-channel](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/devops-guru/add-notification-channel.html), you must specify the `TopicArn` within the `NotificationChannelConfig` object.
**Add an Amazon SNS topic from another account using the console**
1. Open the Amazon DevOps Guru console at [https://console.aws.amazon.com/devops-guru/](https://console.aws.amazon.com/devops-guru/).
1. Open the navigation pane, and then choose **Settings**.
1. Go to the **Notifications** section and choose **Edit**.
1. Choose **Add SNS topic**.
1. Choose **Use an SNS topic ARN to specify an existing topic**.
1. Enter the ARN of the Amazon SNS topic you want to use. You should have already configured permissions for this topic by attaching a policy to it.
1. (Optional) Choose **Notification configuration** to edit notification frequency settings.
1. Choose **Save**.
After you add the Amazon SNS topic to your notification settings, DevOps Guru uses that topic to notify you of important events, such as when a new insight is created.
## Updating your Amazon SNS policy with a notification channel (recommended)
After you add a topic, we recommend that you make your policy more secure by specifying permissions for only the DevOps Guru notification channel that contains your topic.
**Update your Amazon SNS topic policy with a notification channel (recommended)**
1. Run the `list-notification-channels` DevOps Guru AWS CLI command in your account that you want to send notifications from.
```
aws devops-guru list-notification-channels
```
1. In the `list-notification-channels` response, make a note of the channel ID that contains your Amazon SNS topic's ARN. The channel ID is a guid.
For example, in the following response, the channel ID for the topic with the ARN `arn:aws:sns:region-id:111122223333:topic-name` is `e89be5f7-989d-4c4c-b1fe-e7145037e531`
```
{
"Channels": [
{
"Id": "e89be5f7-989d-4c4c-b1fe-e7145037e531",
"Config": {
"Sns": {
"TopicArn": "arn:aws:sns:region-id:111122223333:topic-name"
},
"Filters": {
"MessageTypes": ["CLOSED_INSIGHT", "NEW_INSIGHT", "SEVERITY_UPGRADED"],
"Severities": ["HIGH", "MEDIUM"]
}
}
}
]
}
```
1. Go to the policy that you created in another account using the topic owner ID in [Configuring permissions for an Amazon SNS topic in another account](#sns-permissions-attach-policy). In the `Condition` statement of the policy, add the line that specifies the `SourceArn`. The ARN contains your Region ID (for example, `us-east-1`), the AWS account number of the topic's sender, and the channel ID you made a note of.
Your updated `Condition` statement looks like the following.
```
"Condition" : {
"StringEquals" : {
"AWS:SourceArn": "arn:aws:devops-guru:us-east-1:111122223333:channel/e89be5f7-989d-4c4c-b1fe-e7145037e531",
"AWS:SourceAccount": "111122223333"
}
}
```
If `AddNotificationChannel` is unable to add your SNS Topic, check that your IAM policy has the following permissions.
# Permissions for AWS KMS–encrypted Amazon SNS topics
The Amazon SNS topic you specify might be encrypted by AWS Key Management Service. To allow DevOps Guru to work with encrypted topics, you must first create a AWS KMS key and then add the following statement to the policy of the KMS key. For more information, see [Encrypting messages published to Amazon SNS with AWS KMS](https://aws.amazon.com/blogs/compute/encrypting-messages-published-to-amazon-sns-with-aws-kms/), [Key identifiers (KeyId)](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id) in the *AWS KMS User Guide*, and [Data encryption](https://docs.aws.amazon.com/sns/latest/dg/sns-data-encryption.html) in the *Amazon Simple Notification Service Developer Guide*.
**Note**
DevOps Guru currently supports encrypted topics for use within a single account. Using an encrypted topic across multiple accounts is not supported at this time.
# Troubleshooting Amazon DevOps Guru identity and access
Use the following information to help you diagnose and fix common issues that you might encounter when working with DevOps Guru and IAM.
**Topics**
+ [
## I am not authorized to perform an action in DevOps Guru
](#security_iam_troubleshoot-no-permissions)
+ [
## I want to give users programmatic access
](#security_iam_troubleshoot-keys)
+ [
## I am not authorized to perform iam:PassRole
](#security_iam_troubleshoot-passrole)
+ [
## I want to allow people outside of my AWS account to access my DevOps Guru resources
](#security_iam_troubleshoot-cross-account-access)
## I am not authorized to perform an action in DevOps Guru
If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance.
The following example error occurs when the user `mateojackson` tries to use the console to view details about a fictional `my-example-widget` resource but does not have the fictional `aws:GetWidget` permissions.
```
User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: aws:GetWidget on resource: my-example-widget
```
In this case, Mateo asks his administrator to update his policies to allow him to access the `my-example-widget` resource using the `aws:GetWidget` action.
## I want to give users programmatic access
Users need programmatic access if they want to interact with AWS outside of the AWS Management Console. The way to grant programmatic access depends on the type of user that's accessing AWS.
To grant users programmatic access, choose one of the following options.
****
| Which user needs programmatic access? | To | By |
| --- | --- | --- |
| IAM | (Recommended) Use console credentials as temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions for the interface that you want to use. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/devops-guru/latest/userguide/security_iam_troubleshoot.html) |
| Workforce identity (Users managed in IAM Identity Center) | Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions for the interface that you want to use. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/devops-guru/latest/userguide/security_iam_troubleshoot.html) |
| IAM | Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions in [Using temporary credentials with AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html) in the IAM User Guide. |
| IAM | (Not recommended)Use long-term credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions for the interface that you want to use. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/devops-guru/latest/userguide/security_iam_troubleshoot.html) |
## I am not authorized to perform iam:PassRole
If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to DevOps Guru.
Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service.
The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in DevOps Guru. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service.
```
User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole
```
In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action.
If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.
## I want to allow people outside of my AWS account to access my DevOps Guru resources
You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.
To learn more, consult the following:
+ To learn whether DevOps Guru supports these features, see [How Amazon DevOps Guru works with IAM](security_iam_service-with-iam.md).
+ To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*.
+ To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*.
+ To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*.
+ To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.