crossplane-aws-s3
Upbound’s Crossplane provider for AWS S3, version v2.9.0. You create S3 buckets and their settings as Kubernetes objects in your namespace. The provider makes them in your AWS account.
- API reference: provider-aws-s3 v2.9.0
- API groups:
s3.aws.m.upbound.io(buckets and their settings) andaws.m.upbound.io(ProviderConfig). - Not there: Crossplane itself (compositions, packages) and the cluster-scoped types
(
ClusterProviderConfig, groups3.aws.upbound.io).
- Turn the plugin on: open your control plane, then Plugins → Turn on.
- Give your AWS credentials: a Secret with the label
plugins.ctrlplane.run/copy=true. - Make a
ProviderConfignameddefaultthat reads the Secret. - Make your buckets. Each one must point to your
ProviderConfig.
Replace <namespace> with your control plane’s namespace, for example alice-dev. The site’s
plugin catalog fills it in for you.
# 1. Your AWS credentials. The label copies the Secret to the operator.apiVersion: v1kind: Secretmetadata: name: aws-creds namespace: <namespace> labels: {plugins.ctrlplane.run/copy: "true"}stringData: credentials: | [default] aws_access_key_id = <your key id> aws_secret_access_key = <your secret key>---# 2. A ProviderConfig that reads the Secret.apiVersion: aws.m.upbound.io/v1beta1kind: ProviderConfigmetadata: {name: default, namespace: <namespace>}spec: credentials: source: Secret secretRef: {name: aws-creds, namespace: <namespace>, key: credentials}---# 3. A bucket. The name is the S3 bucket name: it must be unique in all of AWS.apiVersion: s3.aws.m.upbound.io/v1beta1kind: Bucketmetadata: {name: <namespace>-example, namespace: <namespace>}spec: forProvider: {region: eu-central-1} providerConfigRef: {kind: ProviderConfig, name: default}Apply it with kubectl apply -f, or in the site under Resources → Apply resources.
The Secret is copied to the operator within five minutes. Until then, the bucket is not ready.
Check the bucket
Section titled “Check the bucket”kubectl get buckets.s3.aws.m.upbound.ioSYNCED and READY become True when the bucket exists in AWS. If not, look at the
conditions:
kubectl describe buckets.s3.aws.m.upbound.io <name>- Set
providerConfigRefon every resource, withkind: ProviderConfig. Without it, the provider uses aClusterProviderConfignameddefault. That does not exist, so the request is refused. - Use
credentials.source: Secretin aProviderConfig. Other sources (IRSA, WebIdentity, PodIdentity, Upbound) use the identity of the provider pod, which is not yours. They are refused. - Do not set
spec.endpointin aProviderConfig. The provider calls AWS only; a custom endpoint is refused. - When you delete a bucket object, the provider deletes the bucket in AWS. To keep the bucket,
set
spec.managementPoliciesbefore you delete. See the API reference. - To turn the plugin off, delete all its objects first. Your
ProviderConfigcounts too.