Category: AWS

In this article, I’m going to discuss What is AMI in AWS and how to create AMI from EC2 Instance? If you want to know the entire process of creating AMI from EC2 Instance, this article is going to be very helpful for you.

Before Starting the Whole Process, I would love to share some details about AMI in AWS because many people don’t know about it.

What is AMI in AWS?

AMI in AWS stands for Amazon Machine Image. AMI’s are templates that contain all the information needed to launch an instance, including the operating system, application server, and applications. AMI’s are used to launch instances, which are virtual machines that run on Amazon EC2. AWS provides a variety of AMI’s, and you can also create your own AMI’s. When you launch an instance from an AMI, you specify the AMI that you want to use, as well as the instance type, which determines the size and performance of the instance.

You can also specify additional options, such as the security groups and key pairs that you want to use. After you launch an instance, you can connect to it and use it just like any other computer. You can install software, run applications, and store data on the instance. When you no longer need an instance, you can terminate it to stop paying for it.

An Amazon Machine Image (AMI) provides the information required to launch an instance.

This includes the operating system and other software required to run the instance. When you launch an instance, you specify an AMI, which determines the operating system, application server, and applications that are installed on the instance. You can also specify additional options such as the instance type, security groups, and key pairs. After you launch an instance, you can connect to it and use it just like any other computer. You can install software, run applications, and store data on the instance. When you no longer need an instance, you can terminate it to stop paying for it.

AWS provides a variety of AMIs, and you can also create your own AMIs. To create an AMI from an EC2 Instance, you should follow these Instructions.

How to Create AMI from an EC2 Instance

I am going to Create AMI in AWS from an EC2 Instance. I need to create a backup or launch multiple copies of an Amazon Elastic Compute Cloud instance (Amazon EC2), or I obtained a maintenance notification proposing that I create an AMI (Amazon Machine Image) of my instance.

For more details please visit AWS

Create EC2 Instance in AWS

Log in to the AWS account and then go to the AWS Services tab at the top left corner.

1- Click on EC2 under compute.

2- Click on the Launch Instance button in AWS.

3- Select Windows Server 2019 and then click next.

4- Select the type of instance.
Click Next: Configure Instance Details.

5- Type Number of instances – 1
Network – default.
Subnets – default.
Auto-assign Public IP – default
Click on Next: Add Storage.

6- Volume size – default 30Gb.
Add one more volume – 8GB
Click Next: Add Tags.

7- Add a tag
Click on Next: Configure Security Groups.

8- Configure Security Group.
Security group name – dmz-Security
Select Protocols – RDP, Source type Anywhere
Click on Review and Launch

9- Click launch.

10- Select – Create a new key pair
Key pair name – server key pair
Select the download key pair button and then save it in your secured folder
After downloading the key pair click launch instance.

11- You can see its status as running after your instance is up and running.
Select instance (DC-Server) and then click connect.

Create an AMI in AWS from an Amazon EC2 Instance

From the AWS EC2 Instances view, we can create Amazon Machine Images (AMIs) from either running or stopped instances. In this lab, I will stop my instance.

To create an AMI in AWS from an instance

1- Select your instance, click on action menu, select instance state and then select stop.

2- Click Yes, Stop.

3- Select the instance you need to use as the basis for your AMI.

Select Action, select Image and then select Create Image from the context menu.

4- Create Image context menu
Type a unique name and description, and then click on Create Image.

5- Create image request received click close.

6- When the AMI first shows up, it will be in a pending state.

7- Click on Refresh to see your AMI. In a few moments, it transitions to an available state.

8- Select snapshots under elastic block store.

9- You can see Snapshot.

10- Select Instance, click on action menu, select instance state and then click terminate.

11- Terminate instance click Yes, Terminate.

To copy an AMI in AWS using the console

1- Now you can see after deleting instance we have no volume.

2- Select AMI in AWS under Image, AMIs to display the list of AMIs available to you in the Region.
Select the AMI (server-image) to copy. Select action menu, and then select Copy AMI.

3- Destination region* – The Region where you want to copy the AMI.
Name – Type a name for AMI.
Description – By default, the description includes information about the source AMI so that we can distinguish a copy from its original. You can change description if required.
Encryption – Select checkbox to encrypt the target snapshots,
Master Key – choose the KMS key to use to encrypt the target snapshots.
We display the confirmation page to let you know that the copy operation has been launched and to provide you the ID of the new AMI. Click Copy AMI

4- Select Done.

5- Initial status of the target AMI in AWS is pending.

6- The operation is completed and the status is available in AWS.
Select the type of instance for AMI and then click on Launch

7- Click Next : Configure Instance details.

8- Type Number of instances – 1
Network – default.
Subnets – default.
Auto-assign Public IP – default
Click on Next : Add Storage.

9- Now you can see the same settings.
Volume size – default 30Gb.
Add one more volume – 8GB
Click Next : Add Tags.
Click on Next : Configure Security Groups

10- Configure Security Group.
Assign a security group – Select an existing Security group and then select dmz-Security
Click on Review and Launch.

11- Click launch.

12- Select – choose an existing key pair
Select a key pair – server key pair
Click launch instance.

13- Once the instance is running and up, you can see its status as running.

Watch YouTube Video: Create EC2 Instance

In this blog, I will show you how to configure network ACL in AWS. We are going to create a custom VPC network ACL for our VPC and explicitly DENY all access to our public subnet. ACL (Network access control) list is an optional layer of security for the VPC that acts as a firewall for controlling traffic in & out of one or further subnets. You might setup network ACLs with rules comparable to your security groups in order to add an additional layer of security to your VPC.

How to Create VPC Tokyo

1- Login to the AWS account and select AWS Services tab and then select VPC under Networking & Content Delivery.

2- Under Virtual Private Cloud select Your VPCs
Click on Create VPC.

3- Create VPC wizard,
Name tag – VPC1
IPv4 CIDR block – 10.0.0.0/16.
Tenancy – default
Click Create

4- Click close.

5- Now you can see VPC successfully created.

How to Create Subnet

1- Select Subnets.
Choose Create Subnet.

2- Name tag – PublicSubnet.
VPC – select the VPC1 that you created earlier.
Availability Zone
IPv4 CIDR block – enter a valid CIDR block. For example (10.0.0.0/24)
Click Create.

3- Click close

4- Subnets successfully created.

