Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2016 Utah Cloud Summit: Architecting on AWS - Best Practices


Published on

An overview of best practices for architecting on AWS. Covers best practices for security, reliability, performance, and cost optimization.

Published in: Technology
  • Be the first to comment

2016 Utah Cloud Summit: Architecting on AWS - Best Practices

  1. 1. Architecting on AWS: Best Practices Asha Chakrabarty, AWS Solutions Architect
  2. 2. The AWS Well-Architected Framework • 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. 3. Pillars of Well-Architected Security Reliability Performance Efficiency Cost Optimization
  4. 4. Security • The ability to protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies. • Data protection • Privilege management • Infrastructure protection • Detective controls
  5. 5. Security is shared between 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. 6. Key AWS Services for 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. 7. Reliability • The ability of 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. 8. Key AWS Services for Reliability • Foundations: - AWS IAM - Amazon VPC • Change Management: - AWS CloudTrail - AWS Config • Failure Management: - AWS CloudFormation
  9. 9. Performance Efficiency • The ability 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. 10. Key AWS Services for 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. 11. Cost Optimization • The ability to avoid or eliminate unneeded cost or suboptimal resources. • Matched supply and demand • Cost-effective resources • Expenditure awareness • Optimizing over time
  12. 12. Key AWS Services for 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. 13. Design Principles • The Well-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. 14. Questions • A set of questions you can use to evaluate how well an architecture is aligned to AWS best practices.
  15. 15. Next Steps • Read the whitepaper • Apply it to your architectures • Schedule time for an architectural review with your Solutions Architect
  16. 16. Thank you!