DEV Community: Wireshark

What is AWS? AWS Cloud Computing for Beginners

Wireshark — Mon, 22 Dec 2025 10:00:24 +0000

If you’re new to cloud computing, AWS is one of the first platforms you’ll hear about. Whether you’re trying to become a DevOps engineer, build modern apps, run servers, or store data securely, AWS is the go-to platform trusted by millions of companies worldwide.

In this beginner-friendly guide, I’ll break down what AWS is, how it works, and why it matters, using simple language and practical examples.

What Is AWS?

AWS (Amazon Web Services) is Amazon’s cloud computing platform. It is the world’s most comprehensive and widely adopted cloud platform, offering over 200 fully featured services from data centers globally.

Instead of buying physical servers or hardware, AWS lets you rent computing resources over the internet — like servers, databases, storage, security tools, networking, AI services, and more.

Think of AWS as:

A huge online toolbox full of everything you need to build, host, and scale applications.

You only pay for what you use, and you can increase or decrease resources anytime.

Why Do People Use AWS?

Here are the main reasons AWS is the global leader in cloud computing:

1. No need to buy physical hardware

You don’t need a data center, cooling systems, or expensive equipment. AWS handles everything.

2. Pay-as-you-go pricing

No upfront costs. You pay only for what you use, just like buying fuel for your car.

3. High availability and reliability

AWS runs on many data centers across the world, so your applications stay online even if one region has issues.

4. Easy to scale

If you need more storage or computing power, you can scale up in seconds with one click.

5. Secure by design

AWS uses enterprise-grade security — encryption, firewall customization, IAM, compliance, and more.

How Does AWS Works?

AWS is divided into Regions and Availability Zones:

Region = geographical area (e.g., us-east-1 in Virginia)
Availability Zone (AZ) = multiple isolated data centers inside each region

Example: us-east-1 has 6+ data centers.

This ensures:

high performance
backup and redundancy
disaster recovery

When you deploy a server, database, or storage, you pick the region/AZ where it lives.

How to Start Learning AWS

Getting started with AWS doesn’t have to be overwhelming. Here’s a clear, beginner-friendly path to follow:

1. Create a Free AWS Account

Start by creating your AWS account. Amazon offers a 12-month Free Tier that lets you experiment with essential services such as: EC2, S3, Lambda, RDS, CloudWatch, etc.

It is perfect for beginners who want to learn without spending money.

2. Learn the core services

Begin with the foundational AWS services that power most applications:

EC2 for virtual servers
S3 for storage
IAM for security and access control
VPC for networking
CloudWatch for monitoring and logs

3. Do small projects

Practice by building simple AWS projects that strengthen your fundamentals:

Host a static website on S3 to learn storage and permissions
Launch an EC2 instance to understand cloud servers and SSH
Deploy a Node.js app to practice hosting real applications
Configure a VPC with public/private subnets to learn networking basics

4. Explore DevOps Tools

AWS becomes even more powerful when combined with core DevOps tools like:

Linux for server administration
Docker for containerizing applications
CI/CD for automated deployment pipelines
Terraform for Infrastructure as Code (IaC)

Conclusion

AWS is the world’s most popular cloud platform because it gives developers and businesses everything they need to build fast, secure, and scalable applications.

Whether you’re starting a DevOps career, launching personal projects, or preparing for real production workloads, AWS is a powerful skill to master and this guide gives you the foundation to begin.

If you found this guide helpful, kindly hit the Follow button so you don’t miss new lessons. You can also explore my other guides on AWS, like my step-by-step tutorial on creating an EC2 instance.

Launch Your First S3 Bucket: An Easy, Practical Guide for Beginners

Wireshark — Mon, 22 Dec 2025 09:37:42 +0000

Imagine having a personal, unlimited hard drive in the cloud — one that never crashes, can be accessed from anywhere, and grows with your needs. That’s exactly what Amazon S3 (Simple Storage Service) offers.

