
Sets the cors
configuration for your bucket. If the configuration
exists, Amazon S3 replaces it.
s3_put_bucket_cors(Bucket, CORSConfiguration, ContentMD5)
[required] Specifies the bucket impacted by the cors
configuration.
[required] Describes the cross-origin access configuration for objects in an Amazon S3 bucket. For more information, see Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
The base64-encoded 128-bit MD5 digest of the data. This header must be used as a message integrity check to verify that the request body was not corrupted in transit. For more information, go to RFC 1864.
svc$put_bucket_cors( Bucket = "string", CORSConfiguration = list( CORSRules = list( list( AllowedHeaders = list( "string" ), AllowedMethods = list( "string" ), AllowedOrigins = list( "string" ), ExposeHeaders = list( "string" ), MaxAgeSeconds = 123 ) ) ), ContentMD5 = "string" )
To use this operation, you must be allowed to perform the
s3:PutBucketCORS
action. By default, the bucket owner has this
permission and can grant it to others.
You set this configuration on a bucket so that the bucket can service
cross-origin requests. For example, you might want to enable a request
whose origin is http://www.example.com
to access your Amazon S3 bucket
at my.example.bucket.com
by using the browser\'s XMLHttpRequest
capability.
To enable cross-origin resource sharing (CORS) on a bucket, you add the
cors
subresource to the bucket. The cors
subresource is an XML
document in which you configure rules that identify origins and the HTTP
methods that can be executed on your bucket. The document is limited to
64 KB in size.
When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS
request) against a bucket, it evaluates the cors
configuration on the
bucket and uses the first CORSRule
rule that matches the incoming
browser request to enable a cross-origin request. For a rule to match,
the following conditions must be met:
The request\'s Origin
header must match AllowedOrigin
elements.
The request method (for example, GET, PUT, HEAD, and so on) or the
Access-Control-Request-Method
header in case of a pre-flight
OPTIONS
request must be one of the AllowedMethod
elements.
Every header specified in the Access-Control-Request-Headers
request header of a pre-flight request must match an AllowedHeader
element.
For more information about CORS, go to Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
Related Resources
GetBucketCors
DeleteBucketCors
RESTOPTIONSobject
# NOT RUN {
# The following example enables PUT, POST, and DELETE requests from
# www.example.com, and enables GET requests from any domain.
svc$put_bucket_cors(
Bucket = "",
CORSConfiguration = list(
CORSRules = list(
list(
AllowedHeaders = list(
"*"
),
AllowedMethods = list(
"PUT",
"POST",
"DELETE"
),
AllowedOrigins = list(
"http://www.example.com"
),
ExposeHeaders = list(
"x-amz-server-side-encryption"
),
MaxAgeSeconds = 3000L
),
list(
AllowedHeaders = list(
"Authorization"
),
AllowedMethods = list(
"GET"
),
AllowedOrigins = list(
"*"
),
MaxAgeSeconds = 3000L
)
)
),
ContentMD5 = ""
)
# }
# NOT RUN {
# }
Run the code above in your browser using DataLab