Amazon S3 (Simple Storage Service) vs. AWS Fargate

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

If you need to deploy Docker containers, Amazon Fargate is a very good fit. It integrates very well with other AWS services like RDS, EFS, and Secrets manager. You can have a very robust application using those services. In case you have many containers to deploy, it is however more expensive
that if you use other services like ECS or EKS, since they allow you to
share the same infrastructure to deploy multiple containers.

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

• scalability
• ease of use
• agility to up or downsize

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

• can't think of any

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

It's a very practical service to use. If you need to deploy any application with a Database, disk storage, you're pretty much set.

Everything around that can be taken care of using other AWS services. Like secrets manager, certificate manager, RDS ...

And the CI/CD part is also very easy to setup, you only need on AWS CLI command to trigger a deployment, and done !

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

AWS provides different support tiers. They are usually very reactive and are able to help solve the issues very quickly.

As for everything, the higher the support tier you get, the better and faster support you get.

If you're also a part of big company, you probably have solution architects at your disposal to help you with any inqueries.

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

We found the extra cost saved us frustration and time and ultimately money in the long run

Incentivized

Pricing and billing of AWS Fargate is loosely tied to your exisiting AWS billing. You're unlikely to only use Fargate in your AWS subscription, so you get billed for everything alltoghter.

Fargate is naturally a bit more expensive that usuel docker services, but with careful planning and architecturing, you can have a very manageable cost.

You can also rely on Saving plans to reduce your bill.

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

• easier to optimize our computer costs
• transition from server to serverless was easier once we decided to adopt Fargate

Incentivized