Amazon S3 is one of the most beginner-friendly services in AWS. Whether you’re a developer storing app data, a business owner backing up files, or just a curious learner, S3 gives you a secure, reliable, and cost-effective way to store and access data online.

In this guide, we’ll walk step by step through creating your very first S3 bucket and uploading files, so you can see for yourself how easy cloud storage can be.

Core Concepts You Need Before You Start

Before we create a bucket, let’s simplify some key S3 terms:

Bucket → Like a folder where all your files (objects) live.
Object → The actual file you upload (e.g., photo.jpg, report.pdf).
Region → The physical AWS data center where your bucket is hosted (e.g., US-East, Europe, Africa).
Permissions → Settings that decide who can access your files (you, your team, or the public).

Once you understand these, using S3 becomes much easier.

Step-by-Step: Create Your First S3 Bucket

Step 1: Log in to AWS

Go to AWS Console and sign in with your account.

Step 2: Navigate to S3

In the search bar, type “S3” and click on it.

Step 3: Create a Bucket

Click Create bucket.

Enter a unique bucket name (e.g., practical-bucket3). If you have another bucket already that has all the settings configured, you can copy settings from the existing bucket, but we don't have one; this is our first bucket, so we’ll skip and scroll down.

Next we have options about access; this is very important. You can grant public access to your buckets in a variety of ways; you’ll see those listed below. But granting public access is generally not a great idea, which means you don't want your files accessible to the whole public; you just want to limit it to some internal services that are needed to run your application. Public buckets are risky unless you’re intentionally hosting public files (like a website).

So you set the object ownership to (ACLs disabled) and block all public access.

With bucket versioning you can keep multiple versions of objects or files in the bucket; this makes it possible to recover old versions. Maybe your users need to revert to an old version of a video or photo, or they accidentally delete something and they need to get it back, but it also comes in handy if there's some kind of application failure and you need to restore previous versions. By default this is turned off, but if you have a good reason to enable it, you just turn it on.

Tags help you to manage and organize things and are also an easy way to track your costs. For example, if this bucket is going to be used for development purposes only, we’ll say environment equals dev; for other buckets, maybe you have environments equal to production or testing.

You can automatically encrypt new objects stored in the bucket, so we’re going to leave that as the default and set the bucket key to disable. No need to enable KMS or dual-layer yet (those add complexity and extra cost).

Bucket Key applies only if you use “SSE-KMS” because it helps reduce costs when using KMS. But it’s not needed if you choose SSE-S3. This gives you secure, automatic encryption with zero complexity and no extra charges.

There are some advanced settings here as well for object lock; this will prevent objects from being deleted or overwritten. This is a handy feature to have if you have some kind of regulatory requirement to store things, but we’re going to leave it disabled for what we’re doing and then create a bucket.

Congrats you’ve got your first S3 bucket! 🎉

Next is to click on the “practical-bucket3” to open it and as you can see, we’ve not uploaded anything yet, so let’s create a folder. One will be for videos and another one for photos.

Go back and create another folder for videos.

So after creating both, let's go upload something to the photos folder. Click on photos and upload them in the photos folder by clicking on add files.

There are other things you can configure here around permissions and other properties; we're just going to leave everything as default and click upload. This will take some minutes depending on your file size. You can also upload using the AWS command line interface or by using the software developer kit.

At the bottom you'll see the photo file name. If you click on it, you'll see all the details about it. There are additional tabs here as well for permissions and versions; if you’re using versioning, that would have some good information in there for you. The object URL is how you would actually access this through a browser.

If you click on the “Object URL,” you can see the access is denied. You remember that we blocked all public access, so if you actually need to view this photo, you have a couple options.

You can open it right up here by clicking on where the arrow is pointed, and it will be opened in a new tab. You can also choose to download it locally and you could view it there.

