
## Table of Contents

1. [Introduction](#introduction)
2. [SSH into EC2 Instance](#ssh-into-ec2-instance)
3. [Retrieve Metadata](#retrieve-metadata)
4. [Conclusion](#conclusion)

## Introduction

This blog covers a few useful commands to retrieve metadata from an EC2 instance. EC2 instance metadata provides information about the running instance, such as hostname, IP address, and user data.

## SSH into EC2 Instance

To retrieve EC2 instance metadata, first SSH into the EC2 instance and then run the
following commands.

**Run with root privileges**

```
sudo su
```

## Retrieve Metadata

**List all the metadata**

```
curl http://169.254.169.254/latest/meta-data
```

**Get EC2's hostname**

```
curl http://169.254.169.254/latest/meta-data/local-hostname
```

**Get EC2's user data**

```
curl http://169.254.169.254/latest/user-data
```

## Conclusion

The EC2 instance metadata endpoint (`169.254.169.254`) provides a convenient way to retrieve information about your running instance without needing external tools. This is useful for automation scripts, configuration management, and debugging.


A few commands to retrieve EC2 instance metadata, including hostname and user data.

How to Retrieve EC2 Instance Meta Information


#### Table of Contents

1. Create Flow logs
2. Set up IAM role for flow logs
3. Policy Document

## Create Flow logs

Select the VPC to want to use flow logs, click action then click
**Create flow log**.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/xnbezqoi0trexcc1tokk)

Setup Destination log group

If you choose to send to CloudWatch logs, you'll have to set up a destination
log group. Go to CloudWatch and choose
**Log groups**.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/cys5v8t4cknnyzxtoyyx)

### Set up IAM role for flow logs

Click set up permission on the create VPC flow logs page, this UI will only
show on old UI, which will create the following policy to enable flow logs to
read and write to cloud watch.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/vqxucobcf6pu3jmnmekx)

### Policy Document

```
{
  "Statement": [
    {
      "Action": [
        "logs:CreateLogGroup",
        "logs:CreateLogStream",
        "logs:DescribeLogGroups",
        "logs:DescribeLogStreams",
        "logs:PutLogEvents"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ]
}
```

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/bbm4ihsi8xa6ptjawos5)

After setup flow logs, when you hit the EC2 using the VPC, you should see the
following logs from log groups.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/lcbrau7bqjp002gar9sx)


This blog shows how to set up VPC flow logs.

Use VPC Flow Logs


## Table of Contents

