diff --git a/src/content/docs/vulnerability-management/cloud/setup.mdx b/src/content/docs/vulnerability-management/cloud/setup.mdx
index ec0d31d0a48..37fe81c212b 100644
--- a/src/content/docs/vulnerability-management/cloud/setup.mdx
+++ b/src/content/docs/vulnerability-management/cloud/setup.mdx
@@ -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>
@@ -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