How to Create Internet Gateway

1- Click on Internet Gateways new on your left side and then click Create Internet Gateway.

2- Enter a name (IGW1) in the Name tag text box and then click create internet gateway.

3- The internet gateway has been created and is in a detached state. We need to attach it to your VPC. In the action, menu select Attach to VPC.

4- Choose your VPC1 from the drop-down menu and then click Attach internet gateway.

5- The internet gateway changes to attached state.

How to Create Route Table

1- Select Route Tables.
Click on Create route table.

2- Name tag – enter a name for the route table (Public-Route).
VPC – Choose your VPC1, and then select Create.

3- Click Close.

Configure Network ACL in AWS

Routing of public subnets

Now we need to configure the routing for the subnets. Enable traffic from your subnets to Internet by using the internet gateway attached to the VPC.

4- Choose Ohio-Route, Choose Routes tab and then click Edit routes.

Click Add route

The traffic from instances in the subnets predestined to the Internet will be redirected to the Internet Gateway.

Then we are redirected to the Route Table in the Virtual Private Cloud.
Add route for the Route Table – 1 for the traffic to the Internet to be routed using the Internet Gateway.

5- Select Add rules for destination type 0.0.0.0/0 (all packets for the internet) and then for targets select the Internet Gateway.

6- Select (IGW1) have created as in the earliest and then select save routes

7- Click close.

8- Successfully route edited

Choose Subnet Associations tab and then choose Edit Subnet associations.

9- Select your subnet (PublicSubnet) and then click Save.

10- Successfully edit subnet associations.

How to Create a Network ACL

Open the Amazon VPC console

1- Select Network ACLs under Security and then Create Network ACL.

2- Create Network ACL wizard, type a name of your network ACL, and select the ID of your VPC (VPC1) from the list. Then select Yes, Create.

How to associate a subnet with a network ACL

3- Select subnet associations and then click edit subnet associations.

4- Select the subnet checkbox for the subnet to associate with the network ACL, and then choose Save.

To add rules to a network ACL

5- Select Network ACLs, select Inbound Rules and then edit inbound rules.

6- Click Add Rule.

Enter a rule number (for example, 100). The rule number should not already be in use in the network ACL. We operation the rules in order, starting with the lowest number.
We recommend that we leave gaps between the rule numbers (example 100, 200, 300), rather than using sequential numbers (101, 102, 103). This take it easier adds a new rule without having to renumber the existing rules.

Rule	Type	Protocol	Port Range	Destination
100	RDP (3389)	TCP (6)	3389	0.0.0.0/0
200	Custom TCP Rule	TCP (6)	1024-65535	0.0.0.0/0

7- Select Save.

8- Select Outbound Rules tab, and then choose Edit outbound rules.

9- Click Add Rule.

10- Edit Outbound Rule.

Rule	Type	Protocol	Port Range	Destination
100	HTTP (80)	TCP (6)	80	0.0.0.0/0
200	HTTPS (443)	TCP (6)	443	0.0.0.0/0
250	Custom TCP Rule	TCP (6)	1024-65535	0.0.0.0/0

11- Select Save.

Create Instance

1- Select service tab, click on EC2 under compute.

2- Click on Launch Instance button.

3- Select Microsoft Windows Server 2019.

3- Choose t2 micro.
Click Next : Configure Instance details

5- Network – select VPC (VPC1).
Subnets – select PublicSubnet.
Auto Assign Public IP – select Enable.
Click on Next : Add Storage.

6- Click Next : Add Tags.

7- Click on Next : Configure Security Groups.

8- I keep it default Security
Select Protocols ALL traffic, Protocol all, Port Range (0-65535) Select Source Anywhere
Click on Review and Launch.

9- Review the instance details, parameters and then click launch.

10- I am using existing key pair
Click launch instance.

Related: How to create Instance in AWS

Testing Configure Network ACL in AWS

1- Select Instance and then click connect.

1- Select Get Password
Select choose file, choose your key pair, and then click decrypt password
Copy password and then choose download remote desktop file.

3- And login to Instance.

4- Now you can see internet is working.

Related: What is AMI in AWS and How to Create AMI from an EC2 Instance.

In this guide, you will learn how to create an IAM Role AWS Amazon. We can create a role for a service using the AWS Management Console. Because certain services support further than one service role. We can learn how to assign the essential trust & permissions policies to the role so that the service can suppose the role on your behalf. The process that we can use to control the permissions for the role can vary, according to on how the service determines the use cases, and whether or not you create a service linked role.

Create an IAM Role AWS

1- In the AWS Management Console select IAM.

2- Select Roles under Access management.

3- Select Create role.

4- Select directory service and then click Next: Permissions.

5- Type EC2FULL, select (AmazonEC2FullAccess) and click Next: Tags.

6- Add a tag if you need or click Next: Review.

7- Type a role name (ec2access) and then click create role.

8- 1 Role has been successfully created, click on create role for another role.

9- Select Directory service and then click Next: Permissions.

10- Type billing in search bar, select Billing and then click Next: Tags.

11- Click Next: Review.

12- Type a role name (billinguser) and then click create role.

For more details visit AWS

Related: How to Configure Directory Service in AWS

In this article, I will explain how to Create Directory Service in AWS, Managed Microsoft AD directory (AWS Management Console).

Create Directory Service in AWS

In the AWS Management Console, select services tab. In the search bar type directory services and then choose Directory Service.

Under directory service select directories and then choose Set up directory.

On the Select directory type, select AD Connector and then click next.

4- AD Connector information, select directory type and then click next.

Choose VPC and Subnet I am selecting the default settings and then click next.

Active Directory information page, provide the following information, and then click Next.
Directory DNS name – type xpertstec.local
Directory NetBIOS name – default settings
DNS IP Address – type EC2 Instance private IP address
Server account user info – type administrator
Server account password – type the password you want to use for this account and type the password again in Confirm password.
Click next.

Review settings and click create directory

AD Directory successfully created (it will take 5 to 10 minutes) click on directory.

Directory details

How to Configure Directory Services in AWS

In this article, I will show you how to configure directory services in AWS. AWS Directory Service improvement several ways to use Microsoft Active Directory (AD) with other AWS services. Directories stock information about groups, users, and devices, and administrators use them to handle access to information and resources. AWS Directory Service provides several directory choices for customers who need to use existing Microsoft AD or Lightweight Directory Access Protocol (LDAP) aware applications in the cloud. AWS also offers those equal options to developers who want a directory to manage devices, users, groups, and access.

