A load balancer serves as the single point of contact for clients. The load balancer distributes incoming application traffic across multiple targets, such as EC2 instances, in multiple Availability Zones. This increases the availability of your application. You add one or more listeners to your load balancer.

[ Reference Source: AWS documentation ]

Let's start the Lab session in AWS account

In this lab you will learn the following:

• How to create an EC2 instance with user data

• How to make simple VPC

• How to make a security group suit for ELB

• How to configure multiple EC2 with an Application load balancer

Step 1: Create a Simple VPC.

• Search VPC and create VPC as the following VPC setting:

  • Resources to create: VPC Only

  • Name tag - optional: myVPC

  • IPv4 CIDR: 10.0.0.0/16

  • Leave all default and Create VPC

• Select subnets and create subnets as:

  • VPC ID: Select myVPC

  • Subnet Settings: (for subnet1)

    • Subnet name: subnet1

    • Availability Zone: Select 1st zone

    • IPv4 CIDR block: 10.0.0.0/24

  • Add new subnet

  • Subnet Settings: (for subnet2)

    • Subnet name: subnet2

    • Availability Zone: Select 2nd zone

    • IPv4 CIDR block: 10.0.1.0/24

( Note: you can add more than 2 subnets also )

Create subnet

• Create an internet gateway and attach it to VPC as:

  • Internet gateway settings

    • Name tag: myIG

      Create internet gateway

  • Attach to a VPC and select myVPC

    Attach internet gateway

• Select the route table and Create the route table as:

  • Route table settings

    • Name - optional: route

    • VPC: Select myVPC

Create route table

• Select route ID and then go to Routes -> Edit routes -> Add route

  • Destination: 0.0.0.0/0

  • Target: Select internet gateway and select that we created

    and Save changes

• Similarly, Select route ID and then go to Subnet associations -> Edit Subnet associations

  • Select all subnets and Save associations

Step 2: Create a security group for ELB:

Search VPC, scroll down its left sidebar and create a security group as:

• Security group name: ELBsecurity

• Description: Elastic load balancer use it

• VPC: remove existing and select myVPC

• Inbound rules:

  • Add rule

    1. Type: SSH, Source: 0.0.0.0/0

    2. Type: HTTP, Source: 0.0.0.0/0

• Outbound rules:

  • Leave default i.e. Type: All traffic, Source: 0.0.0.0/0

• Create security group

Step 3: Create two EC2 instances.

• Search EC2 and Launch EC2 instance as:

• For the first EC2 instance

  • Name: server1

  • Create a key-pair or choose any existing key.

  • Network Setting > Edit

    • VPC: Select myVPC

    • Subnet: Select subnet1

    • Auto-assign public IP: enable

    • Firewall: Check select existing security group and select ELBsecurity that we created

  • Leave all default and Expand Advanced details

    • Go directly to the user data field at last and copy-paste this:

        #!/bin/bash
        sudo yum update -y
        sudo yum install -y httpd
        sudo systemctl start httpd
        echo "<html><body><h1> Hello! I am server1 </h1></body></html>" > /var/www/html/index.html
      

      Launch instance

• For the second EC2 instance

  • Name: server2

  • Create a key pair or choose any existing key.

  • Network Setting > Edit

    • VPC: Select myVPC

    • Subnet: Select subnet2

    • Auto-assign public IP: enable

    • Firewall: Check select existing security group and select ELBsecurity that we created

  • Leave all default and Expand Advanced details

    • Go directly to the user data field at last and copy-paste this:

        #!/bin/bash
        sudo yum update -y
        sudo yum install -y httpd
        sudo systemctl start httpd
        echo "<html><body><h1> Hello! I am server2 </h1></body></html>" > /var/www/html/index.html
      

      Launch instance

• Also, you can check after the 2/2 check passed whether your instances are publically accessible or not by rendering their public IP in a new tab.

  For example, server2 public IP gives:

  

Step 4: Create an Application load balancer.

• In the left bar of EC2 scroll down and click on Load balancers

• Click Create load balancer -> Application load balancer Create

• Create Application Load Balancer as:

• Basic configuration

  • Load balancer name: balanceLoad

  • Leave all default

• Network mapping

  • VPC: Select myVPC

  • Mappings: Select at least two availability zones for now we have only 2 subnets of different availability zones so select both

• Security groups

  • Security groups: Select ELBsecurity and remove the default one

• Listeners and routing

  • Listener HTTP:80

    Default action: Select a target group but we don't have a target group. Our priority is to create a target group, So select Create target group.

    [you can also create a target group first and then associate at that point.]

  • It renders directly to the Create target group or you can select manually at the left bar of the EC2 instance just below the load balancers

{

• Create target group as:

  • Specify group details:

    • Target group name: targetELB

    • VPC: myVPC

    • Protocol version: leave as HTTP1

    • Leave all default and Next

  • Register targets

    • Select both available instances and Click on Ports for the selected instances: 80 and

      Include as pending below

    • Then Create target group

}

• Go back to Listeners and routing, refresh, and select targetELB

  

Leaving all default and Create load balancer

Step 5: Render the DNS of an Application load balancer.

• Go to load balancer and copy the DNS name of balanceLoad that we created.

• Open a new tab of any browser and paste it.

• Now, observe by refreshing the tab how the load is distributed.