So those are the basics of creating a bucket and a folder and uploading objects to it. So before we wrap up, I want to show you how to delete the S3 bucket. Follow where the arrow is pointed and click on “Buckets.”

Select the name and then come up here to delete. (Check where the arrow is pointed).

In our case the bucket is not empty, so you have to go empty the bucket first by clicking on “empty bucket,” and because this can’t be undone, it will force you to type in “permanently delete” just to be sure. Then click on empty.

So there’s a message up there to actually go delete the bucket itself; you can click on that and confirm by typing the name of the bucket.

And now everything is gone. That’s the basics of S3 on AWS, and you’ve just built your first S3 bucket—but this is only the beginning. In my next tutorial, I’ll show you how to use S3 to host a simple static website. Stay tuned!

👉 Follow me on Medium (and X/Twitter) so you don’t miss it.

How to Deploy a PostgreSQL Database on AWS RDS (Step-by-Step)

Wireshark — Fri, 03 Oct 2025 20:13:34 +0000

Amazon RDS (Relational Database Service) is a managed database service from AWS that makes it easy to set up, operate, and scale relational databases in the cloud.

Instead of manually installing and maintaining a database on a server, RDS handles most of the heavy lifting for you — like: Automatic backups, Software patching, High availability & failover (Multi-AZ), Performance monitoring, Easy scaling (storage & compute).

Using PostgreSQL on RDS gives you the power of a robust open-source database, combined with AWS automation for scaling, backups, and admin tasks.

Prerequisites

AWS account (free to create)

Basic understanding of PostgreSQL

SQL Editor (e.g. PgAdmin, DBeaver) for testing connections

Step 1: Navigate to Amazon RDS

Log into AWS Management Console

Go to RDS service

Step 2: Create a New Database Instance

Click on Databases on the left panel; this page lists all your databases on RDS, and as you can see we currently don’t have any at the moment. So click on “Create database.”

Choose Standard Create and select PostgreSQL from the engine options.

Step 3: Configure Database Settings

In the engine version dropdown, select the version you want to use. In this tutorial, I chose the smaller version which is “PostgreSQL 14.17-R1” then scrolled down to the template section and selected “sandbox” because we just want to get it up and running for demo purposes.

In the settings section, enter a database identifier; this is unique in your account and is used as part of the connection process from the SQL editor.

In this tutorial I’ll change the default DB identifier to “postgresql-01” and set the credentials management to self-managed, then set the password and confirm password. Don’t forget the password, as we’ll use it to connect later.

Step 4: Set Storage and Connectivity

In the instance configuration section, you can set the instance to “db.t3.micro” as we’re currently on demo. Then in the storage section leave all of the options as default values.

The next step is to choose VPC & networking options. The Compute resource, Network type, Virtual private cloud (VPC) and DB subnet group can all remain as default values.

But for the “Public access” option, you can change it to “Yes” so you can connect to it from your computer. You can leave the VPC security group (firewall) and availability zone as default.

Expand the additional configuration and ensure the database port is set to “5432.”

In the database authentication section, leave the default value of the password authentication and also leave the monitoring section as their default values.

Step 5: Launch and Test Connection

It is recommended to keep an eye on the account usage if you plan on using this database, so you don't get any surprises about what you get charged.

Finally, click on "Create Database" at the bottom.

After a few minutes the database list page will be shown, you will see a banner showing your database has been created, and the status will be available.

Now that our Postgres database is created, let's connect to it. In this guide, I’ll use the free SQL editor which is “DBeaver,” but you can use any other editor that can work with Postgres databases.

To get DBeaver you can download from the official website here.

👉 https://dbeaver.io/download

Choose your operating system (Windows, macOS, Linux).

Download and install.

After downloading and installing DBeaver, open it and click on the new connection button in the window that appears, select postgresql as the database and click next.

We will now need to specify the connection details. What hostname should we use. We can find these details on the database page in AWS; so go back to the databases list inside AWS, click on the database name in the list and you’ll see the details page for this database.