Configure Directory Services in AWS

For more details please visit AWS

Create EC2 Instance in AWS

1- Log in to the AWS account and then go to the AWS Services tab at the top left corner. Click on EC2 under compute.

2- Choose instance on the left side and then select Launch Instance button.

3- Choose the default Amazon (64 bit) AMI.

4- Choose the type of instance.
Click Next : Configure Instance details

5- Instance Details

Type Number of instances – 1
Network – default.
Subnets – default.
Auto-assign Public IP – default
Click on Next : Add Storage.

6- Volume size – default 30Gb.
Click Next : Add Tags.
Click on Next : Configure Security Groups

7- Configure Security Group.
Security group name – AD Security
Select Protocols – RDP, All traffic, Source type Anywhere
Click on Review and Launch

8- Click launch.

9- Select – Create a new key pair
Key pair name – active directory key
Choose download key pair and then save it in your secured folder
After downloading key pair click launch instance.

10- After instance is up and running, you can see its status as running
Select instance (DC-Server) and then click connect.

11- Click on get password.

12- Click choose file button.
Select your key pair (active directory key) and then click ok.
Click Decrypt password.

13- Copy password and then select download remote desktop file.

14- Open notepad and paste your password in notepad.

15- Open remote desktop key and then click connect.
Paste password and then click ok.

16- EC2 Instance (AD-Server desktop).

How to change administrator account password in EC2 Instance in AWS

1- Open control panel and select User Accounts.

2- Select Administrator local account.

3- Click on change the password.

4- Copy your EC2 instance password then one we have saved in notepad.

5- Paste here, type new password, confirm password and click change password
Save new password in notepad.

How to change computer name in EC2 Instance in AWS

1- Open server manager, select local server and then computer name.

2- Click on change.

3- Type computer name and then click ok.

4- Click ok

5- Select restart now.

6- After restarting, connect EC2 instance (DC-Server) again and now you can use your new password to connect.

How to install Active Directory in AWS Instance

1- From Server Manager Dashboard, Select Manage and Select Add Roles and Features.

2- Click Next.

3- Select Role-based …….. installation and then Click Next.

4- Select a server from the server pool on which you want to configure active directory and then Click Next.

5- Select Active Directory Domain Services from server roles page.

6- A Windows will popup showing additional required features, Click Add Features.

7- Click Next.

8- Click Next.

9- Click Next.

11- Review the installation and then Click Install.

12- Installation completed, Click Close.

How to Configuring Active Directory.

1- From Server Manager Click on Notifications, click Promote this server to a domain controller.

2- Under the deployment operation Select Add a new forest enters Root domain name (xpertstec.local) and then Click Next.

3- Keep Domain Name System (DNS) server and Global Catalog (GC) checked and then type the directory services restore mode (DSRM) password, Click Next.

4- Ignore warnings “DNS options” window and Click Next.

5- In additional options window, verify the NetBIOS domain name and Click Next.

6- Specify the location of the AD DS database, log files, and SYSVOL folders and Click Next.

7- Review options window and then click Next.

8- When all prerequisite have been successfully passed and Click Install.

9- You will be prompted that your machine successfully configured as a domain controller and will be rebooted automatically.

How to Change DNS IP in EC2 Instance in AWS

1- Launch control panel and then choose network and sharing center.

2- Click on Ethernet

3- Select properties.

4- Choose internet protocol version 4 and then choose properties.

5- Type your EC2 Instance private IP Address under preferred DNS server and click ok twice.

Add Reverse Lookup Zone in Windows Server 2019 NDS step by step

1- In window server search bar type DNS and select it.

2- Expand you DNS server (DC2019)
Right-click on reverse lookup zone option and then select New Zone.

3- Click Next.

4- Select primary zone and click Next.

5- Click Next.

6- Select IPv4 Reverse Lookup Zone and click next.

7- Enter Network ID
Here we need to enter our EC2 Instance private IP address and click next.

8- Click next

9- Click finish.

10- Reverse lookup zone successful created.

11- Open command prompt and then type nslookup.

Creating new Users with Active Directory Users and Computer

1- Launch Server Manager choose tools and then choose Active Directory Users and Computers.
Or type Active directory users and computers in search bar and then select it

2- Expand your domain
Right-click on Users, choose New, and then User from the menu.

3- In the New Object – User dialog, type a First name, Last name, User logon name and then click Next.

4- Type and confirm a password, then click Next.

5- Click Finish.

6- Please follow the above step from 2 to 6 to create a second user
And type user users name and password in notepad

How to Create Directory Services

How to Allow AWS IAM users Access to Billing Dashboard

1- Select your account name and then select My Billing Dashboard

2- IAM user and allow Billing access to billing information click on Edit.

3- Select checkbox active IAM access and then click on Update.

How to Create an IAM Role AWS Amazon

How to Create Application Access URL

1- In the AWS management console select Directory Service.

2- In the Directories page, select your directory ID.

3- Directory details page, select the Application management tab.
Application access URL section, select on the Create button.

4- Enter a URL name (your domain controller example – xpertstec) and then select Create.

5- Next to AWS Management Console select Enable.

6- Now you can seed Delegate console access, click on billinguser under IAM role.

How to Assign Users or Groups to an Existing IAM role

1- Selected role page, under Manage users and groups for this role click on Add.

2- Add users and groups to the role page, under Select Active Directory Forest, choose your active directory (example: xpertstec.local) whichever contains where the accounts that need access to the AWS Management Console. Under Specify which users or groups to add, select find by user and then type the name of the user. In the list select the user you want to add. Select Add to finish.

3- Assigned the users to the role.

4- Select 2nd role (ec2access) under IAM role.

5- Select Add.

6- Select your active directory, search name, select it and then click Add.

7- Assigned the 2nd user to the role.

Configure Directory Services in AWS – Testing.

1- Open directory service click on directory ID.

2- Application access URL, under access URO (xpertstec.awsapps.com) copy this.

3- Open web browser and paste it bar with /console (example: xpertstec.awsapps.com/console) and press enter.
Type username, password and click sign in.

4- Click services tab and then click on EC2.

