6.3 Lab Activity

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

2 hours 48 minutes
Video Transcription
So what? The deployment Now complete.
Let's just take a look over at Azar and see, uh, what was actually created in the system.
I'm gonna navigate over here to the resource groups in the average or console Terra Form Modules. Resource Group. That was the name of the resource group that was created as a result of the Terra form script we just ran. We could see that there's a whole lot, right. We use the virtual network module and that set up a virtual network in various sub nets.
We could use a computer model module to set up the virtual machine,
but you can also see take rear of creating other resources for us, such as a network security group which is going to set up rules around this virtual machine.
Created public I P addresses. Excuse me. This first network security group is relative to the virtual network. Where is the second network Security group is related to the virtual machine. We have here availability sets, network cards and even operating system discs.
So if we didn't use these Mongols, we would have had to lay out
all of these. Resource is in defining in our care reform file. But by using these modules, we kept our terra form file quite simple. And we relied on a pattern that the modules were implementing of running with the assumption of creating a network card, creating an operating zip disk that followed a certain naming convention, creating an availability set,
putting network security groups and associating nose with the virtual machine.
Just a lot of little things that certainly add up to to create a pattern that's reusable and a pattern that we took advantage of.
At this point,
you have learned a lot about terra form. We just learned the power of modules. We've covered a lot of the basics. We've talked about the deployments thean it scripts, initialization process, different providers.
So I'm gonna review the lab activity with you here and now. The procedure give you some guidance and objective. And then when you're done building the lab in the next video, we will be exploring, and I'll demonstrate to you the my solution to the lab activity
and walk through what I did and give you a little
rationalization as to why I did it.
So our real objective of this activity is to create a desert container. Instance. You're familiar with containers. A circuit tater instance really is just a deserves way of allowing you to deploy a container. And that container gets managed so we don't have to worry about creating a virtual machine.
This isn't quite as her cue bernetti service. That would be for more clustering containers,
a little more last x scalability and so forth. We're just gonna do we just have one container? We're just gonna keep it real simple. We're gonna use these are container. Instance. When this is all said and done, you're gonna have something that's deployed you gonna be able to access it through. Ah, you are l and H D P u R l in your browser. And it's gonna look like this.
Um when? When we've done this.
So how you gonna go about this? I'll give you some touch points and some hints, but I'm hoping you can pull with all the training that we've had so far and assemble this solution to the lad activity version for most.
Put the terra form files in a separate directory. Um, because we don't want you to inherit that the terra form state some of the other downloads that we've done in the prior activity. So put your teeth filed in the separate directory. Go ahead and search that terror for module registry. The link is right here on the get home page
we're looking for Right in this circumstance is some sort of
reserve container instances, and you're gonna then locate the module that's published by the person that you like a C. I is a common acronym used for his or container instances. If you're not familiar,
you're gonna greet the Terra phone files, which buildout Thea's er container instance. Uh, you're gonna want to use a certain image this a c I Hello, world. It's on the public public Dr Registry provided by Microsoft. It's what's gonna set up the Web server and just serve back this simplistic page.
So this is the image you're gonna want to use.
And of course, you're gonna want that to configure the module such that the container is running on poor dating and listening Import 80 which is our standard. Http ports, um
finally, another key part of the activities make sure that the terra form files are producing an output and for this particular output. We wanted to be the fully qualified domain name off the Earl
that we're going to use to access and open up this in the browser to open up this container, which gives us the bolo
Web page to show us success. And then finally, that's exactly what you're gonna do. You're gonna take that fairly quiet, qualified domain name that is an output when you run the deployed process and you're gonna open it up in your browser.
And once again, it should look like this. So go ahead, pause the video. Take a deep breath. Think about how you're gonna go about this. Create a new fresh directory. Open up. A main dot T f file is a starting point in your I d on. And your first step is gonna be adding there's there, are in provider, right?
And then, from there you can
extended and find the appropriate modules that that you were able to locate through the Terra form registry. That'll help you set up this container Instance. So thank you. I look forward to returning shortly and reviewing the lab activity outcomes
Up Next