BucketCorsConfiguration is the Schema for the BucketCorsConfigurations API. Provides an S3 bucket CORS configuration resource.
Type
CRD
Group
s3.aws.upbound.io
Version
v1beta1
apiVersion: s3.aws.upbound.io/v1beta1
kind: BucketCorsConfiguration
BucketCorsConfigurationSpec defines the desired state of BucketCorsConfiguration
No description provided.
Reference to a Bucket in s3 to populate bucket.
Policies for referencing.
Selector for a Bucket in s3 to populate bucket.
Policies for selection.
Set of origins and methods (cross-origin access that you want to allow). See below. You can configure up to 100 rules.
Set of Headers that are specified in the Access-Control-Request-Headers header.
Set of HTTP methods that you allow the origin to execute. Valid values are GET, PUT, HEAD, POST, and DELETE.
Set of origins you want customers to be able to access the bucket from.
Set of headers in the response that you want customers to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
BucketCorsConfigurationStatus defines the observed state of BucketCorsConfiguration.
No description provided.
Set of origins and methods (cross-origin access that you want to allow). See below. You can configure up to 100 rules.
Set of Headers that are specified in the Access-Control-Request-Headers header.
Set of HTTP methods that you allow the origin to execute. Valid values are GET, PUT, HEAD, POST, and DELETE.
Set of origins you want customers to be able to access the bucket from.
Set of headers in the response that you want customers to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).
Conditions of the resource.
example
apiVersion: s3.aws.upbound.io/v1beta1
kind: BucketCorsConfiguration
metadata:
name: example
spec:
forProvider:
bucketSelector:
matchLabels:
testing.upbound.io/example-name: s3
corsRule:
- allowedHeaders:
- "*"
allowedMethods:
- PUT
- POST
allowedOrigins:
- https://s3-website-test.upbound.com
exposeHeaders:
- ETag
maxAgeSeconds: 3000
- allowedMethods:
- GET
allowedOrigins:
- "*"
region: us-west-1
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.