AWS Well Architect Flashcards
What are the 5 pillers of a Well Architected
- Resilient Architectures
- Performant Architectures
- Secure Applications and Architectures
- Operationally Excellent
- Cost optimization
EC2 Instance Store
Ephemeral Volumes Only Certain EC2 instance Fixed Capacity Disk type and capacity depends on EC2 instance type Application-Level durability
Design Resilient Architectures
- 1 Choose reliable/resilient storage
- 2 Determine how to design decoupling mechanisms using AWS services
- 3 Determine how to design a multi-tier architecture solution
- 4 Determine how to design high availability and/or fault tolerant solutions
Elastic Block Store
Different Types
Encryption
Snapshots
Provisioned capacity including sometimes IOPS
Independent Lifecycle than EC2 instance
Multiple volumes striped to create large volumes
Amazon EFS
File storage in AWS Cloud Shared Storage Petabyte-scale file system Elastic Capacity Supports NFS v4.0 and v4.1 (NFSv4) protocol Compatible with Linux-based AMIs for EC2 Not Windows compatible
Amazon S3
Consistency model
Storage classes & Durability - standard, standard - IA
Encryption (data at rest) - SSE-S3, SSE-KMS, SSE-C
Encryption (data in transit) - HTTPS
Versioning
Amazon S3 consistence Model
1st write is strongly consistent, updates are eventually consistent. A read right after an update may produce the previous version
Amazon S3 encryption types
SSE-S3 – built in encryption key
SSE-KMS – Key management key is use
SSW-C – Customer provided key
Glacier retrieval types
Expedited – more expensive, up to 5 min
Standard –
Bulk – Slowest but cheapest 12 hours
SQS
Simple Queue Services
Can be used to decouple date flow
Fault Tolerant vs High Availability
High available can have degradation, Fault Tolerant has a higher bar and cannot have degradation
Thoughts on Resilent Arhitectures
Single AZ is never the right answer
AWS managed service is always preferred
Fault Tolerant and High Availability are not the same thing
Expect that everything will fail at some point and design accordingly
Designing Performant Architectures
1) Choose performant storage and databases
2) Apply caching to improve performance
3) Design solution for elasticity and scalability
Which EBS drive type to use
SSD General Purpose 10,000 IOPS, 160 MiB/s
SSD Provisioned IOPS 32,000 IOPS, 500 MiB/s
HDD ThroughPut Optimised 500 IOPS, 500 MiB/s
HDD Cold 250 IOPS, 250 MiB/s
SSD good for random read/write, HDD good for sequential read/write
When to use RDS
1) Complex transactions of comple queries
2) Medium to High query/write rate
3) on more then a single worker node/shard
4) high durability