Amazon S3 is a cloud-based object storage service from Amazon Web Services. It's key features are storage management and monitoring, access management and security, data querying, and data transfer.
N/A
AWS Fargate
Score 9.0 out of 10
N/A
AWS Fargate is a compute engine for Amazon ECS that allows the user to run containers without having to manage servers or clusters. With AWS Fargate there is no need to provision, configure, and scale clusters of virtual machines to run containers.
$0
*per hour
Pricing
Amazon S3 (Simple Storage Service)
AWS Fargate
Editions & Modules
No answers on this topic
Fargate Spot per GB
$0.00138679
*per hour
per GB
$0.004445
*per hour
Fargate Spot per vCPU
$0.01262932
*per hour
per vCPU
$0.04048
*per hour
Offerings
Pricing Offerings
Amazon S3
AWS Fargate
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
*based on US East rates. Price varies region to region.
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.
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.
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.
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
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.
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.
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.
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.
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.
