AWS Discovery Day: Strategies and Tools to Perform Large-Scale Migrations [Webinar]

Learn about the AWS strategy and best practices for performing large-scale cloud migrations. Built from the experiences of helping hundreds of enterprise organizations move to the cloud, these proven techniques and tools will help accelerate your successful journey to the AWS Cloud.

WEBVTT

1
00:08:33.010 --> 00:08:35.610
Craig Cory: Sophia. I think I've scared them all away.

2
00:08:45.100 --> 00:08:52.479
Sophia :: ExitCertified Support: It looks like we have about 20 students so far. Yeah, I think we can probably get started.

3
00:08:52.640 --> 00:09:07.090
Sophia :: ExitCertified Support: I was looking in the wrong place. Yeah. And we got about 20 attendees so far. so I think we're going to get started anytime.

4
00:09:08.260 --> 00:09:10.180
Craig Cory: Fantastic.

5
00:09:10.240 --> 00:09:17.030
Craig Cory: All right. Well, good day, everyone sorry I was looking at the wrong list, and I thought nobody was here.

6
00:09:17.090 --> 00:09:30.219
Craig Cory: I'm glad to see you all joining fantastic. My name is Craig. I'm an inspector with exit certified. We are one of the training partners for aws in North America.

7
00:09:30.260 --> 00:09:38.819
Craig Cory: I've been delivering the aws material for I was just thinking about it about 7 meters now. maybe a little more

8
00:09:38.930 --> 00:09:50.760
Craig Cory: and as a an aws, partner, of course. we are eager to offer you whatever elements you need for getting your training needs satisfied.

9
00:09:51.110 --> 00:10:03.550
Craig Cory: we along with aws present these discovery day topics for different topics within. Aws. Talk about different aspects of things that might be of interest

10
00:10:03.700 --> 00:10:12.479
Craig Cory: to customers, and give you a taste of what? Some of the actually what some of the material will look like. And some of the interactions will look like.

11
00:10:12.970 --> 00:10:15.310
Craig Cory: no, I'm seeing a handout

12
00:10:15.810 --> 00:10:23.180
Craig Cory: somebody you can put items in the chat we don't have. we don't have shared audio today.

13
00:10:23.230 --> 00:10:25.669
Craig Cory: It's gonna be a one way street.

14
00:10:25.770 --> 00:10:32.520
Craig Cory: if you will, but if you've got questions or things, I'm going to try and keep an eye on the chat as well

15
00:10:32.950 --> 00:10:36.669
Craig Cory: as we move through our materials. All right.

16
00:10:38.690 --> 00:10:52.129
Craig Cory: So again, welcome in this is our discovery day to talk a bit about. What aws has to offer you help us if we are looking for our initial migration into aws.

17
00:10:52.450 --> 00:11:17.340
Craig Cory: And of course, part of that that initial journey is the planning the identifying of needs and shortcomings. And then we're gonna highlight some of those elements. Now, the title, you see, says large scale migrations. If we're talking hundreds of applications move your entire architecture into aws. that is kind of the focus, really of the

18
00:11:17.470 --> 00:11:45.609
Craig Cory: the tool sets and the planning process but to be honest, if you've got a smaller subset of items you're looking at, bring into the cloud. the logic is still the same. The concepts are still the same. And frankly, it probably means you can do a little bit quicker. And what we would identify for a very large scale, you know, or we're changing implementation of these these elements here.

19
00:11:46.930 --> 00:12:05.169
Craig Cory: So the basics it starts out really with, you know, hey, why are we thinking to move into the cloud, and there's lots of drivers for Why, a company, a department and enterprise might look to move to the cloud. these are some of the common ones listed here.

20
00:12:05.350 --> 00:12:25.760
Craig Cory: I think maybe not quite the the number one any longer, but the cost reduction is to be a big player in saying, Hey, we'll move to the cloud. We'll save lots of money. It'll be great, and that is certainly viable. that is certainly possible. But there's also kind of a trade off as well of saying, well, it may not be net dollar

21
00:12:25.760 --> 00:12:54.550
Craig Cory: savings, but I'm gonna gain in reliability, and the agility that we have. Now that we're working with the cloud based services. And we're not worrying about hosting equipment and all those elements here. And of course, that's the primary factor coming to the cloud. you're no longer thinking about the the physical data centers, the equipment, the the procurement process and all those basic elements here which

22
00:12:54.550 --> 00:12:59.889
or not necessarily. everybody's, you know. Primary strength

23
00:12:59.900 --> 00:13:12.059
Craig Cory: you're likely working, you know, you, with a company or a department that's got other things to be concerned with. And it's not necessarily just technology. And it's that that you want to work with

24
00:13:12.120 --> 00:13:29.910
Craig Cory: So identifying. What's what's really the the use case to do this? And we see the net benefits. And there are ways to. you know, plan on, what do we anticipate going to the cloud? What benefits we foresee going to the cloud.

25
00:13:30.090 --> 00:13:32.549
Craig Cory: so we'll come along here.

26
00:13:32.590 --> 00:14:00.259
Craig Cory: Now, what can get in the way. well, certainly, if you've not existing investments, you've got long standing software license agreements or you provision resources, or you're committed to certain standing arrangements that might be a bit of an impediment here. certainly, during the migration application interdependencies are going to be an issue. We've got to be able to deal with

27
00:14:00.380 --> 00:14:13.699
Craig Cory: migrating either a collection of applications that can move as a group or find ways to move components, but remain in communication during that transition process.

28
00:14:13.820 --> 00:14:29.109
Craig Cory: Obviously, downtime is gonna be a factor. We want to do this with as little disruption as possible. up from expenses planning on extra cost during the migration. I mean, in essence, you're gonna have

29
00:14:29.110 --> 00:14:44.249
Craig Cory: a period of time where you're doubling up on things you're you're executing. You're running things in the cloud rep and and identify and test out the the viability while still running things on premises.

30
00:14:44.250 --> 00:15:02.839
Craig Cory: And you're likely going to be demanding more and network bandwidth from your data centers. As you are not only serving your standard applications and services, but you're also trying to upload data and duplicate things into the cloud to prep for that cloud based

31
00:15:02.860 --> 00:15:05.899
sort of service that you plan to implement here

32
00:15:06.560 --> 00:15:22.670
Craig Cory: the last 2 come down to people you could have skeptical stakeholders. They're just not sure. And you know where things are fine. Why would we want to change? What's going to be the benefit for me, and there's gonna be a bit of you know. Buy in

33
00:15:22.670 --> 00:15:41.449
Craig Cory: to get the team members on board here, and ideally, we've got a top down agreement. That cloud is the direction we want to go. We see the net benefits. Here are the Here's what's gonna be good for you. Here's why it's been a benefit. The teams.

34
00:15:41.470 --> 00:15:52.549
Craig Cory: and lastly, of course, is lack of expertise. if it's all brand new, then it's there are things that are very different coming into the cloud.

35
00:15:52.960 --> 00:16:22.489
Craig Cory: I don't want to overstate that. I mean frankly, you're gonna operate servers and monitor your applications and keep up on the performance and the scalability. And you're going to address problems and issues just like you do with your on-premises hosted applications that parts, you know. Big picture, not all that different. It's just there are going to be some different tools. Perhaps we want to leverage a little bit of a different way to see how things are going to work.

36
00:16:23.180 --> 00:16:44.689
Craig Cory: So it's important to get people up to speed on. You know, here is the new way that you're going to see your application. Your're going to be accessing your tools and your services going forward, and of course, try to smooth that transition for all of the different members who are going to be affected by this.

37
00:16:45.520 --> 00:17:04.150
Craig Cory: So what's gonna make this successful? Again, if we're leading very large scale. We're talking one disruptive potential implementation across an enterprise. So, as I said, one of the key things is getting the an actual executive level C-suite sponsorship.

38
00:17:04.410 --> 00:17:26.799
Craig Cory: that, there is a true buy in that says, this is what we're looking to do. not necessarily do what we're fired. But this is what we're going to do. We want everybody on board to help us make this happen. In many cases the approach will be a a cloud for strategy. and the idea is simply going forward.

39
00:17:26.800 --> 00:18:02.650
Craig Cory: Anything new along with whatever we migrate to the cloud over the next couple of years. Perhaps it could be a long detailed process. But as we get our current services into the cloud, anything new we're looking to develop. We also want to focus on a cloud based implementation. So we're going to get developers. And you know, new projects up to speed in a cloud hosted environment. That that is where we're going to start the new things. We're not looking back

40
00:18:02.820 --> 00:18:15.219
Craig Cory: now we'll talk about assessing what we have on Prem and deciding what and if everything can move to the cloud, we might have to achieve that. Or maybe that's a bit of a

41
00:18:15.360 --> 00:18:22.899
Craig Cory: a luxury. Perhaps we've got on Gram. We're not necessarily leaving, but we're looking for benefits of that

42
00:18:23.170 --> 00:18:50.739
Craig Cory: now. There will certainly be changes to the organization right? New operating approaches, new processes just the new tools and able to identify. You know, we've been tracking these, you know these particular characteristics and knowing what's going on in environment. And now I got this new place I got to keep an eye on. And how am I going to get those those numbers and those reports, and what they're gonna tell me.