The value to use for this hostname is labelled “endpoint” on the screen. It’s in the form of your database instance name (postgresql-01.cd2s88wgqc0p.us-east-2.rds.amazonaws.com). Copy this value and paste it into the host field in DBeaver.

The port should be “5432,” which matches what is on the AWS database screen. The database field can remain as postgres, and the username field can also remain as postgres.

For the password, enter the password that you specified when you created the database on AWS (this is not your AWS account password); it's the password you created for the Postgres database (remember when i told you to keep it and that you'd still need it?). Check the "save password locally" box if you want to store the password and not have to enter it each time you connect.

Next, click “Test Connection” to test that it is working; you’ll probably get an error such as “connection attempt timed out.” First, it could mean that the database has not been created. Check that the status is available in Amazon RDS and try again. If you still get an error, this can be resolved by creating a security group on Amazon RDS; this will allow inbound connections to the database, which is not something that is set up by default.

To resolve this issue, we need to go back to our RDS window and modify the security group. In the list of databases, click on the database to open the details.

On the connectivity and security tab, we will open the VPC security groups. Click on the entry that appears here called "default"; this will show you the VPC section. We have one security group associated with this database, which we can see here. At the bottom of the screen, we can see the details of the security group; click on the inbound rules tab. On the right of this tab, click on Edit Inbound Rules.

We now see the edit inbound rules page; click on the delete button to delete the existing rule. I suggest deleting and creating a new one in order to avoid errors when you try to modify it.

Then click on "Add Rule." In the type dropdown we will select PostgreSQL; the protocol and port range are already populated. Next is to select the source value of anywhere IPv4, then click on save rules. After a moment, the rule will be saved, and you'll be taken back to the security groups page.

We'll see the PostgreSQL rule that we just created at the bottom of the page; now we can retry our connection when we return to DBeaver and click on test connection again.

If all goes well, we should see a connected window to let us know the connection is successful. Click OK, then click finish on the connection window. You'll see a new option in your connection list called postgres.

Let's create a schema on this database, which is probably the next thing you want to do if you want to use this database. Double-click on the connection, and it will expand. When you expand the databases, you’ll see Postgres and then schemas. Right-click on schemas and select "create new schema."

We’ll name ours “newdb,” then click OK. The new database schema is then created. You can now proceed with creating tables on this schema or on the public schema that came with the database.

So that’s how you create a new Postgres database on Amazon RDS.

If you no longer need the database, you can delete it. This also might be a good way to prevent any charges on your account in the future.

To do this, navigate back to RDS. If you're still on the security group section, you can search for RDS in the search bar like we did earlier in this guide. Then click on databases on the left; on the left of the databases is a circle.

Click on the circle to select the database and then in the actions dropdown at the top, select delete.

If you want to create a snapshot, leave the BOX selected, but i don’t want to do that in this guide, so i’ll uncheck it. Tick the acknowledge box that appears, and i’ll also uncheck “retain automated backups,” as I don’t want that either.

Finally type "delete me" into the field at the bottom and click "delete." After a few moments, the database will be deleted.

So that's how you can set up a new Postgres database on Amazon RDS, connect to it from your SQL editor, and delete it if you no longer need it.

That’s it! You’ve successfully deployed PostgreSQL on Amazon RDS.

If you found this guide helpful, follow me here for more beginner-friendly DevOps and AWS tutorials.

A Beginner’s Guide to AWS DynamoDB: Creating Your First Table

Wireshark — Fri, 03 Oct 2025 11:19:53 +0000

If you’re just starting your cloud journey, you’ve probably come across Amazon DynamoDB.

It’s a fully managed NoSQL database service from AWS, designed for applications that need high performance at any scale.

But if you’re new, it might feel overwhelming.

Don’t worry — in this guide, we’ll walk step by step through creating your very first DynamoDB table and adding data to it.

What is Amazon DynamoDB?

