# Getting started with DevOps Guru
In this section, you learn how to get started with Amazon DevOps Guru so it can analyze your application's operational data and metrics to generate insights.
**Topics**
+ [
# Step 1: Get set up
](get-set-up.md)
+ [
# Step 2: Enable DevOps Guru
](getting-started-enable-service.md)
+ [
# Step 3: Specify your DevOps Guru resource coverage
](choose-coverage.md)
# Step 1: Get set up
Before you get started, prepare by running through the steps in [Setting up Amazon DevOps Guru](setting-up.md).
# Step 2: Enable DevOps Guru
To configure Amazon DevOps Guru to use for the first time, you must choose how you want to set up DevOps Guru. You can either monitor applications across your organization or monitor applications in your current account.
You can either monitor your applications across your organization or enable DevOps Guru for exclusively the current account. The following procedures outline different ways to set up DevOps Guru based on your needs.
# Monitor accounts across your organization
If you choose to monitor applications across your organization, log into your organization management account. You can optionally set up an organization member account as a **delegated administrator**. You can only have one delegated administrator at a time and can modify the administrator settings later. Both the management account and the delegated administrator account that you set up have access to all insights across all accounts in your organization.
You can either add cross account support for your organization using the Console, or you can do so by using the AWS CLI.
## Onboard with the DevOps Guru Console
You can use the Console to add support for accounts across your organization.
**Use the Console to enable DevOps Guru to view aggregated insights**
1. Open the Amazon DevOps Guru console at [https://console.aws.amazon.com/devops-guru/](https://console.aws.amazon.com/devops-guru/).
1. Choose **Monitor applications across your organizations** as the setup type.
1. Choose which account you'd like to use as your delegated administrator. Then, choose **Register delegated administrator**. This provides access to a consolidated view for any account that has DevOps Guru enabled. The delegated administrator has a consolidated view of all DevOps Guru insights and metrics across your organization. You can enable other accounts with SSM quick setup or AWS CloudFormation stack sets. To learn more about quick setup, see [Configure DevOps Guru with Quick Setup](https://docs.aws.amazon.com/systems-manager/latest/userguide/quick-setup-devops.html). To learn more about setting up with stack sets, see [Working with stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacks.html) in the *CloudFormation User Guide*, and [Step 2 – Determine coverage for DevOps Guru](setting-up.md#setting-up-determine-coverage). and [Using CloudFormation stacks to identify resources in your DevOps Guru applications](working-with-cfn-stacks.md).
## Onboard with the AWS CLI
You can use the AWS CLI to enable DevOps Guru to view aggregated insights. Run the following commands.
```
aws iam create-service-linked-role --aws-service-name devops-guru.amazonaws.com --description "My service-linked role to support DevOps Guru"
aws organizations enable-aws-service-access --service-principal devops-guru.amazonaws.com
aws organizations register-delegated-administrator --account-id >ACCOUNT_ID< --service-principal devops-guru.amazonaws.com
```
The following table describes the commands.
| Command | Description |
| --- | --- |
| `create-service-linked-role` | Gives DevOps Guru permission to gather information about your organization. Don't proceed if this step is not successful. |
| `enable-aws-service-access` | Onboards your organization to DevOps Guru. |
| `register-delegated-administrator` | Gives access to the member account to view insights. |
# Monitor your current account
If you choose to monitor applications in your current AWS account, choose which AWS resources in your account and Region are covered or analyzed and specify one or two Amazon Simple Notification Service topics that are used to notify you when an insight is created. You can update these settings later as needed.
**Enable DevOps Guru to monitor applications in your current AWS account**
1. Open the Amazon DevOps Guru console at [https://console.aws.amazon.com/devops-guru/](https://console.aws.amazon.com/devops-guru/).
1. Choose **Monitor applications in the current AWS account** as the setup type.
1. In **DevOps Guru analysis coverage**, choose one of the following.
+ **Analyze all AWS resources in the current AWS account**: DevOps Guru analyzes all AWS resources in your account.
+ **Choose AWS resources to analyze later**: You choose your analysis boundary later. For more information, see [Determine coverage for DevOps Guru](setting-up.md#setting-up-determine-coverage) and [Updating your AWS analysis coverage in DevOps Guru](update-settings.md#update-coverage).
DevOps Guru can analyze any resource that is associated with the AWS account it supports. For more information about the supported services and resources, see [Amazon DevOps Guru pricing](https://aws.amazon.com/devops-guru/pricing/).
1. You can add up to two topics. DevOps Guru uses the topic or topics to notify you about important DevOps Guru events, such as the creation of a new insight. If you don't specify a topic now, you can add one later by choosing **Settings** in the navigation pane.
1. In **Specify an Amazon SNS topic**, choose a topic to use.
1. To add an Amazon SNS topic, do one of the following.
+ Choose **Generate a new SNS topic using email**. Then, from **Specify the email address**, enter the email address you want to receive notifications. To enter in additional email addresses, choose **Add new email**.
+ Choose **Use an existing SNS topic**. Then, from **Choose a topic in your AWS account**, choose the topic you want to use.
+ Choose **Use an existing SNS topic ARN to specify an existing topic from another account**. Then, in **Enter an ARN for a topic**, enter the topic ARN. The ARN is the topic's Amazon Resource Name. You can specify a topic in a different account. If you use a topic in another account, you must add a resource policy to the topic. For more information, see [Permissions for Amazon SNS topics](sns-required-permissions.md).
1. Choose **Enable**.
To configure Amazon DevOps Guru to use for the first time, you must choose which AWS resources in your account and Region is covered, or analyzed, and specify one or two Amazon Simple Notification Service topics that are used to notify you when an insight is created. You can update these settings later as needed.
# Step 3: Specify your DevOps Guru resource coverage
If you chose to specify AWS resources later when you enabled DevOps Guru, you need to choose the CloudFormation stacks in your AWS account that create the resources you want analyzed. An CloudFormation stack is a collection of AWS resources that you manage as a single unit. You can use one or more stacks to include all the resources required to run your operational applications, then specify them so that they are analyzed by DevOps Guru. If you don't specify stacks, then DevOps Guru analyzes all the AWS resources in your account. For more information, see [Working with stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacks.html) in the *CloudFormation User Guide*, and [Determine coverage for DevOps Guru](setting-up.md#setting-up-determine-coverage). and [Using CloudFormation stacks to identify resources in your DevOps Guru applications](working-with-cfn-stacks.md).
**Note**
For more information about supported services and resources, see [Amazon DevOps Guru pricing](https://aws.amazon.com/devops-guru/pricing/).
**Specify DevOps Guru resource coverage**
1. Open the Amazon DevOps Guru console at [https://console.aws.amazon.com/devops-guru/](https://console.aws.amazon.com/devops-guru/).
1. Expand **Settings** in the navigation pane.
1. In **Analyzed resources**, choose **Edit analyzed resources**.
1. Choose one of the following coverage options.
+ Choose **All account resources** if you want DevOps Guru to analyze all supported resources in your AWS account and Region. If you choose this option, your AWS account is your resource analysis coverage boundary. All resources in each stack in your account are grouped into their own application. Any remaining resources that are not in a stack are grouped into their own application.
+ Choose **CloudFormation stacks** if you want DevOps Guru to analyze the resources that are in stacks you choose, then choose one of the following options.
+ **All resources** – All resources that are in stacks in your account are analyzed. Resources in each stack are grouped into their own application. Any resources in your account that are not in a stack are not analyzed.
+ **Select stacks** – Select the stacks that you want DevOps Guru to analyze. The resources in each stack you select are grouped into their own application. You can enter the name of a stack in **Find stacks** to quickly locate a specific stack. You can select up to 1,000 stacks.
For more information, see [Using CloudFormation stacks to identify resources in your DevOps Guru applications](working-with-cfn-stacks.md).
+ Choose **Tags** if you want DevOps Guru to analyze all resources that contain the tags you choose. Choose a *key*, then choose one of the following options.
+ **All account resources** –Analyze all AWS resources in the current Region and account. Resources with the selected tag key are grouped by tag value, if any exist. Resources without this tag key are grouped and analyzed separately.
+ **Choose specific tag values** – All resources that contain a tag with the *key* you chose are analyzed. DevOps Guru groups your resources into applications by your tag's *values*.
For more information, see [Using tags to identify resources in your DevOps Guru applications](working-with-resource-tags.md).
+ Choose **None** if you do not want DevOps Guru to analyze any resources. This option disables DevOps Guru so that you stop incurring charges from resource analyzation.
1. Choose **Save**.