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 Amazon S3 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 Amazon S3 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/s3/default/1.2.1, 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 S3 bucket with encryption, versioning, and public access block configured. The bucket name is automatically lowercased before creation.

Variables

Outputs

Upgrading to 1.2.0

bucket_policy defaults to true, so upgrading an existing bucket attaches the TLS policy. S3 holds a single policy per bucket: this one replaces any policy attached outside the blueprint. Preview the update before applying it (the plan shows aws_s3_bucket_policy.this[0] being created), and set bucket_policy = false if the bucket relies on a policy managed elsewhere. Setting it to false after the policy was replaced deletes the policy; it does not restore the previous one.

Required AWS IAM permissions

The credentials used to deploy this blueprint must allow the actions below. Resource scope: arn:aws:s3:::* (bucket-level) and arn:aws:s3:::*/* (object-level, only needed when force_destroy = true).