Amazon DynamoDB is a serverless, NoSQL, fully managed database with single-digit millisecond performance at any scale.

DynamoDB addresses your needs to overcome scaling and operational complexities of relational databases. DynamoDB is purpose-built and optimized for operational workloads that require consistent performance at any scale. You don’t have to worry about servers, patches, or capacity planning — AWS handles it for you.

DynamoDB falls into the Non-Relational or NoSQL category, and its commonly used for Web and mobile applications, Real-time analytics, Gaming and IoT apps, and any use case requiring scalable, low-latency databases. Instead of storing your data in tables with rows and columns, its commonly represented as JSON code.

Prerequisites

Before you begin, make sure you have:

An AWS account (you can use the free tier).
Access to the AWS Management Console.
Basic familiarity with AWS navigation.

Let's get started and create our first table.

Step 1: Navigate to DynamoDB

1) Log in to the AWS Management Console.

2) In the search bar, type DynamoDB.

3) Click on the service to open it.

Step 2: Create Your First Table
Click Create table.

2) Enter a Table name — for example, Users. Then set the partition key to user_id (Type: String).

Leave other settings as default (for now). Then click Create table.

Congratulations 🎉 you’ve just created your first DynamoDB table!

Step 3: Add Items to the Table

Now let’s add some data. Firstly, you open the table you just created by clicking on (Users).

Secondly, go to the Items tab by clicking on explore table items.

Thirdly, as you can see we don't have any items at the moment, so we’ll click on "Create item."

We indicate the partition key for our “user_id,” so we'll input “1” as the value, and we can also add a new attribute to our items. In this example we’ll use “string” as the data type for our new attribute.

After we input the details, then we go ahead and click on "create item."

Go to the Items tab to see all stored data. You can see our created item in the image below as “Items returned,” such as country, first_name, last_name and state.

Now let's create another item; this second one will be "user_id 2". Input the details and data type, then click on "Create Item."

And as you can see below, we have two different items, and both have different values. The second one has an age but the first one doesn't, while the first one has a city, but the second one doesn't.

Step 4: Scan and Query Items
Go to the Items tab to see all stored data. Use the Scan option to fetch all items, or try a Query to find a user by UserId.

To retrieve the data we just added, click on Query and for the partition key value, enter the key. e.g, “1" and click run. You should see the item below.

Here is the result.

Now let's also try scanning. Click "Scan" and click "Run"; this will show you all items in the table. Remember, queries are more efficient because they use the primary key to locate items directly, while scans have to look through every item in the table.

Congratulations, that’s how you create a DynamoDB table and also add items.

In this beginner-friendly guide, you:

✅ Created your first DynamoDB table.

✅ Inserted items into the table.

✅ Learned how to scan and query data.

From here, you can explore more advanced DynamoDB features like secondary indexes, provisioned capacity, and integrating with AWS Lambda.

DynamoDB might look complex at first, but with practice, you’ll see how powerful it is for modern applications.

If you find this article helpful, stay tuned — I’ll be sharing more beginner-friendly guides on AWS, DevOps, and Cloud Engineering.

👉 Follow me here on [DEV.to] for more tutorials, and connect with me on X (Twitter) to see what I’m building and learning in real time.

Let’s grow our cloud skills together 🚀

# ☁️ Cloud Engineer vs 🔄 DevOps Engineer: Which Path Should You Take?

Wireshark — Sun, 21 Sep 2025 12:14:06 +0000

A beginner-friendly guide to roles, skills, tools, and career growth opportunities in two of tech's most in-demand fields.

👋 Introduction

If you’re starting out in tech, you’ve probably heard the terms Cloud Engineer and DevOps Engineer.

They sound similar. They often work together. But they are not the same role.

Both careers are:

✅ In high demand
✅ Well paid
✅ Essential for modern businesses

But what exactly do they do? And which path is right for you?

Let’s break it down 👇

🏗️ Understanding the Core Concepts