5- Now you can see this user is unable to create EC2 instance because he doesn’t have permission, The user has only billing permission.

6- Sign out this user.

7- Sign in with 2nd user (saleem).

8- Select EC2.

9- This user have full control.

In this blog, I will explain about AWS S3 object lifecycle management. Amazon Simple Storage Service (AWS S3) provides an easy procedure to control the lifecycle of your S3 objects. In the below simple steps, we examine how we can simply set up rules to delete or archive old data in S3 using the AWS SDK for. NET.

Lifecycle Rules

Lifecycle configurations are associated with a bucket. An object lifecycle configuration consists of a set of rules; with every rule determines the objects it acts on and the actions to take. Rules determine which objects they work on by specifying a prefix. A rule can catalog an object to Amazon Glacier, delete an object, or both. The activity related with a rule specifies a time restriction on it, getting in touch the objects that are either ancient than a specific number of days or after a specific date. A rule furthermore has a Status, which can be set to Disabled or Enabled. If you have not set this field, the rule will be disabled by default.

AWS S3 Object Lifecycle Management

Create an S3 Bucket

1- Login to your AWS Management console, select services and then select S3 under storage.

2- Click the Create Bucket button.

3- Enter a Bucket name (bucket2244) and then select Region.

4- Uptick Block all public access checkbox.

5- Bucket versioning select enable.

6- Under advanced settings Object Lock section. If you need to lock object then you select the enable option and then click on the Create bucket button.

7- The AWS S3 bucket (bucket2244) has been created successfully.

Upload Files and Folders to an S3 Bucket step by step

This process will explains how to upload files into an S3 bucket.

To upload files to AWS S3 bucket by pointing and clicking

1- Select your S3 bucket (bucket2244) the name of the bucket that you want to upload your files to.

2- Select Upload.

3- In the Upload dialog box, select Add files.

4- Select files to upload, and then select Open.

5- Click next.

6- To set permissions or properties for the files that we are uploading, select next.

7- Select storage class and then click next.

8- Select upload

9- One text file is successfully uploaded to our (bucket2244) bucket.

How to Create a Lifecycle Policy

1- In the Buckets list, select the name of the bucket that you want to create a lifecycle policy for.

2- Select the Management tab, Lifecycle and then select Add lifecycle rule.

3- Lifecycle rule wizard, type a name (lifecycle) for your rule.

The name should be unique within the bucket.

Choose rule scope – Apply to all objects in the bucket. Click Next

Storage class transition

Select the versions for which you need to define transitions, current or previous versions.
Current version: Define transitions that are applied to the current version of the object.
Previous versions: Define transitions that are applied to all previous versions of the object.

4- I have selected Current and Previous version. Click next

5- Current versions of objects

To add a transition
Under For current object versions, select Add transition.
Object creation Days after creation
Transition to Standard-IA after. 30
Transition to One Zone-IA after. 60
Transition to Glacier after. 180

Select the checkbox I acknowledge that this lifecycle ……….. and then select Next.

6- Previous versions of objects

To add a transition
Under For previous versions of objects, select Add transition.
Object becomes a previous version Days after objects become noncurrent
Transition to Standard-IA after. 30
Transition to One Zone-IA after. 60
Transition to Glacier Deep Archive after. 120

Select the checkbox I acknowledge that this lifecycle ……….. And then select Next.

7- Configuring expiration

Select Permanently delete previous versions, and then type the number of days after an object becomes a previous version to permanently delete the object (365 days).
Select Clean up incomplete multipart uploads and type the number of days after the multipart upload initiation that you want to end and clean up incomplete multipart uploads (7 days).

8- Review the settings for your rule. If you need to make changes, select Previous button. Otherwise, click on Save.

9- You can see it on the Lifecycle.

In this blog, I will explore how to enable cross region replication in different AWS regions. One is Tokyo and one is in Ohio region. Replication copies recently created objects & object updates from a source bucket to a destination bucket. Replication is the automated, nonsynchronous copying of objects crosses buckets in the different or same AWS Regions. For more details about S3 buckets replication concepts and how to utilize replication with the AWS CLI, AWS SDKs.

Enable Cross Region Replication

Create an S3 Bucket (Tokyo region)

1- Login to your AWS Management Console, select services, and then select S3 under storage.

2- Click the Create Bucket button.

3- Enter a Bucket name (tokyobucket22) and then select Region.

4- Uptick Block all public access checkbox.

5- Bucket versioning select enable.

6- Under advanced settings Object Lock section. If you want to lock object then you can select the enable option and then click create bucket.

The AWS S3 bucket (Tokyo region) has been created successfully.

Create an S3 Bucket (Ohio region)

1- Click on the create bucket to create a bucket in other region (Ohio).

2- Bucket name (ohiobucket222), select region (Ohio).

3- Uptick Block all public access checkbox.

4- Bucket Versioning select enable.

5- Advanced settings, under object lock select (enable/disable) and then click create bucket.

6- Buckets has been created successfully (1 in Tokyo and 1 in Ohio Region).

Adding Replication Rule

Add replication rule when the destination S3 bucket is in a different AWS account

1- In the Bucket name list, select the name of the bucket (tokyobucket22) that you want.

2- Select Management

3- Select Replication, and then select Add rule.

4- In the Replication rule wizard, under Set source page, entire bucket, and then click Save.

5- In the Set destination page, under Destination bucket.
Under storage, class select standard and then click next.

6- In the configure rule option, select Create a new role under IAM rule.
Under rule name type a rule name (Rep-Tokyo-Ohio).
Select enable under status and then click next.

7- Review your replication rule and then click save.

8- Replication configuration updated successfully.

How to upload files/folders to an S3 Bucket

This guide will explains how to upload files into an S3 bucket.

To upload files to an S3 bucket

1- Select your S3 bucket (tokyobucket22) the name of the bucket that you want to upload your files to.

2- Select Upload.

3- In the Upload dialog box, select Add files.

4- Select files to upload, and then select Open.

5- Click next.

6- Click on next button, to set permissions or properties for the files that you are uploading.

7- Select storage class and then click next.

8- Select upload

9- One text file is successfully uploaded to our (tokyobucket22) bucket, click Amazon S3.

10- Select other region bucket (ohiobucket222).

11- Now you can see our text file.

To upload files to an S3 bucket other region

1- Select your S3 bucket (ohiobucket222) the name of the bucket that you want to upload your files to. Select Upload.

