1. Sign in to your AWS account
To upload your catalog file to Amazon Simple Storage Service (S3), you must have an AWS account. If you already have an AWS account, sign in at aws.amazon.com. To create a new account- Go to aws.amazon.com.
- Choose Create an AWS Account.
- Follow the prompts to create your account.
2. Provide details to set up your account
To set up your account, provide the following details to your Amazon representative:- Account ID – Send the 12-digit AWS account ID to your Amazon representative by using a secure method. Amazon needs this ID to grant your account access to the S3 catalog folder.
- Root account users: Sign in to the AWS Management Console. Your account ID appears in the upper corner under your account name, or on the Security Credentials page under Account Identifiers.
- IAM or federated users: Your account ID appears in the Support Center in the upper corner.
- AWS CLI: Use the following command.
- List of devices to allow list – Provide a list of Fire TV device serial numbers (DSNs) to enable for testing. After you submit your catalog the staging environment, you can use the allow listed device to verify your content is discoverable.
- Email address – The ingestion system sends emails for both successes and failures. If you want to receive one or both types of emails, ask your Amazon representative to include you on both lists. Use a team or group email address (for example, catalog-team@company.com) instead of personal emails. This allows multiple stakeholders to receive important ingestion notification and makes sure your team receives continuous communication even if team members change.
3. Receive your access configuration
After you send your AWS account ID, your Amazon representative provides the following information:- Your provider prefix – Identifies your catalog within the shared S3 bucket
amazon-media-catalogs. For example, if your provider prefix isacme-streaming, your catalog files live unders3://amazon-media-catalogs/acme-streaming/. - An IAM role Amazon Resource Name (ARN) – You assume this role to obtain temporary credentials for uploading catalog files. The role ARN looks like:
arn:aws:iam::123456789012:role/CatalogUploadRole. - Session tag support – The IAM role supports both
sts:AssumeRoleandsts:TagSessionpermissions. You can pass optional session tags when assuming the role for audit tracking and organizing access logs.
4. Set up AWS CLI and configure role assumption
This step covers installing the CLI, configuring your credentials, and assuming the IAM role for catalog uploads.Install the AWS CLI
If you don’t have the AWS CLI installed, follow the instructions at Installing or updating to the latest version of the AWS CLI in the AWS documentation.Configure your own AWS credentials
To set up your base credentials, runaws configure. You will see the following prompts.
Assume the IAM role for catalog upload
To upload catalog files, you must assume the IAM role that your Amazon representative provided. This gives you temporary credentials scoped to your S3 catalog bucket.Optional: Configure a named CLI profile
For convenience, you can configure a named profile in~/.aws/config that automatically handles role assumption, as shown here.
--profile catalog-upload with any AWS CLI command.