Don't forget to remove and terminate all services that you created during the lab session.

Happy Learning!!!

• Created an Amazon EC2 launch template

• Created an Amazon EC2 Auto Scaling launch configuration

• Configured scaling policies and created auto Scaling group to scale in and scale out the number of servers based on variable load

You need to first create these for this lab:

• VPC with subnet 10.0.0.0/16

  • For Availability Zone 1

    • public subnet: 10.0.0.0/24

    • private subnet: 10.0.1.0/24

  • For Availability Zone 2

    • public subnet: 10.0.2.0/24

    • private subnet: 10.0.3.0/24

• Security Group

  • Inbound rule: HTTP and SSH

[ Visit my previous blogs for Creating VPC and Security group if you had problem ]

Let's begin:

1. In EC2 -> Load Balancing session select Load Balancers and Create load balancer Select Application load balancer

• Basic configuration

  • Load balancer name: WebELB

  • Select VPC: myVPC

  • Mappings: Select at least two AG so select both public subnets of different AG

• Security groups

  • Security group: Select that you created to access HTTP

• Listener and routing

  • Protocol: HTTP Port: 80

  • Create target group as:

    • Target group name: web-app

    • VPC: myVPC

      Next

    • Register the targets session leave it as default and

      Create target group

-Go back to the load balancer tab, refresh, and select the target group that you created

1. Creating a launch template

• In the EC2 left bar there is an instances section in which Launch Templates also select and create launch templates as:

  • Launch template name: webtemp

  • Template version description: For autoscaling use

  • Select Provide guidance to help me set up a template that I can use with EC2 Auto Scaling

  • Application and OS Images: select My AMIs and leave the default option

  • Instance type: t3.micro or other free tiers if exits

  • Key pait(login)-> Key pair name: don't include in the launch template

  • Network Settings-> Subnet: Don't include in launch template Firewall(security group): Select the existing security group and select that you created for HTTP access

  • Leave all defaults and Create launch template

1. Creating an Auto Scaling group

• Choose the Launch template that we created and From Action dropdown select Create Auto Scaling group

  • Name ->

    • Auto Scaling group name: Web Auto Scaling Group

    • All Default and Next

  • Network ->

    • VPC: myVPC

    • Availability Zones and subnets: Select both private subnets

    • Choose Next

  • Load balancing ->

    • Select Attach to an existing load balancer

      • Existing load balancer target groups: Select web-app that you created

    • Health checks:- Select Turn on Elastic Load Balancing health checks

    • Choose Next

  • Configure group Size and scaling policies - optional

    • -> Group size - optional

      • Desired capacity: 2

      • Minimum capacity: 2

      • Maximum capacity: 4

    • -> Scaling policies - optional

      • Select Target tracking scaling policy

        • Metric type: choose Average CPU utilization

        • Target value: 50

        • Choose Next

  • Add notifications - optional

    • Choose Next

  • Add tags - optional

    • Choose Add tag Key: Name Value-optional: WebApp

  • Review and Create Auto Scaling group

1. Verify autoscaling

• Select instances and you see there are 2 WebApp named instances are automatically created

• Select Target Groups and select that you created above and observe health status -> healthy

1. Test auto-scaling configuration

• When the Load of CPU utilization reaches 50%+ after a few minutes you should see your auto-scaling group add a new instance. This occurs because Amazon CloudWatch detected that the average CPU utilization of your Auto Scaling group exceeds 50% and your scale-up policy has been invoked in response. The maximum of 4 instances of name WebApp created according to policy. You can add more if needed.

Have a great day!!!

Following are some important directories in Linux:

1. / (Root Directory): The top-level directory and the starting point of the file system hierarchy.

2. /bin (Binary): Essential command binaries (programs) required for system boot and repair. This host commands executable files like ls, pwd, etc.

3. /boot: Contains the kernel and files needed for the initial stages of the boot process.

4. /dev (Device): Device files representing hardware devices on the system. Files having information about hardware devices.

5. /etc (Etcetera): Configuration files and scripts needed to boot the system and configure various applications. Important for system users and DevOps.

6. /home: Home directories for regular users.

7. /lib (Library): Essential shared libraries and kernel modules.

8. /media: Mount points for removable media such as USB drives or external hard disks.

9. /mnt (Mount): Mount points for temporarily mounted file systems.

10. /opt (Optional): Optional software packages.

11. /proc: A virtual file system that provides information about processes and system resources.

12. /root: Home directory for the root user.

13. /run: Temporary files created by system processes.

14. /sbin (System Binary): Essential system binaries used for system administration.

15. /srv (Service): Data for services provided by the system.

16. /sys: A virtual file system that exposes kernel parameters and information about devices, buses, and other kernel components.

17. /tmp (Temporary): Temporary files that are deleted upon reboot.

18. /usr (User): Secondary hierarchy containing user documentation, games, and other non-essential utilities.

19. /var (Variable): Variable data such as log files, spool directories, and temporary files.

How to work with SNS? Let's make it easy!

Here is a simple example, in which we are going to set an email alert if there are any changes in our EC2 instance.

Step 1: Configure Amazon SNS

1. Search SNS and select it

2. Goto Topics on left bar

3. Click on Create topic

   • Select type Standard

   • Name: EmailAlert

   • Leave all default and Create topic

