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.

  1. LinuxStructured sysadmin training on the LEMP stack, reverse proxying, SSL, backups, log monitoring and mail servers, plus Fail2Ban and SSH hardening on a live EC2 server.
  2. AWSHands-on work with IAM, EC2, S3, CloudFront and RDS, including a custom VPC with public and private subnets, Multi-AZ failover and read replicas.
  3. ProjectsSelf-directed projects (a serverless file storage app, CloudLens and this website) alongside prompt engineering coursework.

Beyond the desk

A weekly AWS exam kept the learning honest. Around it there was the Onam celebration, games of billiards, table soccer and carrom, and turf football on weekends. It was a good three months.

  • Weekly exams
  • Onam
  • Billiards
  • Table soccer
  • Carrom
  • Turf football

How this site was built

  1. Create a private S3 bucketUploaded index.html, error.html and style.css to the bucket root, with Block all public access left on.
  2. Register the domainBought iamkrishnasai.click in Route 53, which created the hosted zone automatically. Verified the contact email.
  3. Request an SSL certificateRequested a public certificate in AWS Certificate Manager in us-east-1, validated it with DNS records created in Route 53, and waited for the status to show Issued.
  4. Create the CloudFront distributionUsed the S3 bucket as the origin with Origin Access Control, added the domain as an alternate domain name, attached the certificate, and set index.html as the default root object.
  5. Lock down the bucketApplied a bucket policy that lets only this CloudFront distribution read the files, so the bucket is never public.
  6. Point the domain to CloudFrontCreated an A alias record in Route 53 that sends the domain to the distribution.
  7. Test itOpened the site over HTTPS on the cloudfront.net address first, then on the custom domain.

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.