SAA-C02 Flashcards
EC2
ENI Cold Attach = while instance is being launched
ENI Warm Attach = while instance is stopped
ENI Hot Attach = while instance is running
ALB - Application Load Balancer
path-based routing = forward requests based on the URL in the request
host-based routing = forward requests based on the host field in the HTTP header
Failed health check event = ALB stops sending traffic to the instance
RDS
Multi-AZ DB Failover = CNAME is switched from the primary db instance to the secondary
Multi-AZ DB Failover RTO = 1 minute
Multi-AZ DB = Amazon RDS automatically creates a primary DB Instance and synchronously replicates the data to a standby instance in a different Availability Zone (AZ)
Keywords: multi-region = cross-region read replica not Multi-AZ option
Security groups
stateful
specify allow rules, but not deny rules
act at the instance level, not the subnet level
can specify separate rules for inbound and outbound traffic
default includes an outbound rule that allows all outbound traffic
You can change the security groups for an instance when the instance is in the running or stopped state.
EKS
Open source
On-premise and in cloud
DynamoDB
Storing metadata for S3 objects
Managing web session data
ECS
Fargate
NACL
stateless
default configuration of the default NACL is Allow
default configuration of a custom NACL is Deny
NACL rules are evaluated by rule number from lowest to highest and executed immediately when a matching rule is found.
CloudTrail
Does not optimize resource utilization
Spot
Flexible start and end times
EBS Volume
Not encrypted by default
Automatically scales the volume size based on usage
volumes will always be in same AZ as EC2
can be used normally while the snapshot is in progress
point-in-time snapshots = back up the data to Amazon S3 + available on short notice
Types: SSD For exam: general purpose = boot OS data (gp2) = general purpose, 3 IOPS per GiB up to max of 16,000 IOPS per volume (gp3) = general purpose = 4x faster than gp2 (io1) = faster performance up to 64k IOPS (large database OLTP, latency sensitive) (io2) = io2 is same price as io1 + higher durability than io1 (database) (OLTP) HDD (Magnetic storage) Low-cost HDD volume (st1) "Throughput Optimized" Cannot be used to boot (big data, data warehouses, ETL) (sc1) Cold hard disk, lowest cost option (cold data fewer scans and low performance. Static images) Cannot be used to boot If talking about big data, warehouses = Throughput = st1 If talking about transactions/transactional DB = (gp2) for lower cost, performance = (io2)
SNS
CloudWatch/EventBridge
automate monitoring and repair - The reboot alarm action is recommended for Instance Health Check failures
When you reboot an instance, it remains on the same physical host, so your instance keeps its public DNS name, private IP address, and any data on its instance store volumes
Trusted Advisor
NLB
EFS
Keywords:
Concurrent read/write
Linux
Subnets
CloudFormation
Templates have version control
Elastic Beanstalk
Easy mode
DAX
DynamoDB cache
DynamoDB milliseconds to microseconds
SQS
Pull model
Standard = Best effort ordering and you might get a message twice
FIFO = max 300 messages per second, no duplicates
FIFO costs more
FIFO is only option for message ordering or message duplication
Keywords:
lengthy processing time = Measure using SQS queue depth metric
backlog per instance metric
Events:
visibility timeout on a message in an SQS queue expires = message will again be available in the queue for processing
Links:
https: //docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html
https: //docs.aws.amazon.com/autoscaling/ec2/userguide/as-using-sqs-queue.html
SNS
Push model
No visibility timeouts No timings Uses Topics for who and where it goes to Subscribers = Kinesis Data Firehose, SQS, Lambda, email, HTTPS, SMS (fanout), platform application endpoints Message size limit = 256 KB Dead letter queue support, only HTTP get retried FIFO or Standard Only SQS subscriber supports FIFO Encryption at rest is option Access Policies support
Keyword: Multiple things need to see events = Add Topic + subscription in the topic
ASG - Auto Scaling groups
On-Demand Instance limits
Lifecycle hooks = run lambda on (startup, before termination, scale out, scale in events)
Scheduled scaling
Events:
Scale in = Selects the Availability Zone with two instances, and terminates the instance that was launched from the oldest launch template or launch configuration
default health checks for an Auto Scaling group are EC2 status checks only. If an instance fails these status checks, the Auto Scaling group considers the instance unhealthy and replaces
Links:
https: //docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html
https: //docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-scheduled-scaling.html