4. Goto subscriptions and select Create subscription

   • In Details Setting

     • Topic: Select EmailAlert

     • Protocol: Select Email

     • Endpoint: your-email-address

   • Create subscription

5. Now, Open your email, select the AWS Notification email and

   select Confirm subscription

   

Step 2: Config Amazon EventBridge

(Another form of CloudWatch)

EventBridge is a serverless service that uses events to connect application components together, making it easier for you to build scalable event-driven applications. Use it to route events from sources such as home-grown applications, AWS services, and third-party software to consumer applications across your organization. EventBridge provides a simple and consistent way to ingest, filter, transform, and deliver events so you can build new applications quickly.

1. Search EventBridge on the search bar and select it, Also click on Buses to expand

   

2. Click on Rules then scroll down and click Create rule

3. Configure Step1: Define rule detail as:

   

4. Configure Step 2: Build event pattern as:

   • Leave all defaults and scroll down to Event pattern

     

     [ Don't panic: Select AWS service then Event type auto-generate ]

5. Configure Step 3: Select target(s) as:

   

6. Leave optional Step 4: optional Configure tags

7. Step 5: Review and create click on Create rule

   

Step 3: Working with the EC2 state

• In the EC2 instance anything you do with instance i.e. Create, stop, Terminate you will receive an alert email.

• For example, let's launch an EC2 instance without any special setup only with the name and existing key leaving all default.

• You receive an email like this:

  

Don't forget to terminate all the things you created !!!

Thanks for Learning the SNS config...

Now you can use MongoDB with ease.

THANKS FOR YOUR TIME

Intra-region VPC peering means the VPC peering connection between different VPCs within the same region.

Inter-Region VPC peering:

Inter-region VPC peering is the VPC connection between different VPCs of different regions.

In VPC peering we have to connect all of these with each other to connect since VPC does not support transition property as shown in the figure above.

In this lab, the following terms are considered:

• we are going to create 3 VPCs, 2 in the same region for intra-region connection and one in a different region for inter-region connection.

• Create at least one public subnet for now for each VPC for creating EC2 instance using that VPC

• EC2 is used to check whether the connection is established or not using the internet gateway and ssh.

Architecture for LAB:

Step 1: Create two VPCs using the configuration in any one region:

• Open your account and select us-east-1 any other region

• Goto VPC and then create two VPCs

For VPC1:

• Your VPCs: VPC settings:

  • Select Resources to create VPC only

  • Name tag - optional: VPC1

  • IPv4 CIDR: 10.0.0.0/16

    Create VPC

• Subnets: Create subnet

  • VPC ID: select VPC1

  • Subnet name: vpc1subnet

  • Availability Zone: us-east-1a or any other as your choice

  • IPv4 CIDR block: 10.0.0.0/24

    Create subnet

• Internet gateways: Create Internet gateway

  • Name tag: vpc1gateway

    Create internet gateway

  • Attach to VPC: Select VPC1

• Route tables: Create route table

  • Name - optional: vpc1route

  • VPC: Select VPC1

    Create route table

  • Select vpc1route ID -> Select Routes -> Edit route -> Add route

    • Destination: 0.0.0.0/0 Target: select internet gateway and then vpc1gateway

      Save changes

  • Select vpc1route ID -> Select Subnet associations->

    Edit subnet associations

    • Select vpc1subnet and Save associations

For VPC2: (in the same region us-east-1)

• Your VPCs: VPC settings:

  • Select Resources to create VPC only

  • Name tag - optional: VPC2

  • IPv4 CIDR: 20.0.0.0/16

    Create VPC

• Subnets: Create subnet

  • VPC ID: select VPC2

  • Subnet name: vpc2subnet

  • Availability Zone: us-east-1a or any other as your choice

  • IPv4 CIDR block: 20.0.0.0/24

    Create subnet

• Internet gateways: Create Internet gateway

  • Name tag: vpc2gateway

    Create internet gateway

  • Attach to VPC: Select VPC2

• Route tables: Create route table

  • Name - optional: vpc2route

  • VPC: Select VPC2

    Create route table

  • Select vpc2route ID -> Select Routes -> Edit route -> Add route

    • Destination: 0.0.0.0/0 Target: select internet gateway and then vpc2gateway

      Save changes

  • Select vpc2route ID -> Select Subnet associations->

    Edit subnet associations

    • Select vpc2subnet and Save associations

Step 2: Create EC2 instances for individual VPCs

FOR first EC2 using VPC1

• Search and open EC2

• Select Instances and Launch instances

  • Name: vpc1server

  • Key pair name - required: Create new key pair

    Key pair name: myk

    For putty select .ppk and for Linux or ssh select .pem

  • Expand Network settings and EDIT as

    • VPC - required: Select VPC1

    • Subnet: Select vpc1subnet

    • Auto-assign public IP: Enable

    • Firewall (security groups): Select Create security group

      (Note: You can individually create SG)

      • Security group name - required: Region1SG

      • Description - required: Its for VPC1 in region 1

      • Inbound Security Group Rules

        • Add security group rule:

          Type: All ICMP - IPv4

          Source type: Anywhere

Launch instances

FOR second EC2 using VPC2

• Search and open EC2

• Select Instances and Launch instances

  • Name: vpc2server

  • Key pair name - required: Create new key pair or Select myk created above

    For putty select .ppk and for Linux or ssh select .pem

  • Expand Network settings and EDIT as

    • VPC - required: Select VPC2

    • Subnet: Select vpc2subnet

    • Auto-assign public IP: Enable

    • Firewall (security groups): Select Create security group

      (Note: You can individually create SG)

      • Security group name - required: Region1SG2

      • Description - required: Its for VPC2 in region 1

      • Inbound Security Group Rules

        • Add security group rule:

          Type: All ICMP - IPv4

          Source type: Anywhere

Launch instances

All Done for Region 1

Step 3: Create VPC in another region as

For VPC3: Change region as us-west-2 or any other region

• Your VPCs: VPC settings:

  • Select Resources to create VPC only

  • Name tag - optional: VPC3

  • IPv4 CIDR: 30.0.0.0/16

    Create VPC

• Subnets: Create subnet

  • VPC ID: select VPC3

  • Subnet name: vpc3subnet

  • Availability Zone: us-west-1a or any other as your choice

  • IPv4 CIDR block: 30.0.0.0/24

    Create subnet

• Internet gateways: Create Internet gateway

  • Name tag: vpc3gateway

    Create internet gateway

  • Attach to VPC: Select VPC3

• Route tables: Create route table

  • Name - optional: vpc3route

  • VPC: Select VPC3

    Create route table

  • Select vpc3route ID -> Select Routes -> Edit route -> Add route

    • Destination: 0.0.0.0/0 Target: select internet gateway and then vpc3gateway

      Save changes

  • Select vpc3route ID -> Select Subnet associations->

    Edit subnet associations

    • Select vpc3subnet and Save associations

Step 4: Create an EC2 instance for VPC in that region

FOR EC2 using VPC3

• Search and open EC2

• Select Instances and Launch instances

  • Name: vpc3server

  • Key pair name - required: Create new key pair

    Key pair name: mykey3

    For putty select .ppk and for Linux or ssh select .pem

  • Expand Network setting and EDIT as

    • VPC - required: Select VPC3

    • Subnet: Select vpc3subnet

    • Auto-assign public IP: Enable

    • Firewall (security groups): Select Create security group

      (Note: You can individually create SG)

      • Security group name - required: Region2SG3

      • Description - required: Its for VPC3 in region 2

      • Inbound Security Group Rules

        • Add security group rule:

          Type: All ICMP - IPv4

          Source type: Anywhere

Launch instances

Step 5: Connect to any initial server

• Change the region: us-east-1

• Select the vpc1server and copy Public IPv4 address

• For window user

  • Download and Open Putty and in session:

    • Host Name (or IP address): paste Public IPv4 address

  • In left Expand +Connection -> Expand +SSH -> Expand +Auth -> Credentials

    • Private key file for authentication: browse and choose myk.ppk that automatically downloaded while creating key pair

  • Click Open

  • Accept if any alert box appears and login as: ec2-user in your case enter the IAM username to connect

• For Linux user

  • Open Bash terminal and go to the directory where you want to perform the SSH command

  • Locate the key pair that downloaded automatically while creating as myk.pem and move to that directory

  • Then paste the following code:

    ssh -i "myk.pem" <IAM-user-name>@<public-ip-address>

Replace <IAM-user-name> and <public-ip-address> with your own.

• Try the following command to check the initial connection with the internet

    ping google.com
  

• Also, try to ping the public IPs of other servers i.e. vpc2server and vpc3server

    ping <public-ip-address>
  

  Replace <public-ip-address> with copied public IP of the server and check connection is established or not.

Step 6: Connect to another server of the same region using the virtual server that we are connected in

• For window users only

  • Open myk.ppk from the downloaded location and copy all contents

  • Using PuttyGen or another platform convert it to pem for example, let's choose any trusted online converter and copy the contents of pem file

• If you are a Linux user you already had pem file so open it and copy the contents

• Now, go to the previously connected server and perform the following command

    nano new.pem
  

  And paste all that you copied using right-click, then Ctrl+O to save and Ctrl+X to exit.

• Now. copy the public IP of vpc2server and perform the following command

    sudo su
    ssh -i "new.pem" <IAM-user-name>@<public-ip-address>
  

  • Replace <IAM-user-name> and <public-ip-address> and select yes if any prompt is asked.

  • Through vpc1server you connected with vpc2server

  • Similarly, ping the public IPs of other servers i.e. vpc1server and vpc3server

      ping <public-ip-address>
    

    Copy and Replace <public-ip-address> with copied public IP of the server and check connection is established or not.

Step 7: Similarly, Connect to the server of the other region

• For window users only

  • Open mykey3.ppk from the downloaded location and copy all contents

  • Using PuttyGen or another platform convert it to pem for example, let's choose any trusted online converter and copy the contents of pem file

• If you are a Linux user you already had pem file so open it and copy the contents

• Now, go to the previously connected server and perform the following command

    nano new.pem
  

  And paste all that you copied using right-click, then Ctrl+O to save and Ctrl+X to exit.

• Now. copy the public IP of vpc2server and perform the following command

    sudo su
    ssh -i "new.pem" <IAM-user-name>@<public-ip-address>
  

  Replace <IAM-user-name> and <public-ip-address> and select yes if any prompt is asked.

  • Through vpc2server you connected with vpc3server located in a different region

  • Similarly, ping the public IPs of other servers i.e. vpc1server and vpc2server

      ping <public-ip-address>
    

    Copy and Replace <public-ip-address> with copied public IP of the server and check connection is established or not.

Which shows the use case of VPC peering.

Close all resources you created

Thank you !!! Happy Learning!

Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the AWS Cloud. It provides cost-efficient, resizable capacity for an industry-standard relational database and manages common database administration tasks.

LAB: Connect VS Code with Amazon RDS

In this lab, we are going to create a basic database in RDS to understand how to establish the connection between the RDS database and VS Code. So that we can access the database created in RDS and use it from VS Code text editor.

Step 1: Create a Database in RDS

• Search RDS and Select it

  

• Then Click on Create database and config as the information given:

  • Choose a database creation method: Standard

  • Engine option: MySQL

  • Templates: Free tier

  • Settings:

    • DB instance identifier: demo-db

    • Credentials Settings > Master Username: admin

    • Credentials Settings > Master password: **********

    • Credentials Settings > Confirm master password: **********

  • Storage:

    • Storage type: General Purpose SSD(gp2)

    • Storage autoscaling: you can uncheck Enable storage autoscaling

  • Connectivity:

    • Compute resource: Don’t connect to an EC2 compute resource

    • Virtual private cloud (VPC): Default VPC

      { Note: If you don't have Default VPC and don't know how to create VPC you can learn from my Here and comment if any doubt. }

    • Public access: Yes

    • VPC security group (firewall): Leave default

    • Availability Zone: You can choose any

  • Database authentication: Check Password authentication

  • Monitoring: Unchecked

  • Additional configuration:

    • Initial database name: demo

    • Backup: Uncheck enable automated backups

    • Encryption: Uncheck Enable encryption

• Leave all Default and Create database

  • After sometime when Status of database modifying or Available

  • click on demo-bd -> Scroll down in Connectivity & Security

  • For future use Copy Endpoint marked as:

    

Step 2: Update VPC Default Security group as:

• Search VPC and Select it

• Scroll the left-side-bar and select the security groups

• Click on the Security group ID which has the Security group name: default

• Click on Edit inbound rules

  • Click Add rule

    • Type: MYSQL/Aurora

    • Source: Anywhere-IPv4 i.e. 0.0.0.0/0 (- If you created a new security group add this rule as inbound as well )

  • Save rules

Step 3: Work with VS Code

• Install VS Code

• Download following extensions

  • 

  • 

  • 

• Create any directory or folder on your computer

• open the folder and right click

  

• Click on Open in Terminal and type the following command to open that folder in VS Code directly

    code .
  

• Click on SQLTools symbol

  

• Also, click on Add New Connection

  

• Select MySQL and fill as:

  

• Click on TEST CONNECTION enter the password you set above while creating RDS

• You should get Successfully connected! message

  

• Now Click on SAVE CONNECTION -> CONNECT NOW

CONGRATULATIONS YOU HAVE SUCCESSFULLY CONNECTED WITH RDS

Now you can do any SQL query and run on VS Code...

Thank you for LEARNING !!!

A virtual private cloud (VPC) is a virtual network dedicated to your AWS account. It is logically isolated from other virtual networks in the AWS Cloud. You can launch AWS resources, such as Amazon EC2 instances, into your VPC.

A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between them using private IPv4 addresses or IPv6 addresses. Instances in either VPC can communicate as if they are within the same network. You can create a VPC peering connection between your VPCs or a VPC in another AWS account. The VPCs can be in different Regions (also known as an inter-Region VPC peering connection).

Pricing for a VPC peering connection

There is no charge to create a VPC peering connection. All data transfer over a VPC Peering connection within an Availability Zone (AZ) is free. Charges apply for data transfer over VPC Peering connections that cross Availability Zones and Regions.

LAB: How to create VPC peering?

Note: In this lab session we are going to create two different instances and try to connect the private IP of one instance by using another instance.

Step 1: Create a First VPC

1. Goto Your VPCs and Create vpc1:

   • Resources to create VPC only

   • Name tag - optional eg. vpc1

   • IPv4 CIDR eg. 10.0.0.0/16

     Create VPC with all other default

2. Goto Subnets and create subnet for vpc1 as:

   • VPC ID select vpc1

   • Scroll down to Subnet settings

     • Subnet name vpc1subnet

     • Availability Zone anyone your choice eg. us-east-1a

     • IPv4 CIDR block: 10.0.0.0/24

       and Create subnet

3. Goto Internet gateways and Create internet gateway as:

   • In Internet gateway setting

     • Name tag: IGvpc1

     • Create internet gateway

   • Click on the popup Attach to VPC

     • Available VPCs -> select a VPC : vpc1

       Attach internet gateway

4. Goto Route tables and create a route table for vpc1

   • Route table settings

     • Name: route_vpc1

     • VPC: Select vpc1

       Create route table

Step 2: Similarly, Create a Second VPC

1. Goto Your VPCs and Create vpc2:

   • Resources to create VPC only

   • Name tag - optional eg. vpc2

   • IPv4 CIDR eg. 194.0.0.0/16

     Create VPC with all other default

2. Goto Subnets and create subnet for vpc2 as:

   • VPC ID select vpc2

   • Scroll down to Subnet settings

     • Subnet name vpc2subnet

     • Availability Zone anyone your choice eg. us-east-1b

     • IPv4 CIDR block: 194.0.0.0/24

       and Create subnet

3. Goto Internet gateways and Create internet gateway as:

   • In Internet gateway setting

     • Name tag: IGvpc2

     • Create internet gateway

   • Click on the popup Attach to VPC

     • Available VPCs -> Select a VPC : vpc2

       Attach internet gateway

4. Goto Route tables and create a route table for vpc2

   • Route table settings

     • Name: route_vpc2

     • VPC: Select vpc2

       Create route table

Step 3: Now, Create a peering connection:

• Goto Peering connections by scrolling down on the left side of the bar

• Click on Create peering connection

• Peering connection settings

  • Name: peerVPC

  • VPC ID (Requester): Select vpc1

  • VPC ID (Accepter): Select vpc2

    Create peering connection

• Select peerVPC -> Actions -> Accept request

Step 4: Last thing to do Modify a route table:

• Goto Route tables

• Select route_vpc1

  • Click on Subnet associations -> Edit subnet associations

    • Available subnets: Select vpc1subnet and Save associations

  • Click on Routes -> Edit routes -> Add route

    Destination: 0.0.0.0/0 Targe: Internet Gateway -> (IGvpc1)

    Destination: 194.0.0.0/16 Targe: Peering Connection -> (peerVPC)

• Similarly, Select route_vpc2

  • Click on Subnet associations -> Edit subnet associations

    • Available subnets: Select vpc2subnet and Save associations

  • Click on Routes -> Edit routes -> Add route

    Destination: 0.0.0.0/0 Targe: Internet Gateway -> (IGvpc2)

    Destination: 10.0.0.0/16 Targe: Peering Connection -> (peerVPC)

Step 4: Now, Smile all VPC work was done. Next goto EC2 -> instances

1. For First Instance

   • Launch instances

   • Name: server1

   • select the existing key or create new

   • Network settings -> Edit

     • VPC: Select vpc1

     • Subnet: vpc1subnet

     • Auto-assign public IP: enable

     • Leave Create a security group checked

     • Leave all default and Launch instance

2. For Second Instance

   • Launch instances

   • Name: server2

   • select the existing key or create new

   • Network settings -> Edit

     • VPC: Select vpc2

     • Subnet: vpc2subnet

     • Auto-assign public IP: desable

     • Leave Create a security group checked

     • Add security group rule

       • Type: All traffic

       • Source type: Anywhere

         [ Note: It is not good practice to set the type All traffic just for basic understanding ]

     • Leave all default and Launch instance

Step 4: Connect the EC2 instance

• After the Status check 2/2 checks passed

• Select the EC2 instance with private IP i.e. server2 and copy private IP

• Then, Select the EC2 instance with public IP i.e. server1

• And Click on Connect at the top, again Connect

• Now, you reached this window:

• Here, perform the following commands:

    sudo su
  

    ping <private-ip-you-copied>
  

  • You get the following output CTRL+C to exit

Don't forget to terminate all the services you started...

Thanks for your time

S3 Standard

• Costly than others

• Use only when you have very critical data which was not afforded to lose

• Low latency, Fast Retrieval, and high throughput performance

• Replication object across all availability zone of any Region

• Fast Retrieval

• Highly Available: Designed for 99.99% availability over a given year

• Supports SSL for data in transit and encryption of data at rest

• S3 Lifecycle management for automatic migration of objects to other S3 Storage Classes

S3 - Intelligent Tiering

• Designed to optimize costs by automatically moving data to the most cost-effective access tier, without performance impact or operational overhead.

• Frequent, Infrequent, and Archive Instant Access tiers have the same low-latency and high-throughput performance as S3 Standard

• The Infrequent Access tier saves up to 40% on storage costs

• The Archive Instant Access tier saves up to 68% on storage costs

• Opt-in asynchronous archive capabilities for objects that become rarely accessed

• The deep Archive Access tier has the same performance as Glacier Deep Archive and saves up to 95% for rarely accessed objects

• Highly availability: 99.9% availability over a given year

• Small monthly monitoring and auto-tiering charge

• No operational overhead, no lifecycle charges, no retrieval charges, and no minimum storage duration

• Objects smaller than 128KB can be stored in S3 Intelligent Tiering but will always be charged at the Frequent Access tier rates, and are not charged the monitoring and automation charge.

• So for more cost optimization need an object size >= 128 KB

S3 - Standard IA

• Same low latency and high throughput performance of S3 Standard

• Replication across all availability zone of any Region

• Resilient against events that impact an entire Availability Zone

• Data is resilient in the event of one entire Availability Zone destruction

• Highly Available: 99.9% availability over a given year

• Supports SSL for data in transit and encryption of data at rest

• S3 Lifecycle management for automatic migration of objects to other S3 Storage Classes

• Fast Retrieval

• Less costly compared to standard

• The minimum Size of the file is 128KB to use the Standard IA storage class

• An object should be there for at least 30 days in Standard to move to Standard IA

S3 One Zone - IA

• No replication: objects in a only single Availability Zone

• Same low latency and high throughput performance of S3 Standard

• Less durable

• Less available: 99.5% availability over a given year

• Lower cost

• Less critical data are stored in this class

• Data should be there 30 days in Standard

• Supports SSL for data in transit and encryption of data at rest

• S3 Lifecycle management for automatic migration of objects to other S3 Storage Classes

S3 Glacier Instant Retrieval

• Data retrieval in milliseconds with the same performance as S3 Standard

• Replication of objects across multiple Availability Zones

• Data is resilient in the event of the destruction of one entire Availability Zone

• Designed for 99.9% data availability in a given year

• 128 KB minimum object size and Data should be there 90 days in other classes to move in Glacier

• S3 PUT API for direct uploads to S3 Glacier Instant Retrieval, and S3 Lifecycle management for automatic migration of objects

• It is a low-cost storage class

• Data Archiving

• Retrieval times are configurable from minutes to hours

• Infrequently access

S3 Glacier Flexible Retrieval

• Low-cost storage, up to 10% lower cost (than S3 Glacier Instant Retrieval)

• For archive data that is accessed 1-2 times per year and is retrieved asynchronously

• Replication of objects across multiple Availability Zones

• Data is resilient in the event of one entire Availability Zone destruction

• Supports SSL for data in transit and encryption of data at rest

• Ideal for backup and disaster recovery use cases when large sets of data occasionally need to be retrieved in minutes, without concern for costs

• Configurable retrieval times, from minutes to hours, with free bulk retrievals

• S3 PUT API for direct uploads to S3 Glacier Flexible Retrieval, and S3 Lifecycle management for automatic migration of objects

S3 Glacier Deep Archive

• Cheapest deep archival storage class designed for long-term retention of data that will be retained for 7-10 years

• Retrieval time within 12 hours

• Infrequental access

• Replication of objects across multiple Availability Zones

• Ideal alternative to magnetic tape libraries

• S3 PUT API for direct uploads to S3 Glacier Deep Archive, and S3 Lifecycle management for automatic migration of objects

S3 on Outposts

Key Features:

• S3 Object compatibility and bucket management through the S3 SDK

• Designed to durably and redundantly store data on your Outposts

• Encryption using SSE-S3 and SSE-C

• Authentication and authorization using IAM, and S3 Access Points

• Transfer data to AWS Regions using AWS DataSync

• S3 Lifecycle expiration actions

KEY Points

• All classes are highly durable i.e. 99.999999999%

• A single bucket can contain objects stored across S3 Standard, S3 Intelligent-Tiering, S3 Standard-IA, and S3 One Zone-IA

• Because S3 One Zone-IA stores data in a single AWS Availability Zone, data stored in this storage class will be lost in the event of Availability Zone destruction.

• S3 Intelligent - Tiering* - Automatic cost savings for data with unknown or changing access patterns

• S3 Standard - Infrequent Access - For long-lived but infrequently accessed data that needs millisecond access

• S3 Glacier Instant Retrieval* - For long-lived archive data accessed once a quarter with instant retrieval in milliseconds

• S3 Glacier Flexible Retrieval (Formerly S3 Glacier)**- For long-term backups and archives with retrieval option from 1 minute to 12 hours

• S3 Glacier Deep Archive*** - For long-term data archiving that is accessed once or twice a year and can be restored within 12 hours

Performance across the S3 Storage Classes

• Bucket name: must be globally unique

• AWS Region: your choice

• Object Ownership: ACLs enabled

• uncheck Block all public access

• Check I acknowledge that the current settings might result in this bucket and the objects within becoming public.

• Bucket Versioning: enable (preferred) or disable as your requirement

• Create bucket

• Click on bucket name and upload the object you want for example any image

• While uploading scroll down and open > Permission

  Predefined ACLs: Grant public-read access

  I understand the risk of granting public-read access to the specified objects.

  [ NOTE: if you forget to give ACL public access check object goto ^Action and scroll down and click make public using ACL -> Make public

• open bucket -> Check the object and Copy URL

Create EC2 instance with the following information:

• Name: my-server

• Key pair: create new key pair

  • Key pair name: mykeypair

  • Private key file format: .ppk For PuTTY user .pem For use with OpenSSH

• Allow SSH traffic
Allow HTTP traffic from the internet (note you may also enable https )

• Launch instance

Run virtual machine

• Connect EC2 using the key you downloaded either by putty or ssh

• After connected as ec2-use

    ]$ pwd
    /home/ec2-user
  

Install Apache server

]$ sudo yum install httpd -y

]$ sudo systemctl status
● ip-172-31-84-163.ec2.internal
    State: running
    Units: 281 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Thu 2023-06-01 17:42:25 UTC; 16min ago
  systemd: 252.4-1161.amzn2023.0.4

]$ cd /var/www/html
]$ pwd

]$ sudo nano index.html

