AWS Security ChangesHomeSearch

AWS AmazonECS documentation change

Service: AmazonECS · 2025-06-19 · Documentation low

File: AmazonECS/latest/developerguide/vpc-endpoints.md

Summary

Updated documentation to consistently use 'Amazon ECS' instead of 'ECS' and clarify agent behavior with VPC endpoints

Security assessment

Changes are branding/terminology updates and clarification about endpoint resolution behavior. No security vulnerabilities or security features are mentioned.

Diff

diff --git a/AmazonECS/latest/developerguide/vpc-endpoints.md b/AmazonECS/latest/developerguide/vpc-endpoints.md
index a38a91bb4..8db4744a4 100644
--- a//AmazonECS/latest/developerguide/vpc-endpoints.md
+++ b//AmazonECS/latest/developerguide/vpc-endpoints.md
@@ -111 +111 @@ When you create endpoints, Amazon ECS also creates a private DNS name for the en
-### Understanding ECS endpoint naming patterns
+### Understanding Amazon ECS endpoint naming patterns
@@ -113 +113 @@ When you create endpoints, Amazon ECS also creates a private DNS name for the en
-It's important to understand that the ECS agent may make requests to endpoints with numbered suffixes, such as:
+It's important to understand that the Amazon ECS agent may make requests to endpoints with numbered suffixes, such as:
@@ -122 +122 @@ It's important to understand that the ECS agent may make requests to endpoints w
-This behavior occurs because the ECS agent uses the [DiscoverPollEndpoint](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DiscoverPollEndpoint.html) API to dynamically determine which specific endpoint to connect to. If your VPC endpoints don't properly handle these numbered endpoint variations, the agent will fall back to using public endpoints, even if you've configured VPC endpoints for the base names.
+This behavior occurs because the Amazon ECS agent uses the [DiscoverPollEndpoint](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DiscoverPollEndpoint.html) API to dynamically determine which specific endpoint to connect to. If your VPC endpoints don't properly handle these numbered endpoint variations, the agent will fall back to using public endpoints, even if you've configured VPC endpoints for the base names.
@@ -126 +126 @@ This behavior occurs because the ECS agent uses the [DiscoverPollEndpoint](https
-The [DiscoverPollEndpoint](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DiscoverPollEndpoint.html) API is used by the ECS agent to discover the appropriate endpoint to poll for tasks. When the agent calls this API, it receives a specific endpoint URL that may include a numbered suffix. To ensure your VPC endpoints work correctly, your network configuration must allow the agent to:
+The [DiscoverPollEndpoint](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DiscoverPollEndpoint.html) API is used by the Amazon ECS agent to discover the appropriate endpoint to poll for tasks. When the agent calls this API, it receives a specific endpoint URL that may include a numbered suffix. To ensure your VPC endpoints work correctly, your network configuration must allow the agent to: