periodic update 12 mar 2020

Author: ckesser

doc_source/AWS_CloudWatch.md

@@ -3,5 +3,6 @@
 **Resource Types**
 + [AWS::CloudWatch::Alarm](aws-properties-cw-alarm.md)
 + [AWS::CloudWatch::AnomalyDetector](aws-resource-cloudwatch-anomalydetector.md)
++ [AWS::CloudWatch::CompositeAlarm](aws-resource-cloudwatch-compositealarm.md)
 + [AWS::CloudWatch::Dashboard](aws-resource-cloudwatch-dashboard.md)
 + [AWS::CloudWatch::InsightRule](aws-resource-cloudwatch-insightrule.md)

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="w5653ab1b5b5"></a>
+## Simplify Infrastructure Management<a name="w5792ab1b5b5"></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="w5653ab1b5b7"></a>
+## Quickly Replicate Your Infrastructure<a name="w5792ab1b5b7"></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="w5653ab1b5b9"></a>
+## Easily Control and Track Changes to Your Infrastructure<a name="w5792ab1b5b9"></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="w5653ab1b5c13"></a>
+## Related Information<a name="w5792ab1b5c13"></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="w5653ab1c26c19b7b9"></a>
+## Syntax<a name="w5792ab1c25c19b7b9"></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="w5653ab1c26c19b7c13"></a>
+## Examples<a name="w5792ab1c25c19b7c13"></a>
 
-### Auto Scaling Group<a name="w5653ab1c26c19b7c13b2"></a>
+### Auto Scaling Group<a name="w5792ab1c25c19b7c13b2"></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="w5653ab1c26c19b7c13b4"></a>
+### WaitCondition<a name="w5792ab1c25c19b7c13b4"></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="w5653ab1c26c19c15c13"></a>
+## Syntax<a name="w5792ab1c25c19c15c13"></a>
 
 The `DependsOn` attribute can take a single string or list of strings\.
 
 ```
 "DependsOn" : [ String, ... ]
 ```
 
-## Example<a name="w5653ab1c26c19c15c15"></a>
+## Example<a name="w5792ab1c25c19c15c15"></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="w5653ab1c26c19c15c17c18"></a>
+### Amazon ECS Service and Auto Scaling Group<a name="w5792ab1c25c19c15c17c18"></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="w5653ab1c26c19c15c17c20"></a>
+### IAM Role Policy<a name="w5792ab1c25c19c15c17c20"></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="w5653ab1c26c19c19b9"></a>
+## Example<a name="w5792ab1c25c19c19b9"></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="w5653ab1c26c19c23c19b4"></a>
+### Add an UpdatePolicy to an Auto Scaling Group<a name="w5792ab1c25c19c23c19b4"></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="w5653ab1c26c19c23c19b6"></a>
+### AutoScalingReplacingUpdate Policy<a name="w5792ab1c25c19c23c19b6"></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="w5653ab1c26c19c23c19b8"></a>
+### Maintain Availability When Updating the Metadata for the cfn\-init Helper Script<a name="w5792ab1c25c19c23c19b8"></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="w5653ab1c26c19c23c19c10"></a>
+### Original Template<a name="w5792ab1c25c19c23c19c10"></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="w5653ab1c26c19c23c19c12"></a>
+### Updated Logical ID<a name="w5792ab1c25c19c23c19c12"></a>
 
 ```
 "LaunchConfigUpdateRubygemsPkg": {

doc_source/aws-attribute-updatepolicy.md

@@ -151,4 +151,4 @@ If you specified `HTTP` or `AWS` for the `Type` property, you must specify this
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
 
 ## See Also<a name="aws-properties-apitgateway-method-integration--seealso"></a>
-+ [Method](https://docs.aws.amazon.com/apigateway/api-reference/resource/method/) in the *Amazon API Gateway REST API Reference*
++ [Method](https://docs.aws.amazon.com/apigateway/api-reference/resource/method/) in the *Amazon API Gateway REST API Reference*

doc_source/aws-properties-apitgateway-method-integration.md

@@ -34,7 +34,7 @@ To declare this entity in your AWS CloudFormation template, use the following sy
 ## Properties<a name="aws-properties-applicationautoscaling-scalabletarget-scheduledaction-properties"></a>
 
 `EndTime`  <a name="cfn-applicationautoscaling-scalabletarget-scheduledaction-endtime"></a>
-The date and time that the action is scheduled to end\.  
+The date and time for the recurring schedule to end\.  
 *Required*: No  
 *Type*: Timestamp  
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
@@ -61,7 +61,7 @@ For more information about cron expressions, see [Cron Expressions](https://docs
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
 
 `ScheduledActionName`  <a name="cfn-applicationautoscaling-scalabletarget-scheduledaction-scheduledactionname"></a>
-The name of the scheduled action\.  
+The name of the scheduled action\. This name must be unique among all other scheduled actions on the specified scalable target\.  
 *Required*: Yes  
 *Type*: String  
 *Minimum*: `1`  
@@ -70,7 +70,7 @@ The name of the scheduled action\.
 *Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
 
 `StartTime`  <a name="cfn-applicationautoscaling-scalabletarget-scheduledaction-starttime"></a>
-The date and time that the action is scheduled to begin\.  
+The date and time that the action is scheduled to start\.  
 *Required*: No  
 *Type*: Timestamp  
 *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-scheduledaction.md

@@ -11,7 +11,8 @@ To declare this entity in your AWS CloudFormation template, use the following sy
 ```
 {
   "[HealthCheck](#cfn-appmesh-virtualnode-listener-healthcheck)" : [HealthCheck](aws-properties-appmesh-virtualnode-healthcheck.md),
-  "[PortMapping](#cfn-appmesh-virtualnode-listener-portmapping)" : [PortMapping](aws-properties-appmesh-virtualnode-portmapping.md)
+  "[PortMapping](#cfn-appmesh-virtualnode-listener-portmapping)" : [PortMapping](aws-properties-appmesh-virtualnode-portmapping.md),
+  "[TLS](#cfn-appmesh-virtualnode-listener-tls)" : [ListenerTls](aws-properties-appmesh-virtualnode-listenertls.md)
 }
 ```
 
@@ -22,6 +23,8 @@ To declare this entity in your AWS CloudFormation template, use the following sy
     [HealthCheck](aws-properties-appmesh-virtualnode-healthcheck.md)
   [PortMapping](#cfn-appmesh-virtualnode-listener-portmapping): 
     [PortMapping](aws-properties-appmesh-virtualnode-portmapping.md)
+  [TLS](#cfn-appmesh-virtualnode-listener-tls): 
+    [ListenerTls](aws-properties-appmesh-virtualnode-listenertls.md)
 ```
 
 ## Properties<a name="aws-properties-appmesh-virtualnode-listener-properties"></a>
