AWS FAQs Flashcards
EC2 - What monthly uptime is guaranteed?
99.99% (EC2 & EBS)
EC2 - What are A1 instances?
General purpose instane with AWS Graviton Processors
EC2 - What are A1 instances used for?
ARM based instances, that deliver good performance, cost savings with a small available memory footprint
EC2 - Use cases for M5 instances
Higher memory footsprint for intensive Web, mobile, gaming or analytics applications
EC2 - What is burstable performance?
Instance provides a baseline level of performance, but can scale up.
When going over the baseline it consumes CPU credits
EC2 - What are High Memory instances usedd for?
Enterprise Software with large RAM use-cases, SAP e.g.
EC2 - When should a memory-optimized instance be used?
All in-memory applications, like databse or analytics
EBS - What happens to the data when the system terminates?
Unlike local instance storage, EBS storage is persisted and not lost
EBS - What are the differences between the volumes types?
SSD: Transactional workloads based on high IOPS
HDD: Throughput based on MB/s
EBS - Can volumes and snapshots be encrypted?
Yes, both for volumes and snapshots. This enables the user to meet security and compliance requirements
Elastic IP - Explain the limits of IP addresses and the use charges
IPv4 IPs are limited, therefore AWS is commited to keep the use efficiently.
So reserving and IP and not attaching it to an instance will be charged.
An public is not required for all instances
ELB - Difference between Classic and Application Load Balancer
Classic: simple load balacer to target EC2 instances
Application: adanced routing for container based architecture or microservices
Can API calls be tracked?
Yes, with CloudTrail
EC2 - Why should an instance be hibernated?
Hibernated instances can be activated quickly.
Content from memory are peristed to an EBS volume
EC2 - How is EC2 billed?
- Paid by use by the hour or second
- Billings starts and the boot sequence and ends on when the instance is terminated
EC2 - How is traffic beteen AZs or regions billed?
1) Data out to another AWS region + 2) Data in from another region
EC2 - How are AZs isolated from each other?
Physically dinstint with independent infrastructure.
Common points of failure (generator / cooling) is not shared across AZs