• Paste the copied URL of the object as:

<img src="https://my-uniue-bucket-1.s3.amazonaws.com/Shared_Responsibility_Model_V2.59d1eccec334b366627e9295b304202faf7b899b.jpg"/>

]$ sudo systemctl start httpd
]$ sudo systemctl status httpd
● httpd.service - The Apache HTTP Server
     Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; preset: disabled)
     Active: active (running) since Thu 2023-06-01 18:08:55 UTC; 17s ago
       Docs: man:httpd.service(8)
   Main PID: 26020 (httpd)

Now you can access your S3 object using the public IP of EC2 instance

....../ THANK YOU FOR YOUR TIME \.....

• A Virtual Private Gateway (VPC) is like a data center but in the cloud. Its logically isolated from other virtual networks from which you can spin up and launch your AWS resources within minutes.

• Private Internet Protocol (IP) addresses are how resources within the VPC communicate with each other. An instance needs a public IP address for it to communicate outside the VPC. The VPC will need networking resources such as an Internet Gateway (IGW) and a route table in order for the instance to reach the Internet.

• An Internet Gateway (IGW) is what makes it possible for the VPC to have Internet connectivity. It has two jobs: perform network address translation (NAT) and be the target to route traffic to the internet for the VPC. An IGW's route on a route table is always 0.0.0.0/0.

