AWS organization : is used create a new aws account from an existing aws account using root user.

Both accounts have separate billing access.

Assume role : The permission policy is assigned to a role , and the role is assigned to a user , (i.e test-
user assumes the role).

IAMpolicy : Permission policy governs the accessibility of resource.

A roles accessibility of resources and scope or privilages etc is governed by the policies attached to it.
IAM role : this role will have full access to the S3 bucket

Step1: create a test user and assign credentials and login and verify

Step2: created a role and assign delivered awsfullaccessS3 policy.

Step3: assign the role to the test user using create “inline policy”

https://661357102560.signin.aws.amazon.com/console

test-user

Fg%K6X)*

"sts:AssumeRole"

Arn of the role : arn:aws:iam::661357102560:role/test-b49-role

Refresh the page

And assume the new role

AWS how to setup VPC, Public, Private Subnet, NAT, Internet Gateway, Route Table?
What is Bastion Host and why it is so important? - Step by Step tutorial (Part-6)

A bastion host is a special-purpose server or an instance to

provide access to a private network from an external network,
such as the Internet.

AWS User Data Tutorial - Step by Step (Part-7

#!/bin/bash
AWS ALB (Application Load Balancer) - Step By Step Tutorial (Part -9)
A load balancer serves as the single point of contact for clients. The load balancer distributes
incoming application traffic across multiple targets
So we create Target groups.

Each target group is used to route requests to one or more registered targets

Logical grouping of EC2 machines

Elastic Load Balancing automatically distributes your incoming traffic

across multiple targets, such as EC2 instances, containers, and IP
addresses, in one or more Availability Zones. It monitors the health of its
registered targets, and routes traffic only to the healthy targets. Elastic
Load Balancing scales your load balancer as your incoming traffic
changes over time. It can automatically scale to the vast majority of
workloads.

#!/bin/bash
yes | sudo apt update
yes | sudo apt install apache?
echo "<h1>Server Details</h1><p><strong>Hostname:</strong> $
(hostname)
</p><p><strong>IP Address:</strong> $(hostname -I | cut-d" “-
f1 )</p>">
/var/www/html/index.html
sudo systemctl restart apach2

AWS EC2 Auto Scaling : Step By Step Tutorial ( Part - 10)

Amazon EC2 Auto Scaling helps you maintain application
availability and lets you automatically add or remove EC2
instances using scaling policies that you define.

Amazon EC2 Auto Scaling helps you ensure that you have the
correct number of Amazon EC2 instances available to handle the
load for your application. You create collections of EC2
instances, called Auto Scaling groups. You can specify the
minimum number of instances in each Auto Scaling group, and
Amazon EC2 Auto Scaling ensures that your group never goes
below this size. You can specify the maximum number of
instances in each Auto Scaling group, and Amazon EC2 Auto
Scaling ensures that your group never goes above this size. If
you specify the desired capacity, either when you create the
group or at any time thereafter, Amazon EC2 Auto Scaling
ensures that your group has this many instances. If you
specify scaling policies, then Amazon EC2 Auto Scaling can
launch or terminate instances as demand on your application
increases or decreases.

Create Target group(empty) after VPC,subnets,routeTab,SG

Create Load balancer and attach TG
Create Auto Scaling Group.

Create Target group(empty) after VPC,subnets,routeTab,SG

Ec2
Not associated with LB
2)Now create a Load Balancer and point to TargetGroup.

And attach TG
3) Create Auto Scaling Group.
Use launch Template to create EC2 instance

Check the health under auto scaling

Network load balancer 1:55

Network load balancing and application load balancing both

handle traffic requests. But they process and direct those
requests with different levels of speed and efficiency.
2:30 diff between ALB and NLB