Amazon Simple Storage Service (S3) Reviews

I use Amazon Simple Storage services professionally as part of our data engineering and ETL workflow. We store both raw and processed data in S3, and then use it with AWS Glue, EMR, and Athena. Our ETL jobs generate Parquet and CSV outputs, which are stored in S3 for downstream consumption and for querying in Athena. Overall, the platform has been especially useful because of its durability, scalability, and seamless integration.

There isn’t much to dislike about Amazon Simple Storage Service. It’s a good product.

Amazon Simple Storage Service solves the problem of storing, managing, and accessing data very well. It addresses a major need for our organisation: S3 simplifies large-scale data processing workflows. Our ETL jobs can directly read and write data from S3 without having to worry about storage capacity, server management, or infrastructure scaling. I also don’t need to worry about features like replication, versioning, and encryption, since it already includes them by default.

I use it for data lake storage, including storing logs, backups, and reports. It also works well for hosting files and static assets, supporting ETL pipeline input/output storage, and handling archival needs and disaster recovery.

Managing permissions, lifecycle policies, and large bucket structures can get complicated at scale. As bucket policies become more complex, coordinating large-scale permissions across multiple teams can be difficult without clear governance standards in place.

It eliminates the need to rely on traditional file servers and offers scalable, durable storage for both structured and unstructured data.

What I like most about Amazon S3 is how cost-effective and easy it is to use, especially when dealing with large volumes of files. We use it to store all the attachments coming from Salesforce, and it has helped us significantly reduce our storage costs compared to keeping everything within Salesforce.

We had earlier been using S-Drive, but moving to S3 turned out to be a better decision from a cost and flexibility standpoint. The integration with Salesforce has been smooth, and the whole process feels seamless. Uploading files from Salesforce to S3 is straightforward, and users can easily access and download them whenever needed.

UI can be improved along with the documentation of integrating AWS with other tools like Salesforce

Very easy to use, very quick, very robust and reliable

UI is very basic. Not so easy to work with via the browser. Also, to do more complex stuff you need to write code using the API

We use it for storing our production data in our data lake.

we can store and retrieve any amount of data without worrying about infrastructure, and it just works reliably.It saves a lot of time on storage management and lets me focus more on building features rather than handling infrastructure.I use s3 on daily basis for upload , get data.It very easy to integrate only need to have keys.Implementation is also easy aws provides sdk for the same.

It doesn’t behave like a traditional file system, which can make certain operations (like renaming or updating files) less straightforward.Pricing also get confusing and sometimes unexpectedly high.

In my case, I’m dealing with multiple projects and a huge volume of images and assets (like VR tours, floor plans, SVGs, etc.), so managing storage locally or on a traditional server would be complex and not scalable.

Amazon Simple Storage Service has unmatched durability (99.99999999%), has virtual unlimited scalabilty and a simple API

Amazon Simple Storage Service (S3) has a complex permisssion model (ACLs, Bucket polices, IAM) that can be confusing. It has no built in folder level move or rename. it also has unexpected costs if you forget lifecyle policies or have high interest rates

Amazon S3 solves durable and scalable object storage without the management of hardware.

I appreciate the granular permission controls and the strong focus on high availability.

Some parts of the setup process tend to be a bit more complicated than they need to be.

Storing application files.

Amazon S3 offers reliable, scalable, and highly durable object storage, with smooth integration across the AWS ecosystem. I find it easy to use, and the setup is straightforward for storing, retrieving, and managing large volumes of data. Its flexibility, the range of storage classes, and strong security controls make it well suited for both frequent access and archival needs. Integration with services such as Lambda, CloudWatch, and EC2 also supports automated workflows and more efficient data management.

While S3 is extremely reliable, managing complex permissions and policies can be challenging, especially for beginners. Costs can also add up quickly if you rely heavily on versioning or perform frequent data transfers. In addition, working with very large buckets containing millions of objects can feel cumbersome without solid organization and well-defined lifecycle policies.

S3 addresses the challenge of scalable, durable data storage. It enables our team to store large volumes of data reliably while maintaining strong availability and security. Its automated integrations with other AWS services also help streamline workflows, optimize costs, and reduce operational overhead, making day-to-day management simpler.

S3 integrates well with the broader AWS ecosystem, making it easy to connect storage with compute, analytics, and backup workflows. Features such as versioning, lifecycle policies, and storage classes help us manage data efficiently, control costs, and enforce retention requirements. Access control through IAM policies and bucket-level permissions allows us to apply the principle of least privilege across teams and applications.

Security is another major strength from an admin perspective. S3 supports encryption at rest and in transit, detailed access logging, and integration with monitoring and auditing tools. These capabilities help meet institutional security and compliance requirements while maintaining operational flexibility.

There are some challenges when using S3 at scale. Cost management requires careful monitoring, especially with data egress, request rates, and long-term storage. From an administrative standpoint, misconfigured permissions or overly permissive policies can pose risks if not governed properly, which makes strong internal controls and regular reviews essential.

AWS S3 offers highly durable and scalable object storage, integrating smoothly with the broader AWS ecosystem. Its features, such as versioning, lifecycle policies, and cross-region replication, make it well-suited for use cases like backups, big data, and application storage. The security options, including encryption and IAM policies, are both robust and straightforward to set up.

Pricing can get complicated for large-scale deployments, particularly when there are frequent data transfers and retrievals. Additionally, the learning curve for new users may be quite steep if they are not already familiar with AWS services.

We rely on AWS S3 to store our application logs, backups, and large data sets. This service has enabled us to achieve high availability and durability without the need to manage any physical infrastructure. The pay-as-you-go model also provides us with cost efficiency and allows us to scale seamlessly as our data requirements increase.