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 Lambda
Score 8.3 out of 10
N/A
AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
DigitalOcean
Score 8.6 out of 10
N/A
DigitalOcean is an infrastructure-as-a-service (IaaS) platform from the company of the same name headquartered in New York. It is known for its support of managed Kubernetes clusters and “droplets” feature.
$5
Starting Price Per Month
Pricing
Amazon S3 (Simple Storage Service)
AWS Lambda
DigitalOcean
Editions & Modules
No answers on this topic
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
1GB-16GB
$5.00
Starting Price Per Month
8GB-160GB
$60.00
Starting Price Per Month
Offerings
Pricing Offerings
Amazon S3
AWS Lambda
DigitalOcean
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Amazon S3 (Simple Storage Service)
AWS Lambda
DigitalOcean
Considered Multiple Products
Amazon S3
Verified User
Engineer
Chose Amazon S3 (Simple Storage Service)
As most of our work loads and the under laying platforms are build on EMR, Spark and AWS Lambda, we did not find HDFS a suitable solution to have all of our data in. HDFS was very costly as we had to maintain data nodes only for the sole purpose of maintaining the extra storage …
Amazon S3 integrates way better with other AWS services and tools, making it the quick choice for your AWS based application. Furthermore, the pricing for Amazon S3 is very competitive and it has all the security and access capabilities to enable your application. Google …
Pricing and Cost Structure are best:Amazon S3:Offers multiple storage classes: Standard, Intelligent-Tiering, Standard-IA (Infrequent Access), One Zone-IA, Glacier, and Glacier Deep Archive while other were costly and figuring out the monthly costs were difficult. The …
Amazon S3 (Simple Storage Service) is the only AWS offering for object storage. DynamoDB is fantastic for unstructured data but does not handle object storage. The relational database service (RDS) is excellent but only applies to use cases with structured table data, and does …
All other alternatives are also good but as our infrastructure was on AWS, Amazon S3 (Simple Storage Service) was a better choice due to its better integration with other AWS services. It was serving the purpose in an economical way. All of our needs were being fulfilled by …
We had already decided to use Amazon S3 (Simple Storage Service) for other compute services, so it made sense to use Amazon for blob storage as well. By using the same cloud vendor, we can more easily integrate between AWS services like Cloudfront. Blob storage is essentially a …
Google Cloud Storage provides many of the same features as Amazon S3 (Simple Storage Service), but they differ quite a bit in the database integrations they provide. The main reason we had to use Amazon S3 (Simple Storage Service) is because our main infrastructure cloud …
S3 provides an on-demand usage model for storage. You only pay for what you use. Nutanix is an on-premises solution and does not allow for usage-based pricing. Azure was less integrated with our current AWS workloads which helped drive our decision to use s3 with the Amazon …
AWS Lambda is much easier to use than the near alternatives. It is so straightforward and lightweight it is my primary service for handling small transactions or triggers. The other services require more setup time and are more complex to use. AWS Lambda takes your code snippet …
When we use Lambda, we do not need to worry about the infrastructure and costs. AWS can handle it all on its own. For an optimum use case, one can always use AWS Lambda along with API Gateway and Route 53 for the best use case. Cloudwatch can help you identify any issues and …
These are all AWS sister products, so I wouldn't say they are competitors but tools in the same box. They all work quite well together and I would say combined they are greater than the sum of their parts. Cloudformation (and SAM) templates make tying them together pretty …
Amazon has a very complex UI and many products to offer. They haven't polished up their UI and it has a much greater learning curve compared to DigitalOcean. However, Amazon Web Services (AWS) does have more comprehensive cloud computing services, which forces some companies to …
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.
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
DigitalOcean is perfect for hosting client websites, running marketing tools, and managing media storage with Spaces and CDN. The use of Droplets to quickly launch landing pages or WordPress sites for campaigns is a Godsend. It’s great for fast, cheap, and scalable solutions. But for complex microservices or projects needing strict compliance (like HIPAA), DigitalOcean may not always be the best fit, but that depends heavily on your project.
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
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
Some products/services available on other Cloud providers aren't available, but they seem to be catching up as they add new products like Managed SQL DBs.
While they have FreeBSD droplets (VMs), support for *BSD OSs is limited. I.e. the new monitoring agent only works on Linux.
There are no regions available on South America.
They don't seem to offer enterprise-level products, even basic ones as Windows Server, MS SQL Server, Oracle products, etc.
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.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
I honestly can't think of an easier way to set up and maintain your own server. Being able to set up a server in minutes and have fully control is awesome. The UX is incredibly intuitive for first-time users as well so there's no reason to be intimidated when it comes to giving DigitalOcean a shot.
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.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
They have always been fast, and the process has been straight-forward. I haven't had to use it enough to be frustrated with it, to be honest, and when I have an issue they fix it. As with all support, I wish it felt more human, but they are doing aces.
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.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
DigitalOcean is an inexpensive product as compared to other products available in the market. The UI is easy and the beginner can also understand the UI with the step by step guide. It provides a lot of custom features and the user needs to pay only for what they are using. Amazon has a complex UI and is on the expensive side. DigitalOcean is simple to use and is easily manageable and the servers can easily be set up without additional cost and such.
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.
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
Positive - Elastic computer instances make it possible to pay for only for what you need.
Positive - Competitive pricing - some of the products that DigitalOcean offers are much cheaper than those offered by competitors.
Negative - Having to go to other cloud computing platforms for more specific, advanced services like Computer Vision optimized services, GPU cloud compute instances, etc...