Downloaded 67 times
Uploaded by1Strategy
2016 Utah Cloud Summit: Architecting on AWS - Best Practices
The document outlines the AWS Well-Architected Framework, which emphasizes architectural best practices across security, reliability, performance efficiency, and cost optimization. It highlights key principles, foundational areas, and AWS services that help in designing efficient architectures while addressing risks and managing costs. Finally, it encourages readers to read further, apply the principles to their architectures, and engage with a solutions architect for a review.
2016 Utah Cloud Summit: Architecting on AWS - Best Practices
- 1. Architecting on AWS: BestPractices Asha Chakrabarty, AWS Solutions Architect
- 2. The AWS Well-ArchitectedFramework • Increase awareness of architectural best practices • Addresses foundational areas that are often neglected • Consistent approach to evaluating architectures • Composed of: • Pillars • Design principles • Questions
- 3. Pillars of Well-Architected SecurityReliability Performance Efficiency Cost Optimization
- 4. Security • The abilityto protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies. • Data protection • Privilege management • Infrastructure protection • Detective controls
- 5. Security is sharedbetween AWS and you AWS Foundation Services Compute Storage Database Networking AWS Global Infrastructure Regions Availability Zones Edge Locations Client-side Data Encryption Server-side Data Encryption Network Traffic Protection Platform, Applications, Identity & Access Management Operating System, Network, & Firewall Configuration Customer applications & contentCustomers Customers have their choice of security configurations IN the Cloud AWS is responsible for the security OF the Cloud
- 6. Key AWS Servicesfor Security • Data Protection: - Elastic Load Balancer - Amazon EBS, Amazon S3, Amazon RDS, AWS KMS • Privilege Management: - AWS IAM, MFA • Infrastructure Protection: - Amazon VPC • Detective Controls: - AWS CloudTrail - Amazon CloudWatch - AWS Config
- 7. Reliability • The abilityof a system to recover from infrastructure or service failures, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues. • Foundations • Change management • Failure management
- 8. Key AWS Servicesfor Reliability • Foundations: - AWS IAM - Amazon VPC • Change Management: - AWS CloudTrail - AWS Config • Failure Management: - AWS CloudFormation
- 9. Performance Efficiency • Theability to use computing resources efficiently to meet system requirements, and to maintain that efficiency as demand changes and technologies evolve. • Compute • Storage • Database • Go Global
- 10. Key AWS Servicesfor Performance Efficiency • Compute: Auto Scaling • Storage: - Amazon EBS - Amazon S3 - Amazon Glacier • Database: - Amazon RDS - Amazon DynamoDB • Go Global: - Global presence with regions spanning the globe - Amazon CloudFront
- 11. Cost Optimization • Theability to avoid or eliminate unneeded cost or suboptimal resources. • Matched supply and demand • Cost-effective resources • Expenditure awareness • Optimizing over time
- 12. Key AWS Servicesfor Cost Optimization • Matched supply and demand: Auto Scaling • Cost-effective resources: - Reserved Instances (RI): prepaid capacity to reduce your cost - AWS Trusted Advisor: inspect your AWS environment and find opportunities to save money. • Expenditure awareness: - Amazon CloudWatch alarms - Amazon Simple Notification Service (SNS) notifications • Optimizing over time: - The AWS Blog and What’s New section on the AWS website - AWS Trusted Advisor
- 13. Design Principles • TheWell-Architected Framework has identified a set of design principles to facilitate good design in the cloud: • General design principles • Pillar-specific design principles Automate responses to security events: Monitor and automatically trigger responses to event-driven, or condition-driven, alerts.
- 14. Questions • A setof questions you can use to evaluate how well an architecture is aligned to AWS best practices.
- 15. Next Steps • Readthe whitepaper • Apply it to your architectures • Schedule time for an architectural review with your Solutions Architect
- 16.
Editor's Notes
- #3 Why is it important? We understand the value in educating our customers on architectural best practices for designing reliable, secure, efficient, and cost-effective systems in the cloud As part of this effort, we developed the AWS Well-Architected Framework, which helps you to understand the pros and cons of decisions you make while building systems on AWS. We believe that having well-architected systems greatly increases the likelihood of business success.
- #7 Data protection: Services such as Elastic Load Balancing, Amazon Elastic Block Store (EBS), Amazon Simple Storage Service (S3), and Amazon Relational Database Service (RDS) include encryption capabilities to protect your data in transit and at rest. AWS Key Management Service (KMS) makes it easier for customers to create and control keys used for encryption. Privilege management: IAM enables you to securely control access to AWS services and resources. Multi-factor authentication (MFA), adds an extra layer of protection on top of your user name and password. Infrastructure protection: Amazon Virtual Private Cloud (VPC) lets you provision a private, isolated section of the AWS cloud where you can launch AWS resources in a virtual network. Detective controls: AWS CloudTrail records AWS API calls, AWS Config provides a detailed inventory of your AWS resources and configuration, and Amazon CloudWatch is a monitoring service for AWS resources.
- #9 Foundations: AWS Identity and Access Management (IAM) enables you to securely control access to AWS services and resources. Amazon VPC lets you provision a private, isolated section of the AWS cloud where you can launch AWS resources in a virtual network. Change management: AWS CloudTrail records AWS API calls for your account and delivers log files to you for auditing. AWS Config provides a detailed inventory of your AWS resources and configuration, and continuously records configuration changes. Failure management: AWS CloudFormation enables the template creation of AWS resources and provisions them in an orderly and predictable fashion.
- #11 Compute: Auto Scaling is key to ensuring that you have enough instances to meet demand and maintain responsiveness. Storage: Amazon EBS provides a wide range of storage options (such as SSD and PIOPS) that allow you to optimize for your use case. Amazon S3 provides reduced-redundancy storage, lifecycle policies to Amazon Glacier (archival storage), and server-less content delivery. Database: Amazon RDS provides a wide range of database features (such as provisioned IOPS, and read replicas) that allow you to optimize for your use case. Amazon DynamoDB provides single-digit millisecond latency at any scale. Space-time trade-off: AWS has regions across the globe, allowing you to choose the optimal location for your resources, data, and processing. Use Amazon CloudFront to cache content even closer to your users.
- #13 Matched supply and demand: Auto Scaling allows you to add or remove resources to match demand without overspending. Cost-effective resources: You can use Reserved Instances and prepaid capacity to reduce your cost. AWS Trusted Advisor can be used to inspect your AWS environment and find opportunities to save money. Expenditure awareness: Amazon CloudWatch alarms and Amazon Simple Notification Service (SNS) notifications will warn you if you go, or are forecasted to go, over your budgeted amount. Optimizing over time: The AWS Blog and What’s New section on the AWS website are resources for learning about newly launched features and services. AWS Trusted Advisor inspects your AWS environment and finds opportunities to save money by eliminating unused or idle resources or committing to Reserved Instance capacity.
- #16 The whitepaper is available on our website