• A subnet is a range of IP addresses within your VPC.

• A route table contains routes for your subnet and directs traffic using the rules defined within the route table. You associate the route table to a subnet. If an IGW was on a route table, the destination would be 0.0.0.0/0 and the target would be IGW.

• Security groups and Network Access Control Lists (NACLs) work as the firewall within your VPC. Security groups work at the instance level and are stateful, which means they block everything by default. NACLs work at the subnet level and are stateless, which means they do not block everything by default.

Configuring Amazon VPC using the AWS Management console:

Step 1: Open the AWS account, search, and click VPC

click again on VPC

Step 2: Click on VPC only, give the name of your choice, and change the required IPv4 CIDR as needed, then leave all other things to default, scroll down, and click Create VPC:

Step 3: After the above interface click on Subnets as shown and again click on Create subnet

Step 4: Select the VPC that we created above

Scroll down and give the Subnet name: private subnet or anything you like which going to be our private subnet, also select any availability zone of that region and specify the IPv4 CIDR block (eg. 10.0.0.0/24)according to your needs.

Also, repeat for a public subnet with a Subnet name: public subnet or anything you like which going to be our public subnet. Also select any availability zone of that region and specify the IPv4 CIDR block (eg. 10.0.1.0/24)according to your needs.

Step 5: After creating two subnets we have to create two route tables so, click on Route tables and then Create route table

