PutCorsPolicy
Important
End of support notice: On November 13, 2025, AWS
will discontinue support for AWS Elemental MediaStore. After November 13, 2025, you will
no longer be able to access the AWS Elemental MediaStore console or AWS Elemental MediaStore resources.
For more information, visit this
blog post
Sets the cross-origin resource sharing (CORS) configuration on a container so that the container can service cross-origin requests. For example, you might want to enable a request whose origin is http://www.example.com to access your AWS Elemental MediaStore container at my.example.container.com by using the browser's XMLHttpRequest capability.
To enable CORS on a container, you attach a CORS policy to the container. In the CORS policy, you configure rules that identify origins and the HTTP methods that can be executed on your container. The policy can contain up to 398,000 characters. You can add up to 100 rules to a CORS policy. If more than one rule applies, the service uses the first applicable rule listed.
To learn more about CORS, see Cross-Origin Resource Sharing (CORS) in AWS Elemental MediaStore.
Request Syntax
{
"ContainerName": "string
",
"CorsPolicy": [
{
"AllowedHeaders": [ "string
" ],
"AllowedMethods": [ "string
" ],
"AllowedOrigins": [ "string
" ],
"ExposeHeaders": [ "string
" ],
"MaxAgeSeconds": number
}
]
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- ContainerName
-
The name of the container that you want to assign the CORS policy to.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 255.
Pattern:
[\w-]+
Required: Yes
- CorsPolicy
-
The CORS policy to apply to the container.
Type: Array of CorsRule objects
Array Members: Minimum number of 1 item. Maximum number of 100 items.
Required: Yes
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors.
- ContainerInUseException
-
The container that you specified in the request already exists or is being updated.
HTTP Status Code: 400
- ContainerNotFoundException
-
The container that you specified in the request does not exist.
HTTP Status Code: 400
- InternalServerError
-
The service is temporarily unavailable.
HTTP Status Code: 500
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: