Amazon S3 (Simple Storage Service) vs. Amazon Virtual Private Cloud (VPC)

For archiving old data that is infrequently accessed it is perfect. You can choose to let it go into cold/glacier storage which saves even further costs but at the expense of accessibility. I like that you can set access rules to automatically move it to the next storage tier after a certain amount of time that it has not been accessed. I also use it a lot with PHP via the API. We have some custom in-house applications that have a fair amount of data uploaded into them. S3 has been a perfect solution to store these files, taking the load off web servers and never having issues with running out of storage.

Incentivized

Amazon Virtual Private Cloud (VPC) is well suited for Early-stage IT-based startups company & Corporate highly cloud scaling-based software [companies].

Incentivized

• Reliable and secure way to store objects in cloud: Storing any type of file(text, pdf, doc, csv, etc) is very easy with S3. Fetching this stored content as and when you require is also pretty easy and can be done using both the console and AWS CLI. Appropriate permissions can be set up for buckets using IAM roles/policies.
• Versioning in buckets: S3 gives you a very handy feature to store multiple versions of objects stored in a bucket.
• Lifecycle policies: You can set up lifecycle policies in S3 that can move your older objects to IA or Glacier. This setup is very easy and can be done within minutes for a bucket.
• Replication: The cross-region replication that S3 provides is wonderful. Beware of the inter-regional data transfer costs though.

Incentivized

• Pricing model & On demand service commitment.
• Well, architectural infrastructure development processing before spending the money.
• AWS VPC are providing hassle-free using with all others services from AWS very easily.
• AWS business support is very helpful & [gives] the right direction according to client’s situations.

Incentivized

• The biggest problem is to rename the bucket. There is no direct way to do it. One need to copy entire content to the different bucket with intended bucket name and then remove the old bucket. Sometimes it creates issues.
• There is no direct way to upload .zip file and extract it to inside the bucket.
• While uploading large files, sometimes you will find a drop of upload speed. I observe it so many times and while checking my internet speed, I find it absolutely perfect. So there must have something wrong on the AWS side.

Incentivized

• The biggest issue with VPC networks is knowing how you can leverage VPC endpoints to ensure your resources within the VPC are not reaching out over the Internet to get to AWS services such as S3 and others.

Incentivized

Due to princing, availability and scalability.

Incentivized

The UI could have some improvements (better filters) and there is a lack of some useful functionality, such as renaming an existing bucket: the latter is much needed in the context of rapidly evolving companies. Overall though, Amazon S3 (Simple Storage Service) is easy to use and to onboard people and tools to, thanks to its various APIs and flexibility.

Incentivized

It depends on your tier within Amazon on how great of support you get. For us we have a dedicated Point of Contact that is great in taking in what we need and discussing it with the S3 team. The best thing is features we need or suggest have a good chance of landing on their roadmap.

Incentivized

S3 is the most mature simple storage service on the web. It has direct competitors from Google and Azure, as well as a bunch of other competitors that focus on different aspects. For example, Backblaze specializes on file backups, and while s3 can also be used for that, Backblaze provides a better price point in exchange for more focused functionality. S3 really shines in that it performs simple things astonishingly well, while also being flexible enough to stretch itself to other situations (data lakes, file mounts, backup/restores systems, web hosting, etc.).

Incentivized

We utilize both AWS and Azure resources for our cloud deployments. The deployment of resources initially was smoother through AWS VPC due to their powerful CLI and Powershell cmdlets. In the past couple of years, the differences between some of the features of AWS VPC and Azure Vnet have diminished. However, the ease of putting things together in a logical flow still belongs in my opinion to AWS.

Incentivized

• Allows us to store large amounts of raw traffic from data providers to allow us to view data our systems received at particular times, in order to reconstruct inputs in case of errors
• Is capable of storing very large amounts of data cheaply without material impact to our business

Incentivized

• AWS VPCs are actively used for following various compliance and regulatory needs such as network separation for PCI DSS. The ability to keep resources and access to those resources controlled through the initial steps of creating VPCs has helped tremendously.

Incentivized