2- In the Upload dialog box, select Add files.

3- Select files to upload, and then select Open. Click next.

4- Select next, to “Set permissions or properties” for the files that you are uploading, choose next.

5- Select storage class and then click next.

6- Select upload.

7- One text file is successfully uploaded to our (ohiobucket222) bucket, click Amazon S3.

8- Select the bucket (tokyobucket22), to check the files is uploaded on other bucket.

9- Now you can’t see the files on (tokyobuket22) bucket.

In this blog, we will show you the steps to create AWS VPC Peering across Region environment. VPC Peering allows traffic from VPC1 to be sent to VPC2, based upon the network address of the particular resource.

AWS VPC Peering Across Region

Environment Overview

For this, we are connecting two VPC’s between Tokyo and Ohio. In the Mumbai region, I have created a VPC with two subnets in a different availability zone.

How to Create VPC

1- Login with AWS account, go to the AWS Services tab and then select VPC under Networking & Content Delivery.

2- Under Virtual Private Cloud select Your VPCs
Click on Create VPC.

3- Create VPC wizard,
Name tag – VPC-Ohio.
IPv4 CIDR block – 192.168.0.0/16.
Tenancy – default
Click Create

4- Click close

5- Now you can see VPC successfully created in Ohio Region.

Create Subnet

1- Select Subnets.
Choose Create Subnet.

2- Name tag – Ohio-Subnet.
VPC – select the VPC-Ohio that you created earlier.
Availability Zone
IPv4 CIDR block – Type a CIDR block. For example (192.168.0.0/24)
Click Create.

3- Click close

4- Subnets successfully created.

Create Internet Gateway

1- Choose Internet Gateways new and then select Create Internet Gateway.

2- Enter a name (Ohio-IGW) in the Name tag text box and then click create an internet gateway.

3- The internet gateway (IGW) just created is in a detached state. Now you need to attach it to the VPC.

choose the action menu select Attach to VPC.

4- Select your VPC-Ohio from the drop-down list and then click Attach internet gateway.

5- The internet gateway changes to attached state.

Create Route Table

1- Select Route Tables.
Click on Create route table.

2- Name tag – Type a name for your route table (Ohio-Route).
VPC – Select your VPC-Ohio, and then select Create.

3- Click Close

Routing of public subnets

We need to configure the routing for our subnets. Enable traffic from the subnets to Internet by using the IGW (internet gateway) attached to the VPC.

4- Select Ohio-Route, Select Routes tab and then click Edit routes. Click Add route.

5- The traffic from the instances in the subnets intended to the Internet will be redirected to the IGW.

Reoriented to the Route Table in the Virtual Private Cloud.
Add route for the Route Table, one for the traffic to the Internet to be routed using the IGW.
Select Add rules for destination type 0.0.0.0/0 (all packets for the internet) and for targets select the Internet Gateway.

6- Select (Ohio-IGW) have created as in the earliest and then select Save routes.

7- Click close.

8- Successfully route edited

Choose Subnet Associations and then select Edit Subnet associations.

9- Select your subnet (Ohio-Subnet) and then click Save.

10- Successfully edit subnet associations.

Steps to create VPC Peering connection across region in AWS

How to Create VPC Tokyo

1- Login to AWS account and choose the AWS Services tab and then select VPC under Networking & Content Delivery.

2- Under Virtual Private Cloud select Your VPCs
Click on Create VPC.

3- Create VPC wizard,
Name tag – VPC-Tokyo.
IPv4 CIDR block – 10.0.0.0/16.
Tenancy – default
Click Create

4- Click close

5- Now you can see VPC successfully created in Tokyo Region.

Create Subnet

1- Select Subnets.
Choose Create Subnet.

2- Name tag – Tokyo-Subnet.
VPC – select the VPC-Tokyo that you created earlier.
Availability Zone
IPv4 CIDR block – Type CIDR block. For example (10.0.0.0/24)
Click Create.

3- Click close

4- Subnets successfully created.

Create Internet Gateway

1- Choose Internet Gateways new option and then click Create Internet Gateway.

2- Enter a name (Tokyo-IGW) in the Name tag text box and then click create internet gateway.

3- The IGW just created is in a detached state. Now we need to attach it to you VPC.

In the action menu select Attach to VPC.

4- Select your VPC-Tokyo from the drop-down list and then click Attach internet gateway.

5- The internet gateway changes to attached state.

Create Route Table

1- Select Route Tables.
Click on Create route table.

2- Name tag – Type a name for your route table (Tokyo-Route).
VPC – Select your VPC-Tokyo, and then select Create.

3- Click Close.

Routing of public subnets

4- We want to configure the routing for the subnets. Enable traffic from the subnets to Internet by using the IGW attached to the VPC.

Select Ohio-Route, Select Routes tab and then click Edit routes.

5- Now traffic from AWS instances in the subnets predestined to the Internet will be redirected to the Internet Gateway.

Then you can redirect to the Route Table in the Virtual Private Cloud.
Add route for the Route Table, 1 for the traffic to the Internet to be routed using the IGW.
Choose Add rules button for destination enter 0.0.0.0/0 (all packets for the internet) and then select the Internet Gateway for targets.

6- Select (Tokyo-IGW) have created as in the earliest and then select save routes.

7- Click close.

8- Successfully route edited

Choose Subnet Associations and then choose Edit Subnet associations.

9- Select your subnet (Tokyo-Subnet) and then click Save.

10- Successfully edit subnet associations.

Creating VPC Peering Connection

1- Under the virtual private cloud, select peering connections.

2- Click on create peering connection button.

3- Provide a name for the peering connection (Peering-Ohio-Tokyo) and select the local VPC (VPC-Ohio) from the drop-down list.

Go to your Tokyo region

4- Select Your VPCs
Select Description and then copy VPC ID

We have created the two VPC’s indifferent under the same AWS account.

5- Select another VPN to peer with
Select the Account as My account
Region – Select Another region
Select other region (in this article I have other region Tokyo)
VPC (Accepter) – Paste VPC ID (Tokyo) we have copied earlier
After selecting the VPC (Requester) and then VPC (Accepter) click create peering connection.

6- Click OK.

7- Now peering connection is created (between Ohio and Tokyo) and in pending status.

Accepting Connection

