AWS devopsagent documentation change
Summary
Fixed broken documentation link to 'Creating an IAM role for SigV4 authentication' section
Security assessment
Corrects documentation reference without security implications; maintains existing security content about IAM roles
Diff
diff --git a/devopsagent/latest/userguide/configuring-integrations-and-knowledge-connecting-remote-a2a-agents.md b/devopsagent/latest/userguide/configuring-integrations-and-knowledge-connecting-remote-a2a-agents.md index c8710fdd9..522a28396 100644 --- a//devopsagent/latest/userguide/configuring-integrations-and-knowledge-connecting-remote-a2a-agents.md +++ b//devopsagent/latest/userguide/configuring-integrations-and-knowledge-connecting-remote-a2a-agents.md @@ -116 +116 @@ Select one of the following authentication methods: - * **Use an existing role** – Select an existing IAM role from the dropdown. The role must have a trust policy that allows the AWS DevOps Agent service principal to assume it (see [Creating an IAM role for SigV4 authentication](configuring-capabilities-for-aws-devops-agent-connecting-mcp-servers.html#creating-an-iam-role-for-sigv4-authentication)). + * **Use an existing role** – Select an existing IAM role from the dropdown. The role must have a trust policy that allows the AWS DevOps Agent service principal to assume it (see [Creating an IAM role for SigV4 authentication](configuring-integrations-and-knowledge-connecting-mcp-servers.html#creating-an-iam-role-for-sigv4-authentication)).