Skip to main content
Qovery creates it in the AWS account of the environment’s cluster, as a Blueprint service in one of your environments.
New to this? You don’t need to know Kubernetes or Terraform. Qovery sets up AWS CloudFront in your cloud account and manages it for you: you fill in a form, or paste the prompt below into your coding agent. The values it publishes, listed under Outputs, reach your other services as environment variables. Qovery tells you when a newer version of the Blueprint is available. Check the requirements in the Reference section before you start, and try it first in a development environment.

Create it

  1. Open the environment, then New service › Blueprint.
  2. Find AWS CloudFront in the catalog and pick the major version.
  3. Fill in the variables. Required ones are marked; the others use their defaults.
  4. Create the service, and deploy it now or later.
You don’t add any file to your repository. Qovery creates the Blueprint from the Console or the API.

Variables and outputs

Generated from qbm.yml at AWS/cloudfront/default/1.0.7, the manifest the Console form is built from.
Outputs become environment variables that other services in the environment can use. By default Qovery also creates an alias for each output, prefixed with the Blueprint’s name; see Aliases Qovery creates for outputs for the naming rules and the cases where no alias is created.

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_values config (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.

Required AWS IAM permissions