Cloud Engineer = Architect & Builder

Think of a Cloud Engineer like an architect + contractor for a new apartment:

Chooses the land → cloud provider (AWS, Azure, GCP)
Builds the foundation → servers, storage, databases
Ensures electricity/plumbing → networking, security

They design and maintain the infrastructure where apps live.

DevOps Engineer = Manager & Automator

Now imagine the DevOps Engineer as the building manager + maintenance crew:

Moves tenants (developers) in smoothly
Sets rules for how updates happen
Automates fixes when something breaks

They focus on processes, automation, and smooth software delivery.

👉 In short:

Cloud Engineer builds the playground
DevOps Engineer sets up and automates the games

🛠️ Essential Skills & Tools

🔹 Cloud Engineer Skills

Cloud Platforms: AWS, Azure, GCP
Infrastructure as Code (IaC): Terraform, CloudFormation
Scripting: Python, Bash
Networking: VPCs, subnets, routing

Tools they use:

AWS (EC2, S3, RDS)
Azure (VMs, Blob Storage, SQL Database)
GCP (Compute Engine, Cloud Storage, Cloud SQL)
Monitoring → CloudWatch, Azure Monitor, Prometheus

🔹 DevOps Engineer Skills

CI/CD Pipelines: Jenkins, GitLab CI/CD, GitHub Actions
Containerization: Docker, Kubernetes
Configuration Management: Ansible, Puppet, Chef
Version Control: Git
Scripting: Python, Go

Focus: Automating processes, speeding up deployments, reducing errors.

🚀 Career Growth

Cloud Engineer Path:

Cloud Architect
Solutions Architect
Cloud Security Engineer

DevOps Engineer Path:

Site Reliability Engineer (SRE)
Release Manager
Head of DevOps

Both paths are:

🌍 In high demand worldwide
💰 Offering six-figure salaries
🚀 Constantly evolving

💡 Which One Should You Choose?

Choose Cloud Engineering if you love infrastructure, security, and large-scale systems.
Choose DevOps Engineering if you enjoy automation, efficiency, and bridging dev + ops teams.

👉 Reality check: You don’t have to choose just one.

A great DevOps Engineer understands cloud.
A great Cloud Engineer benefits from DevOps automation.

🎯 Final Thoughts

If you’re curious about how the internet is built, start with Cloud.

If you’re excited about automation & speed, start with DevOps.

Both are rewarding, future-proof careers. Start small, learn the fundamentals, then branch out.

✍️ If you found this helpful, follow me here on Dev.to — I share beginner-friendly breakdowns on Cloud, DevOps, and Web3 to help you grow faster in tech.

How to Create a Windows Server on AWS EC2 (Beginner’s Guide)

Wireshark — Wed, 10 Sep 2025 07:00:21 +0000

Learn how to set up a Windows Server on Amazon EC2, from creating your instance to logging in via Remote Desktop.

📝 Introduction

Amazon EC2 is like renting a computer in the cloud. Instead of buying a physical server, you can instantly create one online, choose whether it runs Windows or Linux, and use it just like a normal computer—but you only pay for the time you actually use it.

You can choose instance types based on CPU, memory, and storage, and configure networking/security via VPC and security groups. EC2 integrates with other AWS services like IAM, S3, and CloudWatch, making it ideal for hosting apps, testing environments, or production workloads.

When you’re just starting with cloud computing, AWS can feel overwhelming. But don’t worry, launching your first Windows Server on AWS EC2 is easier than it looks.

In this guide, I’ll walk you through every step, from setting up your instance to connecting with Remote Desktop. By the end, you’ll have your own Windows Server running in the cloud, ready for web hosting, development, or even a test lab.

✅ Prerequisites

Before we begin, you’ll need:

An AWS account (sign up here)
Basic familiarity with the AWS Management Console (Don’t worry, we’ll keep it simple)
A key pair (we’ll cover how to create one if you don’t have it)

