Amazon Elastic Transcoder vs. Amazon S3 (Simple Storage Service)

It is well suited in a large setting where people use different file formats and various apps to record and transfer their audio or video files across devices. In such scenarios, the transcoder would of real help to eliminate the hassle of converting the files into desired formats for viewing or doing some other analysis.

The transcoder would not be of much use if all the files have the same format and does not need any conversion from their source file formats. It would prove costly and not useful if it's just an additional step that is of no particular use

Incentivized

Amazon S3 is a great service to safely backup your data where redundancy is guaranteed and the cost is fair. We use Amazon S3 for data that we backup and hope we never need to access but in the case of a catastrophic or even small slip of the finger with the delete command we know our data and our client's data is safely backed up by Amazon S3. Transferring data into Amazon S3 is free but transferring data out has an associated, albeit low, cost per GB. This needs to be kept in mind if you plan on transferring out a lot of data frequently. There may be other cost effective options although Amazon S3 prices are really low per GB. Transferring 150TB would cost approximately $50 per month.

Incentivized

• Works at scale, you can can transcode a high number of videos at the same time.
• Supports a good number of formats.
• Good integration with AWS S3 and other AWS Services.

Incentivized

• Fantastic developer API, including AWS command line and library utilities.
• Strong integration with the AWS ecosystem, especially with regards to access permissions.
• It's astoundingly stable- you can trust it'll stay online and available for anywhere in the world.
• Its static website hosting feature is a hidden gem-- it provides perhaps the cheapest, most stable, most high-performing static web hosting available in PaaS.

Incentivized

• Amazon Elastic Transcoder requires a fair amount of setup.

Incentivized

• Web console can be very confusing and challenging to use, especially for new users
• Bucket policies are very flexible, but the composability of the security rules can be very confusing to get right, often leading to security rules in use on buckets other than what you believe they are

Incentivized

Due to princing, availability and scalability.

Incentivized

It is tricky to get it all set up correctly with policies and getting the IAM settings right. There is also a lot of lifecycle config you can do in terms of moving data to cold/glacier storage. It is also not to be confused with being a OneDrive or SharePoint replacement, they each have their own place in our environment, and S3 is used more by the IT team and accessed by our PHP applications. It is not necessarily used by an average everyday user for storing their pictures or documents, etc.

Incentivized

Support for Amazon Elastic Transcoder is the same as any other service within AWS. If you are familiar with AWS, it is easy to start using Elastic Transcoder

Incentivized

AWS has always been quick to resolve any support ticket raised. S3 is no exception. We have only ever used it once to get a clarification regarding the costs involved when data is transferred between S3 and other AWS services or the public internet. We got a response from AWS support team within a day.

Incentivized

Amazon Elastic Transcoder is in a league of its own when compared to other alternatives in the market. The most noticeable competitor would be either Microsoft or Adobe or Google. When I had a chance to compare Azure products and Amazon products, the difference is obvious and the experience provided by both the products are very different in terms of user experience and interaction with the application. The cost and availability also were taken into consideration when choosing between the two shortlisted choices. So we went with Amazon's product as it is widely used and has support and maintenance which is basically better than the competition.

Incentivized

Overall, we found that Amazon S3 provided a lot of backend features Google Cloud Storage (GCS) simply couldn't compare to. GCS was way more expensive and really did not live up to it. In terms of setup, Google Cloud Storage may have Amazon S3 beat, however, as it is more of a pseudo advanced version of Google Drive, that was not a hard feat for it to achieve. Overall, evaluating GCS, in comparison to S3, was an utter disappointment.

Incentivized

• Less time for integration with this service if you are already in AWS stack
• No real time transcoding is a negative

Incentivized

• It practically eliminated some real heavy storage servers from our premises and reduced maintenance cost.
• The excellent durability and reliability make sure the return of money you invested in.
• If the objects which are not active or stale, one needs to remove them. Those objects keep adding cost to each billing cycle. If you are handling a really big infrastructure, sometimes this creates quite a huge bill for preserving un-necessary objects/documents.

Incentivized