Create it
- Console
- CLI and API
- Coding agent
- Open the environment, then New service › Blueprint.
- Find AWS CloudFront in the catalog and pick the major version.
- Fill in the variables. Required ones are marked; the others use their defaults.
- Create the service, and deploy it now or later.
Variables and outputs
Generated fromqbm.yml at AWS/cloudfront/default/1.0.7, the manifest the Console form is built from.
All 17 variables
All 17 variables
All 7 outputs
All 7 outputs
Reference
From the Blueprint’s README. Creates an AWS CloudFront distribution in front of a single HTTP/S origin (an ALB, application host, or S3 website endpoint) with configurable caching, price class, optional custom domains, and geo restrictions. By default the distribution serves over the CloudFront-managed*.cloudfront.net certificate; set aliases + acm_certificate_arn (certificate must be in us-east-1) to serve custom domains.
Credentials
Uses the Qovery cluster’s AWS credentials (credentials.default: cluster). The credentials must allow the CloudFront and (when using ACM) certificate actions listed under Required IAM permissions.
Variables
Required
Distribution
Origin
Caching / viewer
Custom domain & geo
Outputs
Notes
- Caching uses the self-contained
forwarded_valuesconfig (query string forwarded, cookies not), so the blueprint doesn’t depend on a managed cache policy id. The AWS provider is pinned to~> 5.0. - CloudFront is a global service; the provider
region(from the cluster) only configures the AWS client.