Skip to content

fix: Wording enhancements on the cloud onboarding #23945

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PhaniK-nr wants to merge 1 commit into
base: develop
Choose a base branch
from
+8 −4
Open

fix: Wording enhancements on the cloud onboarding #23945

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions src/content/docs/vulnerability-management/cloud/setup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,9 @@ If you're connecting your AWS account to New Relic for the first time:

### For existing AWS integration users

If your AWS account is already connected to New Relic, you have two ways to enable Security Hub: either navigate to **Infrastructure > Manage AWS integrations** or **Integrations & Agents**. Once there, complete the integration by opting for Security Hub configurations.
If your AWS account is already connected to New Relic, you have two ways to enable Security Hub. Navigate to:
1. [**Integrations & Agents**](/docs/vulnerability-management/cloud/setup/#navigate-to-the-integration-setup). Once there, complete the integration by opting for Security Hub configurations.
2. **Infrastructure > AWS > Manage AWS integrations**

<Steps>
<Step>
Expand Down Expand Up @@ -201,17 +203,19 @@ If you don't see security findings after setup:
* Verify AWS Security Hub is enabled in your monitored regions
* Check that your IAM permissions include Security Hub read access
* Confirm that security findings exist in AWS Security Hub
* Wait for the next polling cycle (up to 12 hours depending on your settings)
* Wait for the next polling cycle 24 hours depending on your settings

### Auto-discovery not finding resources
### Auto-discovery not detecting resources

If resources aren't being discovered:

* Verify auto-discovery is enabled for the correct regions
* Check IAM permissions for EC2, S3, RDS, and other service read access
* Ensure resources exist in the monitored regions
* Verify your IAM role grants read access to all AWS resources in the monitored regions
* Wait for the next discovery scan

For more information, navigate to [Auto-discovery for AWS entities](/docs/infrastructure/amazon-integrations/connect/set-up-auto-discovery-of-aws-entities)

### Performance considerations

* Choose polling frequency based on your security response requirements
Expand Down
Loading