Amazon S3 Reviews

We mostly use this for archiving old data that is infrequently accessed. It has been a good low-cost solution to get away from using on-prem NAS or even further back external hard disks and even CDs. It has ticked a lot of boxes for us in the sense of keeping this data safe and secure without the potential of data loss through external methods.

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 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 are using Amazon S3 for various purposes. We are using it to store backups, to store logs, to store audit trails, to store artefacts, to store website images and to store some other data required by the application. It is being used more like central storage that is economical to serve the purpose of data storage.

Our department was looking for storage service that works smoothly and can make our task easily using for storage big amount of data. So we found that Amazon S3 is the suitable one. S3 is monetary and dependable distributed storage which I'm utilizing [regularly]. Presenting some more highlights like referenced in Cons above could make it exceptional and it would be a shared benefit over different items.

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 (Simple Storage Service) is the quintessential large storage solution used by our organization alongside cloud applications. We use it for storing static files to serve through applications, storing application logs, storing large file, serving static websites through AWS CloudFront, storing machine learning models to be used by AWS Lambda functions, and many more use cases. Amazon S3 (Simple Storage Service) is used across applications for many client solutions we have developed on AWS.

S3 (AWS) is used by my department for storage of files that we are going to process in conjunction with other AWS products such as Transcribe, Translate and Polly. The Glacier feature is also an extremely cheap and durable place to store large video files that are infrequently accessed.

We use S3 to store files that we offer to subscriber customers.

Used across our organization it is the primary data store now for our files rather than Windows file service.

In my organization, we use S3 for nearly every aspect of asset storage -- user files, user profiles, saved application states -- as well as for hosting our primary web frontends (static React.js applications). It's used by the whole organization, both extensively throughout engineering to host our software and assets, and additionally by our operations and other teams as a general purpose host for special content.

It solves the business problem of exposing any sort of asset to external users, as well as serves as a complete website hosting and deployment service stack for static websites.

At this moment it is used at the IT department level, down the road we would like to expand this usage, but we are trying to see how we can safely enable all AWS users with security and compliance in mind. At this moment it allows us to store some temporary data for different infrastructure deployments.

Amazon S3 is heavily used in our company by the development department to store short and long terms files (audio, video, photos, etc) with different policies in the cloud. We trust AWS services, security and infrastructure. S3 is used in conjunction with many other AWS services. For example: with Lambda to perform operations when a file is uploaded, with Cloudwatch to save logs, with Cloudront to serve as CDN and cache, to store files for the web and mobile app, to store static content for the website, etc.

Everything that we need to store of data, without worry with size, or speed, we use Amazon S3. That's our safe alternative. From applications that use it to temporary keep files, to final destination of others, even to keep websites files, S3 is a great and safe alternative. It's the perfect companion to a lot of services, not only AWS.

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.

We mostly use S3 for storage of compliance documents, cloud formation scripts, heavy media files and other materials which need to preserve but used infrequently. We also host some of the static webpages which are just a navigator to the documents.
One of the other most prominent use which we do with S3 is to transfer large files. With strict IMA policies, we can make sure of proper access to these files. While we use other AWS services like EC2 to host machine for any computation purpose, we need to store interim results and final results. We store these results to S3 and kill the EC2 instance.
Also, we have scripts written for transferring S3 objects (not used for more than 2 years) to Glacier to minimize cost factor.

We use Amazon S3 to store files, long term, and short term, from our servers and to share files for various purposes: sending to clients, serving files over the internet on our sites, etc. It acts as our central location for files we serve over the internet.

We are a digital product design and development company. When we build a new web or mobile app, the service we choose to use for application and database hosting may vary, but for serving static assets like images and other file downloads, we are always using Amazon S3. S3 combined with Amazon Cloudfront lets us serve static assets to our users and customers without having to worry about performance.

Amazon S3 is used in our mobile applications inorder to have users upload images to the cloud and bring them back to their device. So when users upload an image, it gets sent to Amazon S3 and when an image is shown on the screen we are also pulling it from the same place lowering the load on our apps. It's used as storage for images only.

We use S3 as our primary storage solution. It is also being used as an intermediary between levels of micro-services. The primary storage in S3 is for heavy access, but we also put a CDN in front of it.

This product is being used across the whole organization as a scalable file store for a variety of different file types. It is highly accessible (distributed CDNs) and very easily integrated into our system.

Amazon S3 is used to store all assets from our users. We store profile pictures, message attachments, and other user-related assets. We currently use Heroku to serve the application and it requires an external storage for these kinds of assets. We chose Amazon S3 because it's the most well known and trusted service for this.

We use S3 for reliably and securely storing audios, medical transcriptions, application logs and pretty much everything else. S3 is our go-to cloud storage service as we are already invested in many other core AWS services like EC2, RDS and CloudWatch. We have been using S3 for around 10 years now, and so far, we have never had an issue with it.