43
00:18:50.740 --> 00:19:04.210
Craig Cory: And how does that factor correlate with what I've been looking at before? definitely much to. Well, today, in our brief brief discussion is that we've got a roadmap

44
00:19:04.250 --> 00:19:38.399
Craig Cory: that we've really laid out. Here is the step by step. We're going to start slowly. We're going to really look at each phase of this process. So we have as few stumbles as possible, and where we do have mistakes, or we find shortcomings in our plan. We're going to re, you know, reconvene and and identify the shortcomings and shore that up to make the effectively iterative process of migration at the end, make it much smoother and more viable. Here

45
00:19:38.720 --> 00:19:53.180
Craig Cory: now something aws is a found for customers is that if they will establish for themselves what's come to be called the cloud center of excellence.

46
00:19:53.230 --> 00:20:05.850
Craig Cory: high floating name, but essentially that you've got a team of the experts, or at least the go to folks for the answers for those ongoing questions during the migration.

47
00:20:05.990 --> 00:20:20.149
You've got a set of folks who are gonna be essentially the arbiters of, how are we doing this? What's the approach we're looking to do here. If I've got a choice of service, a service. B, have we made a decision yet?

48
00:20:20.190 --> 00:20:24.440
Craig Cory: essentially, they keep the plan on track

49
00:20:24.650 --> 00:20:50.669
Craig Cory: right to keep everybody consistent. That doesn't mean that new or changed features might happen in the future. But the goal is that we got some folks who spent maybe more time with everybody else on getting down into the nitty-gritty of cloud services, cloud Features. And what's gonna prove to be beneficial for our migration. That's what's gonna be important.

50
00:20:51.100 --> 00:21:13.400
Craig Cory: of course, maintaining any particular standards compliance requirements. Sla that we have with customers or or other partners. So we know how we have to implement this. And what are the you know? What are the sensitive areas? What are the areas that are going to need the extra focus. When things happen.

51
00:21:13.710 --> 00:21:26.300
Craig Cory: We definitely want to encourage experimentation identify. What's the right mix of services deployment choices. maybe get a consistent

52
00:21:26.490 --> 00:21:50.340
Craig Cory: I don't want to say cookie cutter, but sort of find a a process that's gonna work for the deployments, for the majority of our applications. Get those migrating, get those up to speed in the cloud, get the teams focused on the new tools they need to maintain and manage those services. And then ultimately, we're gonna you know, the goal is to encourage them.

53
00:21:50.340 --> 00:22:05.319
Craig Cory: Hey? You've got, you know. You've got a new environment. You got some new tools take your application, and the benefit we're looking for is that you can advance an experiment and enhance what's going on with our solutions.

54
00:22:06.850 --> 00:22:22.260
Craig Cory: Now, if we break down the process. And definitely, when we're discussing the larger scale deployment, we don't want to short circuit any of these particular steps here. We want to make sure that we're giving them their due attention.

55
00:22:23.230 --> 00:22:28.390
Craig Cory: that that that really is. in the first few steps.

56
00:22:28.550 --> 00:22:43.179
Craig Cory: and the first 2 steps are really to focus on. You can see preparation business planning, all right. Any serious change to an environment, any serious new program. New implementation

57
00:22:43.180 --> 00:23:05.159
Craig Cory: requires that we've got all the players involved. People understand what's coming. We can as best as possible see what each step the way forward is gonna look like. So we know, here's what's happening next. And here's what we anticipate. And here's what we'll do if things are are not correct or have an issue.

58
00:23:05.340 --> 00:23:25.299
Craig Cory: So it's really doing the planning, doing the due diligence. Now, as I mentioned, if you've got just a few services you're looking to migrate, or maybe you're you're at a department level. And it's not maybe a big corporate transition yet. Maybe you're the early adopter. Say, could you go out there and see what this cloud thing looks like

59
00:23:25.300 --> 00:23:42.299
Craig Cory: That could be a simpler approach. But again, don't short circuit the the planning face right just, and it boils down to identifying. What if I got running. What are my options in the cloud? What's going to be needed to host this when I get to aws

60
00:23:42.510 --> 00:24:12.849
Craig Cory: are there choices in aws that might improve what I'm doing. You might offer me benefits right out of the box. or am I looking to get to the cloud? Get off of my local equipment, establish my processes and then start looking to optimize. Right? You can approach this in really all all these formats a choice of, do I get an improvement right out of the box, or am I just looking to get to the cloud and then start

61
00:24:12.940 --> 00:24:27.040
Craig Cory: developing and enhancing what I've got? we're going to drill down on each of these steps here just a little bit But the second primary phase is then identify. What exactly do I have.

62
00:24:27.120 --> 00:24:50.609
Craig Cory: I've got a certain kind of application. Does it have certain dependencies? I've got a web app database. 3 tiered architecture application one are the requirements of those components down to the literal issues. What kind of a cpus and disk space are needed for these? What kind of performance do they demand from their compute

63
00:24:50.700 --> 00:25:14.649
Craig Cory: because I got to be able to host something similar in the cloud. also, what kind of data set do I have? This is a large database, a small database. What kind of time will it take to migrate that data? What am I looking to do on the cloud side? There are database solutions. Do I want to run my own server? Do I want to utilize some other features of aws?

64
00:25:14.820 --> 00:25:24.139
Craig Cory: So really getting to know, what do you have? What are the interdependencies? What are the requirements for that service?

65
00:25:24.360 --> 00:25:46.849
Craig Cory: Who interacts with it? What kind of what kind of privileges will I need to re-establish. What kind of protections do I need to can maintain to make this migration much more viable, and then not to call it the simplest. But ultimately, then, it's a matter of looking at planning for each of these applications

66
00:25:46.890 --> 00:26:11.680
Craig Cory: and implementing what Aws calls their migration factory, which, if you think of it. It's kind of running through the applications implementing our our migration strategy, which is going to involve the right people in the right tools and teams to implement this, but essentially iterate through your small or large list of applications to be moved.

67
00:26:11.780 --> 00:26:26.040
Craig Cory: and you know, move them validate hand them off to the the team owners once you've got it migrated and they take over, you go back, or the team goes back and works on the next migration.

68
00:26:26.960 --> 00:26:29.929
Craig Cory: So that becomes a bit of an iterative process.

69
00:26:33.350 --> 00:26:40.989
Craig Cory: So for the basic stages, again, we want to spend a good amount of time developing the project, identifying what's needed here.

70
00:26:41.970 --> 00:26:48.350
Craig Cory: we have a kind of one way of looking at the migration process, and you can see that

71
00:26:48.690 --> 00:27:00.950
Craig Cory: identifying key elements and looking for cloud native solutions versus simply you replanting a server an app on a server in the cloud itself

72
00:27:01.060 --> 00:27:10.030
Craig Cory: we might be able to retire. Obviously some tech debt here we can isolate and decommission the hardware. We've gone here.

73
00:27:10.190 --> 00:27:16.769
Craig Cory: So the common journey for lots of customers to drive this in the May innovation goes through these key steps.

74
00:27:17.040 --> 00:27:20.439
and it goes over a period of time to make that happen

75
00:27:25.790 --> 00:27:38.449
Craig Cory: now over the past couple of years. Several years now. aws has continue to develop the assistance that they can offer for customers

76
00:27:38.520 --> 00:27:50.379
Craig Cory: during this migration process. All right. Early days. Of course you can get support and discussions with aws, you have professional services.

77
00:27:50.380 --> 00:28:15.090
Craig Cory: They would have teams that have worked with other customers performed migrations, but actually more and more formalized tools have been developed over the last few years. So anytime it's a great time to be migrating to aws but actually, it's it's certainly a as good a time as it's ever been for lots of supporting elements to make things happen.

78
00:28:16.040 --> 00:28:27.990
Craig Cory: So there's a couple of approaches here this references to a service, all the migration ready, this assessment overview. And Mra. All right.

79
00:28:28.200 --> 00:28:31.359
and you can see it's looking at the number of factors

80
00:28:31.580 --> 00:28:49.940
Craig Cory: for your team and your your environment and kind of how ready are you for this transition? Do you have all the things you need? Are there gaps in training or planning or processes.

81
00:28:50.360 --> 00:29:12.169
Craig Cory: before you want to undertake this approach here now, very early on again aws started out. As I said they had some guidelines, and they could give you assistance, and part of the additional guidelines were a document that's been developed and continues to be developed all the cloud adoption framework.

82
00:29:12.320 --> 00:29:15.360
Craig Cory: and this is sort of the

83
00:29:15.450 --> 00:29:43.949
Craig Cory: well. It is the framework. Imagine that for guiding a new, a company to come to the cloud and look at all aspects of how it affects your environment, the people, the technologies, the processes all the aspects, the security, the compliance. Look at all the aspects of what this transition is going to do, how it's going to affect you and really to see, are you ready in each of these areas to approach this.

