Skip to content

Commit

Permalink
Merge branch 'Auto-discovery' of https://github.com/newrelic/docs-web…
Browse files Browse the repository at this point in the history
…site into Auto-discovery
  • Loading branch information
sujitnewrelic committed Feb 18, 2025
2 parents af280cc + a707b22 commit 5b76b27
Showing 1 changed file with 16 additions and 16 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -24,32 +24,32 @@ With Auto-discovery, you can:

The <DNT>**Auto-discovery**</DNT> feature is available only to the **[Advanced Compute](https://newrelic.com/pricing/compute#pricing_plan-compute)** customers. To enroll, navigate to <DNT>**[one.newrelic.com > Administration](https://one.newrelic.com//admin-portal) > Preview & Trails**</DNT>, and enable <DNT>**Auto-discovery**</DNT>.

## Set up AWS integration with auto-discovery [set-up-aws-integration-with-auto-discovery]
## Set up AWS integration with auto-discovery [#set-up-aws-integration-with-auto-discovery]
If you are setting up AWS integration for the first time and want to enable auto-discovery, follow these steps:

<Steps>

<Step>
### Before you begin [before-you-begin]
### Before you begin [#before-you-begin]
To set up AWS integration, ensure you have the following:
* A New Relic [license key](https://one.newrelic.com/api-keys).
* An AWS account with [permissions](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html) to deploy new AWS resources and [IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html).
* A New Relic account with [permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure) for cloud integrations.
</Step>
<Step>
### Select data type [select-data-type]
### Select data type [#select-data-type]

1. Log in to your [New Relic](https://one.newrelic.com/) account and navigate to <DNT>**Infrastructure > AWS**</DNT>.
3. To integrate with AWS, select a New Relic account and continue.
4. Select the data type as <DNT>**Metrics**</DNT>, <DNT>**Logs**</DNT>, or both, and continue.
5. Select <DNT>**Automate AWS with CloudFormation**</DNT> and continue. This is currently the only setup method available for log integration.
</Step>
<Step>
### Select integration method [select-integration-method]
### Select integration method [#select-integration-method]
Automating AWS integration with CloudFormation template is the recommended and the only integration method to enable auto-discovery. This method uses a single CloudFormation template to set up your AWS integration and forward New Relic AWS services metrics, logs, or both. Continue with <DNT>**Automate AWS with CloudFormation (Recommended)**</DNT> .
</Step>
<Step>
### Select integration type [select-integration-type]
### Select integration type [#select-integration-type]

<CollapserGroup>
<Collapser id="metrics-data-type" title="For Metrics data type">
Expand Down Expand Up @@ -86,63 +86,63 @@ Automating AWS integration with CloudFormation template is the recommended and t

</Step>
<Step>
### Enable auto-discovery [enable-auto-discovery]
### Enable auto-discovery [#enable-auto-discovery]
Turn on the scan to enable auto-discovery of your AWS entities and continue. It enables the `cloudformation:StartResourceScan` permission in your AWS account to scan your AWS resources and discover the relationships between them.
</Step>
<Step>
### Connect to AWS [connect-to-aws]
### Connect to AWS [#connect-to-aws]
1. Click <DNT>**Launch your CloudFormation in AWS**</DNT> to navigate to your AWS Console. The CloudFormation stack includes the configured parameters based on your selections in New Relic One, so no additional editing is necessary unless you want to make changes.
2. Copy and paste your license key into your AWS console.

We recommend you store your New Relic license key in <DNT>**[AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html)**</DNT> by keeping the environment variable set to `true` (default value).
</Step>
<Step>
### Deploy the CloudFormation stack [deploy-cloudformation-stack]
### Deploy the CloudFormation stack [#deploy-cloudformation-stack]
After you customize the CloudFormation stack parameters to meet your requirements, click <DNT>**Create stack**</DNT>.
Creating the stack's resources may take several minutes and may generate multiple stacks, depending on how you configure log and metric forwarding. With a single deployment command, you can create a new stack to forward logs from multiple AWS resources.
If stack creation fails, refer to the [troubleshooting procedure](/docs/logs/troubleshooting/aws-log-integration-issues/stack-creation-fails).
</Step>
<Step>
### Validate the AWS data on New Relic [validate-aws-data]
### Validate the AWS data on New Relic [#validate-aws-data]
After the new stack is created, go to <DNT>**[New Relic](https://one.newrelic.com/) > Infrastructure > AWS**</DNT> to view all integrated AWS services. If any New Relic service is connected to AWS entities, you can view its map to see relationships with those AWS entities and the intra-service relationships among them.
</Step>

</Steps>

## Set up auto-discovery for an existing AWS integration [set-up-auto-discovery-for-existing-aws-integration]
## Set up auto-discovery for an existing AWS integration [#set-up-auto-discovery-for-existing-aws-integration]
If you have already set up an AWS integration and want to enable auto-discovery, follow these steps:

<Steps>

<Step>
### Before you begin [prerequisite-for-existing-aws-integration]
### Before you begin [#prerequisite-for-existing-aws-integration]
To update AWS integration, ensure you have the following:
* An AWS account with [permissions](https://docs.aws.amazon.com/ARG/latest/userguide/gettingstarted-prereqs-permissions.html) to deploy new AWS resources and [IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html).
* A New Relic account with [permissions](/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions/#infrastructure) for cloud integrations.
</Step>
<Step>
### Edit account [edit-account]
### Edit account [#edit-account]

1. Log in to your [New Relic](https://one.newrelic.com/) account and navigate to <DNT>**Infrastructure > AWS**</DNT>.
2. To check the Auto-discovery enablement status of your AWS accounts, click <DNT>**Manage Auto-discovery**</DNT>.
3. From the account list, click <DNT>**Enable**</DNT> for the AWS account in which you want to configure auto-discovery.
</Step>
<Step>
### Update the CloudFormation stack [update-cloudformation-stack]
### Update the CloudFormation stack [#update-cloudformation-stack]

1. To update the CloudFormation stack, on the side pane, click <DNT>**Launch Cloudformation Template**</DNT>.
2. On the AWS console, acknowledge the CloudFormation stack and click <DNT>**Create stack**</DNT>.
3. After the stack is created, go back to the New Relic One.

### Select region and frequency of scan [select-region-and-frequency]
### Select region and frequency of scan [#select-region-and-frequency]

By default, New Relic scans all regions enabled in your account once in a day. You can customize it as follows on the side pane:
* To run the scan for specific regions, select or remove regions as per your requirement.
* To change the frequency of the scan, select <DNT>**Once a Day**</DNT> or <DNT>**Twice a Day**</DNT>, as per your requirement.
</Step>
<Step>
### Enable Auto-discovery [enable-auto-discovery]
To enable auto-discovery, on the confirmation screen of New Relic One, click <DNT>**Save**</DNT>.
To enable auto-discovery, On the confirmation screen of New Relic One, click <DNT>**Save**</DNT>.
</Step>

</Steps>
Expand Down Expand Up @@ -172,4 +172,4 @@ To enable auto-discovery, on the confirmation screen of New Relic One, click <DN
6. To disable auto-discovery, click <DNT>**Save**</DNT>.

</Collapser>
</CollapserGroup>
</CollapserGroup>

0 comments on commit 5b76b27

Please sign in to comment.