Section 7: EC2 Instance Store

Included Sections are EBS Overview,

EBS (Elastic Block Store)

is a network drive you can attach to your instances while they run. And it allows your instances to persist data, even AFTER termination.

EBS can only be mounted to one instance at a time

True

EBS are bound to one specific availability zone.

True

EBS Volume uses

the network to communicate the instance since its a network drive and not a physical one, which means there might be a bit of latency.

EBS Delete on Termination Attribute

Controls the EBS behavior when an EC2 instance terminates

By default the root EBS volume is

deleted (attribute enabled)

Use case for EBS Delete on Termination Attribute

preserve root volume when instance is terminated

EBS snapshots

makes a backup (snapshot) of your EBS volume at a point in time. (Can copy snapshots across AZ or Region

EBS Snapshot Archive

moves a snapshot to an “archive tier” that is 75% cheaper

Fast Snapshot Restore (FSR)

Force full initialization of snapshot to have no latency on the first use.

AMI (Amazon Machine Image)

Are a customization of an EC2 instance where you can add your own software, config, OS, and monitoring

AMIs are built for a specific region

True and can be copied across regions

You can launch Ec2 Instances from

-A public AMI: AWS provided
-Your Own AMI: Make and maintain yourself
-An AWS Marketplace AMI: an AMI someone else made

EC2 Instance Store

a high performance hardware disk; good for buffer/cache/scratch data/temporary content.

EC2 Instance Store loses there storage if they are stopped?

True

EBS Volume Types

-General Purpose SSD

-Provisioned IOPS SSD (PIOPS)

-Hard Disk Drives (HDD)

-Throughput Optimized HDD (ST1)

-Cold HDD (SC1)

General Purpose SSD (gp3 & gp2)

Cost-effective storage and low latency. It balances price and performance for a wide variety of workloads.

gp3

can interpedently set the IOPS and throughput

gp2

IOPS and throughput are linked together

Provisioned IOPS

great for databases workloads (sensitive to storage performance and consistency)

Hard Disk Drives (HDD)

cannot be a boot volume

Throughput Optimized HDD (ST1)

low cost HDD volume designed for frequently accessed, throughput-intensive workloads

Cold HDD SC1

Lowest cost HDD volume used for less frequently accessed workloads

EBS Multi-Attach

attaches the same EBS volume to multiple Ec2 Instances in the same AZ (up to 16 instances at a time)

EBS Encryption leverages keys from

KMS (AES-256)

Amazon EFS (Elastic File System)

is a managed network file system that can be mounted on many Ec2 instances. It is compatible with Linux based AMI (not windows)

EFS Scale

1000s of concurrent NFS clients, 10 GB+/s throughput

Performance mode

set an EFS creation time

Throughput mode

-Bursting, Provisioned, Elastic

Bursting

a way for you to have throughput scale with amount of storage your using and going a little over

Provisioned

set your throughput regardless of storage size

Elastic

automatically scales throughput up or down based on workloads (used for unpredictable workloads)

Storage classes

-standard: for frequently accessed files

-Infrequent Access: cost to retrieve files, lower price to store

-Archive: rarely accessed data

Instance store is physically attached to EC2 Instance

true

EC2 Instance store provides best disk I/O performance

true

You have just terminated an EC2 instance in us-east-1a, and its attached EBS volume is now available. Your teammate tries to attach it to an EC2 instance in us-east-1b but he can't. What is a possible cause for this?

EBS volumes are locked to an Availability Zone

Which of the following EBS volume types can be used as boot volumes when you create EC2 instances?

gp2,gp3,io1,io2

You would like to encrypt an unencrypted EBS volume attached to your EC2 instance. What should you do?

Create an EBS snapshot of your EBS volume. Copy the snapshot and tick the option to encrypt the copied snapshot. Then, use the encrypted snapshot to create a new EBS volume.

You have a fleet of EC2 instances distributes across AZs that process a large data set. What do you recommend to make the same data to be accessible as an NFS drive to all of your EC2 instances?

Use EFS

You have launched an EC2 instance with two EBS volumes, Root volume type and the other EBS volume type to store the data. A month later you are planning to terminate the EC2 instance. What's the default behavior that will happen to each EBS volume?

The Root volume type will be deleted and the EBS volume type will not be deleted.

You can use an AMI in N.Virginia Region us-east-1 to launch an EC2 instance in any AWS Region.

False

You would like to have a high-performance local cache for your application hosted on an EC2 instance. You don't mind losing the cache upon the termination of your EC2 instance. Which storage mechanism do you recommend as a Solutions Architect?

Instance Store

You are running a high-performance database that requires an IOPS of 310,000 for its underlying storage. What do you recommend?

Use an Ec2 Instance Store