What I use to learn (the BEST IT training): https://ntck.co/itprotv (30% off FOREVER) *affiliate link
You only need THIRTY CENTS to build your very own hacking lab using real Vulnerable Machines that you are going to break into to start Hacking right now! In this video, Network Chuck will show you how to do this using Kali Linux and AWS so you can have your very own lab that is convenient and fun in order to hack your target!
🧪🧪Try it yourself!! (Links, docs, and walkthrough): https://ntck.co/awslab
🔥🔥Join the NetworkChuck Academy!: https://ntck.co/NCAcademy
0:00 ⏩ intro
2:05 ⏩ What do we need?
6:13 ⏩ Here we go! Time to build our ULTIMATE HACKING LAB
16:05 ⏩The difficult part of the set up!
22:53 ⏩Let’s launch our vulnerable machine!
25:15 ⏩ Time to log in to your Kali box!
29:01 ⏩ Outro
The only way to become a hacker is to start hacking like right now, immediately start breaking stuff. And in this video, you’re going to do that. I’m gonna show you how to build the best hacking lab you’ve ever seen. And it’s only gonna cost you about 30 cents, probably less. Actually. Now the first thing you’re gonna hack today is the YouTube algorithm. Let’s make sure you do hit that light button notification bell comment, subscribe. You gotta hack YouTube today. Ethically of course, now, legit, I’m gonna show you how to build your very own hacking lab with real vulnerable machines, machines that you can practice breaking into to hone your hacking craft. And you don’t need anything like you don’t need this big beefy gaining computer with virtual machines. No, you can have the crappiest laptop or even your iPad, or just really anything that has a web browser.
And I’m not kidding. It will be the best lab you’ve ever had. Now I know what you’re thinking like Chuck, what’s the catch. This sounds too good to be true. Well, there is one catch knowledge, knowledge. You have to know how to do what I’m about to show you. It’s not easy, but in this video, I’m gonna show you how to do it. So that worries out the door. Now, I actually got this idea from watching the hands on hacking course at it, pro TV. The incredible Mr. Daniel Lowry was showing me how to break into vulnerable machines, which is awesome. But the only problem is that to follow along with this and actually try it yourself, you have to build out your own lab, which not everyone can do. So that’s where my mission began. I got my cup of coffee, always need that.
And I set out to find the best solution, the best lab you can possibly build at the lowest cost. And it needed to be accessible to most people, if not everyone. And that is where the cloud comes in there real quick. It pro TV is the sponsor of this video. And seriously, they are my favorite training provider. They are what I used to study and learn it. And especially things like this stuff right here, hacking, I’m actually building out the lab to be able to gain access to all these vulnerable machines. So what I would do is build out this lab and then sign up for it pro TV and follow along with Daniel Lowry and learn how to do this stuff. And it’s not just hacking that they have, they’ve got everything from getting started in it with comp Tia courses. Look at all these things to Cisco networking.
Love it, Python. So just as they’ve got everything. So if you’re ready to get serious about your it career and you wanna learn it like me, check it out, link below it, pro TV slash network. Chuck use the code network, Chuck, and you’ll get 30% off forever, which is kind of crazy. So just, just do it. Okay. So here we go. The super secret awesome hacking lab that will only cost you 30 cents per day. Our lab depends on two things. First we need vulnerable machines and things we can actually hack into. That’s where the incredible site vulner hub comes in. Let me show you what this is. What you’re seeing here is a massive library of vulnerable machines that you can hack into. They’re just sitting there begging to be hacked. Why aren’t you doing that? They want you to hack them and rangy from easy to help.
They pretty much have everything you need to hone your hacking craft. And did I mention it’s free, which is crazy. You just jump into one and click on download and it’s yours, but we do need a place to actually put those machines so we can hack them. And that brings us to our next thing. We need the cloud and specifically AWS. Now I know some of you are probably like, Ew, the cloud, Ugh, no, let me, let me show something to you with the cloud, with just a few clicks, you can have an unlimited lab, whatever your hearts desire, recklessly spinning up a ton of virtual machines to do and saying things because it’s not our computer. It’s, Amazon’s massive
Data centers across the world. So basically you can learn hacking without any limits. Now with our environment, here’s what it’s gonna look like. Well, first create a virtual machine that will be our attacking box, our attacking hacking machine in this lab that will be Cali Linux. And then we’ll create another virtual machine, our target, which will download and get from UB. Now the cloud isn’t free, but I did the math and here’s what’s gonna cost you. Don’t let the sticker shock scare. You this’ll be a total of about 4 cents per hour. Time to get a second mortgage honey, but seriously, that’s it. And that’s only when it’s actually running. You see it when you’re done, you just shut your machines down and then it’s costing you barely anything because that’s how the cloud works. AWS will charge you per second of the stuff you use.
So in our example, let’s say you spin up this lab. That’s about 4 cents per hour. You hack for a marathon of eight hours in a day. That’s about 30 cents. And then when you’re done, just shut it down and that’s it. Now, if you don’t think that’s awesome, then you need awesome lessons. Now. Sure. You can do this completely free on your own computer. Totally. You can spin up virtual box on your machine. And as long as you have extra Ram extra CPU, like a gaming computer, you can do this on your own, but not everyone has that. And honestly, I have all of that. I have a huge home lab, but often I just end up spinning stuff up in the cloud because it’s easier, more convenient and frankly, more fun. Now there is one kind of big, gotcha. You know, it was coming and it’s not that crazy.
The cloud cost money. We just talked about that 4 cents per hour. And that does involve you having a credit card. When you sign up for AWS, you gotta put a credit card down, but they will only charge you for what you use. And as long as you don’t spin up like 20,000 virtual machines, you’re probably gonna be okay. Now the other thought might be, Hey, there are other websites that have pre-built labs. I can just click on and, and play with. And those are actually great, but there’s something special skills to be gained from building out your own hacking lab. It’s something that if you can do it, if you can afford to do this, which 4 cents an hour, I think most of us can swallow that if you can do this, you need to not a requirement, but it will help you out. You’ll be better for it.
All right. I think I had you convinced, right? Like we’re gonna do this right now. You’re gonna do it with me. Okay. And actually one last thought, you’re probably also thinking why doesn’t everyone just do this? This seems almost too easy. And the reason is that it’s just kind of hard. You have to have a bit of cloud knowledge, cuz honestly it’s not the easiest thing to do, but thankfully I’m gonna show you how to do this. I’m gonna hold your hand, walk you through every bit of it right now. So by the end of this video, you’ll have full confidence to create some crazy hacking labs all by yourself. And it’s gonna cost you pennies. Like that’s, that’s literal. I’m not like exaggerating. It’ll cost you pennies. So here we go. What do you need? Well, already covered that you need absolutely nothing. Well, I mean, you’ll need a few things like you’ll need an AWS account, which does require a credit card.
Now what’s cool is that this is your first time ever using AWS. There is a free tier. You get like a lot of stuff for free for 12 months and this lab may end up being free for you. But it still does require a credit card to get signed up. Now for the sake of time insanity, I’m not gonna show you how to do this in this video, cuz I already showed you in this video appear somewhere. I walked you through every step of how to set up an AWS account and also spin up a call Lennox instance with gooey access. So before you continue with this video, make sure you have that AWS account and then come back and see me. I’ll still be here. I’ll wait. Actually. It’s pause the video. UN pause. All right, let’s go. Oh, I forgot to mention you also need coffee.
So if you haven’t already go get up. Go ahead, get up. Brew yourself a cup. And um, let’s get started right now. Okay. Here we go. Time to build our ultimate hacking super secret. Awesome hacking lab. Did I already stay hacking it’s okay. So if you’re not already here in the AWS console, go ahead and get there. Just be here. Are you here? Okay. Let’s start. The first thing we’re gonna do is create the network that we’re gonna play with that. We’re gonna put our virtual machines inside and actually hold on. We’re we’re gonna do one thing before that, depending on your internet speed, you might wanna start this as soon as possible. We’re gonna go out to vulner hub.com. I’ll have all the, the links below all the documentation. Everything you could ever want is below except a girlfriend. Now the vulnerable machine I’m going to demo will be the breach vulnerable.
I can’t say that I’ve been seeing vulnerable too much. I’m just gonna search for breach. I’ll do breach one. You’re gonna jump in there and then I’ll just click on download. I wanna download the mirror. Go ahead and start that process right now. So please just go ahead and start that now while we’re here, I want you to pay attention to a few things. We’ll scroll down just a little bit. Every one of these vulner hub machines will tell you something about their stuff. And more specifically, the things we care about right now are the networking for this particular box. DHCP will be disabled. So it won’t get an IP address by default from your network. But it does come. Prebate hard coded with this IP address. So knowing that we need to create a network inside AWS, which we can do, and it’s amazing and kind of easy that will allow us to hack this box with that subnet.
Let’s do that right now. So over here in AWS land, and by the way, AWS is a huge beast of a monster. Don’t worry. If you feel overwhelmed, I’m gonna walk you through each step. Just hang with me. I’ll guide you. Go up here and click on services and then we’ll scroll down a bit here on the left until we see networking and content delivery. Go ahead and click on this. And then over here on the right, we’re gonna scroll down just a bit until we see VPC, we’re gonna create our own virtual private cloud. So go ahead and click on that. And this will be quick and easy. Check this out. First. Click on launch VPC wizard. I love wizards. You’re wizard, Harry, click on that. So just a few things we’re gonna change here on this page. Under VPC settings, this should be selected by default.
We’re gonna create a VPC and subnets. Cetera. That’s cool. Next we have the name of our VPC. I’m gonna name this reach. And then for the I P four cider block, we need to have this match our network for the vulnerable machine. Here’s what we’ll do. 1 92, 1 60 eight.one, one zero.zero/ 24. This network will contain the IP address of this guy. So we should be golden. Just a few more things. We gotta change. Let’s scroll down just a little bit here. Under availability zones. Let’s just click on one. It should be two by default, click on one and then scroll down just a bit more. We should be solid. So leave everything else is default and click on create VPC and bam, just like that in the cloud, you created your own virtual private cloud, your own network, which by the way is a pretty huge accomplishment.
Quick coffee break just for you, cuz that was awesome. And now inside this network, we’re actually going to put our hacking stuff. The first thing we’ll create is our hacking box. Our Callie Lennox. I’ll walk you through that real quick. I’m not gonna walk you through how to set up a gooey if you wanna do that, watch this video right here. So just as before, we’re gonna go up here and click on services and then we’ll click on compute over here on the left and then we’ll click on EC two, which is what Amazon calls their virtual machine stuff. Click on that. And if we scroll down just a little bit here in the middle, I’ll see a big orange button that says launch instance, click on that and then say launch instance here in the name. I’ll name it vort. Oh, sorry. He who must not be named didn’t wanna offend anybody.
And then we’ll scroll down and choose our Amazon machine image, which is the kind of virtual machine it’s gonna be. Will it be Lennox? Will it be a windows? And this case is gonna be Cali. So right here in the search box, just search for Cali hit enter and it should pull up just right here. Go ahead and select this guy and then click on continue. Now just a few more things here. First let’s select how big this machine’s gonna be. And this will determine how much you pay for it. So by default, right now it’s a T2 medium, which essentially means it has two virtual CPUs and four gigs of memory. If I click on the dropdown here, you can go larger or smaller, whatever your taste is or whatever your wallet can stand. But for the attack box, I’m gonna stick with medium.
Now this is gonna end up costing me about 4 cents by itself per hour. Also a great option would be the T2 small, which will cost you about 2 cents per hour. So pick your poison. I’m gonna go with medium cause I want my box to have a bit more juice next. We’ll need our key pair. This will be a secure way. We’ll access our machine. That doesn’t involve passwords. If you don’t already have one, go ahead and create one. I do walk you through that in my previous video on this. So I’ll click on, create a new pair. I’ll name it, leave everything else is default. Create key pair and notice it did go ahead and download the key H crux.com for me, make sure you save that. Don’t lose that if you lose that, you won’t be able to access this machine anymore. So just don’t lose it and I’ll show you how to use it here in a sec.
And then finally our network settings, which we do need to change because we have a new network. Go ahead and click on edit right here and here for our VPC option. We’re gonna change that from default to our new one, which I called it V uh, breach. So I’ll select breach and then just underneath for the subnet right here, I’m gonna change it from the private to the public subnet. Notice I have two here, private public, we actually created two. I’m gonna choose public. And then here in this drop box, I’m gonna change this auto assign public IP from disabled to enable. Now that should pretty much be everything. Let scroll down just a bit. I’ll double check my settings. Yeah, we’re all good. So now we can click on launch instance and just like magic. You’re creating a virtual machine in the cloud, inside the network that you created, your virtual private cloud.
So cool. Now while that machine is baking at this point, I’m hoping that your breach vulnerable machine is done downloading. If it’s not, well, then take a long coffee break, but mine is. So what I’m gonna go ahead and do real quick is open that up here and extract that zip drive or zip folder extract all. And when it hate to default, uh, extract, or it needs seven zip, which I don’t have need to download real quick. So if you hit an issue, just download seven zip, which is amazing. That was quick. Let’s try it again. Extract files, blah, blah, blah. Okay, close. So now we should have a folder with our breach dot ova file. Now what I’m gonna do to make things simple for later steps. So I’m gonna change the name of this file to just simply breach all lowercase. If you want to go ahead and do that with me, it’ll make things easier to follow along with me, enter to change that name.
Bam, we’re solid. I’ll just so you know, this breach do ova file is our vulnerable machine. That ova file type is what virtual machine managers or hypervisors use to create virtual machines. AWS will actually take this file and convert it to its own format and put it in the cloud, which is gonna be freaking awesome. So we’re gonna walk through that right now and actually this next step might take a little bit because we’re actually gonna be uploading this file to AWS. So if you’re upload speeds on your internet are kind of crappy. This might hurt a little bit. Let’s go ahead and start it now. No more time wasted. Getting back to the Amazon console, just like before, we’re gonna go up here to the top left and click on services and then we’ll scroll down just a bit, actually almost to the bottom to where it says actually it’s the very bottom we’re gonna click on storage.
And then over here on the right, we’re gonna click on S three, which is Amazon storage service. Go ahead and click on that. You see to deploy this ova file. We’re actually gonna have to upload it to a storage place in AWS. Let’s create that place right now. And they actually call their storage stuff. Buckets. I like that. It’s kind of cute. So right here on the left or I’m in the right, you’ll see a create bucket option. Go ahead and click on that. I’m gonna name my bucket V hub stuff for me, just something random. I think it does have to be unique. So keep that in mind and then for the region, just make sure the region matches the region that you use to create your virtual machine and your VPC. So I open up another tab with my console and just notice to the top here top, right?
You can see Ohio. These are the various AWS regions out there in AWS is global. It’s important that we create all our stuff inside the same region. You can see I had U us east, Ohio, or it’s actually called us east two selected. That tells me that when I created my VPC and also my virtual machine, I created it in those regions as well. So if I look at my V uh, my EC two instance, for example, I go to services compute C two, and I’ll just jump into my instances running real quick. There’s my call Lennox box. And I can see right over here under availability zone it’s in us east two. So just confirm that before you step forward. And now that I feel good about it, I’m gonna get back to my S3 bucket creation here. The region us east two is absolutely correct.
I’m good. And then I’ll scroll down just a bit to where it says block public access settings for this bucket. Now we’re not putting anything secret or secure in here. It’s just the boxes that we’re, we’re downloading from V hub, which is free. So I’m gonna unlock this or unblock it. I’m allowing public access. I’m acknowledging down here that, yeah, I know. I’m, I’m opening it up to the world. It’s totally fine. Just don’t put any weird pictures in there or anything. And then that should be it. I’m gonna click on create bucket here at the bottom and it should be done within now. Like that seconds. That was awesome. So what we did here is we created a little bucket in the cloud, a little storage place, like our storage container in the cloud, and now we’re gonna upload our virtual machine, our ova file to that bucket.
So let’s go ahead and do that. I’m gonna click on the bucket right here and now that I’m inside my bucket, I can upload something. So I’ll click on the upload button right here or right here, whatever you prefer, click on upload. And it takes you to another menu. Goodness, we’re like in menu prison, but click on ad files right here. And I’ll go find that in my file system. That ova file breach one zero breach ova open, and I’ll scroll down just a bit and click on upload. Let’s start this party. You can monitor your progress right down here. I’ve got pretty decent internet. So it’s gonna happen pretty fast for me. I hope yours is pretty fast too. If it’s not just be patient. Now I know some of you may just have terrible internet and here’s a quick little hack to avoid all this here in AWS.
We just created a Cally Lenox VM. And if you follow my previous video where you can actually create a gooey without Kelly, Lennox and access it like a regular computer, then you could theoretically, actually not theoretically, you could actually do this. Just access your Kelly Lennox box here in the cloud and using AWS is super wicked, fast internet. You could go off the, the phone hub, download the stuff. And then from your same box, upload it here to AWS to S three bucket. So everything just happens in AWS. All you’re doing is remotely accessing it, which is like little bits of bandwidth. That’s what makes this lab super cool is you never have to leave AWS. You can just stay in there. So if your internet sucks, all you really have to worry about is remote access, take a coffee break because this next step is gonna get a bit hairy.
This is where people kind of get afraid of the cloud and trying to make this work. Cause our job now is to get AWS, to get Amazon, to convert this breach, to ova file into a legit virtual machine image that a AWS can use. And that’s going to involve us accessing the command line here in AWS, but don’t worry. I’m gonna walk you through every step it’s gonna be. Okay. So first things first let’s go ahead and click on our breach. Do Ovia file right here. Just click on it. It’ll bring up a new page and we’re just gonna leave that open cuz there’s stuff right here that we want to have ready to go specifically the, and the ARNs. Just put a pen in that. Let’s get back to our other AWS console tab over here and up here at the top. Right? You’ll see one of my favorite places.
Command line access. Go ahead and click on that box right there. Bam. What this is doing is launching the AWS cloud shell. I’ll just close this box out and right now it’s creating your environment. Just hang tight, quick coffee break. And once the set up, you should see a nice, pretty console that you can access right now. I’m gonna zoom in a bit here. Perfection. Now don’t let this scare you. We’re gonna walk through this. It’s gonna be fine. The first thing we have to do is create a file. So type this with me type in VI and then containers dot JS O N or containers dot JSON, head enter. Now, before you hit anything else type in one letter type in I bam. Now, right here, we’re using this editor in Lennox called them and actually be able to add stuff to this file.
We hit the letter, I to, um, go into insert mode. That’s all we did right there. Just so we can start typing things. Now don’t type that and that’s stupid. Now what we’re gonna do link below again is we’re gonna copy this code. I’ve copied it and I’m gonna right. Click and paste. And what I love about AWS is that it does this. It says, Hey, we got multi-line stuff. You’re about to paste in. Do you wanna edit it first before it goes in? Heck yeah, I do. I wish everything did this. So here let’s change a few things under description. Let’s let’s just change it to, uh, breach format. Ova totally is. And then right here, the URL, this will be the URL of the bucket that contains your, your ova file. Let’s go back and uh, get it from, uh, our bucket here.
It should be this right here. Your S three, just click that. Copy icon, go back to our cloud shell and change this entire URL to your new one. That’s it. So, so now I feel comfortable to click on paste. Go ahead and paste that it’s in there. Now the tricky part is how do we save this file and get out of there. Couple key strokes here. We’ll put it on the screen. Hit escape. Actually make sure you have you’re clicked in here. There we go. Make sure you just have your, the context is here, hit escape, colon, and then the letters double U Q. You should see this stuff start typing in the bottom left. If you do see that, go ahead and hit enter. And you’re good. You just created that file to verify type in LS. And there it is right there. Containers dot JSON.
Now the next step we don’t quite have permission to do right now. We’re about to import VM, which is pretty, pretty cool, pretty hardcore. So we have to give ourselves permission. Now, if I didn mentioned before, please make sure you’re in the region.
And then just as before, you’re gonna paste this content link below and copy it, paste it here. Think everything here is actually good. We don’t have to change anything, hit paste, and then make sure we have this window selected. We’ll hit escape, colon WQ to write and quit and hit enter bam, new follow written, hit LS to verify trust policy dot JSON is there. Now it’s gonna get a bit weirder, just follow along with me every step don’t skip anything we’re thinking gonna paste in this command. Don’t hit enter on it yet and paste it right now here. We’re creating a role that will reference this trust policy that we just created, which means we do need to change the end of it right here. Yours should be the exact same as mine. So just edit it with me. I’m gonna scroll over here to, I’m gonna remove all this and actually I’ll probably have it just like this when you paste it.
So you probably have to change anything. Just make sure it looks like this. That way. It’s actually looking at this file here in our home director. So once it looks exactly like this, go ahead and hit enter and you should be solid. That’s it. Now we’re gonna create one more file. Hang with me here, type in VI and then roll dash policy dot JSON or J O N hit enter we’ll type in I to enter insert mode. And then we’ll copy the command from below the big long thing. I’ll go over here and paste that. And here we are gonna have to change a few things. So here we’re gonna scroll down just a tiny bit until we see your resource. And we see these two URLs here, AR AR N we need this URL to match the bucket that we just created for our virtual machine.
So let’s get back over to our S3 bucket over here. Our tab here, we just want the bucket we created not the file we uploaded. So for me, that bucket I created was V hub stuff for me. So I’m gonna copy all that. Just that get back over to our cloud shell here. I’m gonna paste that in here in the first one, just like that. And then I’ll paste it in the second one and I’ll do it just before that forward slash to where it looks just like this. So here it just contains my bucket, the bucket that contains my ova file. And then just one more thing we have to change in this file. Let’s scroll it down just a bit, just a little bit to where we see another resource here, here with the ARNs. We’re gonna do the exact same thing or replace this with our bucket.
And then the same thing here before, just before the forward slash our bucket. Now that should be everything. All we had to do here was change the ER or Thern to our bucket name. So I click on paste and then just as before, make sure I have this selected, hit escape, colon WQ for right. Quit done. One more thing we have to do to give ourselves permission. Then we’re done with permissions that promise. So again, command below, we’re gonna paste this command and we’re gonna reference that file that we just created over here at the end, which I’m gonna have to edit mine. But the thing you’re gonna paste here should be accurate. Just make sure it looks just like this. If your command looks like that, you’re good to go head enter. Oh, and we now have permission. Now we can actually import and create a virtual machine image here in AWS.
One command, copy and paste just like before and paste this in here. This command is actually importing the image and notice it is referencing that file. The first file we created here with them, the containers dot JS on make sure it looks something like this. If it looks like that, go ahead and hit enter. And the party’s starting. It gave us all the information over here about what’s happening. And we have our status down here. It’s active. And the status message is message is pending. If you’re like, okay, what’s going on? How long do I have to wait? We can check on it real quick with one command. Go ahead and copy and paste like before I’m gonna paste it here. Keeping in mind with this command, it is describing the import image task telling us what’s going on, but we do need to change this part at the end to match this up here.
So actually look at that task and describe what’s happening. So what I’m gonna do is take this, copy it up here. Control C and then down here gonna delete that last portion. Paste that in. Now I wanna hit enter. It should tell me what’s going on. Aha. New status. So currently right now it’s still active and it’s now converting my ova into an AWS machine image, which I can use to create my own virtual machine and hitting the up arrow. We can keep running that command to check on the status. It’ll go through a few statuses like, uh, booting and such. It’ll take a minute. So coffee break. Okay. I’ll run this command once more and let’s see. Perfect. So yours is complete when you see this obviously completed now, quick note, some virtual machines, some OVAs from V hub just won’t work so far.
I’ve just hit one of those most are okay. Things are warm and fuzzy. When you see this not time for the next step, let’s actually deploy this virtual machine. And this part is super easy. Here we go. So just as before, we’ll get back to our services up here, the top left, we’ll scroll down just a bit, click on compute and get back to our EC two service. And just like before we’ll scroll down just a bit, click on launch and instance launch instance, and we’re gonna create a new VM. So here we’ll name it. I’ll name it breach. Keep it simple. And then here’s where the magic comes in. We’re gonna choose an Amazon machine image, but a custom one that we already made. So here in this section, we’ll see right here, we have my AMI click on that now should reveal bam, that import that we just did.
That’s the ova we made or we had, we used, we uploaded that’s it. So just make sure we have that selected. That’s simple. And then we’ll figure some more stuff like we did before the instance type. We could probably get away with the T2 micro on this. So I’ll leave it at that. Just something very small for the key paired login. This is the machine we’re gonna be trying to break into, right? So we’re just gonna select proceed without a key pair. I know. Not recommend it. It’s fine. It’s fine. Trust me then for network settings, let’s make sure this is important. We put this in the VPC that we created. So we’ll click on edit, we’ll change our VPC to the breach VPC. The one that we created yours might be named differently. And then for subnet, just make sure we have the private subnet selected.
Notice the private in there and the naming might be kind of hard to see, but mine is right here. And then there’s one more thing we wanna change by default. AWS will create what’s called a security group, which will protect the virtual machine from access. Now for us, we’re not trying to test AWS to security. We’re just trying to test the vulnerabilities of this machine. So let’s remove all protections that AWS will add for it. So we’re gonna keep the create security group option selected. We’ll scroll down here and make sure we allow everything. And all we’ll do is just edit this first security group rule one. So right now it’s saying, allow SSH. We’re gonna change that. Keeping in mind, we’re right here at the type box. We’re gonna change that from SSH two, all traffic. And that should be it right now. We have the source type being anywhere, source anything we’re solid.
And that should pretty much be it. So we’ve added to our network. We removed all restrictions. And if we scroll down just a bit, all the way to the bottom, we’ll click on launch instance. And right now our vulnerable machine is being deployed to AWS, which is kind of crazy. So now let’s meander over to our EC two instances. And actually from the screen, we can do that just right over here. We see we have our breadcrumbs. I’ll just click on instances. And right here we have our two instances running or breach is pending, but Hey, our call Lennox box is running and actually while breach is baking, let’s go in and access our call Lenox box right now. So just click his instance ID to jump into him. And I want you to notice two things first, look at his private IP address. It has an IP address in the subnet that we created, which will allow us to access and attack the breach box.
We uploaded. It also has a public IP address so we can remotely access him and actually start hacking. That’s what we need right there. Go ahead and copy the public IP before address and then launch your command prompt or terminal and launch mine right now. CMD. Now to log into the server, we will need that key that we downloaded earlier. If I go to CD downloads here in my windows box, I should have it here. Let me LS here. Oh wait, no D IR sorry. Linux. It should be, oh yeah. Right there. HCR dot PEM. I’m gonna use that file. So the command will be SSH dash I, and I’m gonna reference that key PO crux dot P E, and then I’ll connect to my server. The username will be Cali by default at the IP address. I’ll pay set in there and that should give us access.
Ready, set, go. And we’re in Cali box. Now. I also already have gooey access set up for the same box. Here it is. It’s gorgeous. I love it so much. If you wanna know how to do that again, check out the video I’ve already made, and this is that same exact box. Now let’s go check on breach. We’ll get back to our instances and see if he’s done booting. He is running. Let’s jump into him real quick. Now something interesting happened. I did not expect this. Um, the private IP address is different from the one hard coded. So it looks like something happened with this box and an accepted a D ACP address. So now the IP address is 1 42, which I think is totally fine. We’ll test that here in a second. But at this point we have a private network with a vulnerable machine and our attack machine, our attack machine can attack to his heart’s desire.
Let’s try it out real quick. So here I’m in Mike Kelly lakes terminal first. We’ll see if we can, uh, ping that machine. So ping 9 2, 1 68, 1 10, 1 42. Yours may be different. Just make sure you check that IP before IP V4 address the private one. Okay. I can ping him. Let’s do a little Nmap action. Let’s Nmap and I’ll just check if, to see if a poor eighties open nothing fancy here. Aha. It is open, which means there’s probably a website on there. So I’m gonna jump into my gooey instance. This is the same Cali box just in gooey form. Once you start seeing gooey enough, it just feels weird. I don’t know. Anyways, I’m gonna launch Firefox here in my gooey. Said it again.
It’s costing us about what 5 cents per hour, because I went with a heavier box. You may have went with a smaller box, so it’s probably costing you like 4 cents an hour. And the cool thing is, is if I wanted to make a bigger lab, I can, if I wanna add a windows server to this environment, I can, I can go and download more of the boxes from V hub and upload them with the same process and have a hacking lab that’s available from wherever I go. So like legit, you can have a V C app on your phone or your iPad and you can access the same box, just like this, wherever you are in the world. This is my new favorite way to set up a hack and lab. It’s quick. It’s fast. Oh, relatively it’s fast. Once you launch it. And the options are limitless.
Now of course, when you’re done hacking, you’ll want to shut down those instances. So we’ll get back to our AWS console, get back to our instances. And I can just select these two. You guys go to instant state and say stop instance. Or if I’m completely done, I’ll just click on terminate instance. And because AWS charges you per second, that you’re using their services. Once you click stop, you stop paying for the EC two service. Now I know. So of the Republic, well Chuck, no, you’re still gonna be charged for something and yes, you’re right. You see those virtual machines while they turned off, they do still have a disc drive and it’s stored on the EBS service. So basically you’re paying for storage and AWS, when those machines are off. Now, I’ll tell you this, the cost of that is like, you can’t even calculate.
It is so it’s so tiny. So just know when you do stop these instances and they’re not running, you’re basically being charged, nothing like peanuts. I think it was like 3 cents per month.
Is this? I can’t get over how cool this anyways, if you haven’t already, please make sure you hack YouTube today. You gotta hack that YouTube algorithm. If that like button notification, bell comment, subscribe notification bell. Did I say that? Yeah. You gotta hack YouTube today. Ethically of course. And also let me know what you think of this. Like, is it stupid? Do you like, is there a flaw in my design or is it awesome? And are you doing it right now? I wanna know. Let me know below and yeah, that’s pretty much all I got. I’ll catch you guys next time.