🚀 Step 1: Log in to AWS Console

Create an AWS account or sign in if you already have one.
Proceed to sign in using the Root user, then enter your email address and password.

🚀 Step 2: Launch an Instance

1) From the AWS console, search for EC2 and click on it.

2) You can click on Launch instance immediately or go to the dashboard to see your running instances, key pairs, and security groups.

After launching an instance, you’ll be asked to provide a name; in my case i used “MyWindowsServer” as the name.

🚀 Step 3: Choose an Amazon Machine Image (AMI)

The next step is to set the Amazon Machine Image (AMI) to Windows. Under Quick Start, select Microsoft Windows Server 2025 Base.

🚀 Step 4: Choose Instance Type

For testing/demo → t3.micro (Free Tier eligible).
For production/heavier workloads → larger instances like m5, m6i, m7i.

🚀 Step 5: Configure Key Pair

Select an existing key pair or create a new one.
If creating new → choose .pem format, give it a name, and download the file.

⚠️ Keep the .pem file safe—you’ll need it later to decrypt your Windows password.

🚀 Step 6: Configure Network Settings

Use the default VPC (or create a new one if none exists).

To create a new VPC, click on the search bar at the top left and type "VPC," right-click on the VPC, and open it in a new tab.

Click on Create VPC.

The next step is to go back to the previous tab, click on the refresh button, and then click the drop-down button in order to see your new VPC.

Enable Auto-assign public IP.
Create a new security group (e.g., “WindowsServer”).

Make sure RDP (TCP/3389) is allowed in inbound rules.

🚀 Step 7: Configure Storage

By default, AWS provides 30GB of EBS storage.
Adjust only if your workload requires more.

The next step is to scroll down to “Advanced details.” Move down to DNS Hostname, then tick “Enable resource-based IPv4.”

🚀 Step 8: Review & Launch

Review all your settings.
If everything looks good, click Launch Instance.

🚀 Step 9: Connect to Your Windows Server

1) Go to EC2 → Instances (running).

2) Copy the Public IPv4 address of your instance.

3) On your computer, press Win + R, type mstsc, and click OK.

4) Paste the IPv4 address in the Remote Desktop Connection box.

5) In AWS, click connect and select RDP Client → Get Password.

6) Upload your .pem file → click Decrypt Password.

7) Copy the "Administrator" username and "decrypted password".

8) Log in via Remote Desktop.
Click Yes to proceed.

🎉 Congratulations! Your Windows Server is live.

🔧 What’s Next?

From here, you can:

Install enterprise apps or use it as a remote workstation
Host a website (install IIS)
Set up Active Directory for a test lab
Store/backup important files centrally

If you want to log off the Windows Server instance, open your Run dialog box by pressing the keyboard shortcut “Win + R” and type “logoff” then click ok, and your session will be terminated.

⚠️ Tip: Remember to stop or terminate your instance when not in use to avoid unexpected AWS charges.

📝 Conclusion

Launching a Windows Server EC2 instance on AWS is straightforward once you know the steps:

Choose AMI → Pick instance type → Configure security → Launch → Connect via RDP.

With this knowledge, you can now build Windows-based environments in the cloud in just minutes.

✍️ I write about DevOps, Cloud Computing, and Blockchain Infrastructure. Follow me here on Dev.to and Medium (https://medium.com/@jimmybillz2021) to learn along with me!

🐧 Top 10 Linux Commands Every Beginner Must Know

Wireshark — Fri, 05 Sep 2025 15:41:58 +0000

Learning Linux might feel scary at first, but once you master a few essential commands, you’ll be navigating like a pro. In this tutorial, I’ll walk you through 10 must-know Linux commands with real examples and outputs you can try on your own terminal.

Let's get started.🚀

1) pwd – Print Working Directory 📂

This command shows the full path of the folder you are currently in.

👉 This command is helpful when you get lost in multiple directories.

2) ls – List Files

