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
IBM Cloudability
Score 8.8 out of 10
N/A
IBM Cloudability is a cloud cost management and optimization (FinOps) tool that enables IT, finance, and business teams to optimize their cloud spend across all cost sources, all maturity levels, and for all stakeholders.
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.
I don't have much exposure to the tool. I mean, I'm relatively new to using it as a platform, but I haven't really seen the benefit, especially with the actual renewal talks at the company. I'm not seeing what AWS native solutions are, how probability improves on that as opposed to just using AWS and just, I don't know. I'm not seeing the benefit, at least in my eyes.
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
For me, it is a lot of anomaly detection and I think there's a lot of improvement that can be made to show anomalies that happen over time because if it's just day to day or week to week, you may not see the change. But if you see the trend over a period of time, show me something that has grown 40%, 50% over the past three months and maybe you can do those things and we just haven't figured them out yet. So we are very new to the product, but I think anomaly detection for me is one of the bigger things.
Cloudability has been one solution for almost all of our FinOps needs. Except for Data transfer costs, we have covered all use cases and have made significant savings across our cloud infrastructure. Reporting has provided management a deeper analysis into their spending and helped them forecast their budgets for next year
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 gave the IBM Cloudability a 7/10 because it is good, but it could improve in some places. It is easy to get data uploaded and ready to view, but it is only up to a certain point in time, and not live data. As for how it looks, the interface is good for viewing, however navigation could be a little better, maybe supported with a roadmap.
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.
While there have been few support cases where the experience was good. But in multiple support cases it's firstly delayed and even after weeks or months of time, team is not able to provide us with the RCA of the issue. All they are claiming is the issue is now fixed which I still see coming back after few days or weeks as we've never identified and addressed the root cause.
Training was adequate, but the real learning begins when you start using the product, like most things. All major functions were covered so as an entry point, was a good introduction to the product. The training pace was good as well, the areas were covered in decent depth, without being too much of an information overload.
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.
Before Apptio we extensively used the cloud native and in house automated and developed cost optimization tool using python , powershell and leveraging the various cloud native services like AWS systems manager , Azure Functions and Azure automation run books.
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.