Forem: Maxwell Wokocha C.

Create DNS Zones And Configure DNS Settings

Maxwell Wokocha C. — Sat, 14 Mar 2026 02:45:39 +0000

Scenario:

Your organization requires workloads to use domain names instead of IP addresses for internal communications. The organization doesn’t want to add a custom DNS solution. You identify these requirements.

. A private DNS zone is required for contoso.com.

. The DNS will use a virtual network link to app-vnet.

. A new DNS record is required for the backend subnet.

Skilling tasks:

. Create and configure a private DNS zone.

. Create and configure DNS records.

. Configure DNS settings on a virtual network.

Architecture diagram:

Azure Private DNS provides a reliable, secure DNS service to manage and resolve domain names in a virtual network without the need to add a custom DNS solution. By using private DNS zones, you can use your own custom domain names rather than the Azure-provided names.

No 1. Create a private DNS zone.

i. On the Azure portal, search for and select Private DNS zones.

ii. Select + Create and configure the DNS zone.

iii. Select Review + create and then select Create.

v. Wait for the DNS zone to deploy, and then select Go to resource.

No 2. Create a virtual network link to your private DNS zone.

Note: To resolve DNS records in a private DNS zone, resources must be linked to the private zone. A virtual network link associates the virtual network to the private zone.

i. In the portal, continue working on the private.contoso.com DNS zone.

ii. In the DNS Management blade, select + Virtual network links.

iii. Select + Add” and configure the virtual network link.

iv. Select Create and wait for the deployment to finish. If necessary, Refresh the page.

No 3. Create a DNS record set.

Note: DNS records provide information about the DNS zone.

i. In the portal, continue working on the private.contoso.com DNS zone.

ii. In the DNS Management blade, select + Recordsets.

iii. Notice that two A records have automatically been created for each of the virtual machines.

iv. Select + Add and configure a record set. When finished select Add.

Note: This record set implies there is a virtual machine in app-vnet with a private IP address of 10.1.1.5.

Configure Network Routing

Maxwell Wokocha C. — Sat, 14 Mar 2026 02:07:39 +0000

In simple terms, routing is how the internet or a network decides where data packets should go and which route they should take to reach their destination.

Scenario:

To ensure the firewall policies are enforced, outbound application traffic must be routed through the firewall. You identify these requirements.

. A route table is required. This route table will be associated with the frontend and backend subnets.

. A route is required to filter all outbound IP traffic from the subnets to the firewall. The firewall’s private IP address will be used.

Skilling tasks:

. Create and configure a route table.

. Link a route table to a subnet.

Architecture diagram:

Note: Azure automatically creates a route table for each subnet within an Azure virtual network. The route table includes the default system routes. You can create route tables and routes to override Azure’s default system routes.

No 1. Create a route table.

a. Record the private IP address of app-vnet-firewall.

i. In the search box at the top of the portal, enter Firewall. Select Firewall in the search results.

ii. Select app-vnet-firewall.

iii. Select Overview and record the Private IP address.

No 2. Add the route table.

i. In the search box, enter Route tables. When Route table appears in the search results, select it.

ii. In the Route table page, select + Create and create the route table.

iii. Select Review + create and then select Create.

iv. Wait for the route table to deploy, then select Go to resource.

No 3. Associate the route table to the subnets.

i. In the portal, continue working with the route table, select app-vnet-firewall-rt.

ii. In the Settings blade, select Subnets and then + Associate.

iii. Configure an association to the frontend subnet, then select OK.

iv. Configure an association to the backend subnet, then select OK.

No 4. Create a route in the route table.

i. In the portal, continue working with the route table, select app-vnet-firewall-rt.

ii. In the Settings blade, select Routes and then + Add.

iii. Configure the route, then select Add.

Create And Configure Azure Firewall

Maxwell Wokocha C. — Sat, 14 Mar 2026 01:30:33 +0000

An Azure Firewall is a cloud-based network security service in Microsoft Azure that helps protect your virtual network resources by filtering and controlling traffic between your Azure resources and the internet or other networks.

Scenario:

