Click, Click, Cloud.
Really!
Stuart Speers
at AWS Summit 2014
Agenda
→  Introduction and set the scene
→  I.T. is too expensive
→  I.T. Strategy
→  Design Considerations
→  Case Study
...
Technology Challenges!?
I.T. is too expensive!
AWS step in the right direction
→  We all make the same expensive mistakes
§  Sorry “learning's”
→...
Server Huggers!?
You know who you are!
I.T. Strategy
Needs depth across technologies
→  Often defined at a high level for the business
→  Lacks detail
§  e.g. A...
AWS Design Considerations
Reality check
→  AWS provide an excellent framework
§  Needs understanding to gain full benefit...
Case Study – A Website
Business requirements
→  Q - What sort of load do you expect?
§  Don’t know how busy it will be bu...
Case Study – A Website
A typical AWS design
Case Study – A Website
The impact of loose requirements!
Case Study – A Website
Key Lessons
→  Accurate business requirements are critical
§  Avoid bill shock
→  How can you crea...
Thank you for your time
www.enterpriseit.co.nz
Upcoming SlideShare
Loading in …5
×

AWS Summit Auckland 2014 | Click, Click, Cloud! Really! - Session Sponsored by Enterprise IT

629 views
525 views

Published on

Enterprises typically deploy infrastructure solutions with an approved strategy, detailed design and robust support process. Yet many NZ organisations are migrating applications to the cloud without strategy and often design! In this session we will discuss AWS cloud strategy, the importance of design, standards and security to help your organisation migrate to the cloud. We will look at a case study of deploying AWS based on having a strategy and design and then what can unfold without one.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
629
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

AWS Summit Auckland 2014 | Click, Click, Cloud! Really! - Session Sponsored by Enterprise IT

  1. 1. Click, Click, Cloud. Really! Stuart Speers at AWS Summit 2014
  2. 2. Agenda →  Introduction and set the scene →  I.T. is too expensive →  I.T. Strategy →  Design Considerations →  Case Study →  Key lessons →  Q&A
  3. 3. Technology Challenges!?
  4. 4. I.T. is too expensive! AWS step in the right direction →  We all make the same expensive mistakes §  Sorry “learning's” →  AWS Framework is excellent! §  Reliable & scalable §  Cost effective §  HA & DR →  Strategy is lacking! §  It’s to high level §  How can you measure success?
  5. 5. Server Huggers!? You know who you are!
  6. 6. I.T. Strategy Needs depth across technologies →  Often defined at a high level for the business →  Lacks detail §  e.g. App level SLA, RTO, RPO. §  Backup / recovery §  Monitoring §  Consolidation / rationalisation →  Critical to AWS success §  How can you design a solution without a strategy?
  7. 7. AWS Design Considerations Reality check →  AWS provide an excellent framework §  Needs understanding to gain full benefits and avoid bill shock §  Must complete a detailed design →  Customer expectations need realigning §  Click, Click, Cloud – will not meet requirements §  AWS still needs a detailed design §  Testing is still required §  Support is still required
  8. 8. Case Study – A Website Business requirements →  Q - What sort of load do you expect? §  Don’t know how busy it will be but could be huge! §  Must be scalable though! →  Q – What about SLA’s - HA and DR? §  Needs to be redundant as revenue generating →  Q – When do you need it? §  We want to launch in 5 days, so ready in 3 days, thanks.
  9. 9. Case Study – A Website A typical AWS design
  10. 10. Case Study – A Website The impact of loose requirements!
  11. 11. Case Study – A Website Key Lessons →  Accurate business requirements are critical §  Avoid bill shock →  How can you create a design without a strategy §  How can you measure success? →  Need to understand AWS framework and terminology – need validation of design →  Still need detailed design: §  Standards, security, monitoring, backups, etc
  12. 12. Thank you for your time www.enterpriseit.co.nz

×