5. AWS Proserve
Supporting enterprises and partners to accelerate cloud adoption.
Global practice with local teams.
Custodians of the AWS Cloud Adoption Framework.
Medium to long term engagements Strategic, business, operational and technical.
On Demand model – you pay for what you use.
Complements other AWS services e.g.
Solutions Architects, Technical Account Managers etc.
Compliments external AWS partners
7. What do we mean by ‘I.T. Transformation’ ?
Old
New
Time
Benefits • IT Modernization efforts existed since
mainframe migrations
• The focus is on the transition, not on the target
state
• Incorporates change management and
enablement
• Major focus of Enterprise Architecture
8. IT Transformation with AWS
Practice of modernizing the IT function and operating
model, thus enabling companies to effectively include AWS
in their IT environments. IT Transformation focuses on the
journey toward the end state by:
• Managing issues and risks – Project management and scope creep
• Managing customer’s anxiety – Communicate often and effectively
• Building an achievable roadmap – Appropriately plan the transition
9. Transformation goals
Current State
• AWS Awareness – possibly
already tested.
• Some business units may
already be using AWS.
• Lack of confidence in ability to
execute.
• Success Measures not defined
• Existing infrastructure due a
refresh or validity in question.
Cloud IT
Transformation
Future State
• Ability to enter new markets
quickly & safely
• Business focus.
• Increased IT Agility /
Responsiveness.
• Go global instantly
• Infrastructure cost savings.
• Attract & Retain Talent.
10. Transformation with AWS
• Rapid time to live.
• Flexible and testable infrastructure.
• Scalable - up and down.
• Global availability.
• Broad and deep.
• No commitment needed.
• Low cost of entry.
• Tried and tested.
12. Transformation tenets
Focus on the goal and plan a measurable way forwards.
Select an adoption framework.
Build a journey roadmap that is achievable but challenging.
Stick to the plan and move quickly.
Be BOLD.
Build a Cloud Competency Centre and move beyond migration.
13. Cut through the noise
Governance Information Management Strategy Strategic
Planning IT Operations Modernization ROI IT Capability Assessment
IT Process Management CostIT Workforce Optimization
Business Plan Analysis Financial Planning Business Value
Education Benefits Analysis IT Strategy Enterprise Architecture
IT Roadmap Total Cost of Ownership Return on Investment
Business Security Case Development Compliance Hybrid Computing
14. Identify your measures for success.
What is the main business driver ?
• Disaster Recovery or High Availability
• Cost
• Get out of the DC
• Control
• Agility
• …
Can you see inconsistencies within the business?
15. Cloud Adoption Framework (CAF)
In the journey to the
cloud, AWS has
identified 7 key
perspectives
that are important to
consider when
moving to the cloud.
16. Identifying what needs to be done.
We examine each of
these perspectives with
you to identify the
goals, implications,
and specifically what
needs to be addressed
17. Develop an Adoption Roadmap (sample)
Discovery
Workshop
Cloud
Business
Case
Define Security
Requirements
Define Network
Environment
Define
Governance
Structure
Operational
Integration
Security
Operations
Playbook
Cloud
Environment
Optimization
Application
Portfolio
Analysis
Cost and
Billing
Analysis
Training and
Certification
Define Cloud
Environments
Define EA
Policies and
Practices
18. Possible transformation workstreams.
Constant engagement.
3 Year Cloud Transformation Implementation Roadmap
Cloud Business Cases
Application Portfolio
Assessment
Organisational Change Roadmap
Wk2 Wk4 Wk6 Wk8 Wk10 Wk12
Cloud Maturity Assessment
Application PoC
Demonstrable
benefit
Business stream
Operations stream
Tech and Tools stream
Future state
CCC / CCoE
Governance and policy
Training / resource
Execute application migration plan
Build application migration plan
Security
19. Move quickly.
Enterprise wide
Cloud Operating Model
TIME
All In
Legacy
environment
Executive
Sponsorship
,
Hybrid
Architecture
s
Contractual
Framework,
Professional
Services/
Partner
Engagement
Cloud
Centre of
Excellence
Proof of
Concept
Tactical
Project 1
Enterprise-
wide Dev
Ops/ CICD
Capability
Continuous
Improvement
Framework
Cloud
Operating
Model
Circles of
Learning
WHITESPACE
SCALE
PLATFORM (All in)
Tactical
Project 2
See the viability of
the AWS platform
Define Objectives &
Metrics
Better understand
how the AWS
platform benefits
your business
Build Landscapes &
Automation
Strengthen
relationship due to
close collaboration
& mutual goals of
POC.
Application
Migration
Roadmap
Infrastructure Centric Application Centric
CloudValue
Level of Adoption
20. Cloud Competency Centre.
• Seize opportunities within the new
team
– Agile approach
– Embrace DevOps practices
– Infrastructure as code
– Explore new tools and techniques
– Automate as much as possible
– Evangelise cloud within the business
21. Example Cloud Competency Centre structure.
Cloud
Competency
Centre
Co-ordinator
Architects
Application
Engineer
Security
Engineer
Knowledge
Support
Operations
Finance
Legal
24. Strategy: Migrate existing applications.
Requires taking an application inventory and identifying which applications
would be most effective running in the AWS cloud and at what juncture.
Migrated 500 web properties
In 5 months
Migrated clinic trials simulations platform
New product websites in 2 days vs. 2 weeks Simulations in 1.2 hours vs. 60 hours. 64%
reduction in costs
https://aws.amazon.com/solutions/case-studies/unilever/ https://www.youtube.com/watch?v=Vi96WrxAS
go
25. Phased strategy for migration.
Cloud
Assessment
Phase
•Assess Costs
•Assess
Architecture
•Document
current
inventory &
workloads
•Assess
Security
Proof of
Concept
Phase
•Learn AWS
•Build a pilot
•Build Support
within the
organization
Data
Migration
Phase
•Leverage
different
storage options
•Migrate
Application
Migration
Phase
•Lift & Shift
Migration
•Hybrid
Migration
Leverage the
Cloud Phase
•Auto-scaling
•Automation
•Elasticity
•High Availability
Optimization
Phase
•Utilization
•Monitoring
•Efficiency
•Performance
•Re-engineering
26. Trust your support network.
Customer Business Functions
Customer IT
AWS Training
& Certification
AWS
Proserve
AWS SA, TAM
and community
28. Transforming the IT model.
Management
Tools
Architecture
Operations
Server Team
Storage Team
Network Team
Database Team
Platform Team Desktop
App 1 App 2 App 3
Business Unit 1 Business Unit 2
IT Shared Services
Security
29. Transforming the IT model.
App 1 App 2 App 3
Business Unit 1 Business Unit 2
Security
Cloud
Competency
Centre
Agile IT
Governance
Tools
Reporting
Automation
Tools
Architecture
Operations
Server Team
Storage Team
Network Team
Database Team
Platform Team Desktop
IT Shared Services
30. Maturing the IT model.
Agile ITTraditional IT
Agile ITTraditional IT
Transition projects, workloads and people into the new agile cloud
organisation
33. DynamoDB
Create User
Update profile
Send message
Latest messages
Back end
Amazon
Cognito
Javascript
& HTML5 app
Mobile app
Front end
Server-less Backend Applications
35. Keep the business in the loop.
Constant education back to the business on :
• Progress with against key business drivers.
• Cloud technology with concrete examples.
• Benefits that you see but didn’t anticipate.
37. Where this is working.
Shell is a global oil and gas
company
Core operational applications
running in production on AWS
With AWS, Shell has elasticity –
the ability to expand and contract
IT infrastructure as needed
Shell’s Cloud Journey: Operationalising the Cloud Strategy
38. • Founded in 1920, Qantas is Australia’s largest
domestic and international airline
• The airline wanted to develop an in-flight application
that would aggregate and present passenger
information to cabin crew
• By developing the application on AWS, Qantas can
quickly and inexpensively provide cabin crew with
insights into customer needs and wants
Qantas Operates In-Flight Application with Near 100% Availability
Using AWS
39. Vodafone Italy Migrates to AWS and Creates a Secure
Environment for Customer Transactions While Reducing Capital
Costs by 30%
• Vodafone Italy, based in Milan, provides mobile
services for more than 30 million customers
• Customers can buy additional credit—a process
known as “top up”—for SIM cards and as
transactions increased, the company wanted to
offer customers a secure way to top up using a
credit or debit card.
• Vodafone worked with Storm Reply, a member of
the AWS Partner Network, to create a compliant,
secure solution able to handle thousands of
transactions per day
40. Wrap up.
• Get the measure of your customer maturity.
• Migration / new workloads / all in ?
• Engage the support network.
• Apply a framework and ensure nothing is missed.
• Chose a pioneering project with gravitas.
• Make a start and move quickly.
• Define and adhere to controls, compliance and governance.
• Iterate
• Constant business feedback.
http://aws.amazon.com/whitepapers/
Notes de l'éditeur
Opening slide – opening chat – did you see the session with Andy Jassy? Hope you are having a good morning. We are here today to discuss IT Transformation and how at AWS we support the changes needed to be successful. Quick challenge for you – how many times in this presentation do I say the words ‘enterprise’ or ‘journey’ ? I lost count.
AWS Professional Services (proserve) are an enterprise supporting team that’s primary focus is to accelerate AWS adoption. This can be done in many ways but I’ll get to that later in the presentation. AWS Proserve is a global team operating in [TODO – number of countries] countries. This gives ProServe a great opportunity to support multinational strategy for enterprises but with a local focus. This is becoming ever more important as regional offices pool their IT resources for greater agility and efficiency. This is a key benefit when looking at a transformational project that spans multiple timezones.
Some of you may have heard of the AWS Cloud Adoption Framework or CAF. [can I get a quick show of hands?] This is the framework that we use at during cloud adoption programmes. We will go in to this in more detail but it is a reusable framework for plotting an adoption roadmap and measuring progress with the cloud journey, maturity and against business drivers.
Our teams are made up of industry experts with a proven track record in cloud technology, delivery and strategy. Typically an engagement would touch multiple ProServe consultants so that the best possible advice and support can be given what ever the workload requires. If a project requires multiple specialisms, we plan to drop in the best fit consultant as they are needed.
AWS Proserve work in the same cost model as the cloud services in that you only pay for what you use and have full visibilty of usage.
Proserve is positioned in a supporting role. Whilst experienced in business needs such as strategy, improving business cloud maturity and compliance, as well as the technical aspects of cloud technology, we offer advice and hands on mentoring to those that need it. Coming back to that word ‘accelerate’, ProServe look to accellerate adoption by supporting both customer IT and their partners. Proserve can be engaged to fill a gap in a project team, provide on the ground mentoring and advice, identify areas for improvement and make recommendations but all the time looking to hand over that knowledge so that the project team gains valuable experience and understanding that leads to a re-usable skill for the next time.
For this presentation I am going to focus on transforming the customer IT function building on AWS as an enabler to real business agility.
There are many different ways to look at what’s important when talking about moving to a Cloud delivery approach
In our experience working on hundreds of enterprise customer engagements, we see 7 perspectives
It is also important to note that different groups within the customer organization will be more or less involved in discussing different perspectives. Within IT you typically have the applications development folks, the data canter and operations folks, the architects, the PMO, the security team, etc. Outside of IT, you have the business execs, procurement, finance, etc. As you will come to understand, all these views need to be considered in the CAF.
AWS has developed a Cloud Adoption Framework that provides much more detail on each of these domains
As insight in gained for each perspective, well defined roadmaps can be created that reflect initiatives that must be accomplished across all of the perspectives and which will be executed by different teams across the organization. Dependencies can be managed by the core team.
In the example shown, the core team laid out a strategy to complete a business case to justify a value uplift through a cloud-based solution. The team then decided to conduct a discovery workshop, and from the workshop, three core team members started separate initiatives; one defining the requisite governance structure, another defining the network environment, and a third analyzing the application portfolio. Since the core team was meeting regularly to provide updates on their areas the team was able to work together to determine prioritization based on the insights discovered.
This example shows the information collected during application portfolio analysis and from defining the network environment led to next steps of defining security requirements as a top prioritization because of the concern the leadership team expressed, defining the cloud environments so skills gaps could be better determined, and training and certification solutions identified and work started because the core team was informed lead time to delivery would be longer than other initiatives.
An initiative with the operations team was started to plan delivery of new capability, train staff, determine monitoring requirements, and formalize measurement and reporting against service level agreements (SLAs). A member of the core team also work with finance and procurement on cost and billing, another team member focused on reviewing and updating Enterprise policies and practices, and a plan for monitoring and optimization of the cloud environment was defines.
Might!!!
Resend to Shiri
Proserve examples?
This is business change. If you need to ensure
STORY BACKGROUND
Vodafone Italy, based in Milan, is a subsidiary of Vodafone Group Plc, a leading mobile communications corporation that operates in more than 30 countries worldwide.
Vodafone Italy has 7,600 employees in several locations around the country.
The telephony company reported over $8 million in service revenues for fiscal year 2012.
Vodafone wanted to make it easy for customers to use a debit or credit card to top up mobile phones and other broadband devices
The company wanted a flexible infrastructure with the ability to scale up and down
A key requirement for this project was to design a solution that was able to meet PCI DSS-compliant security guidelines and requirements
SOLUTION AND BENEFITS
Working with Storm Reply, Vodafone Italy created TopUp without Login, a system that allows customers to buy credit securely for SIM cars using a credit card or PayPal
Compliant with industry security standards
Scalable solution that can support growth from 1,000 to thousands of transactions per day
Able to design and launch solution in just three months
Flexibility to add third-party service providers and distribution channels
Using Amazon EC2, Amazon VPC, Amazon EBS, Amazon RDS , Amazon ElastiCache, Amazon SES , Amazon SimpleDB and Amazon CloudFront