AWS devopsagent documentation change
Summary
Removed requirement for MCP servers to be publicly accessible, added note about connecting to privately hosted tools, and updated console navigation for credential management.
Security assessment
Change introduces support for private network MCP servers, which enhances security by reducing exposure to public internet. The added note about private tools and updated credential management instructions provide security-related guidance for secure configurations.
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 6454fd692..5ef1ab114 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 @@ -15,2 +14,0 @@ Before connecting an MCP server, ensure your server meets these requirements: - * **Publicly accessible endpoint** – MCP servers must be accessible from the public internet over HTTPS. AWS DevOps Agent does not support connecting to servers hosted in VPCs. - @@ -43,0 +42,4 @@ See [AWS DevOps Agent Security](./aws-devops-agent-security.html) for more infor +###### Note + +If your MCP server is on a private network, see [Connecting to privately hosted tools](./configuring-capabilities-for-aws-devops-agent-connecting-to-privately-hosted-tools.html) + @@ -201 +203 @@ 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 **Settings** page 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 click **Deregister**. Next, **register** your MCP server with the new authentication credentials and re-create any necessary associations with your Agent Space.