periodic update 29 apr 2020

Author: ckesser

doc_source/AWS_Transfer.md

@@ -1,4 +1,4 @@
-# AWS Transfer for SFTP Resource Type Reference<a name="AWS_Transfer"></a>
+# AWS Transfer Family Resource Type Reference<a name="AWS_Transfer"></a>
 
 **Resource Types**
 + [AWS::Transfer::Server](aws-resource-transfer-server.md)

doc_source/GettingStarted.Walkthrough.md

@@ -10,7 +10,7 @@ First, you'll need a template that specifies the resources that you want in your
 AWS CloudFormation is free, but the AWS resources that AWS CloudFormation creates are live \(and not running in a sandbox\)\. You will incur the standard usage fees for these resources until you terminate them in the last task in this tutorial\. The total charges will be minimal\. For information about how you might minimize any charges, go to [http://aws\.amazon\.com/free/](http://aws.amazon.com/free/)\.
 
 **To view the template**
-+ You can view the [JSON](https://s3-us-west-2.amazonaws.com/cloudformation-templates-us-west-2/WordPress_Single_Instance.template) or [YAML](https://s3-us-west-2.amazonaws.com/cloudformation-templates-us-west-2/WordPress_Single_Instance.yaml) WordPress sample template\. You don't need to download it because you will use the template URL later in this guide\. For more information about the template formats, see [AWS CloudFormation Template Formats](template-formats.md)\.
++ You can view the [JSON](https://s3.us-west-2.amazonaws.com/cloudformation-templates-us-west-2/WordPress_Single_Instance.template) or [YAML](https://s3.us-west-2.amazonaws.com/cloudformation-templates-us-west-2/WordPress_Single_Instance.yaml) WordPress sample template\. You don't need to download it because you will use the template URL later in this guide\. For more information about the template formats, see [AWS CloudFormation Template Formats](template-formats.md)\.
 
 A template is a JSON or YAML text file that contains the configuration information about the AWS resources you want to create in the stack\. For this walkthrough, the sample template includes six top\-level sections: `AWSTemplateFormatVersion`, `Description`, `Parameters`, `Mappings`, `Resources`, and `Outputs`; however, only the `Resources` section is required\.
 
@@ -290,7 +290,7 @@ You will create your stack based on the *WordPress\-1\.0\.0* file discussed earl
 
 1. In the **Template** section, select **Specify an Amazon S3 Template URL** to type or paste the URL for the sample WordPress template, and then click **Next**:
 
-   `https://s3-us-west-2.amazonaws.com/cloudformation-templates-us-west-2/WordPress_Single_Instance.template`
+   `https://s3.us-west-2.amazonaws.com/cloudformation-templates-us-west-2/WordPress_Single_Instance.template`
 **Note**  
 AWS CloudFormation templates that are stored in an S3 bucket must be accessible to the user who is creating the stack, and must be located in the *same region* as the stack that is being created\. Therefore, if the S3 bucket is located in the `us-east-2` Region, the stack must also be created in `us-east-2`\.
 

doc_source/ReleaseHistory.md

@@ -2,25 +2,25 @@
 
 AWS CloudFormation is a service that helps you model and set up your Amazon Web Services resources so that you can spend less time managing those resources and more time focusing on your applications that run in AWS\. You create a template that describes all the AWS resources that you want \(like Amazon EC2 instances or Amazon RDS DB instances\), and AWS CloudFormation takes care of provisioning and configuring those resources for you\. You don't need to individually create and configure AWS resources and figure out what's dependent on what; AWS CloudFormation handles all of that\. The following scenarios demonstrate how AWS CloudFormation can help\.
 
-## Simplify Infrastructure Management<a name="w5792ab1b5b5"></a>
+## Simplify Infrastructure Management<a name="w5979ab1b5b5"></a>
 
 For a scalable web application that also includes a back\-end database, you might use an Auto Scaling group, an Elastic Load Balancing load balancer, and an Amazon Relational Database Service database instance\. Normally, you might use each individual service to provision these resources\. And after you create the resources, you would have to configure them to work together\. All these tasks can add complexity and time before you even get your application up and running\.
 
 Instead, you can create or modify an existing AWS CloudFormation template\. A template describes all of your resources and their properties\. When you use that template to create an AWS CloudFormation stack, AWS CloudFormation provisions the Auto Scaling group, load balancer, and database for you\. After the stack has been successfully created, your AWS resources are up and running\. You can delete the stack just as easily, which deletes all the resources in the stack\. By using AWS CloudFormation, you easily manage a collection of resources as a single unit\.
 
-## Quickly Replicate Your Infrastructure<a name="w5792ab1b5b7"></a>
+## Quickly Replicate Your Infrastructure<a name="w5979ab1b5b7"></a>
 
 If your application requires additional availability, you might replicate it in multiple regions so that if one region becomes unavailable, your users can still use your application in other regions\. The challenge in replicating your application is that it also requires you to replicate your resources\. Not only do you need to record all the resources that your application requires, but you must also provision and configure those resources in each region\.
 
 When you use AWS CloudFormation, you can reuse your template to set up your resources consistently and repeatedly\. Just describe your resources once and then provision the same resources over and over in multiple regions\. 
 
-## Easily Control and Track Changes to Your Infrastructure<a name="w5792ab1b5b9"></a>
+## Easily Control and Track Changes to Your Infrastructure<a name="w5979ab1b5b9"></a>
 
 In some cases, you might have underlying resources that you want to upgrade incrementally\. For example, you might change to a higher performing instance type in your Auto Scaling launch configuration so that you can reduce the maximum number of instances in your Auto Scaling group\. If problems occur after you complete the update, you might need to roll back your infrastructure to the original settings\. To do this manually, you not only have to remember which resources were changed, you also have to know what the original settings were\.
 
 When you provision your infrastructure with AWS CloudFormation, the AWS CloudFormation template describes exactly what resources are provisioned and their settings\. Because these templates are text files, you simply track differences in your templates to track changes to your infrastructure, similar to the way developers control revisions to source code\. For example, you can use a version control system with your templates so that you know exactly what changes were made, who made them, and when\. If at any point you need to reverse changes to your infrastructure, you can use a previous version of your template\.
 
-## Related Information<a name="w5792ab1b5c13"></a>
+## Related Information<a name="w5979ab1b5c13"></a>
 + For more information about AWS CloudFormation stacks and templates, see [AWS CloudFormation Concepts](cfn-whatis-concepts.md)\.
 + For an overview about how to use AWS CloudFormation, see [How Does AWS CloudFormation Work?](cfn-whatis-howdoesitwork.md)\.
 + For pricing information, see [AWS CloudFormation Pricing](http://aws.amazon.com/cloudformation/pricing/)\.

doc_source/Welcome.md

@@ -6,7 +6,7 @@ The creation policy is invoked only when AWS CloudFormation creates the associat
 
 Use the `CreationPolicy` attribute when you want to wait on resource configuration actions before stack creation proceeds\. For example, if you install and configure software applications on an EC2 instance, you might want those applications to be running before proceeding\. In such cases, you can add a `CreationPolicy` attribute to the instance, and then send a success signal to the instance after the applications are installed and configured\. For a detailed example, see [Deploying Applications on Amazon EC2 with AWS CloudFormation](deploying.applications.md)\.
 
-## Syntax<a name="w5792ab1c25c19b7b9"></a>
+## Syntax<a name="w5979ab1c25c23b7b9"></a>
 
 ### JSON<a name="aws-attribute-creationpolicy-syntax.json"></a>
 
@@ -57,9 +57,9 @@ The value must be in [ISO8601 duration format](http://en.wikipedia.org/wiki/ISO_
 *Type*: String  
 *Required*: No
 
-## Examples<a name="w5792ab1c25c19b7c13"></a>
+## Examples<a name="w5979ab1c25c23b7c13"></a>
 
-### Auto Scaling Group<a name="w5792ab1c25c19b7c13b2"></a>
+### Auto Scaling Group<a name="w5979ab1c25c23b7c13b2"></a>
 
 The following example shows how to add a creation policy to an Auto Scaling group\. The creation policy requires three success signals and times out after 15 minutes\.
 
@@ -153,7 +153,7 @@ LaunchConfig:
           /opt/aws/bin/cfn-signal -e $? --stack ${AWS::StackName} --resource AutoScalingGroup --region ${AWS::Region}
 ```
 
-### WaitCondition<a name="w5792ab1c25c19b7c13b4"></a>
+### WaitCondition<a name="w5979ab1c25c23b7c13b4"></a>
 
 The following example shows how to add a creation policy to a wait condition\.
 

doc_source/aws-attribute-creationpolicy.md

@@ -15,15 +15,15 @@ You can use the `DependsOn` attribute with any resource\. Here are some typical
 **Note**  
 During a stack update, resources that depend on updated resources are updated automatically\. AWS CloudFormation makes no changes to the automatically\-updated resources, but, if a stack policy is associated with these resources, your account must have the permissions to update them\.
 
-## Syntax<a name="w5792ab1c25c19c15c13"></a>
+## Syntax<a name="w5979ab1c25c23c15c13"></a>
 
 The `DependsOn` attribute can take a single string or list of strings\.
 
 ```
 "DependsOn" : [ String, ... ]
 ```
 
-## Example<a name="w5792ab1c25c19c15c15"></a>
+## Example<a name="w5979ab1c25c23c15c15"></a>
 
 The following template contains an [AWS::EC2::Instance](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html) resource with a `DependsOn` attribute that specifies myDB, an [AWS::RDS::DBInstance](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-rds-database-instance.html)\. When AWS CloudFormation creates this stack, it first creates myDB, then creates Ec2Instance\.
 
@@ -234,7 +234,7 @@ EC2Host:
         Ref: PublicSubnet
 ```
 
-### Amazon ECS Service and Auto Scaling Group<a name="w5792ab1c25c19c15c17c18"></a>
+### Amazon ECS Service and Auto Scaling Group<a name="w5979ab1c25c23c15c17c18"></a>
 
 When you use Auto Scaling or Amazon Elastic Compute Cloud \(Amazon EC2\) to create container instances for an Amazon ECS cluster, the Amazon ECS service resource must have a dependency on the Auto Scaling group or Amazon EC2 instances, as shown in the following snippet\. That way the container instances are available and associated with the Amazon ECS cluster before AWS CloudFormation creates the Amazon ECS service\.
 
@@ -292,7 +292,7 @@ service:
       Ref: taskdefinition
 ```
 
-### IAM Role Policy<a name="w5792ab1c25c19c15c17c20"></a>
+### IAM Role Policy<a name="w5979ab1c25c23c15c17c20"></a>
 
 Resources that make additional calls to AWS require a service role, which permits a service to make calls to AWS on your behalf\. For example, the `AWS::CodeDeploy::DeploymentGroup` resource requires a service role so that CodeDeploy has permissions to deploy applications to your instances\. When you have a single template that defines a service role, the role's policy \(by using the `AWS::IAM::Policy` or `AWS::IAM::ManagedPolicy` resource\), and a resource that uses the role, add a dependency so that the resource depends on the role's policy\. This dependency ensures that the policy is available throughout the resource's lifecycle\.
 

doc_source/aws-attribute-dependson.md

@@ -7,7 +7,7 @@ AWS CloudFormation does not validate the syntax within the Metadata attribute\.
 
 You can retrieve this data using the AWS command [https://docs.aws.amazon.com/cli/latest/reference/cloudformation/describe-stack-resource.html](https://docs.aws.amazon.com/cli/latest/reference/cloudformation/describe-stack-resource.html) or the [DescribeStackResource action](http://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DescribeStackResource.html)\.
 
-## Example<a name="w5792ab1c25c19c19b9"></a>
+## Example<a name="w5979ab1c25c23c19b9"></a>
 
 The following template contains an Amazon S3 bucket resource with a Metadata attribute\.
 

doc_source/aws-attribute-metadata.md

@@ -301,7 +301,7 @@ For an example that specifies the `UpdatePolicy` attribute for an `AWS::Lambda::
 
 The following examples show how to add an update policy to an Auto Scaling group and how to maintain availability when updating metadata\.
 
-### Add an UpdatePolicy to an Auto Scaling Group<a name="w5792ab1c25c19c23c19b4"></a>
+### Add an UpdatePolicy to an Auto Scaling Group<a name="w5979ab1c25c23c23c19b4"></a>
 
 The following example shows how to add an update policy\. During an update, the Auto Scaling group updates instances in batches of two and keeps a minimum of one instance in service\. Because the `WaitOnResourceSignals` flag is set, the Auto Scaling group waits for new instances that are added to the group\. The new instances must signal the Auto Scaling group before it updates the next batch of instances\.
 
@@ -377,7 +377,7 @@ ScheduledAction:
     StartTime: '2017-06-02T20 : 00 : 00Z'
 ```
 
-### AutoScalingReplacingUpdate Policy<a name="w5792ab1c25c19c23c19b6"></a>
+### AutoScalingReplacingUpdate Policy<a name="w5979ab1c25c23c23c19b6"></a>
 
 The following example declares a policy that forces an associated Auto Scaling group to be replaced during an update\. For the update to succeed, a percentage of instances \(specified by the `MinSuccessfulPercentParameter` parameter\) must signal success within the `Timeout` period\.
 
@@ -414,7 +414,7 @@ CreationPolicy:
     MinSuccessfulInstancesPercent: !Ref 'MinSuccessfulPercentParameter'
 ```
 
-### Maintain Availability When Updating the Metadata for the cfn\-init Helper Script<a name="w5792ab1c25c19c23c19b8"></a>
+### Maintain Availability When Updating the Metadata for the cfn\-init Helper Script<a name="w5979ab1c25c23c23c19b8"></a>
 
 When you install software applications on your instances, you might use the [https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-init.html](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-init.html) metadata key and the [https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-init.html](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-init.html) helper script to bootstrap the instances in your Auto Scaling group\. AWS CloudFormation installs the packages, runs the commands, and performs other bootstrapping actions described in the metadata\.
 
@@ -425,7 +425,7 @@ Forcing a rolling update requires AWS CloudFormation to create a new instance an
 
 To force a rolling update, change the logical ID of the launch configuration resource, and then update the stack and any references pointing to the original logic ID \(such as the associated Auto Scaling group\)\. AWS CloudFormation triggers a rolling update on the Auto Scaling group, replacing all instances\.
 
-### Original Template<a name="w5792ab1c25c19c23c19c10"></a>
+### Original Template<a name="w5979ab1c25c23c23c19c10"></a>
 
 ```
 "LaunchConfig": {
@@ -439,7 +439,7 @@ To force a rolling update, change the logical ID of the launch configuration res
 }
 ```
 
-### Updated Logical ID<a name="w5792ab1c25c19c23c19c12"></a>
+### Updated Logical ID<a name="w5979ab1c25c23c23c19c12"></a>
 
 ```
 "LaunchConfigUpdateRubygemsPkg": {

doc_source/aws-attribute-updatepolicy.md

@@ -2,6 +2,8 @@
 
 Contains configuration information for a certificate revocation list \(CRL\)\. Your private certificate authority \(CA\) creates base CRLs\. Delta CRLs are not supported\. You can enable CRLs for your new or an existing private CA by setting the **Enabled** parameter to `true`\. Your private CA writes CRLs to an S3 bucket that you specify in the **S3BucketName** parameter\. You can hide the name of your bucket by specifying a value for the **CustomCname** parameter\. Your private CA copies the CNAME or the S3 bucket name to the **CRL Distribution Points** extension of each certificate it issues\. Your S3 bucket policy must give write permission to ACM Private CA\. 
 
+ACM Private CA assets that are stored in Amazon S3 can be protected with encryption\. For more information, see [Encrypting Your CRLs](https://docs.aws.amazon.com/acm-pca/latest/userguide/PcaCreateCa.html#crl-encryption)\.
+
 Your private CA uses the value in the **ExpirationInDays** parameter to calculate the **nextUpdate** field in the CRL\. The CRL is refreshed at 1/2 the age of next update or when a certificate is revoked\. When a certificate is revoked, it is recorded in the next CRL that is generated and in the next audit report\. Only time valid certificates are listed in the CRL\. Expired certificates are not included\. 
 
 CRLs contain the following fields:

doc_source/aws-properties-acmpca-certificateauthority-crlconfiguration.md

@@ -26,7 +26,7 @@ To declare this entity in your AWS CloudFormation template, use the following sy
 ## Properties<a name="aws-properties-apigatewayv2-authorizer-jwtconfiguration-properties"></a>
 
 `Audience`  <a name="cfn-apigatewayv2-authorizer-jwtconfiguration-audience"></a>
-A list of the intended recipients of the JWT\. A valid JWT must provide an `aud` that matches at least one entry in this list\. See [RFC 7519](https://tools.ietf.org/html/rfc7519#section-4.1.3)\. Supported only for HTTP APIs\.  
+A list of the intended recipients of the JWT\. A valid JWT must provide an `aud` that matches at least one entry in this list\. See [RFC 7519](https://tools.ietf.org/html/rfc7519#section-4.1.3)\. Required for the `JWT` authorizer type\. Supported only for HTTP APIs\.  
 *Required*: No  
 *Type*: List of String  
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)

doc_source/aws-properties-apigatewayv2-authorizer-jwtconfiguration.md

@@ -49,13 +49,13 @@ Specifies the logging level for this route: `INFO`, `ERROR`, or `OFF`\. This pro
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
 
 `ThrottlingBurstLimit`  <a name="cfn-apigatewayv2-stage-routesettings-throttlingburstlimit"></a>
-Specifies the throttling burst limit\. Supported only for WebSocket APIs\.  
+Specifies the throttling burst limit\.  
 *Required*: No  
 *Type*: Integer  
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
 
 `ThrottlingRateLimit`  <a name="cfn-apigatewayv2-stage-routesettings-throttlingratelimit"></a>
-Specifies the throttling rate limit\. Supported only for WebSocket APIs\.  
+Specifies the throttling rate limit\.  
 *Required*: No  
 *Type*: Double  
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)

doc_source/aws-properties-apigatewayv2-stage-routesettings.md

@@ -32,6 +32,7 @@ The maximum capacity\.
 
 `MinCapacity`  <a name="cfn-applicationautoscaling-scalabletarget-scalabletargetaction-mincapacity"></a>
 The minimum capacity\.  
+For Lambda provisioned concurrency, the minimum value allowed is 0\. For all other resources, the minimum value allowed is 1\.  
 *Required*: No  
 *Type*: Integer  
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)

doc_source/aws-properties-applicationautoscaling-scalabletarget-scalabletargetaction.md

@@ -50,7 +50,7 @@ The schedule for this action\. The following formats are supported:
 + At expressions \- "`at(yyyy-mm-ddThh:mm:ss)`"
 + Rate expressions \- "`rate(value unit)`"
 + Cron expressions \- "`cron(fields)`"
-At expressions are useful for one\-time schedules\. Specify the time, in UTC\.  
+At expressions are useful for one\-time schedules\. Specify the time in UTC\.  
 For rate expressions, *value* is a positive integer and *unit* is `minute` \| `minutes` \| `hour` \| `hours` \| `day` \| `days`\.  
 For more information about cron expressions, see [Cron Expressions](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions) in the *Amazon CloudWatch Events User Guide*\.  
 *Required*: Yes