2022-01-17 Chapter 3 - AWS Fundamentals
January 18, 2022•287 words
overview-1; Region; A geographical area comprising two or more availability zones.
overview-2; Availability Zone; A logical data centre comprising one or more physical buildings, with redundant power, networking and connectivity.
overview-3; Edge Location; An endpoint for caching content, typically for AWS CloudFront, Amazon's Content Delivery Network (CDN).
overview-4; Key compute services covered in SAA-002 exam (x3); EC2, Lambda, Elastic Beanstalk
overview-5; Key storage services covered in SAA-002 exam (x5); S3, EBS, EFS, FSx, Storage Gateway
overview-6; Key database services covered in SAA-002 exam (x3); RDS, DynamoDB, Redshift
overview-7; Key networking services covered in SAA-002 exam (x5); VPCs, Direct Connect, Route53, API Gateway, AWS Global Accelerator
overview-8; When choosing an AWS region a customer should take into account {{c1::data sovereignty laws}}, {{c1::latency for users}} and {{c1::AWS services' availability}}.
overview-9; AWS and customers approach security via a {{c1::shared-responsibility}} model.
overview-10; In the {{c1::shared-responsibility model}} for security in AWS, if a customer can carry out an action in the AWS console, then they are likely responsible for the consequences of that action.
overview-11; Three examples of tasks where customers take responsibility for security in AWS are {{c1::configuring security groups and users in IAM}}, {{c1::patching EC2 operating systems}} and {{c1::patching databases running on EC2}}.
overview-12; In the {{c1::shared-responsibility model}} for security in AWS, AWS takes responsibility for tasks such as {{c1::data centres physical security and patching RDS operating systems}}.
overview-13; {{c1::Encryption}} is a shared responsibility where the customer has to choose to {{c1::encrypt}} and AWS has to {{c1::encrypt}} effectively.
overview-14; The AWS well-architected framework comprises five pillars: {{c1::operational excellence | security | reliability | performance efficiency | cost optimisation}}.
overview-15; Multi-site and warm-standby are AWS {{c1::disaster recovery patterns}}. In general, multi-site will have {{c1::higher cost}} and {{c1::quicker failover}} than warm standby.