Periodic update, July 2019

doc_source/AWS_Fargate.md

@@ -24,6 +24,8 @@ AWS Fargate with Amazon ECS is currently only available in the following Regions
 | Asia Pacific \(Seoul\) | ap\-northeast\-2 | 
 | Asia Pacific \(Singapore\) | ap\-southeast\-1 | 
 | Asia Pacific \(Sydney\) | ap\-southeast\-2 | 
+| AWS GovCloud \(US\-East\) | us\-gov\-east\-1 | 
+| AWS GovCloud \(US\) | us\-gov\-west\-1 | 
 
 The following walkthroughs help you get started using AWS Fargate with Amazon ECS:
 + [Getting Started with Amazon ECS](ECS_GetStarted.md)

doc_source/ECS_AWSCLI_EC2.md

@@ -19,7 +19,7 @@ The following steps help you set up a cluster, register a task definition, run a
 This tutorial assumes that the following prerequisites have been completed:
 + The latest version of the AWS CLI is installed and configured\. For more information about installing or upgrading your AWS CLI, see [Installing the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/installing.html)\.
 + The steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) have been completed\.
-+ Your AWS user has the required permissions specified in the [Amazon ECS First Run Wizard](IAMPolicyExamples.md#first-run-permissions) IAM policy example\.
++ Your AWS user has the required permissions specified in the [Amazon ECS First Run Wizard Permissions](security_iam_id-based-policy-examples.md#first-run-permissions) IAM policy example\.
 + You have a VPC and security group created to use\. For more information, see [Tutorial: Creating a VPC with Public and Private Subnets for Your Clusters](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-public-private-vpc.html)\.
 
 ## Step 1: \(Optional\) Create a Cluster<a name="AWSCLI_EC2_create_cluster"></a>

doc_source/ECS_AWSCLI_Fargate.md

@@ -16,7 +16,7 @@ The following steps help you set up a cluster, register a task definition, run a
 This tutorial assumes that the following prerequisites have been completed:
 + The latest version of the AWS CLI is installed and configured\. For more information about installing or upgrading your AWS CLI, see [Installing the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/installing.html)\.
 + The steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) have been completed\.
-+ Your AWS user has the required permissions specified in the [Amazon ECS First Run Wizard](IAMPolicyExamples.md#first-run-permissions) IAM policy example\.
++ Your AWS user has the required permissions specified in the [Amazon ECS First Run Wizard Permissions](security_iam_id-based-policy-examples.md#first-run-permissions) IAM policy example\.
 + You have a VPC and security group created to use\. For more information, see [Tutorial: Creating a VPC with Public and Private Subnets for Your Clusters](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-public-private-vpc.html)\.
 
 ## Step 1: \(Optional\) Create a Cluster<a name="AWSCLI_create_cluster"></a>

doc_source/ECS_GetStarted_EC2.md

@@ -22,7 +22,7 @@ Complete the following tasks to get started with Amazon ECS:
 
 ## Prerequisites<a name="first-run-ec2-prereqs"></a>
 
-Before you begin, be sure that you've completed the steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) and that your AWS user has either the permissions specified in the `AdministratorAccess` or [Amazon ECS First Run Wizard](IAMPolicyExamples.md#first-run-permissions) IAM policy example\.
+Before you begin, be sure that you've completed the steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) and that your AWS user has either the permissions specified in the `AdministratorAccess` or [Amazon ECS First Run Wizard Permissions](security_iam_id-based-policy-examples.md#first-run-permissions) IAM policy example\.
 
 The first\-run wizard attempts to automatically create the Amazon ECS service IAM and container instance IAM role\. To ensure that the first\-run experience is able to create these IAM roles, one of the following must be true:
 + Your user has administrator access\. For more information, see [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md)\.

doc_source/ECS_GetStarted_Fargate.md

@@ -19,7 +19,7 @@ Complete the following tasks to get started with Amazon ECS using Fargate:
 
 ## Prerequisites<a name="first-run-prereqs"></a>
 
-Before you begin, be sure that you've completed the steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) and that your AWS user has either the permissions specified in the `AdministratorAccess` or [Amazon ECS First Run Wizard](IAMPolicyExamples.md#first-run-permissions) IAM policy example\.
+Before you begin, be sure that you've completed the steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) and that your AWS user has either the permissions specified in the `AdministratorAccess` or [Amazon ECS First Run Wizard Permissions](security_iam_id-based-policy-examples.md#first-run-permissions) IAM policy example\.
 
 The first\-run wizard attempts to automatically create the task execution IAM role, which is required for Fargate tasks\. To ensure that the first\-run experience is able to create this IAM role, one of the following must be true:
 + Your user has administrator access\. For more information, see [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md)\.

doc_source/ECS_clusters.md

@@ -6,7 +6,7 @@ The following are general concepts about Amazon ECS clusters\.
 + Clusters are Region\-specific\.
 + Clusters can contain tasks using both the Fargate and EC2 launch types\. For more information about launch types, see [Amazon ECS Launch Types](launch_types.md)\. 
 + For tasks using the EC2 launch type, clusters can contain multiple different container instance types, but each container instance may only be part of one cluster at a time\.
-+ You can create custom IAM policies for your clusters to allow or restrict user access to specific clusters\. For more information, see the [Clusters](IAMPolicyExamples.md#IAM_cluster_policies) section in [Amazon ECS IAM Policy Examples](IAMPolicyExamples.md)\.
++ You can create custom IAM policies for your clusters to allow or restrict user access to specific clusters\. For more information, see the [Cluster Examples](security_iam_id-based-policy-examples.md#IAM_cluster_policies) section in [Amazon Elastic Container Service Identity\-Based Policy Examples](security_iam_id-based-policy-examples.md)\.
 
 **Topics**
 + [Creating a Cluster](create_cluster.md)

doc_source/Welcome.md

@@ -87,7 +87,7 @@ Alternatively, you can install the AWS Command Line Interface \(AWS CLI\) to use
 Amazon ECS can be used along with the following AWS services:
 
 **AWS Identity and Access Management**  
-IAM is a web service that helps you securely control access to AWS resources for your users\. Use IAM to control who can use your AWS resources \(authentication\) and what resources they can use in which ways \(authorization\)\. In Amazon ECS, IAM can be used to control access at the container instance level using IAM roles, and at the task level using IAM task roles\. For more information, see [Amazon ECS IAM Policies, Roles, and Permissions](IAM_policies.md)\.
+IAM is a web service that helps you securely control access to AWS resources for your users\. Use IAM to control who can use your AWS resources \(authentication\) and what resources they can use in which ways \(authorization\)\. In Amazon ECS, IAM can be used to control access at the container instance level using IAM roles, and at the task level using IAM task roles\. For more information, see [Identity and Access Management for Amazon Elastic Container Service](security-iam.md)\.
 
 **Amazon EC2 Auto Scaling**  
 Auto Scaling is a web service that enables you to automatically scale out or in your tasks based on user\-defined policies, health status checks, and schedules\. You can use Auto Scaling with a Fargate task within a service to scale in response to a number of metrics or with an EC2 task to scale the container instances within your cluster\. For more information, see [Service Auto Scaling](service-auto-scaling.md)\.

doc_source/cmd-ecs-cli-up.md

@@ -27,7 +27,7 @@ Some features described might only be available with the latest version of the A
 |  `--vpc vpc_id`  |  Specifies the ID of an existing VPC in which to launch your container instances\. If you specify a VPC ID, you must specify a list of existing subnets in that VPC with the `--subnets` option\. If you do not specify a VPC ID, a new VPC is created with two subnets\. Type: String Required: No  | 
 | \-\-extra\-user\-data string |  Specifies additional user data for your container instance\. Files can be shell scripts or cloud\-init directives\. They are packaged into a MIME multipart archive along with user data provided by the Amazon ECS CLI that directs instances to join your cluster\. For more information, see [Specifying User Data](#cmd-ecs-cli-up-userdata)\. Type: String Required: No  | 
 |  `--instance-type instance_type`  |  Specifies the Amazon EC2 instance type for your container instances\. If you specify an A1 instance type, for example `a1.medium`, and omit the `--image-id` parameter, the ECS CLI uses the the Amazon ECS\-optimized Amazon Linux 2 \(arm64\) AMI AMI ID for the container instance\.  This parameter is supported only with tasks that use the EC2 launch type\.  For more information on EC2 instance types, see [Amazon EC2 Instances](https://aws.amazon.com/ec2/instance-types/)\. Type: String Default: `t2.micro` Required: No  | 
-|  `--image-id ami_id`  |  Specifies the Amazon EC2 AMI ID to use for your container instances\. If you don't specify an AMI ID, the Amazon ECS CLI automatically retrieves the latest stable Amazon ECS\-optimized Amazon Linux 2 AMI by querying the SSM Parameter Store API during the cluster resource creation process\. This requires the user account that you're using to have the required SSM permissions\. For more information, see [Retrieving Amazon ECS\-Optimized AMI Metadata](retrieve-ecs-optimized_AMI.md)\. If you specify an A1 instance type for the `--instance-type` parameter and omit the `--image-id` parameter, the ECS CLI uses the the Amazon ECS\-optimized Amazon Linux 2 \(arm64\) AMI AMI ID for the container instance\.  This parameter is supported only with tasks that use the EC2 launch type\.  Type: String Default: The latest stable Amazon ECS–optimized AMI for the specified Region\. Required: No  | 
+|  `--image-id ami_id`  |  Specifies the Amazon EC2 AMI ID to use for your container instances\. If you don't specify an AMI ID, the Amazon ECS CLI automatically retrieves the latest stable Amazon ECS\-optimized Amazon Linux 2 AMI by querying the Systems Manager Parameter Store API during the cluster resource creation process\. This requires the user account that you're using to have the required Systems Manager permissions\. For more information, see [Retrieving Amazon ECS\-Optimized AMI Metadata](retrieve-ecs-optimized_AMI.md)\. If you specify an A1 instance type for the `--instance-type` parameter and omit the `--image-id` parameter, the ECS CLI uses the the Amazon ECS\-optimized Amazon Linux 2 \(arm64\) AMI AMI ID for the container instance\.  This parameter is supported only with tasks that use the EC2 launch type\.  Type: String Default: The latest stable Amazon ECS–optimized AMI for the specified Region\. Required: No  | 
 |  `--no-associate-public-ip-address`  |  Do not assign public IP addresses to new instances in this VPC\. Unless this option is specified, new instances in this VPC receive an automatically assigned public IP address\.  This parameter is only supported with tasks that use the EC2 launch type\.  Required: No  | 
 |  `--force, -f`  |  Forces the recreation of any existing resources that match your current configuration\. This option is useful for cleaning up stale resources from previous failed attempts\. Required: No  | 
 |  `--tags key1=value1,key2=value2`  |  Specifies the metadata to apply to your AWS resources\. Each tag consists of a key and an optional value\. Tags use the following format: `key1=value1,key2=value2,key3=value3`\. For more information, see [Tagging Resources](#cmd-ecs-cli-up-tags)\. Type: Key value pairs Required: No  | 

doc_source/create-blue-green.md

@@ -19,7 +19,7 @@ The following tutorial shows how to create an Amazon ECS service containing a Fa
 This tutorial assumes that you have completed the following prerequisites:
 + The latest version of the AWS CLI is installed and configured\. For more information about installing or upgrading the AWS CLI, see [Installing the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/installing.html)\.
 + The steps in [Setting Up with Amazon ECS](get-set-up-for-amazon-ecs.md) have been completed\.
-+ Your AWS user has the required permissions specified in the [Amazon ECS First Run Wizard](IAMPolicyExamples.md#first-run-permissions) IAM policy example\.
++ Your AWS user has the required permissions specified in the [Amazon ECS First Run Wizard Permissions](security_iam_id-based-policy-examples.md#first-run-permissions) IAM policy example\.
 + You have a VPC and security group created to use\. For more information, see [Tutorial: Creating a VPC with Public and Private Subnets for Your Clusters](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-public-private-vpc.html)\.
 
 ## Step 1: Create an Application Load Balancer<a name="create-blue-green-loadbalancer"></a>