Your organization requires centralized network security for the application virtual network. As the application usage increases, more granular application-level filtering and advanced threat protection will be needed. Also, it is expected the application will need continuous updates from Azure DevOps pipelines. You identify these requirements.

. Azure Firewall is required for additional security in the app-vnet.

. A firewall policy should be configured to help manage access to the application.

. A firewall policy application rule is required. This rule will allow the application access to Azure DevOps so the application code can be updated.

. A firewall policy network rule is required. This rule will allow DNS resolution.

Skilling Tasks:

. Create an Azure Firewall.

. Create and configure a firewall policy.

. Create an application rule collection.

. Create a network rule collection.

Architecture diagram:

No 1. Create Azure Firewall subnet in our existing virtual network.

i. In the search box at the top of the portal, enter Virtual networks. Select Virtual networks in the search results.

ii. Select app-vnet.

iii. Select Subnets.

iv. Select + Subnet and Configure.

v. Save Changes.

Note: Leave all other settings as default.

No 2. Create an Azure Firewall.

i. In the search box at the top of the portal, enter Firewall. Select Firewall in the search results.

ii. Select + Create.

iii. Use Values provided in your deployment guide to create the firewall.

v. Select Review + create and then select Create.

No 3. Update the Firewall Policy.

i. In the portal, search for and select Firewall Policies.

ii. Select fw-policy.

No 4. Add an application rule.

i. In the Rules blade, select Application rules and then Add a rule collection.

ii. Configure the application rule collection and then select Add.

Note: The AllowAzurePipelines rule allows the web application to access Azure Pipelines. The rule allows the web application to access the Azure DevOps service and the Azure website.

No 5. Add a network rule.

i. In the Rules blade, select Network rules and then Add a network collection.

ii. Configure the network rule and then select Add.

How to Create And Configure Network Security Groups

Maxwell Wokocha C. — Fri, 13 Mar 2026 23:23:41 +0000

What is a Network Security Group?

A Network Security Group (NSG) is a set of security rules that allow or deny network traffic to resources such as:

. Virtual Machines

. Subnets

. Network interfaces

Scenario:

Your organization requires the network traffic in the app-vnet to be tightly controlled. You identify these requirements.

. The frontend subnet has web servers that can be accessed from the internet. An application security group (ASG) is required for those servers. The ASG should be associated with any virtual machine interface that is part of the group. This will allow the web servers to be easily managed.

. The backend subnet has database servers used by the frontend web servers. A network security group (NSG) is required to control this traffic. The NSG should be associated with any virtual machine interface that will be accessed by the web servers.

. For testing, a virtual machine should be installed in the frontend subnet (VM1) and the backend subnet (VM2). The IT group has provided an Azure resource manager template to deploy these Ubuntu servers.

Architecture Diagram:

Skilling tasks:

. Create a network security group.

. Create network security group rules.

. Associate a network security group to a subnet.

. Create and use application security groups in network security group rules.

Note: The NSG requires resources to function so in this article we are going to provision a Windows and a Linux Virtual Machine.

In the portal search for and select virtual machines. Verify both vm1 and vm2 are Running.

Create Application Security Group

Application security groups (ASGs) let you group together servers with similar functions. For example, all the web servers hosting your application.

In the portal, search for and select Application security groups.
Select + Create and configure the application security group.
Select Review + create and then select Create.

Associate the application security group to the network interface of the VM.

In the Azure portal, search for and select VM1.
In the Networking blade, select Application security groups and then select Add application security groups.
Select the app-frontend-asg and then select Add.

Create and Associate the Network Security Group.

In the portal search for and select Network security group.
Select + Create and configure the network security group.
Select Review + create and then select Create.

Create Network Security Group rules

An NSG use security rules to filter inbound and outbound network traffic.

In the search box at the top of the portal, enter Network security groups. Select Network security groups in the search results.
Select app-vnet-nsg from the list of network security groups.
In the Settings blade, select Inbound security rules.
Select + Add and configure an inbound security rule.

Note: The lesser/lower the Priority Number given to the Rule, the Higher the Priority placed on the Rule.

Thank you, see you in the next post.

Working With Git And Github

Maxwell Wokocha C. — Fri, 13 Feb 2026 01:06:27 +0000