84
00:29:43.980 --> 00:30:04.300
Craig Cory: So the Mra built on this and you can see it's effectively about a 60 question survey lines up with the adoption frameworks and goals and focal points. And it's actually done as a one day workshop. So this is, get together with Aws folks.

85
00:30:04.390 --> 00:30:30.639
Craig Cory: you know through an interview process with your key stakeholders. and they kind of walk you through this survey. Hey, where are you on this topic, on in this area. How do you feel you are in ready this year there, or what not? And you know it's not to put calls in your environment is to find any shortcomings, identify any gaps that can be addressed during the planning process.

86
00:30:30.770 --> 00:30:39.260
you know, and enter the next 3 letter acronym. The migration, readiness, and planning approach.

87
00:30:39.490 --> 00:30:44.949
Craig Cory: So this is relatively formal. Right. Get together with aws, folks.

88
00:30:45.210 --> 00:31:00.180
Craig Cory: support team, have a bit of a one day workshop with your stakeholders, and really try to, you know, dig down. And do you know, what is it we're gonna need? All we gotta. We need to show up a few elements here, or we could focus on this a bit more.

89
00:31:00.860 --> 00:31:34.720
Craig Cory: help you with prepping to make this transition right now, the actual results that come out. This is, and then have been a bigger picture. There is a bigger picture You've effectively got these different sections. And you can see here different areas that are going to be necessary for the approach. I should really highlight the the table on the left. These are really the categories of the cloud adoption framework, right? So the business, the people, the governance, the platform security and the actual operations.

90
00:31:34.760 --> 00:31:57.200
Craig Cory: Those are the focal points you can see business related and technical. So there's 2 sides to this. There's all the folks who are going to be impacted by it. And then there's literal what I tend to deal with on, you know, day to day training is. Here's how you make it work in aws the technical type. Somebody pop back real quickly.

91
00:31:57.780 --> 00:32:10.699
Craig Cory: So they show from a project some observations and actions identify if you've got some key over. So they drill down to some examples like, does your particular

92
00:32:10.780 --> 00:32:20.829
Craig Cory: system tracking database? Is it up to date? Does it have all the targeted things you're looking to migrate? Have you set up a

93
00:32:20.900 --> 00:32:27.780
Craig Cory: Cloud Center of Excellence team lead and some business folks to join in that in that group

94
00:32:27.800 --> 00:32:47.739
Craig Cory: due to your particular business environment. Do you have certain regulations requirements. You need to identify. You have an assessment team for any regulatory elements here. So it's really to help you focus on what's specific about our needs. What are we gonna need when we do this? Are we prep for that?

95
00:32:48.060 --> 00:32:50.119
Craig Cory: And again, if we zoom in.

96
00:32:50.390 --> 00:33:05.650
Craig Cory: you got a quick, you know, color noted areas to to address. Obviously, the green areas are really strong in this environment. And we see here I've got I've got a key leader in the

97
00:33:05.690 --> 00:33:17.460
Craig Cory: center of excellence that's established. I've got a stakeholder sign off and funding in place all right. So the greens are very key there.

98
00:33:17.580 --> 00:33:24.679
Craig Cory: and then we've got a few other elements. You know. What's the high level business? Use case. Maybe you haven't flesh that out

99
00:33:24.720 --> 00:33:40.730
Craig Cory: or got everybody you know on board or identifying. No, here's what's gonna be good for you. Where is our shortcut? Yeah. A detailed business case we haven't gotten there yet. Okay, haven't done that, you know. That's an area we can focus more thoroughly on

100
00:33:41.100 --> 00:33:48.900
Craig Cory: short coming here. Project management capability. We haven't really put the team together yet. We still have some folks?

101
00:33:49.170 --> 00:34:13.480
Craig Cory: you know, we're interviewing, or we're looking for key players who want to transition and focus on this project. So you can see where a lot of this is experience and people ready to go. And of course that's going to be maybe the most common aspect as well. This is all brand new, and I don't have cloud people yet. we gotta get folks up to speed.

102
00:34:16.969 --> 00:34:24.909
Craig Cory: So from the MRI itself, you could actually get to a a read out of the Mra results. You got once again the

103
00:34:25.070 --> 00:34:40.979
Craig Cory: adoption framework categories. If you can go to here. So this is a a dashboard, you could connect and look at your results, different aspects of those results. And again, when this is when you go through this process, during that interview, slash.

104
00:34:41.290 --> 00:34:50.080
Craig Cory: you know, seminar day that you're giving honest ratings. Where do you think we are? In each of the characteristics as we walk through this?

105
00:34:51.190 --> 00:35:01.780
Craig Cory: The goal is to as formally as possible identify anything that's going to impede this transition. We want it to succeed. Let's make sure we've got it.

106
00:35:01.950 --> 00:35:09.230
Craig Cory: This is showing how you can visualize the results of this assessment in a few different ways.

107
00:35:09.330 --> 00:35:20.219
Craig Cory: he map chart. So that's been called radar charge. You got different formats here. This has a bit of a kind of a timeline reference to what needs to be addressed.

108
00:35:20.470 --> 00:35:22.160
Craig Cory: Different sequence.

109
00:35:23.700 --> 00:35:41.250
Craig Cory: Right? So this is the help of the project management. Right? So the outcomes of this for you, the customer yourself get consensus on, you know where we are. What are we gonna need? Do we have any key pockets of capability? What are the gaps here?

110
00:35:41.470 --> 00:35:47.899
Craig Cory: aws, you know, evaluate. What's their capabilities? Do? This? Aws has exactly what we're looking for.

111
00:35:47.910 --> 00:35:50.520
Is it a good match right

112
00:35:51.190 --> 00:36:00.420
Craig Cory: fair to say that not everything is gonna be better off in the cloud, depending on its status, and what we need to do with it.

113
00:36:00.620 --> 00:36:05.210
But of course, the action plan is the key here. What can we do to approach this.

114
00:36:06.020 --> 00:36:35.579
Craig Cory: Now for many environments, you might be a smaller team. We're part of a smaller group that's got a large job to perform here, and most certainly you might bring on partners. There are aws partner network folks who are there to assist customers to get migrated to the cloud. even run your cloud environment once it's once it's up and going. I mean, there are service third party services to help you in all these areas.

115
00:36:35.730 --> 00:37:01.770
Craig Cory: if you're working with a partner, then obviously, they need to kind of see, well, where are you in this? in this project approach? identify your needs understand. Are there any situations we might need to address and help them to help you guide your teams through this process? obviously, fewer road locks and a common view of what's needed.

116
00:37:02.030 --> 00:37:11.400
Craig Cory: right? So we know what's coming and how it will approach it. Now, this M. Already is something to do very, very early on.

117
00:37:11.910 --> 00:37:16.070
Craig Cory: and we might even revisit it as we're progressing a bit.

118
00:37:16.630 --> 00:37:39.059
Craig Cory: But the idea, as we break down, you know, in the in the approach to migration overall. We break it down into this assessment readiness planning. And then the actual migration process. Right? That's that's later. In this whole approach. So the MRI comes very early. So we can identify any needs, any elements we need.

119
00:37:39.150 --> 00:37:53.460
Craig Cory: And that's gonna point us to the areas during the readiness and planning where we can say, Well, where do we need to shore up? Submit shoes. What should we jump on first? Let's set up a timeline of processes.

120
00:37:53.460 --> 00:38:10.449
and you can see the broad array of elements here which we'll touch on briefly. But discovery and planning is really the first bit. Looking at literally. What are the applications themselves. Right? I've got this business plan. What is it we're actually going to be migrating here?

121
00:38:10.450 --> 00:38:34.980
Craig Cory: I need to identify the Aws environment to which I will be moving things will address the lending zone idea again. Your skills level, who you got? How many folks do you have? We need to get some people up to speed. We need to bring in partners what kind of the system might be needed for them, fleshing out that business case once again.

122
00:38:35.450 --> 00:38:50.790
Craig Cory: identifying compliance needs the operations, teams, requirements, a new tools, new approaches. What's going to be needed there and depending on the size and scope of the migration and your team members.

123
00:38:50.910 --> 00:38:59.430
Craig Cory: we've got a couple of different migration approaches that we'll talk about. But in essence, ideally, we're going to be able to

124
00:38:59.990 --> 00:39:11.069
Craig Cory: commit at least a small team of folks to just handle migrations, stepping away from what they were doing or bringing them on board for this purpose.

125
00:39:11.090 --> 00:39:19.019
and they're going to deal with each of the different applications across the different departments, the different teams

126
00:39:19.040 --> 00:39:33.100
Craig Cory: they are going to be. The migration experts talk to the stakeholders say your turn. We're going to migrate. Let's get a breakdown of all your needs and dependencies, and let's put it through our migration process

127
00:39:33.720 --> 00:39:50.950
Craig Cory: so to simplify that in general, discover what we've got, an individual need design and plan our deployment approach, build and implement that transitional cloud based deployment

128
00:39:51.090 --> 00:39:58.399
Craig Cory: integrate with any other components. To make sure you've got the supporter validate. The functionality

129
00:39:58.640 --> 00:40:05.020
part of the migration is that we have a sense of usually from the team holders.

