- Midnight Commander remote connect via Shell link (copy files over SSH) and SFTP link using FISH and public key authentication - Mon, Jan 17 2022
- Root login via SSH and SFTP on EC2 instances running Linux - Wed, Jan 12 2022
- Poll: Will you deploy Windows 11 in 2022? - Mon, Jan 10 2022
Simple Storage Service (S3) ^Amazon Simple Storage Service (S3) was one of Amazon’s first cloud services and is the foundation for many of the AWS services. Various ways exist to store and read objects (files) in S3. You can access S3 objects through a web browser, the AWS console, the AWS Command Line Interface, other AWS services, and third-party (on-premises) tools and applications, and developers can use the S3 API to create new software solutions that are based on S3. You’ve probably heard of Dropbox and Netflix.
Simple Storage Service (S3)
AWS Elastic Block Store (EBS) ^Elastic Block Store (EBS) is not really an independent service, as it requires EC2. EBS volumes are essentially virtual disks that you can mount on virtual EC2 instances (virtual machines). Although it is possible to create and manage EBS volumes through the AWS Management Console or the API, it is not possible (as far as I know) to access the data on EBS volumes through ways other than EC2—unlike with S3
Elastic Block Store (EBS)An EBS volume can range from 1GB to 1TB. If you need more than 1TB, for instance for a database system, you can attach multiple volumes to an EC2 instance and then work with striping. The AWS Management Console and the Command Line Tools allow you to create live snapshots of volumes, which you can use to create new volumes. Some EC2 instances have their root file system on EBS volumes; this enables you to easily create a snapshot of an online or offline virtual machine and then create a new AMI (OS image) from the snapshot.
EBS - SnapshotsYou pay $0.10/GB for provisioned EBS storage and $0.095/GB for snapshots. In addition, Amazon charges $0.10 per 1 million I/O requests. In my experience, the latter costs are negligible in most scenarios.
Glacier ^Glacier is an archiving and backup service. Some confusion exists as to whether Glacier is tape-based because it takes three to five hours until archives are available. Although Amazon is secretive about the storage technology behind it, Glacier most likely stores the data on hard disks. You can back up data to Glacier from S3 through the API. Developers can create archiving applications with .NET and Java libraries. And you can use Amazon’s Storage Gateway (see below) to back up data from your data center to Glacier. The AWS Import/Export service also supports Glacier.
AWS Storage Gateway ^The AWS Storage Gateway enables you to connect your data center to Amazon’s storage services S3 and Glacier. The Gateway can run on an EC2 instance; however, in most scenarios, you will run the Gateway on a VMware ESXi or a Hyper-V 2008 R2, on-prem host.
AWS Storage GatewaySo-called Volume gateways are mounted as iSCSI devices from your on-premises application server and can either be cached volumes or stored volumes. With cached volumes, you only store frequently accessed data on-prem, whereas stored volumes keep all data on-prem and asynchronously back up point-in-time snapshots to S3. In addition to Volume gateways, AWS Storage Gateway supports Gateway virtual tape library (VTL), a service that allows you to back up on-premises data to S3 and Glacier using your on-premises backup software. It should become clear by now that Amazon fully supports hybrid clouds—that is, you can move only parts of your IT to Amazon’s public cloud and keep the rest on-prem in your private cloud. This also applies to Amazon’s database services Relational Database Service (RDS), DynamoDB, SimpleDB, ElastiCache, and Data Pipeline, which will be the topics of my next post in this AWS series.