What is Git?

Git is a free and open source software for distributed version control, tracking changes in any set of files, usually used for coordinating work among programmers collaboratively developing source code during software development.

Essential Git Commands:

. Git Push: The "git push" command is used to upload local repository content to a remote repository.
w
. Git Commit: A "git commit -m" takes a snapshot of your repository at one point in time. The "-m" flag helps you add a message to the commit.

. Git Add: The "git add" command adds a change in the working directory to the staging area. It informs Git that you want to include updates to a particular file in the next commit.

. Git Remote Add Origin: The "git remote add origin" creates a new, empty Git repository on your remote server.
Note: You will have to obtain the "git remote add url for the remote repository and add credentials if needed.

How To Push From Our Local Environment To GitHub:

. Download Git Bash.

. Configure Git Bash.

. Work With The Configured Environment.

. Clone Your GitHub Repository.

. Push To GitHub.

. Show The Content.

No 1. Download Git Bash (The Version Compactible With Your Operating System).

No 2. Configure Git Bash: This gives the Git Bash an identity
. "git config --global user.name "add hostname"

. "git config --global user.email "add email"

. "git config --list" verifies that your configuration is in place.

No 3. Work With The Configured Environment:

. Create A Directory Called "Website": "mkdir website"

. Get Into The Created Directory: "cd website"

. Initialize The Directory: "git init" - This command turns the directory called "Website" into a local Git repository.

. To Check The Status Of The Directory: "git status"

. Create A File Inside The Directory Called "Index.html": "touch index.html"

. Open The index.html File: "vim index.html" - Move Into Insert Mode To Be Able To Make Modifications Inside The File.

No 4. Clone Your GitHub Repository.

. Go To Your GitHub Page. Click On The + And Create A New Repository.

. In The Next Page Click on "Code" And Select HTTPS Then Copy The url.

. Go Back To Git Bash To Clone The Repository With The Command "git remote add origin url"

No 5. Push To GitHub.

We Need To Move The File We Added To File Index.html To The Staging Area.

. Check The Status Of The File: "git status"

. Complete The Staging Of The File Content With The Command: "git add index.html"

. Check The Status Again To Verify.

Note: The Highlighted Red File Name Has Just Turned Green To Show That The Staging Level Of The File Content Is Complete.

. Create A SnapShot Of The Whole Update With The Command: "git commit -m"

. Push File To GitHub: "git push origin master"

No 6. Show The Content.

In The GitHub Page And Push The Live URL To View The File Content.

Thank You For Your Time. Till The Next Post.

AWS Networking Fundamentals

Maxwell Wokocha C. — Sat, 07 Feb 2026 14:39:25 +0000

A secure network architecture should be established as a foundational step prior to provisioning cloud resources. Amazon Virtual Private Cloud (VPC) enables organizations to design, isolate, and control their cloud network environments effectively.

What is a VPC?

A VPC (Virtual Private Cloud) in AWS is a logically isolated private network that you create within the AWS cloud, where you can launch and manage your cloud resources securely.

Let's Build A VPC And It's Dependents In AWS.

Go to the AWS Console and search for VPC.

i. Create VPC.

ii. Give the VPC a name, choose a CIDR Block and Number of Availability Zones.

iii. Take the default and Create.

iv. View VPC.

Create A Subnet.

In AWS, subnets are used to segment a VPC into manageable sections.

i. Search and Select Subnet.

ii. Create Subnet.

iii. Choose VPC, Name Subnet, Choose AZ, IPv4 Subnet CIDR Block, Tag and Create Subnet.

Create An Internet Gateway.

An Internet Gateway enables inbound and outbound internet traffic for resources in a public subnet within an AWS VPC.

i. Search and Select Internet Gateway in the AWS Console.

ii. Name and Create Internet Gateway.

Create A Route Table.

i. Search and Select Route Table in the Console.

ii. Create Route Table.

iii. Name Route Table and Select VPC then Create.

Configure Virtual Networks In Azure.

Maxwell Wokocha C. — Fri, 30 Jan 2026 22:54:54 +0000

