Using Encoding with AWS
This article is a part of the Encoding Quick Start Guide.
Axinom Encoding supports a number of Storage Providers and Message Publishers.
If you prefer using Amazon Web Services (AWS), Axinom Encoding supports this natively.
Storage Provider: S3
On AWS, you will likely choose S3 Buckets for your input and output storage.
- Storage Provider: S3
- How to create an S3 bucket in AWS - you can use Amazon S3 console, Amazon S3 APIs, or AWS SDKs
See below for a full example.
tip
You can also use S3-compatible storage, i.e., storage on other clouds which implements the S3-interface.
Message Publisher: SQS
On AWS, you will likely choose Amazon SQS for your message publisher.
See below for a full example.
Job Request Sample
{
"ExternalId": "<job_reference_id>",
"ExternalType": "movie",
"ContentAcquisition": {
"Provider": "AmazonS3",
"UriPath": "https://<your_bucket-name>.s3.us-east-2.amazonaws.com/<input-folder-path>/",
"CredentialsName": "<PLAINTEXT_AWS_ACCESS_KEY_ID>",
"CredentialsSecret": "<ENCRYPTED_AWS_SECRET_ACCESS_KEY>",
"CredentialsProtection": "Encrypted"
},
"MediaMappings": {
"VideoStreamExpression": "^.*\\.(mp4)$"
},
"ContentProcessing": {
"OutputFormat": ["Cmaf"]
},
"ContentPublishing": {
"Provider": "AmazonS3",
"UriPath": "https://<your-bucket-name>.s3.us-east-2.amazonaws.com/<output-folder-path>/",
"CredentialsName": "PLAINTEXT_AWS_ACCESS_KEY_ID",
"CredentialsSecret": "ENCRYPTED_AWS_SECRET_ACCESS_KEY",
"CredentialsProtection": "Encrypted"
},
"MessagePublishers": [
{
"Type": "AmazonSqs",
"UriPath": "https://sqs.us-east-2.amazonaws.com/account-id/<your_Queue-name>",
"CredentialsName": "PLAINTEXT_AWS_ACCESS_KEY_ID",
"CredentialsSecret": "ENCRYPTED_AWS_SECRET_ACCESS_KEY",
"CredentialsProtection": "Encrypted"
}
]
}