AWS Rhyming Game Contest – Exploring Amazon Kinesis

kish — Wed, 16 Sep 2026 01:22:01 +0000

1. Introduction

As part of the Rhyming Game Contest, I was asked to search for an AWS service starting with the first letter of my name.

My first letter is K, so I searched for AWS services beginning with the letter K.

The AWS service I selected is Amazon Kinesis.

2. Selected AWS Service

Amazon Kinesis

Amazon Kinesis is an AWS service used to collect, process, and analyze real-time streaming data.

It can handle streaming data from thousands of sources and process the data with low latency.

3. Why I Selected Kinesis

I selected Amazon Kinesis because:

It starts with the letter K.
It is an official AWS service.
It supports real-time data streaming.
It has practical applications in monitoring, analytics, IoT, and fraud detection.
It can be explored through the AWS Management Console.

4. Accessing Amazon Kinesis

Step 1: Open AWS Management Console

I opened the AWS Management Console and signed in to my AWS account.

Screenshot 1: AWS Management Console

Step 2: Search for Kinesis

In the AWS Console search bar, I searched for:

Kinesis

The search results displayed Amazon Kinesis.

Screenshot 2: Searching for Kinesis in AWS Console

Step 3: Open Amazon Kinesis

I selected Amazon Kinesis from the search results.

Screenshot 3: Amazon Kinesis Console

5. Understanding Amazon Kinesis

Amazon Kinesis can be used to collect, process, and analyze streaming data in real time.

For example, streaming data can come from:

IoT devices
Application logs
Website activity
Monitoring systems
Real-time analytics applications

6. Real-World Example

Consider an online shopping application.

When thousands of customers browse products simultaneously, the application can generate a continuous stream of activity data.

Amazon Kinesis can collect this streaming data and allow applications to process it in real time.

This can help organizations monitor application activity and generate real-time insights.

7. AWS Service Verification

The selected service is officially provided by Amazon Web Services and is named Amazon Kinesis.

The official AWS documentation describes Kinesis as a service for collecting, processing, and analyzing real-time video and data streams.

8. Conclusion

Through this activity, I searched AWS for a service beginning with the first letter of my name.

My selected letter was K, and the AWS service I selected was Amazon Kinesis.

This activity helped me explore an AWS service and understand how cloud platforms can process real-time streaming data.

9. References

Amazon Kinesis – AWS Official Website
AWS Documentation – Amazon Kinesis

Day 1- Deploying My Portfolio with AWS S3 and CloudFront on Cloud Workshop

kish — Tue, 15 Sep 2026 06:58:19 +0000

Deploying My React Portfolio on AWS S3 and Exploring CloudFront

I recently built a basic portfolio website using React and decided to deploy it using Amazon Web Services (AWS).

This was my first hands-on experience deploying a frontend application using AWS services. Instead of stopping at the development stage, I wanted to understand how a website can be hosted using cloud infrastructure.

For this deployment, I worked with Amazon S3 and attempted to configure Amazon CloudFront.

My Portfolio

The portfolio was developed using:

React
JavaScript
HTML
CSS
Vite

It contains sections for:

About Me
Skills
Projects
Contact

After completing the React application, I generated the production files using:

npm run build

The generated files were available in the dist folder.

Step 1: Creating an S3 Bucket

The first step was creating an Amazon S3 bucket for my portfolio.

After creating the bucket, I uploaded the website files into it.

The main file was:

index.html

Along with the other required website assets.

The basic structure was:

S3 Bucket
│
├── index.html
├── assets/
└── other files

Step 2: Configuring Static Website Hosting

After uploading the files, I configured the bucket for static website hosting.

I specified:

Index document:
index.html

This tells S3 which HTML file should be loaded as the main page of the website.

Step 3: Configuring Access

I then worked through the S3 access and permission settings required to make the static website accessible.

This was one of the useful parts of the process because it made me understand that simply uploading a file to S3 does not automatically make it available to everyone.

There are separate considerations for:

Bucket access
Object permissions
Static website hosting
Public access settings
Security policies

After configuring the required settings, I was able to work with the S3-hosted version of my portfolio.

Step 4: Trying Amazon CloudFront

The next step was to add Amazon CloudFront.

The architecture I wanted to create was:

                User
                  │
                  ▼
          Amazon CloudFront
                  │
                  ▼
              Amazon S3
                  │
                  ▼
          React Portfolio

CloudFront acts as a CDN and can distribute website content through AWS edge locations.

I wanted to use it as the delivery layer in front of my S3-hosted portfolio.

The CloudFront Problem

While creating the CloudFront resource, I encountered an AWS account-level verification error.

AWS displayed the following message:

"Your account must be verified before you can add new CloudFront resources."

So, at this stage, CloudFront deployment was not completed.

This was actually an important part of the learning experience.

I initially thought deploying a website would simply be:

Write Code → Upload Files → Website Online

But the process also involves:

Application
    ↓
Build
    ↓
Cloud Storage
    ↓
Permissions
    ↓
Service Configuration
    ↓
Account Verification
    ↓
CDN / Delivery
    ↓
Production Website

What I Learned

This small project helped me understand several AWS concepts practically.

Amazon S3

I learned how S3 can be used to store and serve static website files.

Static Website Hosting

I learned how an index.html file can be configured as the entry point for a static website.

Permissions

I learned that storage, website hosting, and access permissions are separate configuration areas.

CloudFront

I learned the role of CloudFront as a CDN in front of an S3-based website, even though I could not complete the CloudFront deployment because of the account verification restriction.

Cloud Deployment

Most importantly, I learned that deploying an application involves more than writing code. Cloud services have their own account requirements, permissions, security configurations, and service restrictions.

Current Architecture

The part I successfully configured was:

React Portfolio
       │
       ▼
   npm run build
       │
       ▼
    index.html
       │
       ▼
    Amazon S3

The architecture I am working toward is:

                    User
                     │
                     ▼
             Amazon CloudFront
                     │
                     ▼
                 Amazon S3
                     │
                     ▼
             React Portfolio

Next Step

My next step is to resolve the AWS account verification issue and complete the CloudFront configuration.

This started as a simple portfolio deployment, but it gave me practical exposure to React deployment, Amazon S3, static website hosting, permissions, CDN concepts, and AWS account configuration.

It is a small project, but it was a useful first step into cloud deployment.

react #aws #amazonS3 #cloudfront #javascript #webdevelopment #cloud #devops #learning

DEV Community: kish