Skip to content

Commit 006f538

Browse files
Update content/hcp-docs/content/docs/vault-radar/agent/correlate-aws-secrets-manager.mdx
1 parent b10deb1 commit 006f538

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/hcp-docs/content/docs/vault-radar/agent/correlate-aws-secrets-manager.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Before you can correlate findings with AWS Secrets Manager, you need to [deploy
1616

1717
You need one of the following authentication methods:
1818

19-
- IAM Role authentication with an EC2 instance or configured IAM role
19+
- IAM role authentication with an EC2 instance or configured IAM role
2020
- Environment variables authentication with AWS Access Key ID and Secret Access Key
2121

2222
Both authentication methods support an optional assume role ARN for cross-account access or elevated permissions. For more information about assuming roles, refer to the [AWS STS AssumeRole documentation](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html).

0 commit comments

Comments
 (0)