AWS S3 Simple Storage Services

Step By Step Guide to Create S3 Bucket in AWS

S3 is one of the popular web service provided by Amazon. It stands for Simple Storage Services (S3) which not only allows you to store your data on amazon clouds but also you can retrieve your data from anywhere anytime.

In S3, First you need to create bucket which you can understand as a container. In your created bucket, you can store your data (S3 stores data as objects). That data can be anything such as document file, images, videos, code etc. which you can later modify.

Amazon web services management console make this whole process easier for everyone due to its simple interface. 

Step by Step process:

Step 1: To access Amazon S3, you must have an account on Amazon web Services. If you don’t have, then create one by following given on –screen instructions on aws.amazon.com and login.

Step 2: After Login, on left side top corner you can see Services tab.

Click on Services tab and select S3 in Storage category. It will open S3 dashboard.

Step 3: On S3 dashboard,you can see a button namely create bucket. Click on it. It will display a dialogue box that contains four tabs. In first tab, it will ask you bucket name and the region.

a.In bucket name, type a unique name for your new bucket.

b. In region, choose the region where you want the bucket to reside. (In my case, I choose Asia Pacific (Mumbai) India).

Note: You can create more than one bucket here but keep remember that your bucket name must be unique across all existing bucket names in S3 and you cannot change it later, so choose it wisely.

Choose Next

Step 4: Configuration Options: For now, you don’t need to change anything here because it requires cloud watch’s knowledge. 

So remin same and scroll down.

Step 5: Set Permission: Here you can manage permission for your bucket and it is recommended that do not change the default setting of Do not grant public read access to this bucket because granting public read access permissions means that anyone in the world can access the objects in your bucket. So here we also are not changing anything.

So remin same and scroll down.

Step 6: On the Review tab, check the settings. If you want to change something here, choose Edit. If your current settings are correct, choose Create bucket.

Step 7: So now you have a bucket. Let’s add an object to it. As you know object can be anything: A text file, an image, a video etc. 

To upload an object to your bucket, click on your bucket name in bucket name list. 

It will show you a new page which contain Upload button. Click on it.

A dialogue box will open, In Select file tab you can see Add Files button that allows you to select your file that you want to upload, click on it and select your file and then choose Open.

Choose Upload

This is how you can upload your data or object in your bucket.

You can also download your object from your bucket. All you need to do is select the file name that you want to download, right click and choose download.

AWS Route 53 Setup

 How to setup amazon Route 53 in AWS?

Route port 53 is Domain Name System web service. It will route any website from different server to AWS server.

Main functions performed by Route 53 -:

a. domain name register

b. route the website from any server to AWS server

c. Monitor resource health

0. Go to route 53 from aws service panel.

1. Go to DNS management from aws service panel.

2. Create a hosted zone. Enter the domain name you wants to point to amazon (example.com) After creating hosted zone you get ns records. You needs to put this records on your current server where you use hosting. In my case I am using godaddy server for current hosting.

3. Open your current hosting panel, just go to DNS records name server NS click on change. Replace it with your AWS NS records.

4. This may take upto 24 hours to propagate completely. So plan your domain switch accordingly

5. Lets setup a simple apache server on ec2 instance. Keep security group wide open.

-Now we are going to setup some records inside route 53 to point that server. 

6. Go to route 53 then hosted zone and create a new record set by clicking Create record

7. In this record set we are going to use A record. Now we are going to set www to our ip address put ip address of EC2 instance inside value and click create record.

8. Now we are going to create alias record any one who hit www or not go to the same target.(our ip address)

9. Its time to varify your records. If you hit your website name you should see apache2 page. Beacuse you have only install apache2 in Ec2 instance. If you put www you should see the same result.

AWS Ec2 VPC Creation

 How to create VPC in AWS EC2

1. First Go to VPC and Create VPC.

Give a name tag to VPC & IPv4 CIDR block should be 10.0.0.0/16

2 Then After create Subnet.

Select your New VPC

Give a name tag to VPC & IPv4 Subnet CIDR block should be 10.0.0.0/16

3.Create Route Table Attach your VPC with that.

4. Next we are going to Create Internet GatWay. Link Internet Gateway to Route Table. We will Check weather its attached or not

5. Next, Route table is connect internally. Go to Route Table click route. Check the destination and target should be local

6. Attach your internet gatway to your VPC.click om Action then attached VPC, select your VPC then attach internet Gateway.

7. Go to Routes Click on Edit Rule, 0.0.0.0/0 click on internet gateway, select the the gateway which we created earlier then save changes.

8. After that launch ec2 and use VPC and Subnet which we have created

9. Auto Assign IP enable. In step 3 of ec2 creation put these command #!/bin/bash yum update -y yum install -y httpd service httpd start

AWS Ec2 AMI Image Builder step by step

Step by step process of AWS AMI Image Builder

1. First Go to IAM section click on Roles. 

Create role select Ec2 and next.

2. Permissions to policies are required to create ec2 image builder.

3.Select 

EC2InstanceProfileForImageBuilder & AmazonSSMManagedInstanceCore

this policy allow system manager to perform actions on instances create ec2 builder.)