- [Introduction](#introduction)
- [Prerequisites](#prerequisites)
- [Create AWS Classic Load Balancer](#create-aws-classic-load-balancer)
  - [Choose Classic Load Balancer](#choose-classic-load-balancer)
  - [Define Load Balancer](#define-load-balancer)
  - [Assign Security Groups](#assign-security-groups)
  - [Configure Health Check](#configure-health-check)
  - [Add EC2 Instances](#add-ec2-instances)
  - [Done with Creating Classic Load Balancer](#done-with-creating-classic-load-balancer)
- [Conclusion](#conclusion)

## Introduction

This blog shows how to use an AWS Classic Load Balancer from scratch. First, we need to do some preparation. At the end of the setup, you'll have 2 EC2 instances with a public subnet behind the load balancer.

## Prerequisites

The following is a list of preparations before setting up the Classic Load Balancer:

- Create a VPC
- Create 2 Public Subnets
- Create an Internet Gateway
- Create a Route Table
- Create 2 EC2 Instances

## Create AWS Classic Load Balancer

### Choose Classic Load Balancer

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/nzi3mrud96ng7c6laxrw)

### Define Load Balancer

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/uij0yvcjh7ihfyde8sts)

### Assign Security Groups

### Configure Health Check

### Add EC2 Instances

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/twmpbnlpciqrijk1ttsz)

### Done with Creating Classic Load Balancer

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/oru2e9ii3nnud24lhocl)

## Conclusion

By following these steps, you can set up an AWS Classic Load Balancer to distribute traffic across multiple EC2 instances. Make sure to properly configure health checks and security groups to ensure reliable and secure load balancing.


This blog shows how to set up an AWS Classic Load Balancer from scratch. At the end of the setup, you'll have 2 EC2 instances behind a load balancer in a public subnet.

Create AWS Classic Load Balancer


## Table of Contents

1. [Introduction](#introduction)
2. [How to Block Traffic from a Specific IP Address](#how-to-block-traffic-from-a-specific-ip-address)
3. [Find the Network ACL from EC2](#find-the-network-acl-from-ec2)
4. [Find the IP Address](#find-the-ip-address)
5. [Create a New Rule to Block Traffic](#create-a-new-rule-to-block-traffic)
6. [Conclusion](#conclusion)

## Introduction

This blog shows a few ways to use AWS Network ACLs to block traffic to your
site.

## How to Block Traffic from a Specific IP Address

AWS has a few ways to block specific targets from accessing your site — for example,
Network ACL or WAF. Let's assume the following scenario: you have a website
running on an EC2 instance as a web server, and there's one IP address you
noticed that you want to block. You can use the Network ACL as
follows.

### Find the Network ACL from EC2

First, you need to find the Network ACL from your EC2 instance. You can click
**Subnet** from EC2, then click **Network ACL**.

### Find the IP Address

Next, you need to have an IP address. If you want to test with your own machine's
IPv4 address, you can either Google
**what's my IP address** or go to
https://whatismyipaddress.com/
to check your public IP address.

### Create a New Rule to Block Traffic

Create a new inbound rule as follows:

- Rule#: a number smaller than the allow traffic rule.

- Type: ALL Traffic

- Protocol: ALL

- Port Range: ALL

- Source: {Your IP address}/32

- Allow/Deny: Deny

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/ydnzxu0ey3zlnfzabuld)

## Conclusion

Now you should be able to block a specific IP address from accessing your EC2 instance using AWS Network ACLs. This is a quick and effective way to deny unwanted traffic at the network level.


This blog shows a few ways to use AWS Network ACLs to block traffic to your site.

Blocking Traffic from Specific IP Address with AWS Network ACL


## Table of Contents

1. [Introduction](#introduction)
2. [Create a VPC](#create-a-vpc)
3. [Create 2 Subnets](#create-2-subnets)
4. [Create an Internet Gateway](#create-an-internet-gateway)
5. [Create NAT Gateway](#create-nat-gateway)
6. [Create and Update Route Tables](#create-and-update-route-tables)
7. [Create Public and Private EC2 Instances](#create-public-and-private-ec2-instances)
8. [SSH to Public EC2](#ssh-to-public-ec2)
9. [SSH to Private EC2](#ssh-to-private-ec2)
10. [Conclusion](#conclusion)

## Introduction

This blog shows how to create a VPC from scratch:

1. Create VPC
2. Create 2 Subnets — one for the public subnet and another for the private subnet
3. Create Internet Gateway
4. Create a Route Table
5. Create 2 EC2 Instances — one public instance and one private instance
6. Set up NAT Gateway for the private EC2 instance

## Create a VPC

Go to VPC and click create VPC, then enter the information to create the VPC.

- Enter any name for the name field

- IPv4 CIDR, enter IPv4 range as `10.0.0.0/16`

- Choose `Amazon provided IPv6 CIDR block`

- Tenancy, choose Default if you wish to use the default tenancy

After creating the VPC, AWS will generate the following default services:

- Default route table

- Network ACL

- Default Security Group

## Create 2 Subnets

Create a public subnet. Click the Subnets link, and click Create subnet.

- Name, enter any meaningful name.

- **VPC**, choose the VPC just created

- **Availability Zone**, choose the AZ for this subnet

- **IPv4 CIDR block**, enter **10.0.1.0/24** as IPv4
  CIDR block

- **Modify auto-assign IP settings**, enable auto-assign IP
  address for the public subnet

Create a private subnet by clicking the **Create subnet** button.

- Name, enter any meaningful name.

- **VPC**, choose the VPC just created

- **Availability Zone**, choose the AZ for this subnet

- **IPv4 CIDR block**, enter **10.0.2.0/24** as IPv4
  CIDR block

- **Modify auto-assign IP settings**, the private subnet doesn't need
  to enable a public IP address

## Create an Internet Gateway

Create an Internet gateway so the public subnet is able to access the Internet.
Click **Internet Gateways** and click the Create Internet
gateway button.

- Name, enter any value for this Internet gateway.

- Attach this Internet gateway to the **VPC** just created

## Create NAT Gateway

Create a NAT Gateway so the private EC2 will be able to connect to the Internet and
download software if needed. Click the
**Create NAT Gateway** button.

- Click **Create NAT Gateway** button

- **Subnet**, choose the public subnet

- Click allocate the IP address

- Click **Edit route table**

- Click **Add route**

- **Destination**, enter **0.0.0.0/0**

- **Target**, choose the NAT Gateway just created

## Create and Update Route Tables

Use the default route table as the main route table, and associate it with the
private subnet.

- Choose the main route table and click
  **Subnet Associations**

- Choose the private subnet

**Create a route table** to use as a public route.

- Name, enter any name for this new route table

- Choose the VPC created earlier

- Click subnet associations and choose the public subnet

- **Click Edit routes** and click **Add route**

- Destination, enter `0.0.0.0/0` for IPv4 address

- Target, choose the **Internet gateway created earlier**

That's all for setting up public and private subnets for the VPC. Now we'll need to
create EC2 instances and attach them to this VPC.

## Create Public and Private EC2 Instances

Let's create the public EC2 instance first. Go to EC2 and click instance to
create a new EC2 instance.

- Enter configure instance details

- **Network**, choose the custom VPC just created

- **Subnet**, choose the public subnet created earlier

- Leave the rest as default settings and create a new instance

Let's create the private EC2 instance. Go to EC2 and click instance to create a
new EC2 instance.

- Enter configure instance details

- **Network**, choose the custom VPC just created

- **Subnet**, choose the private subnet created earlier

- Leave the rest as default settings and create a new instance

## SSH to Public EC2

Test the EC2 by SSHing into the public EC2 instance and downloading software from the
Internet. The following are examples of how to SSH into EC2 from macOS.

- cd to the location that has the **private key**, something
  that looks like **mykey.pem**.

- `chmod 400 {your_private_key.pem}`

- SSH into EC2 by
  `ssh ec2-user@{ec2 public IP address} -i {your_private_key.pem}`

- Run `sudo yum update` to download software

- If you are able to download the software, then this EC2 can connect to the
  Internet

## SSH to Private EC2

Test the EC2 by SSHing into the private EC2 instance and downloading software from
the Internet. The following is an example of how to SSH into EC2 from macOS.

- SSH into the public EC2 instance

- Download the private key

- SSH into the private EC2 by using the private IP

- `chmod 400 {your_private_key.pem}`

## Conclusion

In this blog, we walked through how to create an AWS VPC from scratch with public and private subnets. We set up an Internet gateway for public access, a NAT gateway for private subnet Internet access, configured route tables, and created EC2 instances in both subnets. With this setup, you have a secure network architecture where public-facing resources are in the public subnet and internal resources are isolated in the private subnet.


This blog shows how to create an AWS VPC from scratch with public and private subnets, internet gateway, NAT gateway, and EC2 instances.

How to Create VPC with Public and Private Subnet


## Table of Contents

1. [Introduction](#introduction)
2. [Setting Up AWS Organizations](#setting-up-aws-organizations)
3. [Inviting Child Accounts](#inviting-child-accounts)
4. [Accepting Invitations](#accepting-invitations)
5. [Organizing Accounts](#organizing-accounts)
6. [Conclusion](#conclusion)

## Introduction

If you just have one AWS account, you can use that account for billing and development. However, if you have multiple AWS accounts, it is hard to manage each account's billing. AWS provides a way to consolidate billing using **AWS Organizations**.

Assume that you have the following different AWS accounts:

  - AWS Account - Use for Development
  - AWS Account - Use for QA
  - AWS Account - Use for Production

For consolidated billing, we'll set up AWS Organizations as follows:

  - AWS Account - Use as Root Account, and billing only
    - AWS Account - Use for Development
    - AWS Account - Use for QA
    - AWS Account - Use for Production

## Setting Up AWS Organizations

Go to the root account (or create a new AWS account to use as the root account for billing). Then go to Services and click **AWS Organizations**, then click **Create Organization**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/fx4wrucodcc9qmsrlsjp)

Click **Create organization**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/sacbjxf56dldml1aevur)

Now the AWS Organization has been created, and you should receive an email for confirmation.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/mkkalhuiehf7nmmchmp2)

After confirming the account, it should appear as follows:

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/nx81uehtkcobj8hprnmt)

## Inviting Child Accounts

Now we will send an invite to all other accounts from the root account.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/gsbowux0utsndhw9kj1h)

After each account receives an invitation email, you should see a list of accounts on the following page:

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/jxjtc2aawmdremqiwgry)

## Accepting Invitations

On each child account, accept the invitation.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/o8vp21uechtwobm4cdzx)

Confirm that you'll join the organization.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/oy0orqv0ogezsazkozqs)

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/o0couoyrhyqsts5q0y8e)

After each account accepts the invitation, this is how the root account's organization view looks:

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/sf0u2mspofn7pmxkn18d)

## Organizing Accounts

You can also organize accounts by renaming or moving them. For instance, you can create dev and marketing folders for each team and assign accounts to each folder.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/vkikjqj2gml0atc9dg5u)

## Conclusion

AWS Organizations provides a convenient way to consolidate billing across multiple AWS accounts. By setting up a root account and inviting child accounts, you can manage billing centrally and organize accounts by team or environment.


If you have multiple AWS accounts, it is hard to manage each account's billing. AWS Organizations allows you to consolidate billing across all your accounts.

How to Create AWS Organization for Consolidated Billing


## Table of Contents

1. [Introduction](#introduction)
2. [Setup Custom VPC](#setup-custom-vpc)
3. [Setup EC2](#setup-ec2)
4. [Create Target Groups](#create-target-groups)
5. [Create Registered Targets](#create-registered-targets)
6. [Create Application Load Balancer](#create-application-load-balancer)
7. [Conclusion](#conclusion)

## Introduction

This blog will show how to create an AWS Application Load Balancer with custom
VPC's EC2 instances.

## Setup Custom VPC

### Create VPC

Go to VPC and click create VPC. Enter the VPC fields as in the example below.

- Name tag: enter your VPC name

- IPv4 CIDR block: enter your CIDR block IP range

- IPv6 CIDR block: choose IPv6

- Network Border Group

- Tenancy: Default (you can choose if you want single-tenant, dedicated
  hardware or not)

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/nuz1eaznan55ydjdddu7)

### Create Subnet

We'll need 2 subnets to create the Application Load Balancer.

- Name tag: enter any name

- VPC: choose the VPC just created

- Availability Zone: choose the availability zone

- IPv4 CIDR block: 172.0.1.0/24

- IPv6 CIDR block: don't assign IPv6 (not needed for this blog)

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80/aggjgcq8l3r1bwcph1tx)

Create the second subnet. For creating an Application Load Balancer, you'll need
at least 2 subnets.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/ghlpqgdiuqnatp4ny9ay)

Set auto-assign IP so EC2 instances will get a public IP address.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/xg8k03u4q3dgungcdoxn)

### Create Internet Gateway

Create an Internet gateway and attach it to the custom VPC.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/i6iajudvzm9jz30wo1fk)

### Setup Route Table

Create a route table for the subnet.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/dzm3594cl2omwejqms3h)

Associate the subnet to the route table.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/vgcmhjrsooaksk2t1ln3)

Set the route table to use the Internet gateway for internet access. Enter the routes
as follows:

Destination: 0.0.0.0/0 (for IPv4 access)

Target: choose the Internet gateway

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/krwph6pibjm8zbxyg6xn)

Now the VPC setup is done. We can use this custom VPC to create our EC2 instances.

## Setup EC2

We'll set up EC2 with simple PHP code. Let's leave everything as default
and create 2 EC2 instances.

- Choose AMI (for example, choose Amazon AMI)

- Choose General Purpose: t2.micro

- Configure Instance Details

      - Network: choose the VPC just created

      - Subnet: choose the subnet just created

      - Leave everything as default

      - Put the following in the User Data field. This will start a simple PHP

  site.

      - ```

  #!/bin/bash
  yum update -y
  yum install httpd -y
  chkconfig httpd on
  service httpd start
  cd /var/www/html
  echo "hi, server-01" > index.html

```



  Configure Security Group

    - Add port 80 so it will be accessible from the browser.




Now, let's create another EC2 instance. Set up everything the same as the first one,
  except the User Data — change it to server-02 as follows:


```

#!/bin/bash
yum update -y
yum install httpd -y
chkconfig httpd on
service httpd start
cd /var/www/html
echo "hi, server-02" > index.html

```


## Create Target Groups


Let's create a target group for the Application Load Balancer. This blog only
  covers setting up HTTP.


  - Target type: choose Instances

  - Enter any name for the target group name

  - Protocol: HTTP - 80

  - Choose the VPC

  - Health checks

    - Enter the path

  - Choose available instances

  - Click Create Target Group

  - Creating a target group is done and associated with a list of instances.

## Create Registered Targets


Click registered targets and add EC2 instances by choosing 2 EC2 instances and
  clicking "Include as pending."


![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/p18kpugbrz9g2tyeekvt)


## Create Application Load Balancer


  - Click Create Load Balancer

  - Choose Application Load Balancer

  - Enter a name

  - Use default HTTP - 80

  - Choose VPC

  - Choose subnets (you'll need at least 2 subnets here)

  - Choose Security Groups

  - Configure Routing (select the target group created earlier)

  - Now the Load Balancer is being created

  - You should be able to see the application load balance between 2 instances


After the Application Load Balancer becomes **active**, copy the DNS
  name to the browser. You should see the site alternate between the two
  servers. This is how you can simply set up an Application Load Balancer
  with AWS.


![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/rja3y1cqjllbypjmetsl)

## Conclusion

In this blog, we walked through creating a custom VPC with subnets, Internet gateway, and route tables. We then set up two EC2 instances and configured an Application Load Balancer to distribute traffic between them. This setup provides basic high availability and load distribution for your web application.


This blog will show how to create an AWS Application Load Balancer with custom VPC's EC2 instances.

How to Setup AWS Application Load Balancer


## Table of Contents

1. [Introduction](#introduction)
2. [Steps to Provision an EC2 Instance](#steps-to-provision-an-ec2-instance)
3. [Conclusion](#conclusion)

## Introduction

This blog shows how to create an EC2 instance on AWS step by step.

## Steps to Provision an EC2 Instance

### Launch Instance

  - Go to Compute and click EC2

  - Click Launch Instance at EC2

  - Choose Amazon Linux 2 AMI

  - Choose Free Tier, t2.micro

### Configure Instance Details

  - Launch with default VPC

  - Enable termination protection

  - Tenancy: use shared for now

  - Enable hibernation as an additional stop behavior

### Add Storage

At Add Storage, use the default root volume.

  - Check "Delete on Termination" — when deleting the EC2 instance, this root device will also be deleted

  - Make it encrypted during the creation of the EC2 instance

### Add Tags

  - Add tags so it is easy to differentiate instances

### Configure Security Group

  - Assume you just need SSH

  - So SSH, TCP, Port 22, 0.0.0.0/0

### Review and Launch

  - Click Review and Launch

  - Create a new private key pair

  - Click Launch Instance — you should be able to see the instance launching

## Conclusion

By following the steps above, you can provision an AWS EC2 instance with the Free Tier t2.micro option. Make sure to configure security groups, enable termination protection, and create a key pair for SSH access. You can further customize the instance settings based on your specific requirements.


This blog shows how to create an EC2 instance on AWS step by step.

Provision AWS EC2 Instance


## Table of Contents

- [Introduction](#introduction)
- [Prerequisites](#prerequisites)
- [Connect to EC2 from macOS](#connect-to-ec2-from-macos)
- [Conclusion](#conclusion)

## Introduction

This blog shows how to connect to an AWS Linux or Ubuntu EC2 instance from macOS.

## Prerequisites

First, make sure you have an EC2 instance and the following two things:

- The private key pair file available on your Mac (it should be something like `*.pem`)
- The AWS EC2 instance's public IP address

## Connect to EC2 from macOS

On your Mac, open the terminal window and navigate to the location that has the `*.pem` file.

Type the following command to set the correct permissions:

`chmod 400 {your.pem}`

It should look like this:

`chmod 400 my-test.pem`

The following is for connecting to Amazon Linux:

`ssh ec2-user@{EC2 Public IP address} -i {YourPem.pem}`

It should look like this:

`ssh ec2-user@123.123.123.123 -i my-test.pem`

The following is for connecting to Ubuntu:

`ssh ubuntu@{EC2 Public IP address} -i {YourPem.pem}`

`ssh ubuntu@123.123.123.123 -i my-test.pem`

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/za51itle9uwuy4ai3sae)

## Conclusion

Connecting to an EC2 instance from macOS is straightforward. Set the correct permissions on your `.pem` file using `chmod 400`, then use the `ssh` command with the appropriate username (`ec2-user` for Amazon Linux or `ubuntu` for Ubuntu) along with the instance's public IP address.


This blog shows how to connect to an AWS Linux or Ubuntu EC2 instance from macOS.

SSH to EC2 Instance from Mac OS


## Table of Contents

1. [Introduction](#introduction)
2. [Create the Target S3 Bucket](#create-the-target-s3-bucket)
3. [Configure S3 Replication](#configure-s3-replication)
4. [Review and Save](#review-and-save)
5. [Important Notes](#important-notes)
6. [Conclusion](#conclusion)

## Introduction

This blog shows how to use S3 replication within your current AWS account.

Before starting S3 cross-region or same-region replication, make sure the
target S3 bucket is ready. If you don't have a bucket, create a new bucket as
described below.

You can use S3 replication for many purposes. For example, you can
replicate S3 objects to different regions with different storage classes.

## Create the Target S3 Bucket

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/wv5fkrmd2ojfmzbvor4x)

Make sure S3 versioning is enabled because S3 replication requires versioning.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/uxeiboza2uspgiui7wux)

Create the S3 bucket.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/dwi88cxbsolhhxbk9wwd)

## Configure S3 Replication

For demo purposes, I have created an S3 bucket containing one file as
shown below.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/xswn1ibiakbyxlzsimfj)

Click **Management** and click the replication option.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/iv0rfnxe5zzpeuhh6zne)

Choose the **Replication rule** and select the source
bucket. Also, choose the target region.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/ojz7t3q85xb0ypq0yczt)

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/fiyyqmyz2ytsq4rfgr3i)

Create an **IAM role**.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/ompodwlkpj5njrugow0u)

## Review and Save

Review the replication rule. If everything looks good, click
**Save**.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/mthxsimjjmtvjh07oui9)

You should see the "Replication configuration updated successfully" message. Now you are ready to replicate S3.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/a9emxi7ub5ktlgrxl3ra)

## Important Notes

A few things to notice: deleting from the source bucket won't affect the
target bucket. However, adding to the source bucket will replicate to the
target bucket.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/gghjp7boeym6pkkvgyxn)

## Conclusion

In this blog, we walked through setting up S3 cross-region replication within an AWS account. Key points to remember are: ensure versioning is enabled on both buckets, create the appropriate IAM role, and note that deletions are not replicated by default. S3 replication is useful for disaster recovery, compliance, and reducing latency for geographically distributed users.


This blog shows how to use S3 replication within your current AWS account for cross-region or same-region replication.

How to do S3 Cross Region Replication


## Table of Contents

- [Introduction](#introduction)
- [Set Up the Connection](#set-up-the-connection)
- [Conclusion](#conclusion)

## Introduction

This blog shows how to SSH to an EC2 instance via the Chrome Extension Secure Shell.

## Set Up the Connection

- First, you need to download the Chrome extension, Secure Shell App.

- If it's the first time, click "Connection Dialog" to set up the connection.

- Enter the public IP address from EC2.

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/wu4tgddlxhbrrdqcqri4)

- After connecting via SSH, this is how it looks.

## Conclusion

The Secure Shell Chrome extension provides a quick and easy way to SSH into your EC2 instances directly from the browser, without needing a separate terminal application.


This blog shows how to SSH to an EC2 instance via the Chrome Extension Secure Shell.

SSH to EC2 Instance via Chrome Extension Secure Shell


## Table of Contents

- [Introduction](#introduction)
- [Connect Using EC2 Instance Connect](#connect-using-ec2-instance-connect)
- [References](#references)
- [Conclusion](#conclusion)

## Introduction

This blog shows how to use AWS EC2 Instance Connect to SSH to an AWS EC2 instance. Unlike using Mac or Windows where you have to download private keys or use PuTTY to SSH to the EC2 instance, this is a much easier way to connect to an EC2 instance by simply clicking a button in AWS.

## Connect Using EC2 Instance Connect

- Right-click the instance and select "Connect".

- Choose "EC2 Instance Connect (browser-based SSH connection)".

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/kq1wssqzffs9r59yr4d1)

- Click "Connect".

![](http://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/x2kkllsyyyn7ngvhdkkh)

## References

- Connecting to your Linux instance using EC2 Instance Connect

## Conclusion

EC2 Instance Connect provides the simplest way to SSH into your EC2 instances. It eliminates the need for managing private key files or installing third-party tools — just click "Connect" in the AWS Console and you're in.


This blog shows how to use AWS EC2 Instance Connect to SSH to an AWS EC2 instance directly from the browser.

SSH to EC2 Instance via EC2 Instance Connect


## Table of Contents

1. [Introduction](#introduction)
2. [Create a Billing Alarm](#create-a-billing-alarm)
3. [Set Up Notification](#set-up-notification)
4. [Confirm Subscription](#confirm-subscription)
5. [Conclusion](#conclusion)

## Introduction

You'll want to set up a billing alarm with AWS when you want to get notified
if the amount reaches a certain limit. The following example shows how to
get an email from AWS SNS when the amount exceeds 5 dollars.

## Create a Billing Alarm

First, let's go to the page to get started.

- Go to **CloudWatch**

- Click **Billing**

- Click **Create Alarm**

- You will land on the **Specify metric and condition page**

- Enter the condition and account. The following example sets an
  alert when the amount is more than $5. Click
  **Next**.

## Set Up Notification

Once you enter the amount, we'll need to create a topic and email. Enter the
**Email** where you want to get notified when the AWS amount exceeds $5.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/c3vsvhyxsh7mxmb8rtpz)

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/nxursqqcmwwqfzqhvjhj)

Create a unique name for this alarm.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/ebbrodsyvj4i4x6sgsdg)

After reviewing, click **Create alarm**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/k7odd5smmyetumrz2ryd)

## Confirm Subscription

At this point, AWS sends a confirmation email to the address you entered earlier.

Go to your email inbox and click to confirm the subscription.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/smzp1ag0irltsgwfxf7f)

Click **Confirm subscription**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/qlthztf45kh3cqhn1w8q)

Now you can see everything is set up. You should get an email when your AWS
spending exceeds $5.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/aueuvfcsy2ezr69nhxha)

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/fei9oizagrtdcvu8y0uw)

## Conclusion

Setting up a billing alarm in AWS is a simple but important step to avoid unexpected charges. By using CloudWatch and SNS, you can receive email notifications when your AWS spending exceeds your defined threshold.

## Reference Links

- Creating a Billing Alarm to Monitor Your Estimated AWS Charges

- AWS Free Tier


This blog shows how to set up billing alarms in AWS to get notified when your spending reaches a certain threshold.

How to Set Up Billing Alarm in AWS


## Table of Contents

- [Introduction](#introduction)
- [Create a Role in the Root Account](#create-a-role-in-the-root-account)
- [Add a User in the Child Account](#add-a-user-in-the-child-account)
- [Switch Roles to Access the Shared Bucket](#switch-roles-to-access-the-shared-bucket)
- [Conclusion](#conclusion)

## Introduction

This blog shows how to share an S3 bucket across different AWS accounts.

First, you'll need to set up multiple AWS accounts by using **AWS Organization**. You can reference this blog to see how to create an AWS Organization.

Once you have set up **AWS Organization**, make a note of the **AWS account ID** that has the S3 bucket you want to share with another AWS account. You'll need it later.

## Create a Role in the Root Account

Go to the root account's **IAM**, click **Roles** to create a new role.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/vcikmqhaucnd6fmw3jlt)

Enter the **AWS account ID**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/c05iw7oasnungrlsv2m4)

Choose the **AmazonS3FullAccess** role.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/wkww2nrb1qthiuyimbny)

Finish creating the role.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/ahkrpkqbp6xfpkccabpk)

## Add a User in the Child Account

After finishing creating the role in the root account, we'll need to go to the child account to add a user.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/rvwsqdptfjuiu7deykwe)

Add a user in the child account.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/oolohttcqpfjvc1qeolh)

Add a new role to the user, and add the user to a group by creating a new group.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/lyvq0tp7t2lmyl11muck)

Add **AdministratorAccess** when creating the new group.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/of937zlou02x9cl0dxnu)

Successfully created a new user.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/drmyjy1vef7h1hdrfmv4)

New admin group with **AdministratorAccess**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/wwwbkb03eacrystpufyd)

## Switch Roles to Access the Shared Bucket

After successfully creating this user, log in to AWS with the new user's username and password. After logging in, go to the user tab and select **Switch Roles**.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/wigjbkctff6pvdtgzg9i)

Enter the account ID and the role name.

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/zcljhrx7o6r4kmic7rbr)

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/jgokyzerroyfyv7uu9mn)

![](https://res.cloudinary.com/dmwrakaup/image/upload/c_fit,h_600,q_80,w_900/txdnmlmxo1vjonuf0xkm)

## Conclusion

To share an S3 bucket between AWS accounts, you need to set up AWS Organization, create an IAM role with S3 access in the root account, add a user in the child account with appropriate permissions, and then use the Switch Roles feature to access the shared bucket. This approach provides a secure and manageable way to share resources across accounts.


This blog shows how to share an S3 bucket across different AWS accounts.

Share S3 Bucket Between AWS Accounts


## Table of Contents

1. [Introduction](#introduction)
2. [GitHub Repo with Node.js Code](#github-repo-with-nodejs-code)
3. [Register AWS Account](#register-aws-account)
4. [Create Elastic Beanstalk Application Running Node.js](#create-elastic-beanstalk-application-running-nodejs)
5. [Create AWS Pipeline](#create-aws-pipeline)
6. [Config Pipeline with GitHub Repo](#config-pipeline-with-github-repo)
7. [Config Pipeline to Deploy to Elastic Beanstalk](#config-pipeline-to-deploy-to-elastic-beanstalk)
8. [Check-in Code to GitHub](#check-in-code-to-github)
9. [Verify AWS Pipeline Building and Deploy](#verify-aws-pipeline-building-and-deploy)
10. [Conclusion](#conclusion)
11. [What's Next](#whats-next)

## Introduction

This blog will show how to use AWS CodePipeline to automate building and
deploying code from a GitHub repo. Following are the steps:

- GitHub repo with Node.js code

- Register AWS account

- Create Elastic Beanstalk application running Node.js

- Create AWS Pipeline

- Config Pipeline with GitHub Repo

- Config Pipeline to deploy to Elastic Beanstalk

- Check-in code to GitHub

- Verify AWS Pipeline building and deploy

## GitHub Repo with Node.js Code

You can create your own Node.js app, but in this blog, we'll use the
Node.js app I already created.

sample aws nodejs app

## Register AWS Account

Make sure you have created an AWS account.

## Create Elastic Beanstalk Application Running Node.js

AWS CodePipeline can deploy code to Elastic Beanstalk or other AWS cloud
platforms, but in this blog, we'll set up deployment to Elastic Beanstalk. For
CodePipeline to deploy to Beanstalk, you'll have to create an application.
Since we are deploying a Node.js app, we'll create an Elastic Beanstalk
Node.js app as follows.

![](https://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/mgbhuqkf8ajrx6qcoxxw)

## Create AWS Pipeline

You can go to AWS services to find CodePipeline and create your first AWS
pipeline based on your region. For testing purposes, be aware to only create what you
need.

![](https://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/tdcitv2egkozdipihjqj)

![](https://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/timchvl1lrv3ih5bmrsp)

## Config Pipeline with GitHub Repo

Click Connect to GitHub, type your username and password for GitHub. Once
GitHub authentication has passed, your GitHub repo is connected with AWS Code
Pipeline. You'll have to provide which GitHub repo and what branch you want
to set up with AWS CodePipeline.

![](https://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/rtyy4wgwcfbrw43vjafu)

![](https://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/tho2x9w248qhgdnjmbgq)

## Config Pipeline to Deploy to Elastic Beanstalk

After you set up the GitHub repo and branch in AWS Pipeline, you'll set up where to
deploy your code. In this blog, we'll set up deployment to AWS Elastic
Beanstalk as follows. Once you configure deployment to Elastic Beanstalk, whenever
you check in your code to the GitHub repo's target branch, the AWS CodePipeline
build process will kick off. If the build succeeds, the code will deploy to
Elastic Beanstalk.

![](https://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/voh8f9xxnfbpdma7al2e)

## Check-in Code to GitHub

Check in to GitHub just like you normally do. Once you push to the
remote repo, the AWS Pipeline build process will start.

## Verify AWS Pipeline Building and Deploy

If everything works well, once you push code to the GitHub remote repo,
your code will build and deploy to Elastic Beanstalk. However, something
might go wrong during build or deploy. Following are things I noticed when I
set up AWS Pipeline with GitHub.

### buildspec.yml

**buildspec.yml** is an important file for AWS Pipeline to build
and deploy to Elastic Beanstalk. Following is an example. You can
reference the Build Specification Reference for CodeBuild for the full reference.

```
version: 0.2
artifacts:
  files:
    - "**/*"
```

### nodecommand.config

**nodecommand.config** is used by AWS Elastic Beanstalk to
run your app. The following example shows that when deploying to AWS Elastic
Beanstalk, it should run the "npm start" command to start the app. For more detailed
syntax, see the AWS documentation for
nodecommand.config.

```
option_settings:
  aws:elasticbeanstalk:container:nodejs:
    NodeCommand: "npm start"
```

## Conclusion

AWS CodePipeline is very powerful for continuous integration and
continuous deployment. If you set up the master branch for production, once
you check in, AWS will start to build and, if the build succeeds, will deploy to
Elastic Beanstalk. You might also create lower environments — development,
QA, or staging — using AWS Pipeline, if you wish to move all your code base, build,
and deploy to the cloud.

About cost: once you set up the AWS CodePipeline, the cost is one active pipeline at $1/month. AWS will also set up CodeBuild, which is pay-as-you-go.

## What's Next

Now that we know how to use AWS CodePipeline with GitHub, next I'd like to try
other code repos and see if they work with AWS as well. Also, I'd like to try not just a
simple Node.js app, but something with Express.js or Nest.js, or
perhaps deploy a .NET app, React, or ASP.NET application.


This blog shows how to use AWS CodePipeline to automate building and deploying a Node.js app from a GitHub repo to AWS Elastic Beanstalk.

Build and Deploy with AWS CodePipeline


## Table of Contents

1. [Introduction](#introduction)
2. [Create Amazon AWS Account](#create-amazon-aws-account)
3. [Create New Application at Elastic Beanstalk](#create-new-application-at-elastic-beanstalk)
4. [Upload Node.js Application to Elastic Beanstalk](#upload-nodejs-application-to-elastic-beanstalk)
5. [Verify Node.js Application Running at AWS Elastic Beanstalk](#verify-nodejs-application-running-at-aws-elastic-beanstalk)
6. [Conclusion](#conclusion)

## Introduction

The following shows how to deploy a Node.js app to AWS Elastic Beanstalk.

## Create Amazon AWS Account

Registering for Amazon AWS is free, so the first thing you have to do is create an
AWS account. You can use AWS as a free trial for up to a year.

The AWS free trial is not unlimited, so be aware of not creating too many instances
of Elastic Beanstalk.

## Create New Application at Elastic Beanstalk

After you have your AWS account, go to Elastic Beanstalk and create a new application.

At the Select environment tier, choose Web server environment.

![](http://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/yasypoxlexwfgz1dmkr8)

At the base configuration, choose the platform as Node.js.

## Upload Node.js Application to Elastic Beanstalk

You can create your own Node.js app, but in this blog I'll use the one I
already created at my GitHub repo sample-aws-nodejs. For testing, you can just download the aws-deploy.zip file.

Once you upload the aws-deploy.zip to Elastic Beanstalk, AWS Elastic Beanstalk will start building the
solution and deploy it to the AWS server.

### nodecommand.config

The important thing for AWS Elastic Beanstalk to build and deploy your Node.js
app is the **nodecommand.config** file.
**NodeCommand** will tell AWS what command to run when you
upload your code. In my sample code, it'll run `npm start`.

![](http://res.cloudinary.com/keystone-demo/image/upload/c_fit,h_600,q_80,w_900/hfr9gury738okwtqivkg)

## Verify Node.js Application Running at AWS Elastic Beanstalk

Click the URL of the site. If the site is not up, go to the Logs and check the log
to see what error message was logged. That'll help you troubleshoot
your issue.

## Conclusion

Now you know you can simply upload your Node.js app to Elastic Beanstalk and
have it hosted. Elastic Beanstalk handles the provisioning, load balancing, and scaling for you, making it a straightforward way to deploy Node.js applications on AWS.


How to deploy a Node.js app to AWS Elastic Beanstalk.

AWS

Subscribe for Updates