Which of the following is a typical use case for Amazon S3?
Amazon S3 is an object storage service designed for large objects like media files. Because you can store unlimited objects, and each individual object can be up to 5 TBs, S3 is an ideal location to host video, photo, or music uploads. This information is found in the video “Object Storage with Amazon S3”.
——————————————————————————————-
Amazon EBS would be ideal for a high-transaction database storage layer. Amazon S3 is not ideal, as it’s considered WORM (write once, read many) storage. EC2 Instance Store is ephemeral, and persistence is needed for databases. EFS is for ideal when you have multiple servers that need access to the same set of files. Check out the video “Amazon EC2 Instance Storage and Amazon Elastic Block Store” for more information.
——————————————————————————————-
Amazon EC2 Instance Store is considered ephemeral storage. EBS is considered persistent storage. This content is covered in the video “Amazon EC2 Instance Storage and Amazon Elastic Block Store”.
——————————————————————————————-
Amazon Glacier Deep Archive is Amazon S3’s lowest-cost storage class and supports long-term retention and digital preservation for data that may be accessed once or twice in a year. It is designed for customers—particularly those in highly regulated industries, such as the Financial Services, Healthcare, and Public Sectors—that retain data sets for 7 to 10 years or longer to meet regulatory compliance requirements.
——————————————————————————————-
Amazon S3 is a regional service. However, the namespace is shared by all AWS accounts, so the bucket name must be a globally unique. This information is covered in the video “Object Storage with Amazon S3”.
——————————————————————————————-
When you use Amazon RDS, it places the DB instance into a subnet which is bound by one AZ. For high availability reasons, you should use a Multi-AZ deployment in case one AZ is temporarily unavailable. This information can be found in the Introduction to Amazon Relational Database Service video and corresponding readings.
——————————————————————————————-
Amazon DynamoDB allows for a flexible schema, so each item can have variation in the attributes outside of the primary and secondary key. This information can be found in the Introduction to Amazon DynamoDB video and corresponding reading.
When using Amazon RDS, you are no longer responsible for the underlying environment the database runs on, instead you can focus on optimizing the database. This is because Amazon RDS has components that are managed by AWS. This information can be found in the Explore Databases on AWS Video.
