Please enable JavaScript.
Coggle requires JavaScript to display documents.
AWS (reliability pillars (Failure management (automation, analyze, backup…
AWS
reliability pillars
basic
Foundation
recovery
how to handle change
design principles
recovery
manual recover
need to guess capacity
multiple single points of failure
key service
cloudWatch
reliability Foundation:
manage your AWS service limits
plan your network topology on AWS
High availability
Reliability: change managment
monitor behavior
Amazon SNS notification
Auto scaling to match demand
Failure management
automation
analyze
backup data regularly
recovery and testing
best practice: disaster management
Performance
feature
selection / review / monitoring/ trade-offs
Design principles
technology
Key service: Cloud watch
Performance selection
appropriate resources
performance efficiency : review
Loading Testing.
trade-off
CDN
Cost Optimization
Design principles
Key service for cost optimization: cost allocation tags
Match Supply and Demand
best practice
expenditure awareness
cost allocation tags
optimization over time
trust advisor.
Identifying new services
review
review benefits
learn AWS best pratices.
build and deploy faster
lower and mitigate risks
make informed decisions
8 . apply AWS well-architected
9, well-architecture review
Your team
solution architecture
10.Parnters
review learning.
Earlier is better
no considered decisions
most workload can be improved
Intent
working together to improve
pragmatic proven advice
throughout lifecycle
Security Pillar
design
service
infrastructure Protection
Service-specific Access Controls
Network boundary protection
security: data protection
Encrypted data and mamaget keys
KMS
Detailed loggging
Versioning
storage resiliency
security: Incident Response
easy way
right, pre-deployted tools
conduct game days regularly
Templated "Clean Rooms"
Core 1
VPC
Elastic Compute Cloud
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html
EBS
Elastic Block Store
S3
Core 2
RDS
DynamoDB
IAM
CloudWatch