You have decided to shut down a data center and move your applications to AWS, and you know you’ll need some help. Whether you need just tools, boots on the ground to move those applications, or someone to teach you how, you can find help among the group of elite partners that the AWS Partner Network has assembled to assist customers with meeting their business objectives. In this session, you will discover the variety of services our partners provide, learn how to select the appropriate partner for your needs, and hear about the experiences of customers who used partners to accomplish big objectives on AWS.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Allen Brown, Solutions Architect, AWS
December 1, 2016
Selecting Migration Partners
ENT310

2. What to Expect from the Session
• Questions to ask yourself
• Understanding of the ecosystem
• Questions to ask your partners
• Some patterns to model your migration on

3. Migrations come in many shapes and sizes, so do
partners.
Managed Service Providers
Cloud Native Specialists
Software Vendors
Large Scale Consultancies
Transformation Specialists

4. You’re looking for a partner compatible with you.
You need to understand your business before you
can pick a partner; there are plenty of skilled
partners who can get the job done.
You want to find compatibility with your objectives
and business first.

5. Checklist of things to know about your business
before you talk to any partners
Know what you are trying to achieve.
Do you have existing partners with the AWS skills you need to meet
your objectives?
What are your values relevant to picking a partner?
What are your internal AWS resources and experience?

6. What are you trying to achieve? What is most
important to you?
Cost Saving
Time to
Market
Agility
Adopt New
Technology

7. What is most important to you
today vs tomorrow?
Today Tomorrow

8. What are your preferences?
› Do you prefer “invented here”?
› Does your business prefer outsourcing?
› Do you prefer learning what you don’t know, then do it
yourself?
› How involved do you want to be with post-migration
operations?
› Do you want to retire technical debt as you move, or is
that a future state?

9. What are your internal AWS resources and
experience?
› Do you have a large enough group of training and
certified AWS resources?
› Have you had any experience moving applications to
AWS?
› Have you established a COE that the rest of your
business can utilize to move their migrations forward?

10. Do you have existing partners with the AWS skills
you need to meet your objectives?
› Are your current partners experienced AWS
practitioners?
› Do they have customer references on AWS?
› Are they part of the AWS APN and hold the AWS
migration competency?
› Do you have a track record of success with your existing
partners?

11. Now that you know who you are, what are your choices for your migration?

12. What are your options?
Teach MeDIY Do It for Me

13. Why would you want to DIY?
• We know what’s best
• Focus on re-architecture
• Want to push to No-Ops
DIY

14. Should I DIY?
Benefits
• Deep knowledge of the outputs
• Maximum benefit from AWS innovation and
abstraction
• Optimize operations as you migrate
Things to think about
• Commitment
DIY

15. What do I need in place before I can DIY?
• Experience
• Cloud COE
• AWS training and certified Software
Engineers
DIY

16. What partners?
ISVs recommended by the AWS Migration
Competency will provide the tools you’ll need
for :
• Discovery and planning
• Business case development
• Workload mobility
• Data mobility
• APM
DIY

17. Previously, Under Armour struggled to manage the rapid
growth of its Connected Fitness platform when its IT resided
in two external data centers. Looking for an alternative, the
company selected AWS for better performance, scalability,
and availability during peak periods, including weekends, New
Year’s Day, and summer months when users tend to use the
Connected Fitness app the most.
During re:Invent 2015, mlbam demonstrated their
stats cast technology built on AWS, which was a
combination of new and existing technology built on
AWS with the demand for operational excellence
and availability.

18. Why would I want someone else to teach me?
• Control
AND/OR
• DevOps
Teach Me

19. Should I ask someone to come teach me?
Benefits
• Gain DevOps mechanisms in your
development and operations
• Safety net if things go wrong
• Expertise on tap
Things to think about
• Commitment
Teach Me

20. What do I need in place before I ask someone
to come teach me?
• We understand our motivation
• Early Cloud COE
• Ready to commit people
Teach Me

21. What partners?
Consulting partners recommended by the
AWS Migration competency are specialists in:
• Transformation for DevOps
• Building platforms
• Teaching while doing
Teach Me

22. In the intensely competitive mobile gaming sphere,
staying ahead isn’t just about developing the latest and
greatest game—it’s about getting to market first and
keeping a grip on consumers’ imaginations. Working with
Pythian, TinyCo’s new infrastructure delivers more
capacity, better scalability and improved performance.
Flux 7 an AWS Migration Consulting partner helped
Rent-A-Center migrate much of their application stacks
to AWS, using a platform built to leverage containers for
maximum flexibility, agility, performance, and scalability
in the face of varying demand.

23. When do you want someone to do it for you?
• Relatively new to AWS
• Committed
• Want to move quickly and OK with lift and
shift
Do It for Me

24. Why would you want someone to do it for you?
Benefits
• Move quickly to get out of your DCs fast
• Big bang migrations
• All the people you need
Things to think about
• You still need domain experts
Do It for Me

25. How should I prepare?
• Domain experts who know your business
• Stakeholder buy in
• Commitment from stakeholder
Do It for Me

26. Leveraging an alliance of AWS Migration Delivery partners
and AWS MSP partners, CapOne intend to shut down 5
major data centers by 2018.
Leveraging AWS Delivery and Consulting partners, GE is
on the journey to migrate thousands of applications to AWS
with a view to over time evolve each of those workloads to
DevOps and NoOps.

27. Want to learn more about our partners?
https://aws.amazon.com/migration/partner-solutions/

28. Thank you!

29. Remember to complete
your evaluations!