Step 6: Give any name you like and select VPC which we created above and then Create route table

For simplicity give names public_route_table and private_route_table and create two route tables.

Step 7: Now click on Internet gateways and Create Internet gateway as:

specify the gateway name as you like and click on Create internet gateway

Step 8: Then click on Attach to VPC and attach that you created above as:

Step 9: Also we have to create NAT as:

1. select NAT gateways and create NAT gateway

1. Give a name eg. my-NAT and select a subnet that needs to be public.

   

   1. Then click on Allocate Elastic IP and Create NAT gateway

Step 10: Add route to route table and associate subnet to the route table

1. Goto route tables and select Route table ID of public_route_table

   

2. Click on Routes -> Edit routes

   

3. Click on [Add route] -> select 0.0.0.0/0 -> Click in the Target section and select Internet Gateway that we created since you are targeting any traffic that needs to go to the internet to the IGW.

1. Save changes -> click on Subnet associations -> Edit subnet associations

   

2. select the public subnet for the public route table and save associations

   

3. Go back and select Route table ID of private_route_table

   

4. Routes -> Edit routes

   

5. Click on Add route -> select 0.0.0.0/0 -> select NAT Gateway -> Save changes

   

6. Goto Edit subnet associations and select private subnet for private route table -> save associations.

   

