Quotas and other considerations for continuous deployment

CloudFront continuous deployment is subject to the following quotas and other considerations.

Quotas

• Maximum number of staging distributions per AWS account: 20

• Maximum number of continuous deployment policies per AWS account: 20

• Maximum percentage of traffic you can send to a staging distribution in a weight-based configuration: 15%

• Minimum and maximum values for session stickiness idle duration: 300–3600 seconds

For more information, see Quotas.

Note

When using continuous deployment and your primary distribution is set with OAC for S3 bucket access, update your S3 bucket policy to allow access for the staging distribution. For example S3 bucket policies, see Give the origin access control permission to access the S3 bucket.

AWS WAF web ACLs

If you enable continuous distribution for your distribution, the following considerations apply for AWS WAF:

• You cannot associate an AWS WAF web access control list (ACL) to the distribution for the first time.

• You cannot disassociate an AWS WAF web ACL from the distribution.

Before you can do the preceding tasks, you must delete the continuous deployment policy for your production distribution. This also deletes the staging distribution. For more information, see Use AWS WAF protections.

Cases when CloudFront sends all requests to the primary distribution

In certain cases, such as periods of high resource utilization, CloudFront might send all requests to the primary distribution regardless of what's specified in the continuous deployment policy.

CloudFront sends all requests to the primary distribution during peak traffic hours, regardless of what's specified in the continuous deployment policy. Peak traffic refers to the traffic on the CloudFront service, and not the traffic on your distribution.

HTTP/3

You cannot use continuous deployment with a distribution that supports HTTP/3.