130
00:40:05.260 --> 00:40:09.150
Craig Cory: what is a successful transition? Look like to you?

131
00:40:09.460 --> 00:40:29.140
Craig Cory: if your apps up and running and working properly, of course. Are you looking for some X number of improvements or changes right as the box or just having viable environment tools you need. And then you're gonna move forward. There needs to be a validation mechanism.

132
00:40:29.770 --> 00:40:31.500
Craig Cory: Got over to the team.

133
00:40:31.610 --> 00:40:51.059
Craig Cory: we'll cut over the cloud based solution, you know. So offline the on-prem implementation. Go to the Cloud Monitor, identify look for any issues, and then get sign off from the team and go to the next application.

134
00:40:58.280 --> 00:41:09.310
Craig Cory: So with the mra. They reference to throwing another 3 letter acronym in here, and I've got to actually look. I don't even know if I remember what it stands for. the map.

135
00:41:12.040 --> 00:41:25.930
Craig Cory: Now that I'm looking at it here. Oh, there we go. The migration acceleration program. Forging me for that. map is another service within. Aws! That can get you some assistance

136
00:41:26.150 --> 00:41:31.800
Craig Cory: again, it is migration acceleration program

137
00:41:32.080 --> 00:41:45.599
Craig Cory: it's all the steps here. If you're interested in taking part in this kind of tool set again, working with aws to develop that schedule and meet and set up all the required elements here.

138
00:41:45.600 --> 00:42:06.100
Craig Cory: Facilitate using the MRI as a guide here. So this is like a next step after we've assessed our, you know, strength and weaknesses with the MRI. We then are moving to kind of an accelerated. Well, we'll get you going in this area. You need to work on this area. We have partners or or assistance. We can get you in these areas.

139
00:42:06.270 --> 00:42:13.139
Craig Cory: and the goal is to build on the observations we got from the Mra itself.

140
00:42:17.820 --> 00:42:39.489
Craig Cory: So phase 2 in essence. is now, you know, really, essentially looking at the individual applications, we're getting down to all. We're really going to migrate out. I got my teams in place. I got a center of excellence, a reference team who can guide or answer the questions that will be coming up during this process.

141
00:42:39.960 --> 00:42:53.889
Craig Cory: We've got to buy in from the top. and we are ready to look at the individual applications and start. you know, approaching the actual migration where we're moving our way towards it.

142
00:42:55.150 --> 00:43:08.480
Craig Cory: So the discovery phase dissecting what you've got a little bit here. Look for a different application patterns, kind of group things in certain ways. Are there certain interdependencies I have to respect.

143
00:43:08.730 --> 00:43:19.299
Craig Cory: what's the design process? not to mention. You know what what teams are involved in? Who are the who are the lead contacts for each of these applications.

144
00:43:19.360 --> 00:43:30.550
Craig Cory: Let's get some, you know. Get some emails and get some references and start some discussions with each of them. about their their hopes and dreams for coming to the cloud.

145
00:43:30.890 --> 00:43:42.270
Craig Cory: and then we'll start working out a backlog or a list, if you will it, to do list of the applications based on a readiness assessment that we're looking at.

146
00:43:44.420 --> 00:43:53.709
Craig Cory: So it's gonna be gathering the data we have for what's in place for what are my applications? Again, here's the owners, the critical nature of the app.

147
00:43:53.810 --> 00:44:02.310
Craig Cory: we kind of want to put a rating on that and assess, you know not only 1 2 things, you know, critical nature to the business and

148
00:44:02.540 --> 00:44:06.130
Craig Cory: kind of an assessment of difficulty, of migration.

149
00:44:06.320 --> 00:44:29.550
Craig Cory: I've got a relatively free standing application. It could be very important, but it doesn't have a lot of inter dependencies. That might be an easier, you know. First choice for an early migration. I've got some very entangled multi applications database relationship. I'm gonna have to untangle and work with that much more carefully.

150
00:44:29.550 --> 00:44:44.399
Craig Cory: Right? So get to the owner. It's a critical nature of the actual applications, the characteristics. Again, port number requirements, performance CPU memory requirements. The infrastructure needed as again to do that.

151
00:44:44.610 --> 00:45:06.330
Craig Cory: get down to the servers. And actually, the physical servers is where you'd look at the, you know, performance metrics and things. now, one thing that's nice. So this is a good chance to properly maybe size the servers to the applications where you may not have been as well sized on premises.

152
00:45:06.510 --> 00:45:35.929
Craig Cory: you might have a couple of standardized, you know, server platforms or Vm platforms, and when you got a new app you deploy the platform and you run the new app, and it might have a more C view than it needs, or you know. But it's done. It took you, cutter again. Operations like things to be very standardized. So I identify what's going to be needed for each of these deployments. Maybe I can better tune or size the

153
00:45:35.930 --> 00:45:52.830
Craig Cory: hosting environment, which, of course, in the cloud is gonna affect what you pay for as well larger servers cost more money. So if you've got the right size implementation for the hardware the performance needs.

154
00:45:53.150 --> 00:46:21.970
Craig Cory: Then you've got a better suited server for the process the network angle we're going to need. What kind of visibility this applications, public facing or definitely not public facing. I need certain ports to be accessible from one service to another. I need user access in certain different ways. Ssh or Rdb. Or other management platform interconnections. So what are going to be the needs there?

155
00:46:22.150 --> 00:46:28.469
Craig Cory: We're going to migrate those as well to control the access to our servers.

156
00:46:29.440 --> 00:46:38.549
Craig Cory: Last, but not least, what are my data storage needs? Right? I've got servers. They're gonna have this space. But I also might have, you know.

157
00:46:38.650 --> 00:46:53.609
Craig Cory: archive data or backups in large data stores. And I want to bring those to the cloud. I want to get off from again. The business driver might be. We're getting out of our data center. There are a number of customers who've done that.

158
00:46:53.670 --> 00:47:06.990
Craig Cory: Others are saying we're gonna downsize, or rather than get that next data center because we are facing size issues. We're going to stay in the one and we're going to do a cloud first going forward.

159
00:47:07.250 --> 00:47:18.939
Craig Cory: Anyway, I've got data. I've got compute. I've got software that I need to get migrated and what are going to be the necessary requirement.

160
00:47:19.880 --> 00:47:26.540
Craig Cory: So during the analysis trying. This, again, is the the discovery phase, the portfolio phase.

161
00:47:26.560 --> 00:47:33.069
How many apps have I got? How many servers I got? A cluster of 2 here and 4 there, and

162
00:47:33.190 --> 00:47:38.379
Craig Cory: are there, you know, key dependencies, as I mentioned, you know, if we could map this out

163
00:47:38.690 --> 00:48:02.099
Craig Cory: or certainly, if you've got the records already in place. The teams have nice discrete records of how these things are all assembled, all the better. If not, we have to go looking and identifying these pieces, allocate and get the right size, arrogant resources like, I said, we might better tune the target environment for the needs of our applications.

164
00:48:03.080 --> 00:48:18.349
Craig Cory: come up with a naming strategy. You might very well have a naming scheme for servers production versus development versus staging departmental naming elements. When you bring things to the cloud.

165
00:48:18.390 --> 00:48:25.170
Craig Cory: we highly recommend that you are labeling your resources in a similar fashion.

166
00:48:25.370 --> 00:48:31.899
Craig Cory: What's called tagging within aws, it's putting labels on to your resources.

167
00:48:31.920 --> 00:48:46.199
And you can have all sorts of different label you know, names and values anything that's meaningful to you. But by all means no. Bring your naming conventions straight over and remain consistent.

168
00:48:49.640 --> 00:48:51.920
Craig Cory: Now this wild diagram

169
00:48:52.240 --> 00:49:17.119
Craig Cory: is to highlight. what are we? This I've got to look closely here. 1, 2, 3, 4, 5, 6 We used to call this. I want to say the 6. Our's the letter R. The 6 rs. Of migration, I think they added a seventh one at some point yeah, there is a seventh one tucked in here now. All right, 1, 2, 3 more about? Well, maybe.

170
00:49:17.220 --> 00:49:25.229
But you know, just to be mnemonic, I suppose, an an our term for each of the approaches to the migration.

171
00:49:25.280 --> 00:49:39.119
Craig Cory: So simply put, we've gone through the discovery. We have, you know, set up our backlog, our list of what are we going to do? First, second, third, we've looked at the critical nature, the complexity assessment.

172
00:49:39.230 --> 00:49:49.580
Craig Cory: And we're, you know, the ideal is, let's pick some simple one off things move a development environment or get that stood up and running and get the Dev teams in there

173
00:49:49.640 --> 00:49:55.000
Craig Cory: things that are obviously not mission critical first. So we can learn from any mistakes.

174
00:49:56.590 --> 00:50:02.710
Craig Cory: But ultimately this point is, we've got these different migration pads. And again.

175
00:50:02.720 --> 00:50:15.149
Craig Cory: nothing earth shattering here. You'll you'll definitely understand what's mean. What's meant. But the ours if you will. The new one that got added to the mix, is this really low date

