AWS devopsagent medium security documentation change
Summary
Changed DNS resolution requirement from VPC-resolvable to publicly resolvable for private connections
Security assessment
Requiring public DNS resolution for private services increases exposure risk by potentially revealing internal hostnames to public networks. This weakens network isolation principles and could facilitate reconnaissance attacks against private infrastructure.
Diff
diff --git a/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-to-privately-hosted-tools.md b/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-to-privately-hosted-tools.md index aaff3a4e3..8e8a5d305 100644 --- a//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-to-privately-hosted-tools.md +++ b//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-to-privately-hosted-tools.md @@ -125 +125 @@ Private connections are account-level resources. After you create a private conn - 11. For **Host address** , enter the IP address or DNS name of your target service (for example, `mcp.internal.example.com` or `10.0.1.50`). The service must be reachable from the selected VPC. If you choose a DNS name, it must be resolvable from the selected VPC. + 11. For **Host address** , enter the IP address or DNS name of your target service (for example, `mcp.internal.example.com` or `10.0.1.50`). The service must be reachable from the selected VPC. If you choose a DNS name, it must be publicly resolvable.