Wed Sep 16 2020
How can I configure an AWS S3 Bucket to test playback of my content?
When you use an S3 bucket as Output for your encodings, they will not automatically allow you to test streaming your encoded content from them. The default security model with S3 does not allow for this.
To enable this model, you will need to do the following:
Allow Public Access ACLs
When you create the bucket, disable the bucket settings that block public access, which are set by default on new buckets. If you use the AWS Console, they are Block new public ACLs and uploading public objects and Remove public access granted through public ACLs. See the AWS Documentation on Block Public Access for details.
If you leave those enabled, you will need to ensure that your scripts set ACL permissions to
PRIVATE on objects output to this bucket (for example muxings, manifests, etc.), or your encodings will fail.
To allow players to request content for streaming from your S3 bucket, you will also need to allow origin access with a CORS configuration.
The following is a good default policy that provides unrestricted access for streaming.
1<?xml version="1.0" encoding="UTF-8"?>2<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">3 <CORSRule>4 <AllowedOrigin>*</AllowedOrigin>5 <AllowedMethod>GET</AllowedMethod>6 <AllowedMethod>HEAD</AllowedMethod>7 <MaxAgeSeconds>3000</MaxAgeSeconds>8 <AllowedHeader>Authorization</AllowedHeader>9 </CORSRule>10</CORSConfiguration>
For more information on how to enable CORS on S3 buckets, see the AWS Documentation
To troubleshoot upload issues to your AWS S3 bucket are explained here.