176
00:50:15.290 --> 00:50:22.430
Craig Cory: now relocate, I think you know, aws to see, more and more customers might be running containers.

177
00:50:22.720 --> 00:50:30.450
Craig Cory: Doctorize the applications, or if you're a Vmware partner and you've got virtual machines on Prem.

178
00:50:30.620 --> 00:50:40.110
Craig Cory: then bringing your containerized apps or your vmware instances, we can bring those directly into the cloud.

179
00:50:40.380 --> 00:50:46.770
Craig Cory: Right? We can host docker containers in the cloud. There are services to help you do that with aws.

180
00:50:46.920 --> 00:51:07.000
Craig Cory: there is also a partnership with vmware where you can utilize your vmware relationship. You continue running vmware hosting environments inside aws, and therefore the motion your servers from on prem to the cloud and back again. If you want.

181
00:51:07.060 --> 00:51:10.710
Craig Cory: utilize your vmware expertise to make that happen.

182
00:51:11.430 --> 00:51:22.169
Craig Cory: So that's the newest a little. Add on to this migration path here. right? And of course, for each of these migration choices.

183
00:51:22.460 --> 00:51:31.860
Craig Cory: it's going to boil down to what are the right tools. What are the right steps? Who's going to be involved here? What are the necessary target

184
00:51:32.010 --> 00:51:37.630
Craig Cory: configuration requirements before I make the transition things like that.

185
00:51:37.790 --> 00:51:45.399
Craig Cory: So from there we looked at what was the original first step, or this simply is, do we call it re-hosting?

186
00:51:45.440 --> 00:52:07.179
And the idea of re-hosting, I think is maybe clear. It's I've got a windows application running on windows. Server on Prem. I'm gonna bring up a windows server platform in the cloud and run my application. I'll migrate the data. I'll bring the application in any of its components, and I'll go from hosting it here to hosting it over there

187
00:52:07.880 --> 00:52:12.710
Craig Cory: this could potentially well, it's typically the simplest transition.

188
00:52:12.860 --> 00:52:26.909
Craig Cory: I'm not doing a whole lot to change things. I'm just not going to run the hardware anymore. So in essence, what's the approach to that? Maybe I'm just gonna manually, you know, reinstall and configure my app over in the cloud.

189
00:52:26.930 --> 00:52:37.990
Craig Cory: Not necessarily. You know a whole migration quote unquote. I gotta get the data set over there as needed for the app. or you might be able to leverage some automation tools

190
00:52:38.270 --> 00:52:49.379
definitely re-osing is something that a number of tools can assist us in doing. they can scan what you got. They can set up what's needed to host it. And they can make the transition.

191
00:52:49.940 --> 00:52:52.420
Craig Cory: So there's a lot of tools to help doing that

192
00:52:52.670 --> 00:52:57.900
Craig Cory: now a variation on that is called re platforming.

193
00:52:58.520 --> 00:53:04.589
and again they got the this quick, easier lift and shift. This one called lift and Reshape.

194
00:53:05.250 --> 00:53:11.899
Craig Cory: I guess. Put it on and put it on a workout plan But really re-platforming is to say.

195
00:53:11.910 --> 00:53:32.170
Craig Cory: Okay, I've got an applications, and let's say it's running on windows. Server 2,013. I think there was one, and of course 2,013 is a lot of days. If that's viable, 2,016 from 2,012, that's what it was. I got a 2012 hosted application like, well, that's kind of no longer supported by Microsoft.

196
00:53:32.310 --> 00:53:37.039
Craig Cory: It's not really a viable forward step over coming to the cloud.

197
00:53:37.200 --> 00:53:52.640
Craig Cory: Now is my opportunity, and really my requirement to say, Well, let's see how I can get my app on to 2022, or whatever the latest windows server platform is. I'm not as much a windows, Guy.

198
00:53:52.900 --> 00:54:15.719
Craig Cory: I'm more Linux guy But let's determine, you know. Let's get on the newer platform. And this is what re-platforming is about. I'm gonna get on the newer version of the operating system. Or maybe I'm running an older version of my software, and now is a good time to upgrade the version of the software that I'm running something off the shelf, some third party application

199
00:54:15.890 --> 00:54:42.970
Craig Cory: not to mention. And this is part of the next transitional approach. but maybe I'm gonna go to that vendor and say, you know, I'm gonna host your a new version of your app in the cloud. Do you have any more cloud? So there's licensing models or purchasing bottles, and maybe looking to see if I can enhance that as well, and I would wrap that into the next section which we call repurchasing

200
00:54:43.900 --> 00:54:50.340
Craig Cory: right now, repurchasing my literally being, you know the old third party solution I was using.

201
00:54:50.450 --> 00:55:00.549
Craig Cory: maybe it's kind of end of lines, for you know I might be perfectly happy with it, but the vendor doesn't have really any kind of cloud focused approach.

202
00:55:00.580 --> 00:55:25.949
Craig Cory: Or there are newer cloud based solutions, including software as a service offerings by vendors. Maybe I'm in the transition to a whole new solution for my Hr application or my expensing app or my customer customer management application. Maybe I'm gonna just move to something entirely new.

203
00:55:27.220 --> 00:55:46.029
Craig Cory: Right? So of course, from a migration standpoint, that's really getting a new agreement going with a new provider and then migrating the data, probably doing some transitional adjustment to get your data set into the new solution.

204
00:55:46.730 --> 00:55:55.060
Craig Cory: So we're really talking more of an install on a setup than we are on migration, but the data still has to be migrated. Of course.

205
00:55:56.990 --> 00:56:01.700
Craig Cory: Now the last migration model we call it refactoring.

206
00:56:02.290 --> 00:56:12.780
Craig Cory: and what you know, we like to highlight that the idea, of course, of coming into the cloud coming to Aws. it has some different

207
00:56:12.990 --> 00:56:18.849
Craig Cory: benefits to the way that your applications are modeled and deployed.

208
00:56:18.860 --> 00:56:23.840
you come to the cloud aws is very much about

209
00:56:24.000 --> 00:56:32.029
Craig Cory: running small, discrete, executable applications on an as needed basis.

210
00:56:32.100 --> 00:56:45.359
Craig Cory: So what we see in the our contextual approach come into the cloud, our customers looking at their large applications and saying, we should really break those down, and you want more microservice approach.

211
00:56:45.410 --> 00:56:53.950
Craig Cory: or a smaller, more modular approach, where I can actually host or execute the different module elements

212
00:56:54.270 --> 00:57:15.139
Craig Cory: leveraging different solutions in aws. There again I could containerize some of these, some could run on servers, some could actually leverage some of our server less features where I've got executed environments, and I don't have to worry about servers. I don't think about the platform to run my executables.

213
00:57:16.050 --> 00:57:23.429
Craig Cory: So in a lot of cases, certainly for your own in-house applications, if they reactive development.

214
00:57:23.550 --> 00:57:38.519
Craig Cory: Possibly already in a more modular designed approach, as such as it is the idea of refactoring or approaching your applications in a more calling, cloud, centric manner.

215
00:57:38.870 --> 00:57:51.410
Craig Cory: whether it's a big transition from how you've had your application in the past. Or maybe you're actually just conforming to a platform, a different platforming environment to host that

216
00:57:51.440 --> 00:57:53.999
Craig Cory: modular architecture.

217
00:57:54.470 --> 00:58:07.909
Craig Cory: but for the the biggest bang for the buck as far as running an on Prem app and having a cloud hosted solution is to be able to leverage all of the beneficial aspects of the cloud.

218
00:58:08.860 --> 00:58:13.010
Craig Cory: and that, again, is taking advantage of difference.

219
00:58:13.750 --> 00:58:34.400
Craig Cory: Execute environments, different implementation choices and leveraging the best ones for each solution. Here. That's the key. Now for many customers. Again, they're re-hosting, or maybe re-platforming will throw relocated. Just getting what I've got on from getting it over to the cloud.

220
00:58:34.580 --> 00:58:42.699
Craig Cory: We're trying to decommission our data center, or, you know, off offload and not do as much investment locally.

221
00:58:42.710 --> 00:58:50.540
Craig Cory: We want to get it in the clouds. Let's get it over there, and then maybe we'll think about leveraging other cloud benefits here

222
00:58:50.820 --> 00:59:17.570
Craig Cory: go to production. And actually, what used to be at the end of this line was optimize going forward right? I'm in the cloud now. I've got some new capabilities, new ways to do things as each team learns about those possible benefits expanding on how they've implemented things from the past from an on prem mindset. To now this cloud based mindset

223
00:59:22.240 --> 00:59:27.060
Craig Cory: to come up with that backlog again. We want to decide. What what should I do first?

224
00:59:27.110 --> 00:59:54.989
Craig Cory: What should I move last? What has the most entanglements? and that would be the bottom left. Your application complexity here. how many dependencies? And of course, other interactive components? Am I going to have to deal with, as I untangle, at least physically, to get something in the cloud, while some dependent components remain on Brand for a period of time. Of course, there is a critical nature to the business.

225
00:59:55.390 --> 01:00:09.420
Craig Cory: what's gonna be the impact? What's the size of the data set? You know how much activity does this application see? And not to mention different environmental priorities, as they say, probably

