AWS Elemental MediaStore

2018/02/08 - AWS Elemental MediaStore - 3 new api methods

Changes  AWS Elemental MediaStore now supports per-container CORS configuration.

GetCorsPolicy (new) Link ¶

Returns the cross-origin resource sharing (CORS) configuration information that is set for the container.

To use this operation, you must have permission to perform the MediaStore:GetCorsPolicy action. By default, the container owner has this permission and can grant it to others.

See also: AWS API Documentation

Request Syntax

client.get_cors_policy(
    ContainerName='string'
)
type ContainerName

string

param ContainerName

[REQUIRED]

The name of the container that the policy is assigned to.

rtype

dict

returns

Response Syntax

{
    'CorsPolicy': [
        {
            'AllowedOrigins': [
                'string',
            ],
            'AllowedMethods': [
                'PUT'|'GET'|'DELETE'|'HEAD',
            ],
            'AllowedHeaders': [
                'string',
            ],
            'MaxAgeSeconds': 123,
            'ExposeHeaders': [
                'string',
            ]
        },
    ]
}

Response Structure

  • (dict) --

    • CorsPolicy (list) --

      The CORS policy of the container.

      • (dict) --

        A rule for a CORS policy. 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.

        • AllowedOrigins (list) --

          One or more response headers that you want users to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).

          Each CORS rule must have at least one AllowedOrigin element. The string value can include only one wildcard character (*), for example, http://*.example.com. Additionally, you can specify only one wildcard character to allow cross-origin access for all origins.

          • (string) --

        • AllowedMethods (list) --

          Identifies an HTTP method that the origin that is specified in the rule is allowed to execute.

          Each CORS rule must contain at least one AllowedMethod and one AllowedOrigin element.

          • (string) --

        • AllowedHeaders (list) --

          Specifies which headers are allowed in a preflight OPTIONS request through the Access-Control-Request-Headers header. Each header name that is specified in Access-Control-Request-Headers must have a corresponding entry in the rule. Only the headers that were requested are sent back.

          This element can contain only one wildcard character (*).

          • (string) --

        • MaxAgeSeconds (integer) --

          The time in seconds that your browser caches the preflight response for the specified resource.

          A CORS rule can have only one MaxAgeSeconds element.

        • ExposeHeaders (list) --

          One or more headers in the response that you want users to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).

          This element is optional for each rule.

          • (string) --

DeleteCorsPolicy (new) Link ¶

Deletes the cross-origin resource sharing (CORS) configuration information that is set for the container.

To use this operation, you must have permission to perform the MediaStore:DeleteCorsPolicy action. The container owner has this permission by default and can grant this permission to others.

See also: AWS API Documentation

Request Syntax

client.delete_cors_policy(
    ContainerName='string'
)
type ContainerName

string

param ContainerName

[REQUIRED]

The name of the container to remove the policy from.

rtype

dict

returns

Response Syntax

{}

Response Structure

  • (dict) --

PutCorsPolicy (new) Link ¶

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.

See also: AWS API Documentation

Request Syntax

client.put_cors_policy(
    ContainerName='string',
    CorsPolicy=[
        {
            'AllowedOrigins': [
                'string',
            ],
            'AllowedMethods': [
                'PUT'|'GET'|'DELETE'|'HEAD',
            ],
            'AllowedHeaders': [
                'string',
            ],
            'MaxAgeSeconds': 123,
            'ExposeHeaders': [
                'string',
            ]
        },
    ]
)
type ContainerName

string

param ContainerName

[REQUIRED]

The name of the container that you want to assign the CORS policy to.

type CorsPolicy

list

param CorsPolicy

[REQUIRED]

The CORS policy to apply to the container.

  • (dict) --

    A rule for a CORS policy. 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.

    • AllowedOrigins (list) --

      One or more response headers that you want users to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).

      Each CORS rule must have at least one AllowedOrigin element. The string value can include only one wildcard character (*), for example, http://*.example.com. Additionally, you can specify only one wildcard character to allow cross-origin access for all origins.

      • (string) --

    • AllowedMethods (list) --

      Identifies an HTTP method that the origin that is specified in the rule is allowed to execute.

      Each CORS rule must contain at least one AllowedMethod and one AllowedOrigin element.

      • (string) --

    • AllowedHeaders (list) --

      Specifies which headers are allowed in a preflight OPTIONS request through the Access-Control-Request-Headers header. Each header name that is specified in Access-Control-Request-Headers must have a corresponding entry in the rule. Only the headers that were requested are sent back.

      This element can contain only one wildcard character (*).

      • (string) --

    • MaxAgeSeconds (integer) --

      The time in seconds that your browser caches the preflight response for the specified resource.

      A CORS rule can have only one MaxAgeSeconds element.

    • ExposeHeaders (list) --

      One or more headers in the response that you want users to be able to access from their applications (for example, from a JavaScript XMLHttpRequest object).

      This element is optional for each rule.

      • (string) --

rtype

dict

returns

Response Syntax

{}

Response Structure

  • (dict) --