As per https://docs.aws.amazon.com/acm/latest/userguide/acm-regions.html, ACM has a restriction that requires certificates to be created in the us-east-1 region in order to be used with CloudFront:

To use an ACM Certificate with Amazon CloudFront, you must request or import the certificate in the US East (N. Virginia) region. ACM Certificates in this region that are associated with a CloudFr

Manual Deployment documentation refers to cloudfront-http-redirect AWS Lambda blueprint, that is available in N.Virginia region, but not in the others.However, in other regions serverless app with the very same name is available which is confusing.

The documentation should clearly state that lambda should be deployed in N.Virg

This was discussed briefly in #47. Currently in our "with CloudFront" recipe and in my blog post we recommend invalidating the CloudFront cache after the deployment.

The mechanism suggest

According to S3 CORS configuration Amazon documentation there is a bug in configuration of allowed origins.

Example from documentation shows that each CORS rule need to consist only one AllowedOrigin parameter:

<CORSConfiguration>
 <CORSRule>
   <AllowedOrigin>http://www.example1.com</AllowedOrigin>

   <AllowedMethod>PUT</A

With CloudFormation sort of becoming legacy at this point, it would make sense to split the documentation and move it into the respective sub-directories.

This would allow for a more independent development of the Terraform module. Plus, less clutter, which is always good.

from help:

…
        --connections-critical-over N
                                     Trigger a critical if connections usage is over a percentage
        --connections-warning-over N Trigger a warning if connections usage is over a percentage

parameters passed --connections-warning-over 70 --connections-critical-over 85
check output: `CheckRDS CRITICAL: RDSNAME: ; DatabaseCon

The README documents the follow behaviour for the enabled input variable:

However when actually using this variable, all resources for this module are still created. On inspection of the [main.tf file](https://github.com/cloudpo

To help with installation in strict environments, we'd like to create a 5th template that only installs resources for IAM. This template would contain all of the policies and roles needed by resources created in other templates, such as Lambda. IAM resources in other templates will come out.

A template for IAM resources will allow an organization with IT duties separated across groups to instal