226
01:00:09.440 --> 01:00:26.779
Craig Cory: getting dev and test environments up and going in the cloud early on is going to be an easy win or an easier win. You're not. You're not threatening any production applications at that point, and you get your migration team gets to get to practice

227
01:00:27.210 --> 01:00:29.400
Craig Cory: right practice. Not bad.

228
01:00:32.900 --> 01:00:39.570
Craig Cory: Now, the literal nature of discovering what is in our portfolio, what do we have on our data center

229
01:00:39.690 --> 01:00:52.329
Craig Cory: again, you might have a well well documented record of every application and every interrelationship they have. Every team is very thorough

230
01:00:52.470 --> 01:01:04.839
Craig Cory: But ultimately there's gonna be those factors where you there's some over here running in Rack 13 on the second shelf. I don't know what this is who owns this? What's it doing?

231
01:01:05.030 --> 01:01:14.670
Craig Cory: So what issue is finding a way to discover what you've got running out in your environment and getting down to the details.

232
01:01:15.170 --> 01:01:17.960
Craig Cory: So they mentioned the discovery tool here.

233
01:01:17.990 --> 01:01:33.939
Craig Cory: you know. Get to the reality. 2 key approaches installing an agent on all of your servers. or can I get by with some kind of external agent list? Probing solution?

234
01:01:34.270 --> 01:01:36.400
Craig Cory: That's what this boils down to.

235
01:01:36.470 --> 01:01:43.299
with an agent based solution. Now, this means you're installing the little piece of software on your production environment.

236
01:01:43.340 --> 01:01:52.050
Craig Cory: and that could certainly be in conflict with some security requirements. So that's that's the nature of the choices we're making here.

237
01:01:52.160 --> 01:02:01.820
Craig Cory: but if I've got an agent installed on a server, then it can scan and monitor and capture data ongoing for that servers

238
01:02:01.970 --> 01:02:29.029
Craig Cory: processing and execute environment. It can capture exactly what goes on. You know, over a 2 week period. We want to get a good data collection. Get a sense of? Again, CPU and memory requirements. Disk space demands. What kind of I/O, what kind of network traffic does this implement? What ports are active on this server, so the more intimate the scanning capability, the more thorough, the better.

239
01:02:29.980 --> 01:02:34.859
we need to place that data, you know, somewhere centralized and accessible

240
01:02:35.940 --> 01:02:43.569
Craig Cory: and then identify in any dependencies, right? Or by servers or applications interdependent with other servers.

241
01:02:43.600 --> 01:02:47.910
Again, that will jive with maybe the port number interactions

242
01:02:48.160 --> 01:02:56.409
Craig Cory: like, I said, performance, other elements there. and are there any known constraints with this on premises? Solution?

243
01:02:57.100 --> 01:03:11.560
Craig Cory: Try to identify that. Not bad. If you've got a method of doing that cost analysis of your on prem solutions here. in many cases, environments have done a breakdown of, you know, per server cost per month.

244
01:03:11.590 --> 01:03:17.740
Craig Cory: You know. What's the what overall costing somebody get a sense of what their spend is.

245
01:03:18.260 --> 01:03:27.900
Craig Cory: and that's a very nice thing you could use to compare with tools that can look at, spend in the cloud, which is very much on a usage level.

246
01:03:30.530 --> 01:03:35.360
Craig Cory: Now, quick note here what's called the landing zone. Think of the landing zone as

247
01:03:35.950 --> 01:03:46.850
Craig Cory: what's the architectural structure in aws where I'm gonna run my applications right? And they're showing you some examples here.

248
01:03:47.120 --> 01:03:54.869
Craig Cory: The approach that's become the standard and the recommended approach by aws for customers

249
01:03:55.270 --> 01:04:00.160
Craig Cory: is that you create a multi-account environment.

250
01:04:00.190 --> 01:04:08.629
Craig Cory: and an account is, you know, one membership if you will, with aws create an account to get a 12 digit number. That's an account.

251
01:04:08.990 --> 01:04:32.739
Craig Cory: but for isolation purposes for organizational purposes, customers are more and more leveraging independent multiple accounts to separate workloads from a, you know, from a a security or a compliance standpoint key. Dev separate from broad keep

252
01:04:32.740 --> 01:04:45.940
Craig Cory: local separate from 4 in the inner involvement, whatever you might want to deal with right? So this diagram is showing the little dotty boxes would be the different accounts here.

253
01:04:46.910 --> 01:04:58.830
Craig Cory: and multiple accounts. Aws has a utility or a service to manage that called organizations. So we actually have a managing organization's account.

254
01:04:58.860 --> 01:05:03.400
Craig Cory: and it's gonna manage the member accounts of the organization.

255
01:05:03.510 --> 01:05:22.860
Craig Cory: So you deploy your organizations. And again, your accounts, part of me. And you can have accounts. You can see for the sandbox, for people to practice. You've got a dev free, broad, and broad shared services other elements. Also, in this multi account approach

256
01:05:23.070 --> 01:05:34.059
Craig Cory: is to take the login, the record keeping the performance, monitoring from all your various independent accounts.

257
01:05:34.090 --> 01:05:46.229
Craig Cory: and centrally track those in what they're calling core account here. But essentially, you know, logging and performance monitoring account.

258
01:05:46.650 --> 01:05:55.920
Craig Cory: So everything's in the central place. It's separate from where it's being generated. It can be monitored by separate teams who have that responsibility.

259
01:05:56.540 --> 01:06:05.369
Craig Cory: But big picture is, I've got to think about the architecture in the cloud before I bring up some servers, and I gotta have

260
01:06:05.660 --> 01:06:22.349
Craig Cory: something in like, where am I going to host this? So the landing zone discussion is going to be part of that initial thing. So we got to get this out there, set up and going, and somebody able to understand it before my first application can go to the cloud

261
01:06:26.690 --> 01:06:34.820
Craig Cory: mentioned already the center of excellence. This is in your environment. Your team members, possibly with partner assistance

262
01:06:35.120 --> 01:06:57.959
Craig Cory: to get your you know your key layers kind of the standard bearers who do we go to when we have questions, when we need to resolve issues, or, or, you know, conflicts over choices kinda to have a standard bearer, if you will, and of course, somebody who's maybe got an answer to a question. I don't know how to do this. how do we want to approach this

263
01:06:59.450 --> 01:07:02.339
Craig Cory: that we can go to

264
01:07:03.510 --> 01:07:07.269
now? They look at a few different elements here

265
01:07:07.500 --> 01:07:15.679
Craig Cory: a decentralized approach for the cloud where you've got, you know, effectively. Each business unit kind of runs its own

266
01:07:16.130 --> 01:07:32.579
Craig Cory: loud department, if you will. They do their own thing. They've got their own strategies. for shared services. You might have a more centralized approach, different strategies, but managed by a central team

267
01:07:32.720 --> 01:07:39.130
Craig Cory: or, again, center of excellence. We've got a standardized strategy

268
01:07:39.250 --> 01:07:45.600
Craig Cory: that's able to adjust and modify for different delivery requirements. Right?

269
01:07:46.160 --> 01:07:55.850
Craig Cory: And of course, the most standardized, most structured would be that everything has a central approach. I'm a central reference.

270
01:08:02.070 --> 01:08:15.749
Craig Cory: So again, this starts with the business case. why does it make sense for us to go to? Aws? we've got to look at the cost of this migration itself. As I said, you're going to spend more money on the migration

271
01:08:16.000 --> 01:08:28.070
Craig Cory: to get to that place cost of ownership modeling. We have tools to do that business value assessment. And what kind of optimizations are we anticipating?

272
01:08:28.319 --> 01:08:38.289
Craig Cory: And we can attempt to, you know again, monetize or or put numbers against that to decide how best to make this happen.

273
01:08:41.460 --> 01:08:52.790
Craig Cory: So start from a a focus business case. Here, you can see we went through the Mra, and that might have helped us refine the business case a bit more

274
01:08:53.120 --> 01:08:57.590
Craig Cory: accelerator content which came from that map.

275
01:08:57.740 --> 01:09:11.699
Craig Cory: my mediation migration acceleration program to try again. It's more finally tuned. And then, when we're getting into the real readiness and planning phase, we've got the detailed approach here

276
01:09:13.080 --> 01:09:20.439
Craig Cory: that are down to each department or each team. Here is what you're looking for in this migration, and what we hope to achieve from it.

277
01:09:22.479 --> 01:09:25.569
Craig Cory: obviously planned out all these elements of

278
01:09:25.609 --> 01:09:36.420
Craig Cory: summarize all of this, you're spending time planning, assessing it, doling out expectations and identifying steps to take here

279
01:09:38.319 --> 01:09:55.669
Craig Cory: ultimately, then you've reached the line where, hey? It's time for that first app on the backlog. we start the migration day one here set up a process. You'll look at the details of this app. Look at requirements. Look at our landing zones and the environment we've got.

280
01:09:55.910 --> 01:10:12.690
Craig Cory: and we'll look at migrating an application, and maybe several iterations of an application but the goal is to, you know. Start, simply get a little bit of success under your belt, and or have some issues and address them and learn from them.