Step 11: Now create two EC2 instances, one for the public subnet and another for the private.

1. Search EC2 and select instances -> Launch instance

   • Name: myPublic

   • Create key pair (give any name and select pem for Linux user and ppk for putty user)

   • Network setting -> Edit

   • VPC: select that we created above

   • subnet: public subnet since it is public instance

   • Auto-assign public IP: enable

   • *Leave all default or you can add as other thing as required.

2. Again Launch instance for private subnet

   • Name: myPrivate

   • Select same key pair (if same key selected convert ppk file to pem if putty used) or create new key (give any name and select pem)

   • Network setting -> Edit

   • VPC: select that we created above

   • subnet: private subnet since it is private instance

   • Auto-assign public IP: disable

   • *Leave all default or you can add other things as required.

Step 12: Connect to the private instance using public instance

1. Connect public instance using a key that we created.

2. create new file nano new.pem and paste content of pem file that we downloaded (or converted from ppk file)

3. Give permission as

    chmod 400 new.pem
   

4. Connect to private instance from public instance

    ssh -i new.pem ec2-user@<private-ip-of-myPrivate-instance>
   

   Now check ping google.com to confirm private instance connected with internet or not

Benefits of AWS-Restart

• Access free AWS cloud skills training

• Build skills aligned with AWS certification

• Connect with employers and launch your career

• and many more

AWS-re/start Course Agenda:

• Introduction to Cloud Foundation

• Linux

• Networking

• Security

• Python Programming

• Databases

• About AWS services

• Evaluation and Exam preparation

  

Let's Go!!!

Launch your career with a unique IDEA.

for more information regarding cloud and AWS, you can visit

• https://aws.amazon.com/

• https://docs.aws.amazon.com/

[ copyright: AWS ]