@@ -36,4 +39,10 @@ The health check information for the listener\.
 The port mapping information for the listener\.  
 *Required*: Yes  
 *Type*: [PortMapping](aws-properties-appmesh-virtualnode-portmapping.md)  
+*Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
+
+`TLS`  <a name="cfn-appmesh-virtualnode-listener-tls"></a>
+A reference to an object that represents the Transport Layer Security \(TLS\) properties for a listener\.  
+*Required*: No  
+*Type*: [ListenerTls](aws-properties-appmesh-virtualnode-listenertls.md)  
 *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-appmesh-virtualnode-listener.md

@@ -10,6 +10,7 @@ To declare this entity in your AWS CloudFormation template, use the following sy
 
 ```
 {
+  "[BackendDefaults](#cfn-appmesh-virtualnode-virtualnodespec-backenddefaults)" : [BackendDefaults](aws-properties-appmesh-virtualnode-backenddefaults.md),
   "[Backends](#cfn-appmesh-virtualnode-virtualnodespec-backends)" : [ [Backend](aws-properties-appmesh-virtualnode-backend.md), ... ],
   "[Listeners](#cfn-appmesh-virtualnode-virtualnodespec-listeners)" : [ [Listener](aws-properties-appmesh-virtualnode-listener.md), ... ],
   "[Logging](#cfn-appmesh-virtualnode-virtualnodespec-logging)" : [Logging](aws-properties-appmesh-virtualnode-logging.md),
@@ -20,6 +21,8 @@ To declare this entity in your AWS CloudFormation template, use the following sy
 ### YAML<a name="aws-properties-appmesh-virtualnode-virtualnodespec-syntax.yaml"></a>
 
 ```
+  [BackendDefaults](#cfn-appmesh-virtualnode-virtualnodespec-backenddefaults): 
+    [BackendDefaults](aws-properties-appmesh-virtualnode-backenddefaults.md)
   [Backends](#cfn-appmesh-virtualnode-virtualnodespec-backends): 
     - [Backend](aws-properties-appmesh-virtualnode-backend.md)
   [Listeners](#cfn-appmesh-virtualnode-virtualnodespec-listeners): 
@@ -32,6 +35,12 @@ To declare this entity in your AWS CloudFormation template, use the following sy
 
 ## Properties<a name="aws-properties-appmesh-virtualnode-virtualnodespec-properties"></a>
 
+`BackendDefaults`  <a name="cfn-appmesh-virtualnode-virtualnodespec-backenddefaults"></a>
+A reference to an object that represents the defaults for backends\.  
+*Required*: No  
+*Type*: [BackendDefaults](aws-properties-appmesh-virtualnode-backenddefaults.md)  
+*Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
+
 `Backends`  <a name="cfn-appmesh-virtualnode-virtualnodespec-backends"></a>
 The backends that the virtual node is expected to send outbound traffic to\.  
 *Required*: No