Amazon S3 Reviews

I work with AWS Cloud since 2021. I have experience with AWS IAM for user management and love using EC2. I heavily use S3 and VPC. 

Additionally, I'm focused on cloud security products like security groups, policies, permissions, Security Hub, and Inspector.

S3 is a great service offering numerous possibilities. It allows for storing objects and files of various types. I appreciate its capability to create static websites and integrate with services like CloudFront, EC2, and DynamoDB. 

Despite being focused on security, I leverage features such as cryptography and integration with CloudTrail.

We host applications on Amazon Web Services (AWS). We set up EC2 for running various applications and utilize S3 storage for data storage. For databases, we use MySQL and Microsoft API instead of AWS databases.

Amazon S3 is easily scalable and provides fantastic performance, especially in comparison to other cloud solutions like OCI and Azure. Its availability is high, almost at 99%, which is important for ensuring reliable access to stored data.

I use Amazon S3 for storing objects, like files and documents. It is particularly valuable for personal projects where some of the files are stored there.

Your data is secured, and you don't have issues with running out of storage. It provides a positive impact on operations.

My primary use case for Amazon S3 includes using it for backups and deploying a website on an S3 bucket. Additionally, for my organization, it is used to deploy websites and leverage its architecture for deploying applications.

Amazon S3 has been beneficial because it is cost-effective and simplifies my data management through its life cycle policy, which automatically manages data I no longer need.

One of the use cases is to store Veeam backups. It's more complex than Veeam, which is simpler.

S3 is essentially object storage, a place to store data that you can set up however you want. We usually connect to S3 using the API. It requires an access key and a secret key, which we input into the application we're connecting from. Then, that application can see the S3 bucket as if it were local, and we can copy stuff into it.

The best thing about S3 is the security. I can enable encryption at rest using a KMS server, a key management server. Key management servers encrypt data, and you need the key to decrypt it. Without the key, you can't access the data. Amazon allows you to use your own servers or theirs. They offer Amazon encryption, which you decide on when you create the bucket. The bucket also has all the other features like versioning.

We can do versioning and life cycles. The biggest plus for me as a storage admin is the different tiers: standard, infrequent access, Glacier, and Glacier Deep Archive. The differences between these tiers are cost and data retrieval speed. Standard tier data is considered "hot," meaning it's accessible anytime, but it's expensive.

If you want to archive data you won't need often, or if you have ample time to retrieve a backup, the most cost-effective option is Glacier Deep Archive. It's very cheap, but the disadvantage is that when you request data, it takes up to 24 hours to become accessible.

There are no limitations on how much you can store, but the biggest limitation is that you cannot use Glacier Deep Archive from the console. You can't go into the AWS console and copy something directly into Deep Glacier, but you can do it from the command line. If you have programmatic access, there's a command to put data directly into Glacier Deep Archive.

We don't use anything AI on AWS right now. The AI stuff isn't really too useful for us yet. We're just playing around with Copilot from Microsoft, which is more on the Azure side. We haven't leveraged any AWS AI stuff yet. We've basically just been playing around with Amazon Bedrock, but haven't done anything in production with it.

The primary use case for Amazon S3 is as a storage service for structured and unstructured data. I use it for storing data for websites with different domains. My company and I use it internally for cloud-based services.

The most valuable features of Amazon S3 include scalability, durability, reliability, security, access control, cost-effectiveness, performance, speed, data management, analytics, static website hosting, seamless integration with other AWS services, and budgeting features. 

I find the cost-effective models particularly suitable for our needs. The performance with high-speed data retrieval and support for large file uploads is crucial. Security measures like encryption, access controls, and the block public access feature are also important. 

Another useful feature is the MFA delete function that prevents accidental and malicious data deletions.

I use Amazon S3 mostly to store files. Instead of storing files in a blob, I store them in Amazon S3 and give the reference to my database. At any point in time, if I want to process the files, I get them from Amazon and process them.

Amazon S3 is scalable and available. It's particularly useful for archiving data; I can configure it to keep files for six months before archiving them to Glacier. This flexibility in retrieving data or storing it makes it valuable.