281
01:10:13.210 --> 01:10:20.070
before we get to the mission critical and the highly interdependent and complex components here.

282
01:10:21.640 --> 01:10:24.339
Craig Cory: if we can identify. And really

283
01:10:24.420 --> 01:10:30.190
Craig Cory: I don't know. Document slash orchestrate the operations.

284
01:10:30.250 --> 01:10:36.619
Craig Cory: I mean, monitor, how it goes, the logging, the provisioning, identify all the steps you're taking

285
01:10:36.940 --> 01:10:48.260
so that you can plan for you know any backups, disaster, recovery, etc., Your goal is to set up this iterative process again, they can just keep on rolling

286
01:10:49.050 --> 01:10:54.810
Craig Cory: as the success has become more and more the higher percentage, if you will.

287
01:10:57.070 --> 01:11:08.100
Craig Cory: Now, another approach to this is just looking at. Who's responsible? Who's kept in the loop? Who's just informed on the different steps of the process.

288
01:11:08.240 --> 01:11:18.350
Craig Cory: So a racy chart is a giving us that kind of a breakdown, responsible, accountable, consulted and informed. They through a support in here as well.

289
01:11:19.180 --> 01:11:30.100
Craig Cory: But you've got to know different team or role role jobs identified here. the activities which are essentially kind of running

290
01:11:30.710 --> 01:11:37.090
Craig Cory: when I call this and that serving timeframe in this case.

291
01:11:37.270 --> 01:11:56.519
Craig Cory: But we're just identifying, you know, who's going to need to be involved. Who's the go to the lead? Who's responsible for each of these steps? Who's Who's kept informed? who do I go to? If there's a problem what consults so kind of break down?

292
01:11:56.860 --> 01:11:59.500
Craig Cory: How will you approach the needs of each of these

293
01:12:01.240 --> 01:12:05.999
Craig Cory: kind of getting during the end here. So I'm just gonna cover these last bits

294
01:12:06.090 --> 01:12:10.450
Craig Cory: we've touched on them. We just got a slide on each one of these. But

295
01:12:10.660 --> 01:12:32.929
Craig Cory: of course, understanding the security requirements, you know, for your, you know, corporate security legal requirements. whatever is necessary, governmental requirements identify what you need, and of course, have a ideally a team that's going to be responsible for keeping track of the steps and the compliance needs.

296
01:12:36.450 --> 01:12:44.049
Craig Cory: Now, one of the first things we talk about in the Aws training very early on

297
01:12:44.150 --> 01:12:47.590
is that coming to the cloud as a shared responsibility?

298
01:12:48.050 --> 01:12:49.680
Craig Cory: You are

299
01:12:50.720 --> 01:12:57.420
Craig Cory: getting rid of your hardware and your data centers to some degree.

300
01:12:57.570 --> 01:13:03.949
And you're coming to aws is like, Hey, could you do that? All that hardware stuff for me. Could you do the infrastructure?

301
01:13:04.180 --> 01:13:15.569
Craig Cory: I don't want to do that anymore. it's tedious and repetitive, and it's just churn. It doesn't give me net benefits here. It's just where things have to go.

302
01:13:15.680 --> 01:13:22.040
Craig Cory: So that's aws the responsibility of the cloud, as they like to say.

303
01:13:22.090 --> 01:13:43.719
Craig Cory: which is added simplest. We'll protect the data centers. We'll protect the equipment. We'll protect the services. We'll maintain them and keep the Up Times with a variety of slas of performance, and we'll provide you with compute storage, database networking across the globe

304
01:13:44.140 --> 01:13:46.360
Craig Cory: right all around the world. Here

305
01:13:47.200 --> 01:13:59.180
Craig Cory: now, when you bring your solutions to our hosted environment, you, the customer are still responsible for that application you're deploying.

306
01:13:59.530 --> 01:14:18.480
Craig Cory: Does it work properly? Who's in charge of running it? Who's got permissions to configure it? where is your data going to be stored? Are you going to encrypt your data? What's going to be the communications method? Are you going to encrypt traffic between your servers and your other elements

307
01:14:19.140 --> 01:14:25.699
you are responsible for protecting your applications and the OS. It's running

308
01:14:27.820 --> 01:14:33.880
the platform there for you. But you gotta keep the services running and the security of the data.

309
01:14:37.990 --> 01:14:55.839
Craig Cory: Now to get a ride down to some tools. Aws! Has expanded in years, expanded a little bit into some more tools here, and I was just having a look. And there's actually some newer things that I've not even seen before. So there's a lot of good stuff.

310
01:14:56.500 --> 01:15:12.779
Craig Cory: all right. but simply puts There's a section in your Aws management console all about my migration. and there's a centralized tool called the migration hub, which is referenced right there. Look for the shield

311
01:15:13.080 --> 01:15:22.930
Craig Cory: migration Hub. Now the I guess it's early on is that this is a one stop place to see all the phases of your migration.

312
01:15:23.060 --> 01:15:40.839
Craig Cory: So in the Hub there are discovering records. and there is a discovery tool that aws offers an agent based tool that you can install and gather data from your systems. Right? It comes to a database in your cloud account.

313
01:15:41.840 --> 01:15:58.880
Craig Cory: And then there are migration tools. And in fact, this is where some enhancements have come along new. It's not new. It's but the newest migration tool to the mix is literally called the Server Migration Service.

314
01:15:59.730 --> 01:16:11.619
Craig Cory: there you are right there. server, migration service. Now, if you know anything about aws, you would know that that would likely be called SMS

315
01:16:11.730 --> 01:16:17.469
Craig Cory: server migration Service. But the fact is, we have something else called SMS.

316
01:16:17.640 --> 01:16:27.699
Craig Cory: So for a better or worse, the server migration service is called mg, n, as in migration.

317
01:16:27.930 --> 01:16:41.969
Craig Cory: all right. So Mgm. Is the Server migration service. But just to know a very robust tool, we're literally moving servers and applications from an on to a cloud.

318
01:16:42.130 --> 01:16:53.009
Craig Cory: There is a focus database, migration service as well. That's been with us for a little while. Longer service migration services.

319
01:16:53.040 --> 01:16:56.969
Craig Cory: the newest of the migrating tools to get here.

320
01:16:58.120 --> 01:17:00.229
Craig Cory: What's here?

321
01:17:03.260 --> 01:17:04.400
Craig Cory: All right

322
01:17:05.750 --> 01:17:16.390
Craig Cory: now? He's certainly you can see a number of other elements here. let me point back over to the decision support, application discovery Service. That's the agent driven tool.

323
01:17:16.460 --> 01:17:27.959
Craig Cory: You install the agent on your servers, and it just got a sits there and listens, and it records information to a database in the cloud in your cloud account.

324
01:17:28.760 --> 01:17:31.410
Craig Cory: And then you've got some migration tools

325
01:17:31.520 --> 01:17:44.820
Craig Cory: There's an older application migration service that was focused on Vm's migrating, not not bare metal server and and the like.

326
01:17:45.880 --> 01:17:55.019
Craig Cory: and that just to highlight it. So it gets rolled into the migration list or a number of data transmission tools.

327
01:17:55.630 --> 01:18:12.659
Craig Cory: data storage and transfer. So we need to get data from our on prem environment to the cloud? Do I have a little bit of data? Do I have a lot of data? Do I have ongoing upload needs? Or one huge transition to get repositioned.

328
01:18:12.840 --> 01:18:19.869
Craig Cory: There are different tools to make different forms of data, migration itself

329
01:18:19.910 --> 01:18:24.699
effectively. Is it over network connectivity and using bandwidth.

330
01:18:24.840 --> 01:18:33.960
Craig Cory: or the one solution here called snowball. which is literally writing my data to a device and ship it back to aws.

331
01:18:39.660 --> 01:18:47.050
Craig Cory: So from all of this again, what really seems to guide at least initial.

332
01:18:47.200 --> 01:18:52.819
Craig Cory: you know, getting over the first early hurdles. Is that strong justification?

333
01:18:53.160 --> 01:19:02.890
Craig Cory: we have. you know, intention to go to the cloud. We have these reasons why we have seen and device how it's going to benefit us.

334
01:19:03.010 --> 01:19:08.570
Craig Cory: an effective business case and the process to create it helps remove friction

335
01:19:09.050 --> 01:19:13.110
Craig Cory: right? Convince the the skeptics ideally

336
01:19:13.190 --> 01:19:21.180
Craig Cory: helped them with the transition as well. if we have a strong business case, we're gonna migrate faster.

337
01:19:21.740 --> 01:19:25.879
Craig Cory: I want to stay true to the true to the goal, if you will.

338
01:19:27.190 --> 01:19:38.060
Craig Cory: some of the key thoughts, you know, some infrastructure savings as we get things migrated, we can be powering things down right? We can save a little time.

339
01:19:38.250 --> 01:19:49.589
Craig Cory: ultimately looking at the post. Migration cost assessments right? And what do we see as the other kinds of business benefits here?

