Create an instance in any subnet/vpc. Attach an extra volume and create a file in that volume. Install apache, create an AMI of the existing system and then create an instance with that newly created AMI. Verify that Apache is already installed and file is also present in the newly created Instance.

 

  1. Launch an EC2 instance in your preferred subnet/VPC using the AWS Management Console or the AWS CLI. During the instance launch, attach an additional EBS volume to it.
  2. Connect to the instance using SSH or Remote Desktop.
  3. Mount the additional EBS volume to the instance and create a file in it.
  4. Install Apache on the instance using the appropriate package manager for your operating system.
  5. Once Apache is installed, stop the instance and create an AMI from it using the AWS Management Console or the AWS CLI.
  6. Launch a new instance from the newly created AMI in the same subnet/VPC as the original instance.
  7. Connect to the new instance using SSH or Remote Desktop and verify that Apache is installed and the file you created in step 3 is present in the additional EBS volume.

Comments

Post a Comment

Popular posts from this blog

Error Solving : -bash: /usr/local/bin/kubectl: cannot execute binary file : after Kubernetes installation: you're trying to run the kubectl command on an EC2 instance in AWS

Image
you're trying to run the kubectl command on an EC2 instance in AWS, the first thing to check is whether you've downloaded the correct version of kubectl for your instance's operating system and architecture. follow these steps to resolve it: You can download the correct version of kubectl using the following commands: For Linux x86_64: curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" copy this link and paste it into your terminal and press Enter. if your system requires arm64 then copy the below link and paste it into the terminal and Enter. For Linux arm64: curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl" you will get the following screen. now, Make sure you have the correct version of kubectl for your system architecture. Once you have the correct version of kubectl , Enter the following command: ==> chmod +x kubec...
Read more

Nodejs Application project : using Aws, Jenkins, Docker, Kubernetes

Image
  Step-1: Login to your Aws account and create an instance for Node.js Project. Step-2: Install  Jenkins in your nodejs server (if you don't know how to install Jenkins, follow my DevOps sample project Part -1). Step-3: Once the installation is finished of Jenkins, go to plugin installation and click on Manage Plugins. Then Search for the " Nodejs " plugin and install it. Step-4: Now, Click on New Item and enter the Project Name and select FreeStyle Project . Then click OK . Step-5: write your description and then select the Git option for the git repository clone(if you did not install git plugin , please install it first). Now go back to the dashboard and click on configuration and select Global Tool Configuration, now go down and select node js and enter the name nodejs, and the rest leave it as it is.  Now save it this page and go back to our project Configuration page. Step-6: Enter the Nodejs Project Repository Link. Step-7: Scroll down and select Provide Node...
Read more

Create two public subnets and two private subnets in two different availability zones(AZ) ( one public and one private subnet in each AZ).Create an instance of webserver (like apache ) in each AZ and an instance of db server in any AZ. Attach web servers to ELB and make sure to support cross zone availability.

  Step 1: Create a VPC (if not already created) Go to the Amazon VPC console. Click on "Create VPC." Enter the details such as CIDR block and VPC name. Click on "Create VPC." Step 2: Create the subnets In the VPC console, select "Subnets." Click on "Create subnet." Enter the subnet details such as the VPC ID, availability zone, CIDR block, and subnet name. Repeat the above steps to create the remaining subnets. Step 3: Create the security groups In the VPC console, select "Security Groups." Click on "Create security group." Enter the details such as the security group name, description, and VPC ID. Add inbound and outbound rules as required. Step 4: Launch the instances In the EC2 console, click on "Launch instance." Select the AMI and instance type. In the "Configure Instance Details" section, select the appropriate VPC, subnet, and security group. Configure the rest of the instance settings as required. R...
Read more