Amazon S3 Reviews & Insights

We use s3 buckets for having terraform state file management, keeping cloudwatch log group logs, keeping website static content, keeping cost optimization reports. The s3 bucket are helpful because it can hold any type of object and which can be automatically deleted whenever it is not required using the lifecycle management.

Keeping reports, cloudwatch log groups logs, emr artifacts, automatic backup keeping of platform data. The access control lists and bucket policies do provide ways to restrict the access to the bucket to certain teams which is helpful for production data. Also can be used to have multiple versions of an object which helps if some issue occurs in the latest release

At my organization, we primarily use Amazon S3 (Simple Storage Service) as a catch all storage solution. In particular, we have built our entire data lake around it, so we have “raw layer” buckets, “clean layer” buckets and so on. There are of course other uses, such as simple “data dump” buckets but in general we aim to use Amazon S3 (Simple Storage Service) as our main storage solution.

I believe that Amazon S3 (Simple Storage Service) is perfect for a Data Lake implementation: this is because you can either have buckets per layer or you can organize layers in the prefix of a single bucket; either way, you have flexibility to organize your data as you prefer. I would not recommend it if your data strategy and naming convention changes often, as it’s not easily possible to move data from one bucket to another (and you cannot rename the existing one, which is probably one of the features I miss the most)

We are using Amazon S3 (Simple Storage Service) as our main storage for static files, saved reports, and short and long-term backups. Amazon S3 (Simple Storage Service) has many different storage types that allow us to optimize our data storage spend quite well, but unfortunately not to the fullest. With the built in web access, and good integration with CloudFront we are also able to serve media to the world with a simple and low-cost solution. Having file-level access control is also a major plus that we utilize often.

Amazon S3 (Simple Storage Service) is well suited for storing data for varying time periods, while optimizing access control and cost. It has an extensive API and SDK to allow software to access files on Amazon S3 (Simple Storage Service), with the correct permissions schema. It is not, however, enough for serving large websites on its own, and integration with CloudFront is recommended. It is not a filesystem, so software needs to know how to write to Amazon S3 (Simple Storage Service) in order to utilize it.

We leverage Amazon S3 capabilities to a multitude of scenarios. We store audio recording files for our application, we use it as a storage backend for our vault application and we also use it to store analytics data for Redshift to consume from. Amazon S3 is always something we look at when solving business problems that requires storing data because of its ease of use and scalability with affordable price. it is also easy to share data externally and to integrate with applications. It provides reliable storage scalability for analytics and business data as well.

If you need to store files that will be accessed or shared to multiple parties Amazon S3 is a viable solution. If you need to grain control access to those files, Amazon S3 has a lot of capabilities as well. If your tool can use Amazon S3 as backend, it is also a good choice due to the price. You can also use it as a web hosting solution for small websites. It is great for backing up and archiving application and database data.
I would not recommend it to be user on high-performance computing where you need really really slow latency. If you need to transit large chunks of data I would be careful as well to avoid the high costs of AWS data transfers.

We are using S3 as a images and files storage, Earlier we were using our own static ip based server but we faced to many server downs and request failed. So we moved to S3 and now we are very happy with the S3 because request failure rate has gone down. Response time is very low and returning responses very quickly.

Where we want the quick responses and we have to manage too many files then we can use the S3, But if we are not processing the files to many times its not required to use the S3. If we want to use a file from different servers then its a very good option to store the file at a central point like S3 and use it from the different servers.

We store user-generated content, backups, raw event data, logs, and other raw data in S3. This data is used by our product in serving content to our users, by our operations team to maintain site availability, by our analytics teams, and by our developers to debug our production systems.

If you have data you may someday need but don't have immediate high volume access patterns, S3 is great.
Serving images and static content via s3 works very well and provides smoke performance (and can be coupled with CloudFront for distribution if necessary). Do not treat s3 like a general-purpose key-value store. Do not try to coordinate or create consensus using s3.

Amazon S3 is the backbone of our data storage. We store 90% plus of all data in S3. It also serves as a backup and disaster recovery plan as we take other storage solutions and back them up to S3. It is also used for data flow and transfer from/to internal/external vendors.

• We use S3 as an entry point (landing zone for data). We can then transform (normalize) the data and store it again.
• S3 has great services built around automating tasks to be done when an object is updated/created/deleted.
• S3 has built-in replication for back up and disaster recovery.

It is not great that some of it features require you to think about how you want to store your data. For example to get the cheapest usage it is recommended to use less objects with greater size instead of many objects of tiny size.

We use Amazon S3 (Simple Storage Service) to persist large blobs of data that would be otherwise expensive or otherwise challening to store in one of our database systems. We use S3 primarily for areas of the business where it's important to easily store large pieces of data, such as images and large JSON data sets, or where it is important to share that data between multiple types of services.

Amazon S3 (Simple Storage Service) is particularly well-suited for cases where you have already made the decision to use Amazon's cloud software resources and need to add the option of storing files for use from one or more services. Amazon S3 (Simple Storage Service) is also a good choice for its native integration with Amazon's CDN, Cloudfront. In general, using Amazon S3 (Simple Storage Service) will make less sense if you are already using other services from another vendor, such as Azure.

We use Amazon S3 across the whole organization to store business material, marketing material, web assets, and customer generated content like images and certificates. It is very good value, very reliable, and very fast. Access via the console and the API let's us upload and download data from many locations. The cost is so good that we don't concern ourselves with any kind of limitation to how much data we create.

Amazon S3 handles file storage exceptionally well and has the necessary features to be useful to anyone. S3 would not be ideal as a substitute for a computer hard drive but would be as a backup for that hard drive, or an extension of it, which you can delegate access to and where your internet speed is the only factor to consider.

We used S3 for storing data on the cloud so that the data is available for our customers constantly without any dependency. We also use S3 to host static websites. S3 has different classes for storage so data can be stored according to customers' needs and charges and are levied accordingly.

Amazon S3 is well suited for hosting a static website in a very short time and also for storing a huge chunk of data while using AWS services. It was difficult for us to integrate it with Azure cloud services as S3 has tight AWS integration.