Amit Kumar Mahato’s Post

Transcript

Let's understand the concept of EC2 instance connect. On my previous video you might have seen I have created one pem file, used command prompt, use couple of commands to connect to the EC2. But what if I see I can do this by just with the click of a button. That is what is known as EC2 instance connect. It is an inbuilt feature? In our EC2 where we can connect to the let's see Linux instance easily, we got to keep in some of the points. One of the point is are easy to instance should have an IPV 4 address. It can be the private or it can be public. In this hands on will be demonstrating the public one for private. There's a concept of EC2 instance connect endpoint. So that is a. Complicated and required networking concepts will not go into that but public EC2 instance connect is easier and will do in the hands on. The important point is that the Third Point that is we need to connect to the instance via SSH or RDP. So for SSH you might have recorded from the previous video that we need put 22 open. So that what concept. Will apply in the hands on, So let's dive into the hands on now. Alright, we are at the Amazon console, let's open EC2. I'll type C2 here. Let's open EC2. Alright. Next we need to launch an instance. Let's launch an instance. There are a couple of prerequisites as mentioned. So one of the prerequisites is. Also the EMI. So there are a list of EMI. I'll show you All right. There's a prerequisite for the EC2 instance connect AMI as well. So we will demonstrate using Linux two. So this is the version or later it's pre installed in the following AMI. So let's. Name this easy 2. Instance connect. I'll name it. Uh, let's see private. Why I'm writing private IP? Because I won't use public IP. I'm purposely creating one mistake so that you will be able to see like how the prerequisites determine whether we can connect to the EC2 instance connect or not. So I'll keep this default T2 micro keep here. Let's create. Key pair, I'll write EC2. There, let's go ahead and do it. Let's save the key pair file. Yep, it's saved. And by default if we see auto assign public IP, it's enabled. So it will assign one public IP address we don't want in this video. Let's disable this. I have disabled it. And default VPC is the this one default I have attached. So I have purposely doing some kind of mistake. Though we can connect using public EC2 instance endpoint connect but I'm purposely disabling it so as to create some trouble I'll create a select the default one let's. I've also missed one thing that is the SSH port. I have not opened it, so let's not launch instance. Now I know I won't be able to connect, I mean will face some trouble. So let's face the trouble to show you there are prerequisites. Let's go through it that see public IPV 4. It should be the private or public IPV 6 is not supported. So there is a concept of endpoint connect. We'll see it. Now let's refresh this. Yeah, it's running. So EC2 instance connect works like this, You just got to click here the instance, then this button Connect. It's as simple as that. But if you look see it's disabled, this button is disabled. Why? Let's read this. With no public IPV 4 address you can't use EC2 Instance Connect right? So this is just mentioned. Look at this point, public IPV 4 address right? Alternatively you can try connecting using EC2 instance Endpoint Connect. So there is a. Different concept of it. This is bit twisty and tricky. We won't go into this in this video or the simplicity, so let's create. Another EC 2:00 so that I can demonstrate the correct way of it. It launched the instance. I'll write EC2. Instance connect this time and let's give it a public IP. So we'll have public IP address. I'll Scroll down a bit. Yeah, T2 micro keep your. I'll use the existing one which I have created previously just a few moments back and here if you look public IP it's enabled so there's an easy way out. If I select this SSH from anywhere I'll be straight away able to. Do the EC2 instance connect right? Also there is another way like the inbound rules which we have connected or configured previously in my last video you can also do it. So let's use a facility what Amazon gives us allow us access from any traffic. So that two prerequisites for EC2 instance connect Just note public IP address should be enabled and also SSH port 22 right? Keeping this all the settings as default, let's launch the instance. And let's see whether this time it works or not. So this is my new instance ID I have. The other EC2 instance as well. So this was the old one if you look here. Old one that is a private IP and this one is having the public IP. We can check the difference for now. See for the private IP, there is no public IP assigned to it there it is blank. But we have a private IP. Private IP is internal to the AWS. And public IP that is we can connect if it is outside of our EWS network. So I hope this one is ready. Yep, our public IP address instance is ready. So if you look here, the major difference between the private and the public one is this one. It has a public IP before address. EC2 instance and also having the private IP definitely. So let's do the magic. Will click on the connect for the EC2 instance connect. This time. If you look, there is no difficulty with the button. The button is by default enabled and username is easy to user. So let's click. And try connecting it and see whether this time if we face any problem or not. Yep, as we can see. Here we go. This is our Linux instance, so let's try some of the commands to test, like whether it's really Linux or not. Touch zero byte file. OK, so let's create one file that is I'll VI file. I'll write this One South this. Is. Cloud Guru Amit. So let's save it. Escape Q. Enter. I'll do LS. To list the files. Yep, so all the files are displayed. So let's check this. Yep, we are good. So this is how we can connect instantly with just with a click of a button that is this one. Easy to instance connect. Just select this one and instance connect. Click this button right here so it will. We can connect easily rather than in previous video we have used pem file inbound rules so many things right? Also, let's do one thing. In previous video I haven't done this. We know that in AWS everything cost. EC2 has the EBS volume and all storage is attached. Compute is attached. So we are paying for compute and storage anytime. All right, let's try to clean up the resources. Now let's try to delete this unwanted EC2 instance. We'll go to the instance state, terminate instance. And so here it ask. EBS volume is attached by default. We don't need it. So yeah, that's how we terminate an instance. Always terminate an instance if you're not using it because in cloud we pay what we use. That is, we know that each EC2 instance has its own storage as well. That is the EBS volume 8 gigs we have. Installed on our PC on our root volume, so this was getting wasted. Will be charged for it. Also the compute power if you use so for EC2 instance connect this one we have already logged in. So let's check the size, see 8 gigs root volume we have provisioned. We are provisioning every time so this is the use and this is available one. So we have saved. A couple of bucks. Yep, this got terminated. So that's how we launch connect using EC2 instance. Connect and terminated instance. So please, please, please don't go away. Let's meet in next part of this series.