Please watch the below video tutorial and like, share and subscribe my channel. Have a nice day!!!
Showing posts with label AWS. Show all posts
Showing posts with label AWS. Show all posts
How to enable password based login on AWS Linux Instance very easily...
How to install AWS SSM Agent on Ubuntu/Linux EC2 Instance to know Used Memory Utilisation
Please watch the below video tutorial and like, share and subscribe my channel. Have a nice day!!!
#memory #EC2 #SSM #howto #AWS #ubuntu #linux
How to Enable and Use the Serial Console for AWS EC2 Instances for Linux...
How to setup Sequrite UTM for AWS site to site VPN
Please follow all the steps as shown in the tutorial and don't forgot to subscribe my channel. Have a nice day!!!!
#utm #aws #howto #sequrite
How to Up gradation of Window Server 2008 R2 to Window Server 2019 on AWS Cloud
Hi viewers!!! in this tutorial I'll explain how to perform an up gradation of Window Server 2008 R2 to Window Server 2019 on AWS Cloud.
To upgrade the Window server 2008 R2 to Window server 2019 We can use the following two method provided by AWS
01. Automatic Up gradation
02. Manual In-Place up gradation
We can’t upgrade directly from window server 2008 R2 to Window server 2019.Hence the Server up gradation path we have followed is mentioned below.
WINDOW SERVER 2008 R2 -> WINDOW SERVER 2012 R2 -> WINDOW SERVER 2019
In this up gradation process the main advantage is that it does upgrade the existing server to a new version hence we don’t require to re-install or re-configure the application again on a new instance.
Steps need to be done for Automatic Up gradation
01.
The first requirement for this is that our
server should be managed by AWS System Manager.
02.
Secondly we have to taken the Latest AMI of our server before up gradation, however the system takes the AMI
automatically during the up gradation process but still we need to took AMI as a safety measure
.
03.
Next check that your C drives have enough space
as per the best practice around 30 GB
should be free space on C drive for up gradation to OS version.
04.
Now go the
System Manager and then click on the Automation
option on the left side panel.
05. Then
Search for the document starts with ‘AWSEC2-Clone”
then selects the AWSEC2-
06. Now choose or set the following parameter within the document
1. Choose the execution option as Simple execution.
2.
InstanceID
-: (Required) the
instance running Windows Server 2008 R2.
3. InstanceProfile.-: (Required) The IAM instance profile. This is the IAM role used to perform the Systems Manager automation against the Amazon EC2 instance and AWS AMIs.
4. TargetWindowsVersion-: (Required) Select the target Windows version like window server 2012 R2.
5.
SubnetId-: (Required) this is the
subnet for the upgrade process and where our source EC2 instance resides.
Verify that the subnet has outbound connectivity to AWS services, including
Amazon S3, and also to Microsoft (in order to download patches). As a best practice I have chosen the
different subnet to perform the up gradation.
07. After we have entered the above parameters, we need to selected Execute button. And the
automation begins. We can also monitor the execution progress.
08. This
will take approx. 1.5 to 2 hours depending on the Instance Size and data also. The
automation process has around 56 tasks.
09. After the automation completes, we can launched an Amazon EC2 instance using the new AMI ID to review our upgrade from the AMI console of AWS.
That’s it we have successfully upgraded our window server 2008 R2 to window server 2012 R2. After upgrading we have to update our window with the latest patches.
Steps need to be done for Manually Up gradation
For Up gradation from the Window
server 2012 R2 to window Server 2019 first we used the automation method but this method failed to successfully execute the document. I don't know the actual cause.
Hence we use the next method which is manually in-place up gradation. So here the steps as mentioned below to perform this
01.
First take the latest AMI of the Window Server
2012 R2 instance.
02.
Now note two parameter i.e. Instance ID and Availability
Zone this we will need in future.
03.
Now login into your Window Server 2012 R2 instance and check that there is enough space
for up gradation for this method we need at least 10GB free space.
04.
Next uninstall the EC2config application this will
also uninstall the SSM Agent.
05.
Now go to the installation location and do the
clean up by deleting the EC2config and SSM Agent folder.
06.
Now go to the ProgramData folder and delete the
EC2Config and SSM Agent folder also from there.
07.
Now download the latest version of EC2Launch
application and PowerShell script from the AWS official website. We can find
the like by just Google them on the net.
08.
Now open the PowerShell script with the PowerShell
application and execute the script.
09.
After that download the latest SSM Agent from
the AWS official site and install on the Server.
10.
Once the above steps are finished, then go to the EC2
instances console on AWS .
11.
In the navigation pane, choose Snapshots,
Public Snapshots.
12.
Add the Owner filter and choose Amazon
images.
13.
Add the Description filter and enter Windows
2019 English Installation Media. Press Enter.
14.
Select the snapshot that matches the system
architecture and language preference we are upgrading to. For example, select Windows
2019 English Installation Media to upgrade to Windows Server 2019.
15.
Choose Actions, Create Volume.
16.
In the Create Volume dialog box, choose
the Availability Zone that matches your Windows instance, and choose Create.
17.
In the Create Volume dialog box, choose
the Availability Zone that matches our Windows instance, and choose Create.
18.
In the Volume Successfully Created
message, choose the volume that we just created.
19.
Choose Actions, Attach Volume.
20.
In the Attach Volume dialog box, enter
the instance ID and choose Attach.
21. Begin the upgrade by using Windows PowerShell to mount the installation media ISO from the volume that we have attached to the instance. Using the following command
Mount-DiskImage <Path>\Filename.ISO
22. Then
cd into the mounted media and then run the following command in powershell.
./setup.exe
/auto upgrade
23.
For Select the operating system you want to
install, in our case I have chosen the Window server 2019 Datacenter
Desktop version from the list, and choose Next.
24.
For Which type of installation do you want?,
choose Upgrade.
25.
Complete the wizard.
26. Now just wait for about 1 to 1.5 hour to complete this process. After that your server will be upgraded to new OS version i.e. Window server 2019.
27. Now I login into the new server and check that everything is working perfectly.
Wow!!! that's it, we have successfully up graded our Window Server to latest version. I hope you like this blog please feel free to leave the comment in comment section if you need to clear any doubt. Have a nice day!!!!
#aws #cloud #windowserver2008 #howto #tutorial #windowserver 2019 #upgradation
How to create EFS storage in AWS
Hi viewers!!! in this tutorial I will show you how you can setup the EFS (Elastic File System) on AWS and then mount on your Linux machine. So let start I have also made a video tutorial on how to setup the EFS volume so please watch that also......
So first of all What is the EFS and What are the benefits of having EFS in AWS?
Here is the answer : Amazon EFS is a fully-managed service that makes it easy to set up, scale, and cost-optimize file storage in the Amazon Cloud.
Amazon EFS file systems can automatically scale from gigabytes to petabytes of data without needing to provision storage. Tens, hundreds, or even thousands of Amazon EC2 instances can access an Amazon EFS file system at the same time, and Amazon EFS provides consistent performance to each Amazon EC2 instance. Amazon EFS is designed to be highly durable and highly available. With Amazon EFS, there is no minimum fee or setup costs, and you pay only for what you use.
All EFS file systems, regardless of size, can burst to 100 MiB/s of throughput. File systems with more than 1 TiB of Standard storage can burst to 100 MiB/s per TiB of data stored on EFS Standard. If you require higher amounts of throughput to EFS IA than your file system allows, use EFS Provisioned Throughput.
The above picture gives us a clue about how that work in AWS environment.
Below in the picture you can find out the how it works and what steps are need to be perform
Image source: AWS site.
Here is the video tutorial where I show all the steps to configure and mount the EFS storage on CentOS and you can also follow this article to see the steps by steps procedures to setup EFS for Amazon Linux OS.
Steps
- First log into your aws account and search for EFS or select the service and from there choose the EFS services as showing below.
- Once you click on EFS option you will see the below screen shot.
- Now here you need to click on the Create file system but before that Very Important: Please don’t skip this step otherwise you may be not able to mount your EFS system on machine. So what we need to do is first create your own security group by going to EC2->Security Group ->Create a New Security Group and the following rules as showing below
Please change the source field as per your network subnet or you can use 0.0.0.0/0 if you want to all traffic from anywhere.
- So in the create the file system wizard first step is “Configure the Network Access” here in this steps you need to select your VPC for which you want to create the EFS and also you need to select the subnets of the VPC, you can select all the subnets of the VPC or any specific subnet here also. And the last one is you need to select the security group and this is very important step here choose the security group that we have created for EFS storage do not use the Default one. Please see the below picture
- In next step we need to “Configure the system settings” so in this step you need to configure the tag, lifecycle management, choosing throughput mode, choosing performance mode and enable the encryption setting. We have chosen the default one you can choose as per your requirement. All these option are self-explanatory you can read more about these option in the snapshot given below
- In next step we need to configure the “Client Access” we leave this section as default for this tutorial however you can make the changes as per your requirement.
- At last we need to review the settings and click on “Create File System”
- Once click on the Create File System the next screen show that the file system is successfully created but wait here you cannot mount the EFS as yet since the “mount target point” is under creating mode so we have to wait until the “mount target point” show “Available”. Please see the below screenshots
Okay that’s it we have setup our first EFS in AWS successfully now let’s configure the client machine. I’m using the Amazon linux machine.
- So first you need to ssh into your linux machine and then run the following command
- Now let’s wait till the system install the require packages
- Now create a directory where we can mount our new EFS system. I have created a directory name “efs” in the root directory of system.
- Now mount the EFS storage on your local machine
- Now let’s check the EFS is properly mounted or not
Wow!!! That’s it we have done it…… one more tip if you need to mount the EFS storage on Ubuntu, CentOS or RED Hat Linux then please install the nfs-utils package on these system as showing below
And thanks again!!! to visit my blog again please feel free to leave any comment or contact us if you have any queries.
How to setup AWS client VPN on Ubuntu OS and Resolved SSL missing & AES-256-GCM not present error
Hello Dear friends!!! in this tutorial I'll show you install AWS Client VPN on ubuntu OS. Few days back we have setup the AWS Client VPN on our AWS account to allow the remote user to access network resources of our private VPC.
The setup of AWS Client VPN on AWS is very straight forwarded you can follow the AWS Doc which described all the procedure step by step. The client side setup is also very simply for Window and MAC OS however AWS client VPN do not work out of the box on Ubuntu OS.
When we tried to install the AWS Client VPN on Ubuntu OS first we got the error of "Openssl AES-256-GCM not present error" so the resolution of this issue is just install the latest version on Openvpn on your Linux distribution next we try to installed the latest version of openvpn manually we got the error "configure: error: ssl is required but missing" so to resolve this issue we need to install the three dev package libssl-dev, liblzo2-dev,libpam0g-dev .
Okay enough writing , now I'm mentioning all the steps below steps by steps and you can also watch the video for all the steps as showing below
So here are the steps
01. First install the following packages
sudo apt-get install --reinstall network-manager network-manager-gnome network-manager-openvpn network-manager-openvpn-gnome
02. Download the latest openvpn file from the following location
wget https://swupdate.openvpn.org/community/releases/openvpn-2.4.7.tar.gz
03. Now Install the following packages first update the apt repository
sudo apt-get update
then install the following package to compile openvpn package
sudo apt-get install build-essential
after then install the following three development packages
sudo apt-get install libssl-dev
sudo apt-get install liblzo2-dev
sudo apt-get install libpam0g-dev
04. Now extract and compile the openvpn package
tar xfz openvpn-2.4.7.tar.gz
then change the current folder to openvpn extracted folder
cd openvpn-2.4.7
now run the following command one by one this will compile and install the latest openvpn
./configure
make
make install
to view the latest openvpn version run the following command
openvpn — version
05. Then give the normal user the sudoers right to run the openvpn as admin
sudo nano /etc/sudoers
and add the following line below the root user permission
<username> ALL=(ALL:ALL) /usr/local/sbin/openvpn
please change <username> with the user name to whom you give the rights
06. now run the openvpn with the config file
sudo openvpn --config /etc/openvpn/client-config.ovpn
Wow!!! now you are connected to your AWS Client VPN to access your private VPC.
That's it I hope you like this tutorial. And thanks again!!! to visit my blog again please feel free to leave any comment or contact us if you have any queries.
