AWS re:Invent 2017: How to Assess Your Organization's Readiness to Migrate at Scale (ENT211)

good afternoon how's everyone doing thank you so today we're here to talk about readiness when it comes to migrating to AWS obviously I don't know just a show of hands how many of you are either in the process of or have started embarked on a journey of migrating at scale to AWS great awesome so as you can imagine you know from extreme your own experiences you've seen some challenges and hopefully some of the things that I'm gonna share with you today will help you you know we move some of those blockers or make your or accelerate your pace or for those of you who are starting or looking at this journey just accelerate the overall journey your overall migration and maximize your return on investment so by way of introduction my name is saudi-led me with the AWS professional services team I've been a cloud infrastructure architect for about four-and-a-half years for the last two years have been part of the global migration practice that we have within the AWS professional services team based in the US and a lot of what I'm going to share with you is based on the hundreds of engagements that we've had when I say we I mean AWS professional services with our customers helping them through large-scale complex migrations we found that these are the key elements that folks should really hone in and focus if they want to achieve success when they start migrating at scale right so should be using lists what we're going to cover today is first we're going to look at some of the common migration drivers to set things into context why would somebody look at migrating at scale in the first place and just from a point of reference for us at scale means 500 and above workloads but that's an arbitrary number and any everything that I'm gonna share with you today can and will apply to if you're doing looking at doing something smaller in scope right oh and also forget to mention we'd like this to be interactive so I don't have content for a full hour but I would like to talk more about use cases and specific questions you may have so there are two mics in both Isles feel free to get up at any time during the presentation if you have any questions comments happy to take them as we go so like I mentioned common migration drivers we're going to define what migration readiness means which is I essentially the crux of this presentation and we'll dive into the six core focus areas we'll talk also about we'll talk a little bit about the cloud adoption framework and I hope that a lot of you at this point are aware or are familiar with the cloud adoption framework a lot of the content methodology tools best practices that we work off of within AWS is based on the perspectives emanating from the cloud adoption framework and if you're not familiar with it I highly encourage you to go look up the cloud adoption adoption framework white paper and all the perspectives are listed there and then at the end of the talk we'll talk we'll touch upon what are some key levers that you have at your disposal what are some areas or where are some areas you can go to help to get help if you needed to as you are embarking on your journey to the cloud then you start accelerating at a much more rapid pace migrating workloads so common migration drivers and hopefully or probably you will recognize or can relate to many of these as drivers within your own organizations as well right so even though every Enterprise has their own unique blend of drivers we have seen they pretty much fall into these categories or yes right big one is obviously increasing agility we have a lot of enterprise customers that are estimating anywhere between thirty to seventy percent an increase in productivity when they're migrate their workloads to AWS we see obviously a lot of data center consolidation application rationalization especially enterprises who have been very acquisitive in the past and start dealing with infrastructure spoil it the value proposition for the cloud is really strong for them you also hear a lot of companies looking to completely reimagine the way they do operations and transform the way they conduct business or whether it's being able to go to market really quickly or transforming the way they do support and operations internally there's a strong value proposition for them as well and finally you have all the physical related benefits of not having to manage data centers not having to pay for cooling electricity and obviously most enterprises and I'm sure many of you are are cost conscious and so though being able to reduce the cost and the you know the expenses of maintaining and managing infrastructure is very appealing so what do we mean by readiness our experience has shown us that there are six important areas that are listed up here that are really paramount for you to be able to achieve success prior to embark to starting a might large-scale migration to AWS and I can tell you from personal experience many of the well-intentioned well-funded large projects that had a lot of partners involved a lot of internal customer customer resources involved have stalled or run into issues because they didn't do their due diligence and invest the proper time and effort into the six and so like I said earlier based on our experiences the if you spend more upfront in terms of allowing yourselves to making sure you have the proper framework for handling these six core areas you're much mater you're much better poised for success so for us executive sponsorship refers to the role of senior leadership in their organization to be able to obtain and maintain buy-in from key stakeholders whether they're internal or external right and we'll dive into all of these in more detail obviously second we want you know business case typically is something that drives an organization in the first place to say hey you know based on the common migration drivers we just saw a slide ago we want to really push forward and move to the cloud and we need to have a strong compelling business case that we can share with our board or any other stakeholders that we have to make sure we are we're on the right track people most important asset you have in your organization obviously the creating a framework for them to be able to grow to be trained to mobilize them in the first place will help them will help you as somebody who's leading a migration project or is involved in a migration project to remove any potential blockers as they may arise right most of my time is spent with customers not dealing with platform related technical problems it's more related with people and process right and so if you invest the time and energy energy upfront - sorry focus on training informing mobilizing your team's and we'll talk more about what that means in a few minutes you much better poised for success additionally foundational experience we found that organizations that allow their teams to take advantage of AWS and get hands-on experience with AWS the platform the capabilities even if it's in just in a sandbox environment if it if it's just a lab even if it's just quick labs training what have you have a much higher rate of success because going back to the people side of things if they are familiar with the the platform and the capabilities they're much more or less less inclined to pose or come up with blockers because now they really understand the value proposition and what are the things that can do in terms of you know either from an Operations perspective or go-to-market perspective or even from an application resiliency perspective right visibility for us visibility refers to having insight knowledge awareness around what your IT estate looks like and so I would say probably 80 to 90 percent of the customers that I work with do not have a well-defined output of what their portfolio is so they may have outdated cmdbs they have spreadsheets they have infrastructure that is managed by a third-party provider it's very difficult to get real-time data it's very difficult to get dependency data and so a lot of times you know when you start thinking about hey I need to migrate 500 applications a thousand applications I want to close the data center it's not trivial to start thinking about what are the risks that I'm incurring if I move you know a significant subset of my portfolio into the cloud not knowing all the application dependencies right so from a risk and cost perspective they're really vulnerable at that stage and then finally operating models so most enterprises I work mostly with enterprise customers they all have a mixture of operating models and I will get into what that means when we touch on that topic but really you know if you think about having you know third party providers managing part of your infrastructure I'll give you a simple example I have a customer I just worked with recently they had three different providers managing the same stack for them one was managing their server hardware another one was managing their OS and a third one was managing their applications and so if you think about from a process perspective all the hoops they have to jump to to do provisioning to make any kind of change really it becomes really cumbersome right so migrating to the cloud doesn't necessarily mean you have to do away with everything that you're doing today but you have a lot more tools at your disposal that if you wanted to make change changes possible right and so we'll touch you a little bit about that we'll talk about that so let's go into the first one this is a real Tuffy right guys executive sponsorship is not something that you know if I go in front of it if I go to a meeting and I say hey you seen your leader you need to do a better job at communicating and all that that's not an easy conversation but it's you know we really feel that we need to speak truth to power and what we think about when we say executive sponsorship is you can't pull it off if the executive is not committed if the senior team leaders senior leadership team has won has not formulated a properly proper strategy and evangelized that and communicated that throughout the organization many times I find myself in meetings with folks who are not sure why we're there in the first place even though we have to close the data center in six months right so it's important for them to have that kind of communication so laying out a communication plan and that sometimes mean you know working with somebody allocating somebody within your organization to be able to one formulate it but also executed manage and we'll run with it as you go through the migration project so supporting the communication channels whatever they may be and also creating new roles and learning paths so this is an important one because when you start evangelizing your strategy and the reasons why you're going to the cloud the first questions everybody's going to ask you as a leader is what's going to happen to my job what's going to happen to this role to this division to this team so you need to have an answer for them ahead of time right and so we can help you craft one as well but we'll talk more about this and also part of this is well really senior leadership should make the commitment and put skin in the game in terms of realigning folks and making this a priority if migrating to the cloud and changing the way you do business is as important as you say it is then you have to put skin in the game and either hire folks or reallocate priorities so that the folks that you have can spend their time working on the cloud migration initiative right the other piece of this is everything we do at a table yes we really really care about measuring you know KPIs and success overall so what we try to instill in our customers is coming up with a framework where the KPIs that are specific to your organization so whether it could be the cadence of your migrations how fast you migrate how many servers or workloads you're migrating a week or every any given sprint how much you reducing your cost your operational costs whether it's because you are having outsourced provider or because now you're doing it in a DevOps fashion and you don't have to pay the same vendor to manage your infrastructure or your application or so any any successful impactful meaningful criteria that the organization cares about has to be outlined and documented and tracked at the onset of the migration project right so even before you start talking about when I'm gonna migrate my first workload you should have a framework for being able to communicate to all stakeholders this is how we're going to measure success as we go along on this journey part of you know obviously again the sponsorship is making sure you create a coalesce a coalition of leaders across the organization right so if you know there are pockets of the organization that are not necessarily receptive to change that are not necessarily have a different vision or historically have been reluctant to work hand in hand I mean I see this all the time there's like different piell's that are in conflict with each other at times there are different conflicting priorities budgeting politics what-have-you right so the role of the leader at this in this stage is really to make sure you can build coalition across different areas so you have a unified team moving onwards and this is really important this is more subtle but you know what we've seen is if you are able to reinforce even small wins even small steps as you go through this journey it really changes the mindset of your organization a lot a lot of folks now raise their heads and take notice and say oh you know so-and-so did this you know they were able to do this in the cloud and they got kudos and they said somebody sent out a newsletter about it maybe I could do something like that and try it my hands at you know building something cool in the cloud or helping migrate some kind of workload so reinforcing that commitment and whether it's through newsletters doing lunch and learns internally informational emails blogs whatever right any kind of mechanism that helps you ultimately you know commits build and maintain momentum because that's really the name of the game and that's what we want our senior leaders to be able to instill in the organization as we go through this right and the reason this is the first point that I'm talking about is because most of the time projects stall because people are not sure what their role is and they're not really sure where senior leadership stands and expect to what they have to do with this initiative right with a large-scale initiative so a constant reinforcement build the momentum and maintain it as you go along so the next point is business case and business case has a lot to do with like I mentioned earlier providing your organization with a data-driven approach of why we're moving to the cloud in the first place all right so people are gonna come up out of the woodwork and say hey you know I don't know if we should be doing this why are we doing in this this in the first place if they understand data and they follow if they understand the metrics that are provided in a business case then they can then you have a case to talk to them about you know these are the reasons why we feel it's a significant value add or significant value proposition for us as an organization to to move there right and these these are the benefits that we can get so this is just a sample output of a high level one and it doesn't have to necessarily mean anything but all I wanted to show you share with you is like we have mechanisms and tools in place with in AWS to help you both estimate migration costs run rates do TCO analysis and anything along those those lines we have a cloud economics team if you're not aware that we can tap into and help you on that on that in that process specifically and the business case is usually it's something that happens in in steps right it's an iterative approach and what what happens is early on we usually have a conversation with sponsor or senior leadership team and they want to understand ballpark figures they'll say to me sort of tell me how long how much is this gonna cost me and how long will it take me ballpark for me to close this data center and move it to AWS right and mass and so they are the level of data is fairly coarse you know they may have some spreadsheets they may have some output of an outdated tool let's say hey we got 4,000 vm's in this data center and this is kind of the breakdown between Linux Windows what have you and you know give us some pricing we want to bring our own licenses or we want to use AWS provided licenses these are the database engines that we have so very coarse level and then they'll say so then we'll do a directional business case with them at that point so it will be high level estimates of what they can do you know depending on we'll given some options worst-case best-case how are things looking in terms of if they wanted to do undermanned pricing reserve pricing and so on and which regions they would like to select and on and on but then once we get past that point then we'll get we'll sit down and we'll do a more refined approach or another pass at the business case and that's the drill down where we dive deep into understanding exactly the specifics of what is actually in scope of the migration so maybe from a data center you have 4,000 VMs but maybe 3,500 of them are in scope the other 500 are moving to another data center or they being shut down retired the Commission they're part of an app rationalization project what-have-you right and then we'll sit down with specific teams and they'll say yeah I have these 200 VMs but I'd necessarily want to migrate them I'm going to be platform 100 of them so that changes a little bit the the equation right and then finally we have a detailed one which is we can provide five year estimates of you know what is your ROI going to be based on the pace at which you migrate your workloads and it's much more detailed again we have resources and tools on our side and we have a cloud economics team that that's all they do for living all day all night and they are more than happy to help you with refining your business case as you go along right so business case key so we talk sponsorship business case people you know so people really is fundamental obviously you can't get anything done with that without the team's alignment and by and we have a couple of different things you can do with from from readying your organization when it comes to the people side of things right so we obviously AWS offers a ton of training you know you can build your technical skills we have some business essential skills also you can tap into you don't necessarily need to be a techie to be able to be comfortable and and talk the lingo and understand the platform we have some self-paced online labs we have free tier accounts that you can you know start up and test and experiment with on the platform we have certifications you can you know determine if your how well ready how ready you are in terms of your understanding of the platform and its capabilities solutions architects awesome resources there they work with you in the account and they can do things like immersion days and I don't know how many of you are familiar with immersion days but there basically will go really deep with you on a specific topic of your choice that's important to your organization so if you tell me I want to work on I want to understand conformation they'll do it one day to day immersion day with with multiple teams if they have to repeat it strictly on cloud formation and they can go deep on the specific needs of your organization right so and then we have AWS professional services which is a team that I mean we do a lot of workshops anywhere from educating customers and getting them ramped up but also it's very much instilling best practices and providing the guidance necessary for them to be able to you know migrate at scale successfully but you know that the key takeaway from this is the experiences that we've we've had is like the people are really the folks are gonna be able to say you're successful or you're not right so if you empower them with the right tools and lay the proper foundations for them to be successful so creating roles creating framework for them to grow a clear path for them in terms of their transition from the way they are operating or working today to the way they will in the future is fundamental for them to be able to come on board and work with you and so yeah so that's and then the other piece to the this is the training aspects is creating a center of excellence so center of excellence could mean Tiger team could mean task force could mean many different things we call it center of excellence you call it whatever you like but it's a core team that's fundamentally at the center of the organization that really understands everything about the organization from the tools people processes side of the house and they have a somewhat good experience and understanding of the cloud capabilities right it's a so it's a it's a it's a group of folks who can marry the two and the reason we say we want them to be very knowledgeable because I've had customers who've created Co ease with partners or have had partners lead them they can work as well but there's more success if you have folks who understand your culture that are embedded in that team that can actually influence the decisions that are being made on emanating from that team right so for our center of excellence is a team that's really focused on an understanding what are the processes the policies the standards the tools all those different aspects that are important and relevant for an organization like yourself when you're looking at migrating and they are you also able to define the RACI matrix of who would be the right folks to tap and say hey tap on the shoulder and say hey I want to have you would you be interested in working on a migration team or what skills do we need as an organization because we understand our organizational strengths and weaknesses that we need to ramp up to be able to achieve this kind of initiative right and so they also be able to do skills assessment and we can assist with that providing job descriptions like I mentioned earlier understanding so having folks really being immersed and involved and trying to see what is the path for them in their organization how they're going to evolve into this new role in this new operational paradigm in the cloud so alongside that you know we have foundational experience or what I mentioned earlier was having them be be able to experiment and test out the capabilities most of the large-scale migration projects that we see are typically with customers who have a baseline foundation so they may have some production accounts with us they may have been running production workloads with us so maybe not maybe they've been running dev tests with us for like a couple of years even but they have some basic understanding of the platform and the capabilities and what we've seen is if you start fresh and if you go in day one with nobody in your organization having any experience with AWS talking to them about high velocity sprints and migrating servers and changing your operational paradigm becomes a very difficult conversation right so the more exposure you give them to the to the platform and the more you have them interact and test out and experiment the better you will be in terms of being able to scale the cadence and the velocity of your migrations and go to this so ultimately you know as you go through training your team's giving them access to the to the baseline capabilities of testing you know we have like I mentioned earlier we have free tier accounts they can play with we we want them to be get to a place where they have enough exposure and interaction to have intelligent conversations internally amongst yourselves so if you're an organization and you have to decide am I going to lift and shift workloads or I'm gonna reap lat forum you want to know that the people at the table having the conversation understand the pros and cons of each and what is what are the implications or what are the ramifications for your organization as you move along right so if I decide to reap lat form a database how is this gonna impact what I'm doing from a licensing costing operating model from a skills and people model versus if I did just move there to ec2 right so that's that's the place we want to be at so that the people on your side in the organization are in a capacity to make informed decisions and not put up blockers because they don't necessarily understand the capabilities of the platform right so operating models this is probably the one that most people overlook most often right what they'll do is they say hey we know how we operating we have maybe we have s LA's Ola s maybe we have documentation may be we have escalation processes in place we have some third party partners providing support maybe we have all of that but what they don't think about is when you move we're close to the cloud what is the impact in your day-to-day operating model and like I said earlier you may have most companies that I've interacted with have more than one operating model and that could be because you have decentralized operations or it's because you have centralized operations but you have different pockets not necessarily abiding by the same rules and standards for various reasons right I'm not saying it's right or wrong that's just the reality of the experiences that we sing but what we're seeing in the field so understanding your operating models what are the tools and processes people are leveraging today and really fundamentally it's about knowing why you are operating a certain way why are you in the state that you are today is paramount for you to be able to make decisions on how where you want to be tomorrow once you start migrating to the cloud right it's you know there's a lot of times where you have decisions being made outside of the core team around big decisions such as how we're gonna you know outsource potentially part of our infrastructure or we're gonna have others manage this for us but that's why I'm going back to my earlier point that you need to have people who understand the organization and the culture within your Co EE within your task force within your Tiger team who really understand the context so they can make the right decisions moving forward when you start migrating to the cloud and operating at scale and so the three typical operating models that we see and you see a mixture of this in different organizations I've seen organizations with all three I've seen organizations with just one but you know you have on the left side you have the traditional model which you have a separation of you know development and operational teams and they manage different pieces of the infrastructure right and so this is more in the line of you know you have traditional delivery SCLC processes you're using waterfall typically it's a high-touch model and you know the workloads are dependent on various teams for service delivery so you may have to go to different teams to get something done in your infrastructure today right then you have the automated efficiency where you have you know you have some traditional on-prem operations of applications but you have a lot more operation involved right so you may have points across that the DevOps team potentially could be leveraging or impacting in terms of delivery of the service and then you know this is more of an agile approach for the most part and then you have the DevOps full-blown DevOps which is the the idea of you you build it you own it right so you have a team that builds the an application and they run it and they operate it in the cloud and this is a shift for some teams and for some others it's not because they've been doing it for a long time but what I want to the key take away from this slide is you can you can have all of these models in the cloud you have all of these models in on-prem as well but you have to understand which of these models best fits you and if that's a change a direction a path that you want to embark upon you need somebody in the organization to make the case for it from from a culture from a process from skills from a tooling perspective of why a specific model makes sense right and we're not here to say you need to be all DevOps you know I would love it if you were but you could be automated efficiency you can be traditional we want you to be successful and efficient with a model that you have chosen right but you have to do it for the right reasons and that's why it's it's key that the folks who are making these kinds of decisions upfront before you start your journey our folks who are really who really understand the context and the culture of the organization and can make those decisions from a you know well-informed place most of the trouble that are running with customers they start migrating and different teams start migrating different types of workloads and they get to a place where they have more operating models in the cloud than they did on Prem and now so they're thinking oh my god I got you know I had all this overhead of management of from operations perspective on Prem now I have a lot more in the cloud because I didn't think this through and because it's a decentralized model now we have to reassess so we'll put the brakes on on the project for instance and revisit it and come up with a new plan right so the point of this session really is I'm trying to share with you you know the mistakes or the gotchas that you could the pitfalls that you might run across and hopefully you know when you walk away from this session you'll say you'll know like these are the key areas that you need to invest time and energy in I'm fleshing out before you start a migrate large-scale migration project at any rate right and then then the next one is visibility and so visibility for us like I mentioned earlier is gaining that level of high fidelity in your data so that typically happens through an automated discovery tool of some sort because we all know manual discovery is cumbersome and error-prone at best and so we're trying to flesh out not only the technical requirements or potential blockers that a automated tool could could provide or shed light on but we also want to flesh out the business requirements because part of any good migration story like I said earlier is a business case so you want to understand from not only from a licensing perspective but from a you know alignment with business strategy and vision alignment with your operating models understanding your support models and your contracts and your providers and you know generally understanding what do you want to do with it what's active roadmap for any application that you're supporting today ahead of starting the migration right because you will get to this place where you will want to understand which of these six R's you will select for your applications and you cannot make this decision from a well-informed place if you don't have the right amount of visibility right and that means understanding business and technical requirements so the six ARS from from our perspective retain retire we host we platform refactor we purchase they have varying degrees of complexity they provide varying degrees of benefits most enterprise customers that we work with a large scale migration project employ all of these so part of their portfolio state is you know they'll what all of these six ours will be mapped to some of their applications in their estate I have yet to come across an enterprise that was moving you know even if they said I want to do lift and shift for everything there was always always something that was either retired or repurchased or we platform or what have you right so you cannot make this decision of how do you bucket eyes your applications when you're going to start the migration without really understanding your application and knowing you know what your dependencies are what your risks are what are the costs impact of migrating a specific workload for each of these you know your your cost posture is going to be very different right so what I mean by that is not just the easy to run rate or what you're going to say on AWS it's from a application development and all the way to support all the way to licensing and anything from a Productivity if you're measuring productivity from a developer side on your on your side of the house or if you're outsourcing that piece of it as well all of those that will be impacted depending on the type of are you select right so again this decision must come from the place of well-informed data understanding culture context why are we doing this what is our operating model going to look like why we want to get to that place with the data that we have with the history that we have and making the right choices when it comes to these six R's right and so what we try to do with customers is get them to this place based on all the things that we talked about you know executive sponsorship visibility doing a business case foundational experience operating models is say okay you have you know these are your drivers for you and you know we do a assessment and we determine you know based on what are the key four criteria that are relevant to your important to you which migration path or which are will you select for specific types of applications so I've had customers who were who were or focus was de-risking for instance they had a lot of 2003 Windows workloads or they had databases that they wanted to continue a stop support and and move to a different database engine because the contract was about to renew and they wanted to migrate to a different platform before they had to renew the contract right so from that perspective that could influence it there are that you select the path that you select for your migration of your workloads for here you see for instance its application end-of-life how much budget is there so you get a ton of agility if you refactor an application but it's somewhat resource intensive right so you have to rewrite it you have to re are connect it you might have to do design sessions building a lot of thing so it's it's not that so that's something that you have to consider as well it's not that trivial from a resource perspective and then you have others like hey I'm on deadline do I have time to do any kind of refactoring do I need it what's the support model can we just move it as is and get and close the data center because that's more important let's do we host right so that's the place we want to get to with customers but really everything that I've said so far comes from the experience of any of those six points is not well addressed we run into trouble because customers have to slow down and we don't want you to slow down we want you to be successful as a matter of fact one of the things that we work on is helping customers build migration factories that scale themselves so not just the cadence at which you you scale your ec2 or your lifts and shifts or your we hosting workloads but you can also increase scale up and down your factory itself as you on board new people new team members new tools new processes so that's what we are after really and so what does old me and so if you wanted to put all this into action right so you know I talked a lot about these are some of the blockers and gotchas and these are the areas you need to focus on so we have some things at AWS that we can help you with right the goal of this session is not to say go tackle these six on your own the goal is to say these are the six C's should focus on and this is where we're going to help you with if you want our help so everything that we've built internally is based on the cloud adoption framework I mentioned this a little bit earlier this is the URL at the bottom if you haven't seen it I strongly encourage you to go read that white paper and it's basically talks about these six perspectives and if you think for a second about the the six items that I shared at the throughout this session they're more or less aligned to a lot of these right we have the business for the business case we have people we talked about platform with foundational experience we have security and operations obviously security is fundamental to everything we do from an Operations perspective so a lot of the perspectives that each of these six boxes or rectangles is called the perspective identifies a set of capabilities that we try to help the customer build right so whether it's how you know what is the transformation going to look like for them from for instance a security perspective what is the security posture today and how will the migration impact their security posture tomorrow right in the cloud so that's just a plug for the cloud adoption framework but just so you wear everything I'm going to show you after this is based on the fundamental principle that we strongly believe these six perspectives of what drive an organization to be able to transform successfully so we have this great tool called the AWS migration readiness assessment and it's something that based on the six perspectives we've created with all the experience of the hundreds of engagements we've done with large-scale migration customers what are the areas that we feel customers have trouble pain points is there a way for us to identify those gaps early on with a customer and show it to them before we even start the migration project so maybe we can start plugging tackled plugging away at the gaps that they have before we start a large-scale migration journey that will involve a lot of resources investment on their part time energy right and this is what we came up with and so the this provides this view that you're seeing here is an output of a completed heat map a completed readiness assessment right and what this shows is the areas that are red are areas that for instance this specific customer did not score well on it's a series of questions that we go through that based on the six CAF perspectives outline what are the areas they may potentially run into trouble and what we try to do with this with the with this output and this is the output the customer you will see is what are the deficiencies you may have today and what are some areas you need to focus on to be able to ramp up your capabilities across those six CAF perspectives before you start the migration project right we know if you address these capabilities if you get this this this radar to a good place where you get you know to 80% for instance you're much better place to be successful in your migration journey and not pausing not slowing down not stopping then if you don't because of all the things we just went through the last 45 minutes or so right we calling out specifically co e training discovery of data so fidelity of data is being called out here what is your security readiness model do you have a business case do you have commitment you know all these things that we touched upon it from the the six core areas or call that specifically here and so we'll show this to the customer and we'll say this is some of the areas that you have gaps today and we have a Frank and open discussion about them and I'm by the way this the the answers to these questions are provided to us by the customer right so we don't fill this in ourselves but we help the customer fill it in and so it's kind of like having a mirror reflected and they see this is the current state of our organization are we really in a good place today to start migrating and at scale to AWS and sometimes the answer may be no the answer may be no I need to go invest in my operating model no I need to go invest in my people I need to build a stronger business case right and that's ok with us because we know if you do this you take the right steps you will be poised for success afterwards all right my goal is not to say everybody's ready to migrate let's do it tomorrow doesn't matter what we'll do it right my goal is to make sure you do it successfully because it's a large transformation project it's complicated it impacts a lot of people right so you want to do it right and you want my's cost and risk so this is the the readiness assessment and basically what we'll do is based on each area where there's a red you might say okay so what does this do after we what's that action what's the next step is we'll work with them on plugging that gap so if there's for instance this is pointing to the application discovery data as a gap and so one of the areas we can we can help the customer with in this specific case is to help them procure evaluate bake off an automated discovery tool we have a number of discovery tools out there that are have been really successful with customers and so this might be one way of plugging that gap right another example is the people side of things we have maybe the gap there is to send more more of their team's to training right maybe not they don't have enough foundational experience so exposing them to more training whether it's say immersion days quick labs workshops self-paced learning what-have-you and finally it's building a cloud team so maybe there is no clear organization or it's clearer central team within the organization that can make decisions around how we move forward so what are the patterns one of the six R's that we're going to employ what is a cloud operating model going to look like you know what are the tools the processes what are the standards we're going to have to follow right it needs to be some cohesiveness in the organization that says this is the way we're going to move forward so we can you know some of these areas are about helping ramping ramping up establishing a team like that setting them up with scales and getting them ready so that they can in turn share that knowledge and ramp up the internal teams this is another one with security we might have to do we might conduct security workshops with a customer understanding what the security posture is sometimes getting them to a place where they have a proper security playbook for the cloud maybe that could be a potential blocker for the seats he says you know I'm not comfortable until we have a good playbook or we've done enough experiment a experimenting with the security services so that that's just some examples of the outputs of a AWS migration readiness assessment so but fundamentally you know when we do this we do an MRA the next step really is to say you know it's great to do training it's great to do immersion days it's great to do a workshop here and there but how do we do this in a systematic fashion how do we do this if a customer comes to it comes to me and says you know I don't feel ready how do I get there how do I get ready really quickly right or or if we do a migration readiness assessment and we realize it's red across the board which happens fairly often believe it or not and they say okay so that's okay that's good but what are we what I do now I need help ramping up getting to the place where I start becoming yellow and green so I can start migrating so I can start evangelizing that hey this is something real in my organization we're gonna start doing this right and so what we have also our disposal within AWS we've created the migration readiness and planning engagement and what this is is basically in a number of agile sprints in a short time frame depending on obviously you know what the MRA the migration readiness assessment outputs are they will feed directly into this type of engagement and they will basically say in essence okay if I was read on for instance the skills and center of excellence I will spend you know two sprints bringing in a number of resources where there's AWS preserve professional services or partners to help you ramp that up ramp up that capability to get you to a place where you're comfortable then scaling that out internally right our goal our mission is not to go and you know sit with you in a room for 12 months and teach you everything there is to know about AWS our goal is to teach you that hey these are the levers you can employ so that you internally can scale your knowledge within the organization and come to us whenever you need it right and so the same thing with discovery we have a number of tools within the AWS professional services team that allow us to take output of a discover of discovery data of a discovery tool parse and analyze the data and provide weighted scoring a prioritized list of a core backlog for all the applications in your estate for instance if that's that was something that was lacking business case help we can do that as well migration experience is another area where a lot of times we actually found that for from a tactical perspective of hands on keyboards it's really helpful for the migration team wherever that may be to be able to have some experience of migrating a few workloads so what we'll do is we'll sit down and work out okay you know we have this let's say hypothetically a thousand applications we have you know eight you know 60% of them are three tier application Java apps and then 20% are you know two-tier you know windows with side base for instance what have you and let's take the ones that that we see that are very prevalent in the portfolio and let's have the teams migrate one of them when what that exposes the team to is the actual sequence of steps that they must go through to be able to migrate in one application successfully all the way from discovery planning designing building migrating write testing validating integrating cutover decommissioning the whole spectrum and then once they be they see that process it really instills a lot of confidence and you can take that process and replicate it and then you start getting a migration velocity right because now you have a team that's been able to do one now next week if you can do to the following week they can do 10 right and we do this per pattern because you have a lot of similar patterns in all your portfolios and it's not just you know every application is a snowflake so that's where we look for and that's what migration experience is really talks to there and that's it but basically the migration readiness and planning engagement is a way for us to systematically ramp up the capabilities of you all it's in a place where you can start expanding that knowledge that experience internally within your organization's right so we are here to help we're on professional services we're in the bottom we have a ton of partners I know I've given you a lot to think about but you know I don't want it to make it seem like it's daunting like all the big all the six items are listed they're big they're big topics it's not something trivial I we get that so but we have a lot of resources to help you right and so what I want to quickly go through a wig is I'm running out of time we have the migration competency I don't know if you all familiar with the migration competency we've created a migration competency in 2016 where we have a number of customer we have thousands of partners obviously but we have a certain number of partners who have achieved the migration competency level as well and these are partners that customers have relied on to help them migrate in some capacity and these are these are just the samplings of this is accurate as of last month or a few weeks ago but all the partners are listed on our public website and you can see them there and obviously we have a whole slew of tools right because another big piece of the puzzle for folks is okay what are the tools I'm going to need to be able to migrate it's not just the know the people side of things or the resources so along all if you look at the three dimensions on top the migration readiness assessment migration migration readiness and planning and the actual migration of applications we have tools in all those categories that can help so from inventory and business case we have you know discovery tools sodomize risk networks tsts illogic aptio on the business side of things some of you may be familiar with these tools some of you some of these are already well-established you know enterprise tools that you may have interacts perience with same with a migration discovery and readiness you have a lot more application dependency mapping that becomes more critical right when you start thinking about migrations and actually migrating we're closed so tools like New Relic dynaTrace up dynamics can give you that level of fidelity on the dependency side and then you have the actual migrating the bits and bytes so calendar a demotion Vella strata depending on the use case the workload your RTO RPO how much of a nowadays you can take how much are you willing to spend right we have our own tool AWS SMS DMS great one for databases so it's just a matter of you know most of my customers have a combination of these tools you know there's not more size fits all when it comes to migrating because your IT portfolio is not is not all the same and then lastly I think much my talk wouldn't be complete if I didn't give you a customer logos slide up these are all they see is someone I'm sorry this some of the customers that we've worked with part of our migration journey with them and so a lot of the learnings that I've shared up to this point have come from our experiences with some of these customers you see here you know I want to call out maybe a couple NL out of Italy in partnership with Accenture they were able to migrate 6000 servers in ten months but the interesting thing is they were able to keep the existing change management process while doing it right so a lot of folks think oh I need to completely change the way I'm looking at this as to be completely separate team isolated no they were successful because they were committed they had buy-in they had good help they had the right tools and they really wanted to do it and the whole organization was behind it right and another one we have maybe I'll call out is this sorry yeah the other one I wanna call out is Capital One and Capital One is you do sing its data centers from eight to three by 2018 and Capital One is a great customer because they they're pretty much using every single service so testing every single service that we have that we have but they run most of their a lot of the critical workloads anywhere from dev tests you know all the way to mission critical workloads on on AWS and and they're really looking at reinventing the way they do mobile banking so the other the last thing I'll leave you with is I definitely check out this link aws.amazon.com slash migration a lot of great content both in terms of tools partners don't forget about the cloud adoption framework white paper and I'll open it up for questions I add we've got a little time if you have any questions from anyone

Channel: Amazon Web Services

Views: 7,847

Keywords: AWS re:Invent 2017, Amazon, Enterprise, ENT211, Migration

Id: id-PY0GBHXA

Length: 58min 38sec (3518 seconds)

Published: Tue Nov 28 2017