AWS MediaStore Container
This page shows how to write Terraform and CloudFormation for MediaStore Container and write them securely.
aws_media_store_container (Terraform)
The Container in MediaStore can be configured in Terraform with the resource name aws_media_store_container. The following sections describe 2 examples of how to use the resource and its parameters.
Example Usage from GitHub
resource "aws_media_store_container" "example" {
name = var.store_name
}
resource "aws_media_store_container" "this" {
name = var.name
tags = var.tags
}
Parameters
-
arnoptional computed - string -
endpointoptional computed - string -
idoptional computed - string -
namerequired - string -
tagsoptional - map from string to string
Explanation in Terraform Registry
Provides a MediaStore Container.
AWS::MediaStore::Container (CloudFormation)
The Container in MediaStore can be configured in CloudFormation with the resource name AWS::MediaStore::Container. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
Parameters
AccessLoggingEnabled
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
ContainerName
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
Minimum: 1
Maximum: 255
Pattern: [\w-]+
Update requires: Replacement
CorsPolicy
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.
Required: No
Type: List of CorsRule
Update requires: No interruption
LifecyclePolicy
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
MetricPolicy
Not currently supported by AWS CloudFormation.
Required: No
Type: MetricPolicy
Update requires: No interruption
Policy
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
Tags
Not currently supported by AWS CloudFormation.
Required: No
Type: List of Tag
Update requires: No interruption
Explanation in CloudFormation Registry
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.
Frequently asked questions
What is AWS MediaStore Container?
AWS MediaStore Container is a resource for MediaStore of Amazon Web Service. Settings can be wrote in Terraform and CloudFormation.
Where can I find the example code for the AWS MediaStore Container?
For Terraform, the gauravgitdir/Jack and niveklabs/aws source code examples are useful. See the Terraform Example section for further details.