A virtual network (VNet) is a logically isolated, private network in the cloud that lets your resources communicate securely, much like a traditional on-premises network, but without the physical hardware.

What a Virtual Network Does:

. Connects cloud resources:
Virtual machines, databases, app services, and containers can communicate with each other.

. Controls traffic flow:
You define IP address ranges, subnets, routing, and security rules.

. Isolates resources:
Keep workloads private and protected from the public internet.

. Connects to on-premises networks:
Using VPN gateways or Azure ExpressRoute.

. Enables secure internet access:
Decide what can go in and out using Network Security Groups (NSGs) and firewalls.

Scenario

Your organization is migrating a web-based application to Azure. Your first task is to put in place the virtual networks and subnets. You also need to securely peer the virtual networks. You identify these requirements.

. Two virtual networks are required, app-vnet and hub-vnet. This simulates a hub and spoke network architecture.

. The app-vnet will host the application. This virtual network requires two subnets. The frontend subnet will host the web servers. The backend subnet will host the database servers.

. The hub-vnet only requires a subnet for the firewall.

. The two virtual networks must be able to communicate with each other securely and privately through virtual network peering.

. Both virtual networks should be in the same region.

Skilling tasks:

. Create a virtual network.

. Create a subnet.

. Configure VNet peering.

Architecture Diagram.

Create hub and spoke virtual networks and subnets:

An Azure virtual network enables many types of Azure resources to securely communicate with each other, the internet, and on-premises networks. All Azure resources in a virtual network are deployed into subnets within the virtual network.

a. Sign in to the Azure portal.

b. Search for and select Virtual Networks.

c. Select + Create and complete the configuration of the app-vnet. This virtual network requires two subnets, frontend and backend.

i. On the Basics Tab, Create a Resource Group, Name the Resource Group and Select a Region.

ii. Go to the IP Address Tab, Populate the IP address and Configure Subnet from the deployment guide.

iii. Create the second Subnet.

Note: Leave all other settings as their defaults. When finished select “Review + create and then Create.

d. Create the Hub-vnet virtual network configuration. This virtual network has the firewall subnet.

i. Choose the Resource Group RG1, Name Vnet, Select a Region then Select the IP Addresses Tab.

ii. Configure Azure Firewall Subnet.

Then Review and Create, Create.

Configure a peer relationship between the virtual networks.

Virtual network peering enables you to seamlessly connect two or more Virtual Networks in Azure.

a. Search for and select the app-vnet virtual network.

b. In the Settings blade, select Peerings.

c. + Add a peering between the two virtual networks.

i. Give the Remote peering link a name and Virtual network.

ii. Choose a Local virtual network peering link name.

Note: Leave all other settings as their defaults. Select “Add” to create the virtual network peering.

d. Once the deployment completes, verify the Peering status is Connected.

Thanks for your time, till my next post.

AWS CloudWatch.

Maxwell Wokocha C. — Fri, 23 Jan 2026 02:18:53 +0000

In real systems, CloudWatch answers one key question:

“Is my system healthy right now?”

CloudWatch does this using four core components:

. Metrics – numeric data over time
(CPU usage, memory, network traffic)

. Logs – detailed event records
(application logs, system logs, errors)

. Alarms – automated responses
(send alerts when thresholds are crossed)

. Dashboards – operational visibility
(a single screen showing system health)

If your system is running in production and CloudWatch is not configured, you are flying blind.

CloudWatch (Monitoring & Alerts)

LAB 1: Monitor EC2 CPU

. Launch an EC2 Instance.

. Name Instance, Choose AMI And Create Key Pair.

LAB 2: Go To CloudWatch And Set CPU Utilization.

. Go To Metrics, Choose All Metrics.

. Choose EC2 In The Metrics, Then Per-Instance Metrics Because It's Our Area Of Concentration.

. Choose CPU Utilization.

LAB 3. Configure an SNS(Simple Notification Service) Topic (Alert Channel)

. Name Alert.

. Choose The Type As Standard And Take The Default In The Other Settings Then Create Topic.

LAB 4: Subscribe Your Email.

. In The Page Of The Created Topic, Choose Create Subscription.

. Set Up Email And Create Subscription.