8- Go to your other region (Tokyo).
Select Peering Connection

9- Click on Action menu and then click accept request.

10- Click on the Yes, Accept button.

11- VPC peering connection has been established successfully.

12- Now peering connection is in active status (Tokyo).

13- Now peering connection is in active status (Ohio).

Updating the Routing Tables in Ohio Region

1- Go to Ohio region and access VPC dashboard. Click on the Routing table’s link.

2- Select Ohio-Route, Select Routes tab and then click Edit routes.

3- Add the new route entry for Tokyo VPC Network range.
We use 10.0.0.0/16 range as the VPC network in the Tokyo region.
choose the peering connection as a target from the drop-down list.

4- Select peering-Ohio-Tokyo and then click save routes.

5- Click close

6- Successfully route edited.

Updating the Routing Tables in Tokyo Region

1- Go to Tokyo region and access VPC dashboard. Click on the Routing tables.
Select Tokyo-Route, select Routes tab and click on edit routes.

2- Now, add the Ohio region VPC network in Tokyo Routing Table. We use 192.168.0.0/16 range as the VPC network in Ohio region.
Select Peering Connection

3- Select peering-Ohio-Tokyo and then click save routes.

4- Click close

5- Successfully route edited

Create Instance (Tokyo Region)

1- Choose service tab and then choose EC2 under compute.

2- Choose instance on your left side and then select Launch Instance button.

3- Choose Microsoft Windows Server 2019.

4- Choose the instance type as per your requirements.
Click Next : Configure Instance details.

5- Network – select VPC (VPC1-Tokyo).
Subnets – select Tokyo-Subnet.
Auto Assign Public IP – select Enable.
Click on Next : Add Storage.

6- Click Next : Add Tags.

7- Here we can tagged the instance (Tokyo-Instance)
Click on Next : Configure Security Groups

8- Create new Security Group.
Security group name – Tokyo-Security
Choose Protocols RDP, ALL ICMP – Ipv4, choose Source Anywhere
Click on Review and then Launch

9- Review instance details and then click launch.

10- Choose Create a new key pair
Type a name of your key (tokyo-ohio-peering)
Click the download key pair button and then save it in your secured folder

11- After downloading and saving your key pair, click launch instance.

12- Instance created.

Create Instance (Ohio Region)

1- Click on service tab and then select EC2 under compute.

2- Select instance tab and then click on Launch Instance button.

3- Select Microsoft Windows Server 2019.

4- Click Next : Configure Instance details.

5- Network – select VPC (VPC-Ohio).
Subnets – select Ohio-Subnet.
Auto Assign Public IP – select Enable.
Click on Next : Add Storage.

6- Click Next : Add Tags.

Here we have tagged the instance (Ohio-Instance)

7- Click on Next : Configure Security Groups.

8- Create a new Security Group.
Security group name – Ohio-Security
Protocols RDP, ALL ICMP – Ipv4, choose Source Anywhere
Click on Review and Launch

9- Review details and then click launch.

10- Select Create a new key pair
Type a name to your key (Ohio-Tokyo-Peering)
Click download key pair button and save it to secured folder

11- After downloading key pair and saving it, click launch instance.

12- Ohio-Instance successfully created.

Testing VPC Peering Connection

1- Select Tokyo-Instance (Tokyo Region) and then click connect.

2- Select Get Password.

3- Select choose file and select your key pair and then click decrypt password.

4- Copy password and click on download remote desktop file.
And login to Tokyo-Instance.

5- Search Firewall & network Protection.

6- Disable firewall & network protection.

We have successfully tested the connectivity between these two regions using the ping command. We are able to ping the server each other without any issue.

Tokyo-Instance desktop.

Open command prompt and ping Ohio-Instance IP address.

Ohio-Instance desktop.

Open command prompt and ping Tokyo-Instance IP address.

Related: How to Enable Cross Region Replication for Amazon S3.

Related: AWS VPC Peering Connection in Same Region

In this article, I will show you the steps to create a VPC peering connection same region in AWS environment in same region.

AWS VPC Peering Connection Same Region

How to Create VPC

1- Login to your AWS account and go to the AWS Services tab and then select VPC under Networking & Content Delivery.

1st VPC

2- Under Virtual Private Cloud select Your VPCs
Click on Create VPC.

3- Create VPC wizard,
Name tag – VPC1.
IPv4 CIDR block – 10.0.0.0/16.
Tenancy – default
Click Create

4- Click close.

Create 2nd VPC

1- Click create VPC

2- Name tag – VPC2.
IPv4 CIDR block – 192.168.0.0/16.
Tenancy – default
Click Create

3- Click close

4- Now you can see two VPC created.

Create Subnet in AWS

1- Select Subnets and then choose Create Subnet.

2- Name tag – VPC1-Subnet.
VPC – choose VPC that we have created earlier.
Availability Zone – Select one zone.
IPv4 CIDR block – type a valid CIDR. (For example – 10.0.0.0/24)
Click Create.

3- Click close

2nd Subnet

1- Choose create subnet.

2- Name tag – VPC2-Subnet.
VPC – choose the VPC that we have created earlier.
Availability Zone – Select one zone.
IPv4 CIDR block – type a valid CIDR. (For example – 192.168.0.0/24)
Click Create.

3- Click close

4- Subnets successfully created.

Create Internet Gateway

1- Choose Internet Gateways new option and then click on Create Internet Gateway.

2- Enter a name (VPC-IGW) in the Name tag text box and then click create an internet gateway.

3- The internet gateway has been created is in a detached state. Now we want to attach it to our VPC.

In the action menu select Attach to VPC.

4- Select your VPC1 from the drop-down list and then click Attach internet gateway.

5- The internet gateway changes to attached state.

2nd Internet gateway

1- Click create internet gateway.

2- Enter a name (VPC2-IGW) in the Name tag text box and then click create an internet gateway.

3- The internet gateway has been created is in a detached state. Now we want to attach it to your VPC.

Select Attach to VPC.

4- Select your VPC2 from the drop-down list and then click Attach internet gateway.

5- The internet gateway changes to attached state.

Create Route Table

1st Route Table

1- Select Route Tables.
Click on Create route table.

2- Name tag – Type a name for your route table (VPC1-Route).
VPC – Select your VPC1, and then select Create.

3- Click Close

2nd Route Table

1- Click create route table.