4. Click continue without adding tags then name the role and click create role. (amazonLinuxImagebuilderRole).

5. Now roles is Create lets navigate to ec2 image builder to create a image pipeline.

6. Create image pipeline(The image pipeline in Image Builder defines all aspects of the process to customize images. It consists of the image recipe, infrastructure configuration, distribution, and test settings.)

7. For this case we use Amazon Linux for image OS. Lets choose the image for latest version.

8. You can create component to add to image recipe.

9. For this example we gona use 2 build component(docker-ce-linux, Version: 2.3.1) (amazon-corretto-8-jre, Version: 3.3.1)

10. Test case select (simple-boot-test-linux | Version 2.3.0)

11. Give Name to pipeline - Ec2ImagebuiderPipeLine

12. Select Iam role which we created earlier to associate to instance profile.

13. Select Schedule builder, Schedule the pipeline weekly every monday 12 o'clock. (optional)If you want you can select SNS services for reciving notification regarding piplines.

14. Provide name of AMI.(AmazonLinuxImage). review your setting and create pipeline. After this the pipeline has been created.

15. You needs executes the pipline manually by clicking on action and run pipeline. Now you can see pipeline is executed.

16. Lets Look at ec2 console page

17. Building instance is started then refresh the page after this you Test Instance is instance started

18. Again refresh the page, In last both tested and terminated

19. Check if Image is avaivable or not.

20. Image can also be found in AMI page for future uses.

AWS Amazon Machine Image (AMI)?

What is an Amazon Machine Image (AMI)?

An Amazon Machine Image (AMI) is a template that contains everything needed to launch an EC2 instance (virtual server).

Think of an AMI as a blueprint or master copy of a computer.

When you launch an EC2 instance, AWS copies the AMI and creates a new virtual machine.

Simple Real-Life Example

Imagine you’re opening a new branch of your company.

Every office needs:

• Windows
• Microsoft Office
• Chrome
• Antivirus
• Company software

Instead of installing everything every time, you create one master computer with all the software installed.

Whenever you need a new computer, you simply clone the master computer.

👉 That master computer is like an AMI.

AWS Example

Suppose you’re hosting a website.

Every server needs:

• Ubuntu
• Apache
• PHP
• MySQL Client
• Git
• AWS CLI

Without an AMI:

Launch EC2

↓

Install Ubuntu Updates

↓

Install Apache

↓

Install PHP

↓

Install Git

↓

Install AWS CLI

↓

Deploy Website

Time:
 30–60 minutes

With a custom AMI:

Launch EC2

↓

Everything Already Installed

↓

Website Ready

Time:
 2–5 minutes

What’s Inside an AMI?

An AMI usually contains:

• ✅ Operating System (Ubuntu, Amazon Linux, Windows, etc.)
• ✅ Installed software (Apache, Nginx, Docker, Java, etc.)
• ✅ Application code (optional)
• ✅ Configuration files
• ✅ Security settings
• ✅ Startup configuration

Think of it as a complete server template.

AMI → EC2 Relationship

AMI (Template)

        │

      Launch

        │

        ▼

EC2 Instance (Running Virtual Server)

AMI = Template
 EC2 = Running Server

Real Example

Imagine you work for a software company.

Every developer needs a server with:

• Ubuntu 24.04
• Docker
• Git
• VS Code Server
• Node.js
• AWS CLI

Instead of installing these tools on every new server, you create one AMI.

Whenever a new developer joins:

Launch EC2

↓

Select Company AMI

↓

Server Ready in Minutes

No manual installation is needed.

Types of AMIs

1. AWS-Provided AMIs

These are created and maintained by AWS.

Examples:

• Amazon Linux 2023
• Ubuntu
• Windows Server
• Red Hat Enterprise Linux

Use these when you need a standard operating system.

2. AWS Marketplace AMIs

Created by third-party vendors.

Examples:

• WordPress
• Jenkins
• MongoDB
• Cisco Firewall
• SQL Server

These often come with pre-installed software.

3. Custom AMIs

Created by you or your company.

Example:

Ubuntu

+

Apache

+

PHP

+

Git

+

AWS CLI

+

Company Application

This custom AMI can be reused to launch identical servers.

Example Workflow

Launch EC2

↓

Install Apache

↓

Install Docker

↓

Configure Server

↓

Create AMI

↓

Launch 100 New EC2 Instances

↓

All Servers Identical

Why Use an AMI?

• 🚀 Launch servers quickly
• ⏱️ Save setup time
• 🔄 Keep all servers identical
• 📈 Scale easily
• 🔒 Include security patches and configurations
• 🤖 Support automation with Auto Scaling

AMI vs EC2 Instance

AMIEC2 InstanceA template or blueprintA running virtual serverCannot run applications by itselfRuns your applicationsUsed to create EC2 instancesCreated from an AMIReusableCan be started, stopped, rebooted, or terminated

Interview Question

Q: What is an Amazon Machine Image (AMI)?

Answer:

An Amazon Machine Image (AMI) is a preconfigured template used to launch EC2 instances. It includes the operating system, installed software, configurations, and other settings required to create a virtual server. By using an AMI, you can quickly launch multiple EC2 instances with the same configuration.