LAB 5: Create a CloudWatch Alarm.

. Go To Cloudwatch.

. In Cloudwatch, Go To Alarm And Choose All Alarms.

. Create Alarm.

. Select Metrics.

. Select EC2.

. Select Per-Instance Metrics.

. Select The Correct Name Of Your Instance And Select CPU Utilization Then Select Metrics.

LAB 6: Set Threshold/Conditions.

. Select Notification Then Next.

. Name Alarm Then Next.

. Create Alarm.

. Go To Your Email And Confirm The Subscription.

Let's Stress The CPU And See If We Get A Notification In The Email.

. Go To The Instance And Install Something To Stress The CPU. Run The Following Command: sudo yum install stress -y,
stress --cpu 2 --timeout 300

. Email Notification.

Create An Azure Virtual Machine Scale Set(VMSS) From A Custom Image.

Maxwell Wokocha C. — Fri, 02 Jan 2026 02:52:08 +0000

What is a Virtual Machine Scale Set (VMSS)?

An Azure Virtual Machine Scale Set allows you to create and manage a group of load-balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule.

Skills Needed:

. Create a Virtual Machine.
. Add and Format Disk in the Virtual Machine.
. Create an Azure Compute Gallery.
. Capture the Virtual Machine Image.
. Create a Virtual Machine Scale Set.

No 1. Create a Virtual Machine.

. Go to Azure portal and search for Virtual Machine.

. +Create Virtual Machine.

. On the Basics tab create a new Resource Group.

. Name Virtual Machine and Choose a Region.

. Choose Availability Zone.

. Choose Security type.

. Choose Image.

. Create an Admin Account for the Virtual Machine.

. Carefully select the Inbound Ports and Check the box to Confirm the eligibility of the image chosen.

. On the Monitoring Blade disable Boot Diagnostics then Review and Create.

Disabling Diagnostics prevents the main computer in the cloud from monitoring your activities.

. After passing validation then Create.

. After Deployment, then go to Resources.

No 2. Add and Format Disk in the Virtual Machine.

. On the Overview of the Virtual machine go to the Settings blade and select Disks.

. Create and Attach a New Disk.

. Name Disk, and choose the Disk Size then Apply.

. Connect the Virtual Machine, remote into the Virtual Machine via RDP and Format the Disk.

. Download RDP File and Login.

. In the Virtual Machine, search for Disk Management in the search bar.

. Right click on the unallocated Disk and click on New Volume then Next.

Disk successfully formatted and provisioned for use.

No 3. Create an Azure Compute Gallery.

. In Azure Portal, search for Azure Compute Galleries.

. +Create.

. Choose the same Resource Group as the Virtual Machine created, Name the Azure Compute Gallery then Review and Create.

. Create.

No 4. Capture the Virtual Machine Image.

. Go to the Virtual Machine and the Overview page click on Capture and select Image.

. On the Basics tab, the Subscription, Resource Group and Region must be the same.

. Enable Image Share to Azure Compute Gallery and Choose the created Gallery to save the Captured Image.

. Choose Operating System State.

Note: There are two types of Operating System state- Generalized and Specialized.

Generalized are Virtual Machines created from this image require hostname, admin user, and other Virtual Machine related setup to be completed on first boot.
Specialized are Virtual Machines created from this image are completely configured and do not require parameters such as hostname and admin user/password.

. Give the Captured Virtual Machine Image a Target Name.

. Give it a Version number and how long it should be operational for.

. Give it a Replication Number then Review and Create.

. Create.

Note: When you click on create to create the captured virtual machine image it immediately shuts down the main virtual machine.

No 5. Create a Virtual Machine Scale Set.

. Once Deployment of the Captured Virtual Machine is complete then go to Resource.

Note: A Captured VM Image can be used to:

Create a Virtual Machine of the exact specification as the Virtual Machine is created out of.
A VMSS that is a Virtual Machine Scale Set.

. +Create VMSS.

. Take the default on Subscription, Resource Group, and Region then Give the VMSS a Name.

. Select Orchestration Mode.

Note: The two types of Orchestration Mode:

Flexible is when you want the VM to be highly available with the same specification.
Uniform is when you want a large scale stateless workload, which means it can be of different specifications.

Scaling Mode is set at No Scaling because of the purpose of this article as we do not want it to spring up virtual machines automatically.

. Review and Create.

. Create.

. We have successfully created a Virtual Machine Scale Set that is highly available.

Thanks once again for your time, until my next post.

How To Create An App Service Application In Azure.

Maxwell Wokocha C. — Tue, 30 Dec 2025 01:29:05 +0000

Here is a step by step guide on how to create an App Service Application in Azure.

What is PaaS?

PaaS (Platform as a Service) is a cloud computing model where Microsoft provides a complete, managed environment for you to build, deploy, and manage applications without the headache of managing the underlying infrastructure.

There are two ways to create an App Service Application in Azure with PaaS:

. Azure Portal.
. CLI (Command Line Interface).

Today, we are looking at creating a PaaS Application through Azure portal.

To create an App Service Application, 3 major services in Azure must be explored/created. The services are as follows:

. A Resource Group.
. App Service Plan.
. Empty Web Application.

Let's delve into it:

No 1. Open Azure portal and search for "App Services".

No 2. Click the +create button then choose "web app".

No 3. Create a "Resource Group".

No 4. Name Instance.

Please note: Naming your instance here creates a an empty web link highlighted with the red arrow above.

No 5. Choose Runtime Stack.

No 6. Choose a Region, here we will go with "Canada Central".

No 7. Take the default on "Windows Plan" then choose Premium for "Pricing Plan".

Note: Choosing the Price Plan in the Service Plan Tier determines the type of plan/computer Microsoft will provision for your work.

No 8. Zone Redundant, leave enabled then "Review and Create".

No 9. Create.

No 10. Go to the Resource of the Web-App Portal.

No 11. Click on the link created in the Web-App Portal to ensure it's an empty Web Application.

No 12. On the WebApp Portal search for " Development Tools" then choose "Advanced Tools".

No 13. Click on "Go".

No 14. Sign into the page Microsoft provisions for you.

No 15. On the page provisioned, click on "Debug Console" then choose "PowerShell".

No 16. On the PowerShell page click on "Site"

No 17. On the "Site" page click on "wwwroot".

No 18. On "wwwroot" page click on the pencil icon(Edit).

No 19. Now go to open a fresh tab and go to chatGPT. Then type a command prompt of whatever you would want to build.

No 20. Copy Prompt from ChatGPT and Paste in the PowerShell Page provisioned by Microsoft.

Note: Delete anything inside the PowerShell page before pasting the ChatGPT prompt.

No 21. Save Changes.

No 22. Go back to the Web-App Portal created in Azure.

No 23. Click on the link in the page to ensure that some contents have been uploaded there.

No 24. Content uploaded successfully in the PaaS Application created.

Thanks for studying with this guide until next time.

Creating An AWS Elastic Beanstalk: Step By Step Guide To Auto Scaling.

Maxwell Wokocha C. — Thu, 25 Dec 2025 04:40:15 +0000

What is Elastic Beanstalk?

Elastic Beanstalk is a service by AWS that makes it easy to deploy and manage web apps. You upload your code, and it takes care of the:

. Server setup & configuration
. Scaling (auto-adjusts resources)
. Load balancing
. Monitoring & health checks

Elastic Beanstalk supports popular frameworks like:

. Node.js
. Ruby
. Python

The platform allows the tech to focus on coding, it takes care of the infrastructure.

Now, let us learn how to Create, Deploy and Manage Web apps with Elastic Beanstalk.

No 1. Open your AWS console and type Elastic Beanstalk to the search bar and select Elastic Beanstalk.

No 2. Create application.

No 3. Select webserver environment and go to Application information to give the App a name, in this article, we are going to name it (MvpApp).

No 4. Scroll down to platform, click the dropdown and select Node.js.

No 5. Choose the default on the rest configuration and Click Next.