2- Name tag – Type a name for your route table (VPC2-Route).
VPC – Select your VPC2, and then select Create.

3- Click Close

4- Two routes successfully created.

CREATING VPC PEERING CONNECTION

1- Under virtual private cloud, click on peering connections.

2- Click on create peering connection button.

3- Type a name for the peering connection
VPC (Requester) select the VPC1 from the drop-down list.

4- We have created the two VPC’s under the same AWS region.
Select another VPN to peer with VPC2

5- After selecting VPC (Requester) and VPC (Accepter) click create peering connection.

6- Click OK.

7- Now peering connection is created and in pending status.

Accepting Connection

8- Click on Action menu and then click accept request.

9- Click on the Yes, Accept button.

10- VPC peering connection has been established successfully.

11- Now peering connection is in active status.

Routing of public subnets

Now you need to configure the routing for our subnets. Enable traffic from the subnets to Internet via the internet gateway attached to the VPC.

1- Select VPC1-Route, Select Routes tab and then click Edit routes.

2- Click Add route.

3- Click on Add rules button for destination enter 0.0.0.0/0 (all packets for the internet) and then for targets select the Internet Gateway.

4- Select (VPC1-IGW) have created as in the earliest.

5- Click on Add button again type 192.168.0.0/24.
Under Target select peering connection

6- Select peering VPC1-VPC2 and then click save routes.

7- Click close.

8- Successfully route edited.

9- Choose Subnet Associations and then choose Edit Subnet associations.

10- Select your subnet (VPC1-Subnet) and then click Save.

11- Select VPC2-Routes, select Route tab and then click Edit routes.

12- Click Add route.

13- Click on Add rules button for destination type 0.0.0.0/0 (all packets for the internet) and for targets select the Internet Gateway.

14- Select (VPC2-IGW) have created as in the earliest.

15- Click on Add button again type 10.0.0.0/24.
Under Target select peering connection

16- Select peering VPC1-VPC2 and then click save routes.

17- Click close

Successfully route edited

18- Select VPC2-Route, select Subnet Associations, and then click on Edit Subnet associations.

19- Select your first subnet (VPC2-Subnet) and then click Save.

Create Instance

1- Choose service tab, click on EC2 under compute.

2- Choose instance tab and then click on Launch Instance button.

3- Select Microsoft Windows Server 2019.

4- Select General purpose t2 micro
Click Next : Configure Instance details

5- Network – select VPC (VPC1).
Subnets – select VPC1-Subnet.
Auto Assign Public IP – select Enable.
Click on Next : Add Storage.

6- Click Next : Add Tags.

7- Here we have tagged the instance (VPC-Server1)
Click on Next : Configure Security Groups

8- Create a new Security Group.
Security group name – VPC-Security
Select Protocols RDP, ALL ICMP – Ipv4, Select Source Anywhere
Click on Review and Launch

9- Review details, parameters and then click launch.

10- Select Create a new key pair
Type a name to your key (VPC Peering key)
Click on download key pair and then save it in your secured folder

11- After downloading and saving your key, click launch instance.

Now we need to create a second EC2 instance

Network – VPC2
Subnet – VPC2-Subnet
Auto-assign Public IP – Enable

Add Tag
Name – VPC-Server2

Testing VPC Peering Connection Same Regions

1- Choose VPC-Server1 and then choose connect.

2- Choose Get Password

3- Click on choose file, select your key pair and then click decrypt password.

4- Copy password and then click on download remote desktop file.
And login to VPC1-Server.

5- Search Firewall & network Protection and open it.

6- Disable firewall and network protection.

7- VPC-Server1 desktop.
Run command prompt and then ping VPC-Server2 IP address.

8- VPC-Server2 desktop.
Run command prompt and then ping VPC-Server IP address

Create VPC NAT Gateway, NAT Gateway is a high-availability AWS manageable service that makes it easily to connect to the Internet from instances inside a private subnet in an Amazon (VPC) Virtual Private Cloud. Previous, you needed to launch a NAT instance to enable NAT for instances in a private subnet.

Create VPC NAT Gateway in AWS

To know about NAT Gateway please visit AWS

How to Create VPC

1- Log in with AWS account and select AWS Services tab and then select VPC under Networking & Content Delivery.

2- Virtual Private Cloud – select Your VPCs
Select Create VPC.

3- Create VPC wizard,
Name tag – My-VPC
IPv4 CIDR block – 10.0.0.0/16.
Tenancy – default
Click Create.

4- Click Close.

5- Now you can see two VPC created.

How to Create Subnet in AWS

1st Subnet

1- Select Subnets and then select Create Subnet.

2- Name tag – PublicSubnet.
VPC – Select the VPC (My-VPC) that you created earlier.
Availability Zone – Select Availability zone.
IPv4 CIDR block – type a valid CIDR block. (For example – 10.0.0.0/24)
Click Create.

3- Click Close.

4- Subnet successfully created

2nd Subnet

Select Create Subnet

5- Name tag – PrivateSubnet.
VPC – select the VPC (My-VPC) that you created earlier.
Availability Zone – Select Availability zone.
IPv4 CIDR block – Type a valid CIDR block. (For example – 10.0.2.0/24)
Click Create.

6- Click Close.

7- Subnet successfully created.

Create Internet Gateway

1- Select Internet Gateways new and then click Create Internet Gateway.

2- Enter a name in the Name tag text box and then click create internet gateway.

3- Internet gateway successfully created and in a detached state. Now we need to attach it to your VPC.

Choose Attach to a VPC button, or in the action menu select Attach to VPC.

4- Select your VPC (My-VPC) from the drop-down list and then click Attach internet gateway.

5- The internet gateway changes to attached state.

Create VPC NAT Gateway in AWS

Create a Route Table

1st Route Table

1- Select Route Tables.
Click on Create route table.

2- Name tag – Type a name for your route table (Public-Route)
VPC – Select your VPC (My-VPC), and then select Create.

3- Click Close.

4- Route Table successfully created.

2nd route table

Click Create route table

5- Name tag – Type a name for your route table (Private-Route)
VPC – Select your VPC (My-VPC), and then select Create.

6- Click Close.

7- Subnet successfully created.

Routing of Public Subnets

Now you need to configure the routing for our public subnets. Enable traffic from the public subnets to Internet by utilize the internet gateway attached to the VPC.

