AWS whitepapers documentation change
Summary
Fixed URL formatting for AWS Fargate and EC2 links by adding double slashes
Security assessment
Change only corrects URL path syntax without altering security-related content or introducing security context
Diff
diff --git a/whitepapers/latest/containers-on-aws/containers-services-on-aws.md b/whitepapers/latest/containers-on-aws/containers-services-on-aws.md index cbca1b5a5..1cecf8ef7 100644 --- a//whitepapers/latest/containers-on-aws/containers-services-on-aws.md +++ b//whitepapers/latest/containers-on-aws/containers-services-on-aws.md @@ -13 +13 @@ AWS is an elastic, secure, flexible, and developer-centric cloud provider, which - * [**Amazon Elastic Container Service**](https://aws.amazon.com/ecs/) (Amazon ECS) is a fully managed container orchestration service which provides a convenient way to rapidly launch thousands of containers across a broad range of AWS compute options. You can use your preferred CI/CD and automation tools with Amazon ECS. There is no complexity of managing a control plane, add-ons, and nodes with Amazon ECS. Amazon ECS offers two launch types – [Amazon EC2](https://aws.amazon.com/pm/ec2) and [AWS Fargate](https://aws.amazon.com/fargate) (discussed later). With the Amazon EC2 launch type, Amazon ECS provides an easy lift for your applications that run on VMs. Your Amazon ECS clusters have container instances, which are Amazon EC2 instances running an Amazon ECS container agent. The agent communicates instance and container state information to the cluster manager. The Amazon ECS container agent is included in the Amazon ECS-optimized AMI, but you can also install it on any Amazon EC2 instance that supports the Amazon ECS specification. Your containers are defined in an [Amazon ECS task definition](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) that you use to run individual tasks or tasks within an [Amazon ECS service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html). An Amazon ECS service enables you to run and maintain a specified number of tasks simultaneously in a cluster. The task definition can be thought of as a blueprint for your application that you can specify parameters such as the container image to use, which ports to open, the amount of CPU and memory to use with each task or containers within a task, and the IAM role the task should use. + * [**Amazon Elastic Container Service**](https://aws.amazon.com/ecs/) (Amazon ECS) is a fully managed container orchestration service which provides a convenient way to rapidly launch thousands of containers across a broad range of AWS compute options. You can use your preferred CI/CD and automation tools with Amazon ECS. There is no complexity of managing a control plane, add-ons, and nodes with Amazon ECS. Amazon ECS offers two launch types – [Amazon EC2](https://aws.amazon.com//pm/ec2) and [AWS Fargate](https://aws.amazon.com//fargate) (discussed later). With the Amazon EC2 launch type, Amazon ECS provides an easy lift for your applications that run on VMs. Your Amazon ECS clusters have container instances, which are Amazon EC2 instances running an Amazon ECS container agent. The agent communicates instance and container state information to the cluster manager. The Amazon ECS container agent is included in the Amazon ECS-optimized AMI, but you can also install it on any Amazon EC2 instance that supports the Amazon ECS specification. Your containers are defined in an [Amazon ECS task definition](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) that you use to run individual tasks or tasks within an [Amazon ECS service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html). An Amazon ECS service enables you to run and maintain a specified number of tasks simultaneously in a cluster. The task definition can be thought of as a blueprint for your application that you can specify parameters such as the container image to use, which ports to open, the amount of CPU and memory to use with each task or containers within a task, and the IAM role the task should use.