AWS Security ChangesHomeSearch

AWS AmazonECS documentation change

Service: AmazonECS · 2026-06-28 · Documentation low

File: AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate_windows.md

Summary

Made two wording changes: 'above' to 'preceding' and 'below' to 'in the following sections' for improved clarity.

Security assessment

These are non-substantive editorial improvements. The internet routing options (NAT gateway vs public IP) remain unchanged with no security implications addressed or added.

Diff

diff --git a/AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate_windows.md b/AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate_windows.md
index a5de6fc69..1d8f01f67 100644
--- a//AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate_windows.md
+++ b//AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate_windows.md
@@ -128 +128 @@ Before you can run a Windows task on your Amazon ECS cluster, you must register
-The above example JSON can be passed to the AWS CLI in two ways: You can save the task definition JSON as a file and pass it with the ``\--cli-input-json` file://`path_to_file.json`` option.
+The preceding example JSON can be passed to the AWS CLI in two ways: You can save the task definition JSON as a file and pass it with the ``\--cli-input-json` file://`path_to_file.json`` option.
@@ -155 +155 @@ Output:
-After you have registered a task for your account, you can create a service for the registered task in your cluster. For this example, you create a service with one instance of the `sample-fargate:1` task definition running in your cluster. The task requires a route to the internet, so there are two ways you can achieve this. One way is to use a private subnet configured with a NAT gateway with an elastic IP address in a public subnet. Another way is to use a public subnet and assign a public IP address to your task. We provide both examples below. 
+After you have registered a task for your account, you can create a service for the registered task in your cluster. For this example, you create a service with one instance of the `sample-fargate:1` task definition running in your cluster. The task requires a route to the internet, so there are two ways you can achieve this. One way is to use a private subnet configured with a NAT gateway with an elastic IP address in a public subnet. Another way is to use a public subnet and assign a public IP address to your task. We provide both examples in the following sections.