340
01:19:49.630 --> 01:19:52.619
Craig Cory: It's not necessarily just net dollars.

341
01:19:53.350 --> 01:20:04.719
Craig Cory: more agility, more innovative environments better place for developers to expand on their projects. and lots of other elements. Here.

342
01:20:05.850 --> 01:20:21.009
Craig Cory: a lot of ways you approach your transition. And again, there is a kind of a speedy approach. Let's get to the cloud and think about changes later. or maybe incorporating some changes in the transitional phase

343
01:20:21.260 --> 01:20:29.900
Craig Cory: that it depends on where you and your applications and your teams are in the process. And part of what's the business driver like? I said.

344
01:20:30.450 --> 01:20:46.179
Craig Cory: we've got a 7, you know. We had a 5 year plan, and I've got 250 applications. We've got several dozen that are home grown. We're gonna spend the time and start early, we factoring some of those.

345
01:20:46.860 --> 01:20:51.330
I didn't mention the other 2 words. By the way, now we're back to the picture.

346
01:20:51.700 --> 01:21:07.609
Craig Cory: there might be some solutions. You are going to keep on like I said. There are some things that will not move to the cloud or won't be viable in a cloud, which is x 86 based platforms of

347
01:21:08.540 --> 01:21:21.090
Craig Cory: and a nice side benefit. You might find some things you don't need any more. You could retire some services that they're running and forgotten, or you've got lots of small

348
01:21:21.170 --> 01:21:32.179
Craig Cory: small services you can combine into something larger. so you might find out some retired services as well, you know. That's just net gain right out of the box.

349
01:21:34.340 --> 01:21:45.199
Craig Cory: this is the chart for each of those approaches here. and they don't have the relocate on the chart here. I don't know why, but again, that relocate is the new member.

350
01:21:45.910 --> 01:21:53.429
Craig Cory: If your container eyes or vmware, you're literally just bringing that image to a new hosted place.

351
01:21:53.760 --> 01:21:56.680
Craig Cory: and you can transition that in a matter of minutes.

352
01:22:00.840 --> 01:22:01.710
Craig Cory: Alright.

353
01:22:04.730 --> 01:22:15.060
Craig Cory: they're using this shirt to kind of identify where do we see our my direction? Choices I got. Oh, we're going to re-host about 40%,

354
01:22:15.190 --> 01:22:23.980
Craig Cory: 30% re platform. That kind of makes sense. Right? We're running on some servers. I'll get some servers in the cloud and we'll host it over there.

355
01:22:25.360 --> 01:22:26.490
Craig Cory: Okay.

356
01:22:29.170 --> 01:22:43.110
Craig Cory: now, of course, our role here is to offer you the training the back of the the planning and and execution for all your needs within. Aws.

357
01:22:44.970 --> 01:23:04.869
Sophia :: ExitCertified Support: I'm going to invite and see if I can find her here. Yeah, so we are. You still with me? I think she is. Hey, Craig? Yes, I am still with you. And that seems like a good note to share our summer day, or some are ready. Savings

358
01:23:04.930 --> 01:23:06.689
Sophia :: ExitCertified Support: sounds good.

359
01:23:07.930 --> 01:23:10.569
Sophia :: ExitCertified Support: and just 1 s I'll bring that up there.

360
01:23:15.320 --> 01:23:23.070
Craig Cory: So let me just say here, while while Sophie is bringing up some of our information. thanks, everybody for joining me

361
01:23:23.150 --> 01:23:39.479
Craig Cory: this this presentation has been reported. and the link for that recording Sophia will put into the chat here again. I didn't see any chat questions, so if you have any questions right now you might want to drop in there

362
01:23:40.320 --> 01:23:46.049
Craig Cory: we can make that happen. I can try to answer those.

363
01:23:47.760 --> 01:23:50.240
Sophia :: ExitCertified Support: Thank you. Crack! And I'll share my screen now.

364
01:23:50.310 --> 01:23:51.720
Craig Cory: Excellent!

365
01:23:55.700 --> 01:24:06.450
Sophia :: ExitCertified Support: All right, I do have to apologize. My full. My full screen window is trying to take over both my monitors, so I'm gonna leave it all But Is everyone able, or at least, Craig, are you able to share

366
01:24:06.730 --> 01:24:07.850
Craig Cory: that works?

367
01:24:07.940 --> 01:24:15.850
Sophia :: ExitCertified Support: Very good? All right. So we do have a summer promo for classes. If you want to learn more about this, I'm going to put a link into the chat window for everyone.

368
01:24:15.990 --> 01:24:43.210
Sophia :: ExitCertified Support: It covers pretty much. All of our live virtual classes, mostly the public ones. But if you want to find out about private ones, for instance, if your company is interested in private training. You just want to follow that link and click on. Get a quote, and you can chat with one of our representatives about private training. But for public classes. You can get up to $500 off a hundred, as you see on the screen off a one day. Course 200 on a 2 day course, etc. you can actually save quite a bit there.

369
01:24:43.380 --> 01:24:49.219
Sophia :: ExitCertified Support: But you do want to make sure, if you look at that link that you register for that class before the deadline.

370
01:24:49.850 --> 01:24:52.149
Sophia :: ExitCertified Support: And that deadline is on the website.

371
01:24:52.930 --> 01:25:06.169
Sophia :: ExitCertified Support: And as Craig mentioned about the recording for today, you'll be able to see that tomorrow, at the following URL, that I'm also pasting into the chat window for everyone. So that's in our resources section of the website.

372
01:25:06.280 --> 01:25:08.440
Sophia :: ExitCertified Support: And you should see that under videos.

373
01:25:08.670 --> 01:25:10.420
So I'll give you just an example.

374
01:25:12.130 --> 01:25:21.989
Sophia :: ExitCertified Support: If you go to resources and scroll down, you'll see our videos section here. and you should see that tomorrow with the same title as the Discovery day today.

375
01:25:23.460 --> 01:25:33.559
Sophia :: ExitCertified Support: So if anyone has any questions about that summer promo, or about how to access the recording feel free to reach out to me in the chat window. you can also email us any time altogether.

376
01:25:34.280 --> 01:25:38.340
Sophia :: ExitCertified Support: Team's email address into the chat window as well.

377
01:25:40.860 --> 01:25:56.350
Sophia :: ExitCertified Support: That's live virtual exit, certified.com. That's my team that I'm from. whether it's for a live virtual class or not will help you get routed to the same. You know the right person that you're trying to look for. Either way. If we don't know the answer to something. We're always happy to help and find that answer for you.

378
01:25:56.840 --> 01:26:03.709
Sophia :: ExitCertified Support: but otherwise definitely recommend that you look into that deal that we have for training. Now it's pretty good savings. We try to do that most summers and

379
01:26:03.720 --> 01:26:08.809
Sophia :: ExitCertified Support: get you ready for the fall, coming up and get you situated with whatever that you need.

380
01:26:09.670 --> 01:26:11.760
Sophia :: ExitCertified Support: So, Craig, I'm gonna stop sharing now.

381
01:26:13.520 --> 01:26:18.029
Craig Cory: That's fantastic. I'm just going to put up the

382
01:26:19.420 --> 01:26:21.990
this last slide. Where are you?

383
01:26:22.580 --> 01:26:26.390
Craig Cory: That's the one I wanted all right. Thank you.

384
01:26:26.400 --> 01:26:34.069
Craig Cory: this mentions Miles Brown. He wasn't with us today. He's usually my co-conspirator in these

385
01:26:34.220 --> 01:26:53.510
Craig Cory: discover days. but I am right gory. one of the instructors. I've got a great set set of team members here who deliver not just aws, training many, many other services as well. Platforms, architectures.

386
01:26:53.680 --> 01:27:06.939
Craig Cory: but you know we would be happy with the the links and information Sophia provided happy to help you with any of your training needs absolutely. And I wanted to make a quick note.

387
01:27:07.350 --> 01:27:24.500
Craig Cory: today's presentation is actually a nice summary of a 3 day migration class. So there is a some hands on some labs to try out some of the services But there is a 3 in a class which goes into this

388
01:27:24.520 --> 01:27:41.909
Craig Cory: detailed planning approach with a little more, little more detail, if you wish. and since you mentioned the different promotional offers here, it it made me think, too, majority of Aws training are 3 day classes. Just so you understand that.

389
01:27:42.260 --> 01:27:54.219
Craig Cory: But by all means come to our website, have a look at what's being offered. It is the full aws certified trading selection.

390
01:27:54.700 --> 01:27:58.429
and we'd be happy to get you going on your aws journey.

391
01:27:59.160 --> 01:28:02.540
Craig Cory: I look forward to seeing any of you in training going forward.

392
01:28:03.660 --> 01:28:07.529
Craig Cory: Thank you. Everyone appreciate you spending the time with me today.

393
01:28:07.980 --> 01:28:10.679
Sophia :: ExitCertified Support: Thank you, Craig. Have a good one. Everyone.

AWS Discovery Day: Strategies and Tools to Perform Large-Scale Migrations [Webinar]

To watch enter your email address

Alert!

Modal Title

Error!

Default Title

Prompt

Confirm

Login