This command lists the files and folders in your current location.

These are other options to use:

ls -l → shows details (permissions, size, date).
ls -a → shows hidden files (those starting with a dot .).

3) cd – Change Directory

This command can be used to move into another folder.

cd .. → go back one folder.
cd ~ → jump back to your home directory.

4) mkdir – Make Directory 📂

This command creates a new folder.

5) touch – Create an Empty File

This command is a quick way to create new files in linux.

6) cp – Copy Files and Directories

 This command copies files/folders from one place to another.

7) mv – Move or Rename Files

 This command is used to move or rename files/folders.

Rename example:

8) 8. rm – Remove Files

 This command deletes files/folders. ⚠️ Careful—there’s no recycle bin!

Once you delete a file in linux, it’s gone permanently unlike windows/mac. There’s no built-in "trash" the system doesn’t move it anywhere, it just erases the reference to it immediately.

Delete folders:

9) cat – View File Content

 This command displays text inside a file.

10) man – Manual Pages

  This command shows help and documentation for any command.

Press q to quit the manual.

📌 In Summary

These 10 beginner-friendly Linux commands are the foundation of working in the terminal. Once you’re comfortable with them, you can explore more advanced topics like file permissions, system processes, and package management.

Make sure you practice daily. The more you type these commands, the faster you know how to use them better.

DEV Community: Wireshark

What is AWS? AWS Cloud Computing for Beginners

What Is AWS?

Why Do People Use AWS?

1. No need to buy physical hardware

2. Pay-as-you-go pricing

3. High availability and reliability

4. Easy to scale

5. Secure by design

How Does AWS Works?

Most Popular AWS Services

1. EC2 — Virtual Servers

2. S3 — Storage

3. RDS — Managed Databases

4. IAM — Identity and Access Management

5. VPC — Virtual Private Cloud

6. Lambda — Serverless Functions

7. CloudWatch — Monitoring & Logs

How to Start Learning AWS

1. Create a Free AWS Account

2. Learn the core services

3. Do small projects

4. Explore DevOps Tools

Conclusion

Launch Your First S3 Bucket: An Easy, Practical Guide for Beginners

Core Concepts You Need Before You Start

Step-by-Step: Create Your First S3 Bucket

Step 1: Log in to AWS

Step 2: Navigate to S3

Step 3: Create a Bucket

How to Deploy a PostgreSQL Database on AWS RDS (Step-by-Step)

Prerequisites

Step 1: Navigate to Amazon RDS

Step 2: Create a New Database Instance

Step 3: Configure Database Settings

Step 4: Set Storage and Connectivity

Step 5: Launch and Test Connection

A Beginner’s Guide to AWS DynamoDB: Creating Your First Table

What is Amazon DynamoDB?

Prerequisites

Step 1: Navigate to DynamoDB

# ☁️ Cloud Engineer vs 🔄 DevOps Engineer: Which Path Should You Take?

👋 Introduction

🏗️ Understanding the Core Concepts

Cloud Engineer = Architect & Builder

DevOps Engineer = Manager & Automator

🛠️ Essential Skills & Tools

🔹 Cloud Engineer Skills

🔹 DevOps Engineer Skills

🚀 Career Growth

💡 Which One Should You Choose?

🎯 Final Thoughts

How to Create a Windows Server on AWS EC2 (Beginner’s Guide)

📝 Introduction

✅ Prerequisites

🚀 Step 1: Log in to AWS Console

🚀 Step 2: Launch an Instance

🚀 Step 3: Choose an Amazon Machine Image (AMI)

🚀 Step 4: Choose Instance Type

🚀 Step 5: Configure Key Pair

🚀 Step 6: Configure Network Settings

🚀 Step 7: Configure Storage

🚀 Step 8: Review & Launch

🚀 Step 9: Connect to Your Windows Server

🔧 What’s Next?

📝 Conclusion

🐧 Top 10 Linux Commands Every Beginner Must Know