Krishnasai

Cloud and DevOps graduate. I completed a 3-month CloudOps internship at EPI-USE, and I build and deploy things on AWS.

Download my CV

Projects

  • Serverless file storageUpload, download and share files with S3, Lambda, API Gateway, DynamoDB and Cognito.
  • Portfolio website on AWSThis site, hosted on S3 and served over HTTPS through CloudFront on my own Route 53 domain.
  • CloudLensScans an AWS account, uses Amazon Bedrock to flag likely exam leftovers, analyses cost, and emails a PDF report. Read-only: it reports and never deletes.

Days in EPI-USE

I joined EPI-USE as a CloudOps intern in July 2026 and spent three months there. Here is how they went.

Month 1: Linux and DevOps

One month. Countless commands. Many errors. And even more learning. It was about learning by doing: experimenting, troubleshooting and understanding how systems work behind the scenes.

What I explored

  • Linux system administration and filesystem
  • Users, groups and permissions
  • Bash scripting and automation
  • Process and disk management
  • LVM, swap and cron jobs
  • Networking, IP addressing and subnetting
  • DNS and BIND
  • Firewalls: UFW and iptables
  • LAMP/LEMP stack and WordPress
  • Nginx, Apache and SSL
  • MySQL/MariaDB and backup management

The biggest lesson: troubleshooting is not about avoiding errors, it's about understanding them. Every error became a chance to ask what happened, why it happened and how to fix it.

Month 2: AWS and cloud

One phase. Dozens of AWS services. Real resources launched, broken, fixed and cleaned up. I built on the cloud every day, with hands-on tasks and regular exams to test what I learned.

What I explored

  • AWS global infrastructure, IAM users, groups, roles and policies
  • EC2: launch, SSH, User Data and pricing models
  • EBS and EFS storage
  • Elastic Load Balancing and Auto Scaling
  • S3: versioning, lifecycle, encryption and replication
  • CloudFront static website delivery
  • VPC: subnets, route tables, Internet Gateway, NAT, NACLs vs Security Groups, peering and Flow Logs
  • RDS MySQL, Multi-AZ failover and Read Replicas
  • DynamoDB and ElastiCache (Redis)
  • Security: GuardDuty, WAF, Security Hub, Inspector, Macie and Secrets Manager
  • Monitoring: CloudWatch, CloudTrail and AWS Config
  • Containers with ECS and Fargate
  • Serverless: Lambda and API Gateway to Lambda to DynamoDB

What I built

  • A serverless cloud file storage app with S3, Lambda, API Gateway, DynamoDB and Cognito
  • This portfolio website on S3 and CloudFront, with a custom Route 53 domain and HTTPS
  • CloudLens, an AI-powered tool that detects AWS resources, analyses their cost using Amazon Bedrock, and emails a PDF report

Month 3: Projects and AI

I applied my AWS and AI skills to self-directed projects, alongside coursework in prompt engineering.

Beyond the desk

Life at EPI-USE was never only about the screen. Every week brought an AWS exam that pushed me to learn a little more, and every break brought something to look forward to: a quick game of billiards, a lively round of table soccer, or a careful turn at carrom. Onam filled the days with flowers, music and laughter, and on weekends we headed to the turf for football. These are the days I'll remember the longest.

Thank you to EPI-USE and my mentors for the platform, the guidance and the support throughout this journey.

Collage of memories from EPI-USE: Onam celebrations, the team, the game room and my intern badge

About

I completed my internship at EPI-USE, where I learned AWS and Linux system administration through hands-on projects. This site is hosted on S3 and served through CloudFront.

  • S3
  • CloudFront
  • Lambda
  • DynamoDB
  • Route 53
  • ACM
  • Linux

Contact

Email me at krishnasaiii2you@gmail.com or find me on GitHub. My CV is here as a PDF.