Upload
brett-gillett
View
377
Download
3
Embed Size (px)
Citation preview
Best Practices for Web Infrastructure
on Amazon Web Services
Softchoice: an IT solutions & managed services company.
• $1 Billion + USD revenue• 46 North American Locations • 1,200 Employees
• Over 150 Hybrid IT Engineers and Architects • Dedicated Cloud Practice• Community of highly tenured cloud technologists• Top 7 of Global Managed Service Providers
How to Contact meBrett Gillett, Cloud Practice Lead
Twitter: @brettg98 LinkedIn:https://ca.linkedin.com/in/brettgillett
Agenda• Web Infrastructure Survey • Why? • Field of Dreams • AWS Services & Reference Architecture • Best Practices • “Gotchas” - Lessons learned • How we can help • Q&A
Too long to turnaround requests
Difficulty simulating test & development
Scaling to meet traffic demands
Outgrowing current infrastructure
Lack of Budget
What are your biggest challenges aroundweb infrastructure?
1
2
3
4
5
21%
37%
17%
15%
10%
“Demand for our website is spiky and can lead to bad response times”
“We don’t want to have to buy new hardware”
“We need to improve the availability of our website”
“We spend too long managing the infrastructure our website runs on”
Why?
Field of Dreams
VPC EC2 AutoScaling ELB Route53
S3RDS IAM Cloud Trail Config
Reference Architecture in AWS• Security from day one • Multiple availability
zones • Hybrid deployment • Managed database • Bootstrap EC2
Best Practices
Flickr: citylovesyou_ffm
Design for Failure
Security
Flickr: Holly Victoria Norval
“Right Sizing”Flickr:Carlos ZGZ
Horizontal ScalingFlickr: Emilian Robert Vicol
Flickr: Luke Ma
Use PaaS(Platform-as-a-Service)
Use Reserved Instances
Use Reserved Instances
(where it makes sense)
Flickr:TheGabeC
SummaryBest Practice• Things will fail - design for failure • Start with security in mind from day one• Make sure you’re not paying for infrastructure that’s not being used
• Use the smallest EC2 instances you can and scale horizontally
• Leverage PaaS where it makes sense to lessen the administrative burden
• Use Reserved Instances (RIs) when (and where) it makes sense.
“Gotchas”Lessons Learned
Understand Costs
UnderstandCosts
Flickr:Images Money
Reserved Instances
Flickr:TheGabeC
Reserved Instances
Pace ofInnovation
Flickr:Michael Gil
Drift
Drift
Flickr: Nic Redhead
Summary“Gotchas”• Understand how AWS services are billed - no surprises • Beware the “double-edged” sword known as Reserved Instances (RIs)
• Find ways to keep pace • Monitor and control “Drift” in your AWS infrastructure
Customer Story
How we can help
How we can helpSoftchoice Services - Web Foundations Accelerator
Services Highlights• Get you started fast in AWS
• Security from day one • Highly available infrastructure
How we can helpSoftchoice Services - Keystone for AWS
Services Highlights• Act as an “extension of your bench”
• Get access to a team of AWS experts
• On-going monthly insights • See on-going value from services in AWS
How we can helpSoftchoice Services - AWS Analyzer
Services Highlights• Full audit of existing AWS infrastructure
• Ensure that your getting value for your spend
• Ensure that your AWS environment is secure
How to Contact meBrett Gillett, Cloud Practice Lead
Twitter: @brettg98 LinkedIn:https://ca.linkedin.com/in/brettgillett
https://creativecommons.org/licenses/by/2.0/