AWS::MediaStore::Container - AWS CloudFormation


The AWS::MediaStore::Container resource specifies a storage container to hold objects. A container is similar to a bucket in Amazon S3.

When you create a container using AWS CloudFormation, the template manages data for five API actions: creating a container, setting access logging, updating the default container policy, adding a cross-origin resource sharing (CORS) policy, and adding an object lifecycle policy.


To declare this entity in your AWS CloudFormation template, use the following syntax:


{ "Type" : "AWS::MediaStore::Container", "Properties" : { "AccessLoggingEnabled" : Boolean, "ContainerName" : String, "CorsPolicy" : [ CorsRule, ... ], "LifecyclePolicy" : String, "MetricPolicy" : MetricPolicy, "Policy" : String, "Tags" : [ Tag, ... ] } }


Type: AWS::MediaStore::Container Properties: AccessLoggingEnabled: Boolean ContainerName: String CorsPolicy: - CorsRule LifecyclePolicy: String MetricPolicy: MetricPolicy Policy: String Tags: - Tag



The state of access logging on the container. This value is false by default, indicating that AWS Elemental MediaStore does not send access logs to Amazon CloudWatch Logs. When you enable access logging on the container, MediaStore changes this value to true, indicating that the service delivers access logs for objects stored in that container to CloudWatch Logs.

Required: No

Type: Boolean

Update requires: No interruption


The name for the container. The name must be from 1 to 255 characters. Container names must be unique to your AWS account within a specific region. As an example, you could create a container named movies in every region, as long as you don’t have an existing container with that name.

Required: Yes

Type: String

Pattern: [\w-]+

Minimum: 1

Maximum: 255

Update requires: Replacement


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 to access your AWS Elemental MediaStore container at 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.

Required: No

Type: Array of CorsRule

Update requires: No interruption


Writes an object lifecycle policy to a container. If the container already has an object lifecycle policy, the service replaces the existing policy with the new policy. It takes up to 20 minutes for the change to take effect.

For information about how to construct an object lifecycle policy, see Components of an Object Lifecycle Policy.

Required: No

Type: String

Update requires: No interruption


The metric policy that is associated with the container. A metric policy allows AWS Elemental MediaStore to send metrics to Amazon CloudWatch. In the policy, you must indicate whether you want MediaStore to send container-level metrics. You can also include rules to define groups of objects that you want MediaStore to send object-level metrics for.

To view examples of how to construct a metric policy for your use case, see Example Metric Policies.

Required: No

Type: MetricPolicy

Update requires: No interruption


Creates an access policy for the specified container to restrict the users and clients that can access it. For information about the data that is included in an access policy, see the AWS Identity and Access Management User Guide.

For this release of the REST API, you can create only one policy for a container. If you enter PutContainerPolicy twice, the second command modifies the existing policy.

Required: No

Type: String

Update requires: No interruption


Property description not available.

Required: No

Type: Array of Tag

Update requires: No interruption

Return values


When you pass the logical ID of this resource to the intrinsic Ref function, Ref returns the name of the container.

For example: { "Ref": "myContainer" }

For more information about using the Ref function, see Ref.


The Fn::GetAtt intrinsic function returns a value for a specified attribute of this type. The following are the available attributes and sample return values.

For more information about using the Fn::GetAtt intrinsic function, see Fn::GetAtt.


The DNS endpoint of the container. Use the endpoint to identify the specific container when sending requests to the data plane. The service assigns this value when the container is created. Once the value has been assigned, it does not change.