Public-Route

1- Select Public-Route, select Subnet Associations, and then click on Edit Subnet associations.

2- Select your first public subnet (PublicSubnet) from the list and navigate to its Summary section and then click Save.

3- Select Routes tab and then click Edit routes.

4- Now the traffic from instances in the public subnets intended to the Internet shell be redirected to the Internet Gateway.

Then you redirected to the Route Table in the Virtual Private Cloud.
Add route for the Route Table – one for the traffic to the Internet to be routed using the Internet Gateway.
Click Add rules for destination type 0.0.0.0/0 (all packets for the internet) and for targets select the Internet Gateway.

5- Select (VPC-IGW) have created as in the earliest and then click save routes.

6- Click close.

Private-Route

7- Select Private-Route, select Subnet Associations, and then click on Edit subnet associations.

8- Select PrivateSubnet and then click save.

9- Successfully edit routes.

Create Instance

1st EC2 Instance

1- Choose service tab and then click on EC2 under compute.

2- Select instance on your left side and then click on Launch Instance button.

3- Select Microsoft Windows Server 2019.

4- Choose the type of instance you require based on your requirements.
Click Next : Configure Instance Details.

5- Network – select VPC (My-VPC).
Subnets – select PublicSubnet.
Auto Assign Public IP – select Enable.
Click on Next : Add Storage.

6- Click Next : Add Tags.

7- Here we have tagged the instance (Public Instance)
Click on Next : Configure Security Groups

8- Create a new Security Group.
Security group name – VPC-Securit
Choose Protocols RDP, HTTP, HTTPS and then Select Source Anywhere
Click on Review and then Launch.

9- Review instance details, parameters and then click launch.

10- Select Create a new key pair
Type a name to your key (Private-key)
Click download key pair and save it in your secured folder

11- After downloading key pair and saving your key, click launch instance.

12- Click view instances.

2nd EC2 instance

Network – My-VPC
Subnet – PrivateSubnet
Auto-assign Public IP – Disable

14- Tow Instance created.

How to login with AWS Instance

1- Select Public Instance and then click connect.

2- Select Get Password.

3- Select choose file and select your key pair and then click decrypt password.

4- Copy password and click on download remote desktop file.

5- Successfully login with Public Instance.

6- Search remote desktop connection and then select it.

7- Go back to your instances and choose Private Instance
Copy Private IP.

8- Paste in remote desktop connection and then click connect.

9- Inter your private instance credential and then click ok.

10- Private Instance server desktop.

Test the internet is working.

Type pint 8.8.8.8 and hit enter.

How to Create a NAT Gateway

1- Go back to your VPCs and select NAT Gateways.

2- Select Create NAT Gateway.

3- Select PublicSubnet.

4- Click on Allocate Elastic IP address.

5- Elastic IP Allocation ID created click on Create a NAT Gateway.

6- Click Close.

7- NAT Gateway is in pending status.

8- Select Route Tables
Select Private-Route
Select routes tab and then click on Edit routes.

9- Click Add route and type 0.0.0.0/0
Under target from drop-down menu select NAT Gateway.

10- Select newly create NAT Gateway and then click save routes.

11- Click Close.

12- Route table successfully edited.

14- Now NAT Gateway is in available status.

Go back your private instance and you can see it start pinging.

VPC – Subnet – IGW – Route table

In this blog, I will show you how to create a virtual private cloud (VPC), Subnet, Internet Gateway, and route tables in the AWS Management console.

VPC – Subnet – IGW – Route table

How to Create VPC

1- Login to your AWS account and go to the AWS Services tab and then select VPC under Networking & Content Delivery.

2- Select Your VPCs under virtual private cloud

3- Click on Create VPC.

4- Create VPC wizard,
Name tag – My-VPC.
IPv4 CIDR block – 192.168.0.0/16.
Tenancy – default
Click Create

5- Click close

6- Now you can see two VPC created.

How to Create Subnet in AWS

1- Select Subnets and then click on Create Subnet.

2- Name tag – My-Subnet.
VPC – Select the VPC that you created earlier (My-VPC)
Availability Zone – Select an Availability zone.
IPv4 CIDR block – Enter valid CIDR block. For example (192.168.0.0/24)
Click Create.

3- Click close

4- Subnet successfully created

Create Internet Gateway in VPC

1- Select Internet Gateways new and then click Create Internet Gateway

2- Enter a name in the Name tag text box and then click create internet gateway.

3- The internet gateway just created and it is detached state. Now we need to attach it to your VPC.

Click Attach to a VPC, or in the action menu select Attach to VPC.

4- Choose your VPC from the drop-down list and then click Attach internet gateway.

5- The internet gateway changes to attached state.

Create Route Table

1- Select Route Tables, and then click on create route table.

2- Name tag – Type a name (My-Route table).
VPC – Select you’re (My-VPC) and then select Create.

3- Click Close

4- Route Table successfully created.

Routing of public subnets

Now you need to configure the routing for our public subnets. Traffic Enable from your public subnets to Internet by using the IGW attached to the VPC.

1- Select My-Route table and then select Subnet Associations

2- Click on Edit Subnet associations.

3- Select subnet ID (My-Subnet) and then click Save.

4- Select Routes and then Click edit route

5- Traffic from instances in the public subnets destined to the Internet will be redirected to the IGW.

Then you are redirected to the Route Table in the Virtual Private Cloud.
Click Add rules for destinations enter 0.0.0.0/0 and then select Internet Gateway.

6- Select (My-IGW) and then click save routes.

7- Click close

Create EC2 Instance

1- Select service tab, click on EC2 under compute.

2- Click on Launch Instance button.

3- Select Microsoft Windows Server 2019.

4- Select – General purpose t2.micro
Click Next : Configure Instance details

5- Network – select VPC (My-VPC).
Subnets – select My-Subnet.
Auto Assign Public IP – select Enable.
Click on Next : Add Storage.

6- Click Next : Add Tags.

7- Here we have tagged the instance (vpc server)
Click on Next : Configure Security Groups

8- Create a new Security Group.
Security group name – VPC-Security Group
Select Protocols RDP, HTTP, HTTPS, Select Source Anywhere
Click on Review and Launch

9- Review instance details and parameters and then click launch.

10- I am using existing pair key

11- Click view instances.

12- Now Instance created

For more details how to create EC2 Instance