AWS devopsagent documentation change
Summary
Updated terminology from 'click' to 'choose' in UI instructions, fixed anchor link for IAM role documentation, and changed section title from 'Connecting multiple AWS Accounts' to 'Connecting Remote A2A Agents'
Security assessment
Changes are purely editorial/terminology updates with no security implications. The IAM role documentation link correction improves accuracy but doesn't alter security content. No vulnerabilities or security features are addressed or added.
Diff
diff --git a/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-mcp-servers.md b/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-mcp-servers.md index 86ccc0f6e..784a342da 100644 --- a//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-mcp-servers.md +++ b//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-mcp-servers.md @@ -60 +60 @@ MCP servers are registered at the AWS account level and shared among all Agent S - 4. Find **MCP Server** in the **Available** providers section and click **Register** + 4. Find **MCP Server** in the **Available** providers section and choose **Register** @@ -74 +74 @@ MCP servers are registered at the AWS account level and shared among all Agent S - 6. Click **Next** + 6. Choose **Next** @@ -91 +91 @@ Select the authentication method for your MCP server: - 2. Click **Next** + 2. Choose **Next** @@ -100 +100 @@ Select the authentication method for your MCP server: - 2. Click **Next** + 2. Choose **Next** @@ -109 +109 @@ Select the authentication method for your MCP server: - 2. Click **Next** + 2. Choose **Next** @@ -118 +118 @@ Select the authentication method for your MCP server: - 2. Click **Next** + 2. Choose **Next** @@ -139 +139 @@ Configure additional authorization parameters based on the selected authenticati - 6. Click **Next** + 6. Choose **Next** @@ -158 +158 @@ Configure additional authorization parameters based on the selected authenticati - 7. Click **Next** + 7. Choose **Next** @@ -171 +171 @@ Configure additional authorization parameters based on the selected authenticati - 4. Click **Next** + 4. Choose **Next** @@ -182 +182 @@ AWS SigV4 authentication allows AWS DevOps Agent to connect to MCP servers that - * **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)). + * **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)). @@ -192 +192 @@ AWS SigV4 authentication allows AWS DevOps Agent to connect to MCP servers that - 5. Click **Next** + 5. Choose **Next** @@ -201 +201 @@ AWS SigV4 authentication allows AWS DevOps Agent to connect to MCP servers that - 2. Click **Submit** to complete the registration + 2. Choose **Submit** to complete the registration @@ -218 +218 @@ After registering an MCP server at the account level, you can configure which to - 3. In the **MCP Servers** section, click **Add** + 3. In the **MCP Servers** section, choose **Add** @@ -228 +228 @@ After registering an MCP server at the account level, you can configure which to - 6. Click **Add** to connect the MCP server to your Agent Space + 6. Choose **Add** to connect the MCP server to your Agent Space @@ -237 +237 @@ AWS DevOps Agent will now be able to use the allowlisted tools from your MCP ser -**Updating authentication credentials** – If your authentication credentials need to be updated, you will need to re-register your MCP server. Navigate to the **Capability Providers** page in the AWS DevOps Agent console, locate your MCP server, remove any active associations, and click **Deregister**. Next, **register** your MCP server with the new authentication credentials and re-create any necessary associations with your Agent Space. +**Updating authentication credentials** – If your authentication credentials need to be updated, you will need to re-register your MCP server. Navigate to the **Capability Providers** page in the AWS DevOps Agent console, locate your MCP server, remove any active associations, and choose **Deregister**. Next, **register** your MCP server with the new authentication credentials and re-create any necessary associations with your Agent Space. @@ -241 +241 @@ AWS DevOps Agent will now be able to use the allowlisted tools from your MCP ser -**Removing MCP server connections** – To disconnect an MCP server from an Agent Space, select the server in the **MCP Servers** section and click **Remove**. To completely delete an MCP server registration, remove it from all Agent Spaces first, then delete the account-level registration. +**Removing MCP server connections** – To disconnect an MCP server from an Agent Space, select the server in the **MCP Servers** section and choose **Remove**. To completely delete an MCP server registration, remove it from all Agent Spaces first, then delete the account-level registration. @@ -309 +309 @@ Connecting GitLab -Connecting multiple AWS Accounts +Connecting Remote A2A Agents