No 6. Create Service Role, EC2 Instance Profile and a Keypair.
Service role: It is an IAM (Identity and Access Management) that allows a service to perform actions on your behalf.
EC2 instance profile: Works with EC2 instances. It is a container for an IAM role that can be attached to an EC2 instance when it is launched.
Key Pair: Though optional but its a very important tool in AWS to help combat cyber attacks. A key pair in AWS, is a set of security credentials used to prove your identity when connecting to an Amazon EC2 instance.

No 7. Click on Create Service Role and Take the default, then Next.

No 8. Add Permission and take the default then Next.

No 9. Scroll down and click create role.

Service Role successfully created.

No 10. Create EC2 Instance Role.

No 11. Scroll down then click Next.

No 12. Add Permission Policy and click next but in this article take the default and click next.

No 13. Name the instance role, then Scroll down and click Create.

EC2 Instance Profile Created Successfully.

No 14. Go back to the previous page and refresh for the instance profile created to populate.

No 15. Create a key pair. To create key pair, open your AWS console in another tab, type key pairs to the search bar and select key pairs.
NOTE: You can select a key pair if you have created one already.

No 16. Select create key pair.

No 17. Name key pair.

No 18. Take the default and select create key pair.

No 19. Refresh and select key pair from the dropdown.

No 20. Click on next.

No 21. On the dropdown arrow select the default VPC and enable public IP address.

No 22. Select a region for the instance subnet.

No 23. Scroll down then Next.

No 24. On the EC2 security groups, click the dropdown arrow then select the default security group.

No 25. Take the default then Next.

No 26. Choose Enhanced on the Health Reporting.

No 27. Take the default then Next.

No 28. Create.

No 29. App environment launched successfully.

No 30. What to look out for when you launch the domain in a browser.

Other services launched by elastic beanstalk by default.

No 31. Search EC2 on your main page.

No 32. View dashboard.

No 33. Click Instance running.

No 34. Click the name of the App.

No 35. Connect EC2 Instance.

No 36. Scroll down and connect.

No 37. EC2 instance created by Elastic Beanstalk.

No 38. S3 bucket created by Elastic Beanstalk.

No 39. Auto-Scaling group created by Elastic Beanstalk.

Thanks for your time, till my next post..

How To Create An EC2 Instance in AWS.

Maxwell Wokocha C. — Mon, 15 Dec 2025 03:02:26 +0000

Launch Your Digital Frontier: The Ultimate Guide to Creating Your First AWS EC2 Instance
In the modern digital landscape, the ability to rapidly deploy and scale computing resources is not just an advantage it's a necessity. Tired of wrestling with dedicated hardware or struggling to keep pace with fluctuating demand?

Enter AWS Elastic Compute Cloud EC2: the powerhouse that redefined cloud computing. EC2 allows you to rent virtual servers known as instances on Amazon's robust infrastructure, giving you control over virtually every aspect of your compute environment.

Whether you're looking to host a high-traffic website, deploy a cutting-edge machine learning model, or simply test a new application, your journey into scalable cloud power starts here.

Ready to stop paying for physical servers and start deploying instances with a few clicks? This comprehensive guide will walk you through the essential steps to launch your very first EC2 instance on AWS, turning you from a cloud newcomer into a confident architect in minutes.

Step-by-Step: Launching the EC2 Instance.

A. Navigate to the EC2 Dashboard.
. Log in and find the "Launch Instance" button.

B. Step 1: Choose a name for the instance and an Amazon Machine Image (AMI)

. Give the server a name.

. AMI is a template for your instance's operating system and initial content.

C. Step 2: Choose an Instance Type.

. Instance Type defines the hardware (CPU, RAM, storage, network performance).
. Selecting the t2.micro or t3.micro for the Free Tier.

D. Step 3: Create a key pair.

. After creating the key pair, it goes to the download of the computer.

E. Step 4: Configure Network settings and firewall.
. Take the default on Network settings.
. Allow RDP and HTTP traffic on firewall.

F. Step 5: Launch Instance.

F. Step 6: Go to RDP Client File then get password.

. Upload the key pair file downloaded earlier.

. Decrypt password.

H. Step 7: Go to RDP Client and download remote desktop file.

. Downloaded RDP Client file goes to the computer download.
. Connect RDP and use decrypted password to sign in.

I. Step 8: Login into Server via RDP.