# Enabling DevOps Guru for RDS
<a name="working-with-rds.enabling"></a>

When you enable DevOps Guru for RDS, you enable DevOps Guru to analyze anomalies in resources such as DB instances. Amazon RDS makes it easy to discover and enable recommended functionality for an RDS DB instance or DB cluster. To achieve this, RDS makes API calls to other services, such as Amazon EC2, DevOps Guru, and IAM. When the RDS console makes these API calls, AWS CloudTrail logs them for visibility.

To allow DevOps Guru to publish insights for an Amazon RDS database, complete the tasks in the following sections.

**Topics**
+ [Turning on Performance Insights for your Amazon RDS DB instances](#working-with-rds.enabling.pi)
+ [Configuring access policies for DevOps Guru for RDS](#working-with-rds.enabling.policy)
+ [Adding Amazon RDS DB instances to your DevOps Guru coverage](#working-with-rds.enabling.cf)

## Turning on Performance Insights for your Amazon RDS DB instances
<a name="working-with-rds.enabling.pi"></a>

For DevOps Guru for RDS to analyze anomalies on a DB instance, make sure that Performance Insights is turned on. If Performance Insights isn't turned on for a DB instance, DevOps Guru for RDS notifies you in the following places:

Dashboard  
If you view insights by resource type, the **RDS** tile alerts you that Performance Insights isn't turned on. Choose the link to turn on Performance Insights in the Amazon RDS console.

Insights  
In the **Recommendations** section at the bottom of the page, choose **Enable Amazon RDS Performance Insights**.

Settings  
In the **Service: Amazon RDS** section, choose the link to turn on Performance Insights in the Amazon RDS console.

For more information, see [Turning Performance Insights on and off](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.Enabling.html) in the *Amazon Aurora User Guide*, or [Turning Performance Insights on and off](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PerfInsights.Enabling.html) in the *Amazon RDS User Guide*.

## Configuring access policies for DevOps Guru for RDS
<a name="working-with-rds.enabling.policy"></a>

For a user to access DevOps Guru for RDS, they must have permissions from either of the following policies:
+ The AWS managed policy `AmazonRDSFullAccess`
+ A customer managed policy that allows the following actions:
  + `pi:GetResourceMetrics`
  + `pi:DescribeDimensionKeys`
  + `pi:GetDimensionKeyDetails`

For more information, see [Configuring access policies for Performance Insights](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.Enabling.html) in the *Amazon Aurora User Guide* or [Configuring access policies for Performance Insights](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PerfInsights.access-control.html) in the *Amazon RDS User Guide*.

## Adding Amazon RDS DB instances to your DevOps Guru coverage
<a name="working-with-rds.enabling.cf"></a>

You can configure DevOps Guru to monitor your Amazon RDS databases either in the DevOps Guru console or the Amazon RDS console. 

 In the DevOps Guru console, you have the following options: 
+ Turn on DevOps Guru at the account level. This is the default. When you choose this option, DevOps Guru analyzes all supported AWS resources in your AWS Region and AWS account, including Amazon RDS databases.
+ Specify AWS CloudFormation stacks for DevOps Guru for RDS.

  For more information, see [Using CloudFormation stacks to identify resources in your DevOps Guru applications](working-with-cfn-stacks.md).
+ Tag your Amazon RDS resources.

  A *tag* is a custom attribute label that you assign to an AWS resource. Use tags to identify the AWS resources that make up your application. You can then filter your insights by tag to view only those created by your application. To view only insights generated by the Amazon RDS resources in your application, add a value such as `Devops-guru-rds` to your Amazon RDS resource tags. For more information, see [Using tags to identify resources in your DevOps Guru applications](working-with-resource-tags.md).
**Note**  
When you tag Amazon RDS resources, you must tag the database instance and not the cluster.

To enable DevOps Guru monitoring from the Amazon RDS console, see [Turning on DevOps Guru in the RDS console](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/devops-guru-for-rds.html#devops-guru-for-rds.configuring.coverage.rds-console). Note that to enable DevOps Guru from the Amazon RDS console you must use tags. For more information about tags, see [Using tags to identify resources in your DevOps Guru applications](working-with-resource-tags.md).