Remember this simple formula:

AMI = Blueprint (Template)

↓

EC2 Instance = Running Server

Easy analogy: If a house blueprint is an AMI, then the actual house built from that blueprint is an EC2 instance. You can build many identical houses from one blueprint, just as you can launch many identical EC2 instances from one AMI.

AWS VPC (Virtual Private Cloud) Creation – Step-by-Step Guide

A VPC (Virtual Private Cloud) is your own private network inside AWS where you can launch resources like EC2 instances, RDS databases, Load Balancers, and more.

VPC Architecture

                     Internet
                         │
                 Internet_Gateway
                         │
                 +----------------+
                 |      VPC       |
                 | 10.0.0.0/16    |
                 +----------------+
                  │             │
          Public Subnet     Private Subnet
         10.0.1.0/24        10.0.2.0/24
             │                  │
          EC2 Server        Database Server
             │
       Public IP Address

Step 1: Login to AWS Console

1. Login to AWS
2. Search VPC
3. Open VPC Dashboard

Step 2: Create VPC

Click

Create VPC

Choose

VPC only

Fill details

Field	Value
Name	My-VPC
IPv4 CIDR	10.0.0.0/16
IPv6	None
Tenancy	Default

Click

Create VPC

Your VPC is ready.

Step 3: Create Public Subnet

Go to

Subnets → Create subnet

Choose your VPC

Enter

Field	Value
Name	Public-Subnet
Availability Zone	ap-south-1a
IPv4 CIDR	10.0.1.0/24

Click

Create Subnet

Step 4: Create Private Subnet

Again click

Create Subnet

Field	Value
Name	Private-Subnet
AZ	ap-south-1b
CIDR	10.0.2.0/24

Click

Create

Step 5: Create Internet Gateway

Go to

Internet Gateways

Click

Create Internet Gateway

Name

My-IGW

Click

Create

Now

Select the IGW

Click

Actions → Attach to VPC

Choose

My-VPC

Done.

Step 6: Create Route Table

Go to

Route Tables

Click

Create Route Table

Name

Public-RouteTable

Select

My-VPC

Create.

Step 7: Add Internet Route

Open the Route Table

Click

Routes → Edit Routes

Add

Destination	Target
0.0.0.0/0	Internet Gateway

Save.

This route means:

"Send all internet traffic through the Internet Gateway."

Step 8: Associate Public Subnet

Inside Route Table

Choose

Subnet Associations

Click

Edit

Select

Public-Subnet

Save.

Now only this subnet has internet access.

Step 9: Enable Auto-Assign Public IP

Go to

Subnets

Select

Public-Subnet

Choose

Edit subnet settings

Enable

✅ Auto-assign Public IPv4

Save.

Step 10: Launch EC2 Instance

Go to EC2

Launch Instance

Choose

• Amazon Linux
• t2.micro (Free Tier)

Under Network

Select

My-VPC

Select

Public-Subnet

Enable

Assign Public IP = Enabled

Launch.

Now your EC2 can access the internet.

Final Architecture

                  Internet
                      │
              Internet Gateway
                      │
        -----------------------------
        |          My-VPC           |
        |      10.0.0.0/16          |
        |                           |
        |    Public Subnet          |
        |    10.0.1.0/24            |
        |          │                |
        |   EC2 (Public IP)         |
        |                           |
        |---------------------------|
        | Private Subnet            |
        |10.0.2.0/24                |
        |      │                    |
        |   RDS / Private EC2       |
        -----------------------------

Components Summary

Component	Purpose
VPC	Creates your private AWS network
Subnet	Divides the VPC into smaller networks
Public Subnet	Resources can access the internet
Private Subnet	Resources stay isolated from the internet
Internet Gateway	Connects the VPC to the internet
Route Table	Controls where network traffic goes
Security Group	Instance-level firewall
Network ACL	Subnet-level firewall

Best Practices

• Use separate public and private subnets.
• Keep databases (RDS) in private subnets.
• Allow only necessary ports in Security Groups (e.g., SSH: 22, HTTP: 80, HTTPS: 443).
• Use CIDR blocks that don't overlap with other networks (e.g., 10.0.0.0/16).
• Use at least two Availability Zones for high availability.
• For private subnets that need outbound internet access (e.g., software updates), use a NAT Gateway in a public subnet instead of exposing them directly.

Interview Questions

1. What is a VPC?
2. What is the difference between a public and private subnet?
3. What is an Internet Gateway?
4. What is the purpose of a Route Table?
5. Why do we use CIDR notation?
6. What is the difference between a Security Group and a Network ACL?
7. Can an EC2 instance in a private subnet access the internet? (Yes, via a NAT Gateway if configured.)
8. Why should databases be placed in a private subnet?
9. Can multiple subnets exist in one VPC? (Yes.)
10. What happens if you don't attach an Internet Gateway to a VPC?

This workflow creates a basic, production-style VPC that you can use for hosting web applications while keeping backend services such as databases securely isolated.

please provide list of these steps

AWS VPC Creation – Step-by-Step Checklist

Step