Krishnakumar Ambily

I assisted one of the data centers in migrating more than 500 physical servers into OpenVZ and KVM VMs to reduce the infrastructure cost. I also implemented configuration management using Ansible scripts for the smooth management of VMs.

I designed and deployed a highly available, fault-tolerant, and cost-effective infrastructure for a worldwide prosperity-index website, using AWS EC2 instances, Elastic Load Balancers, Auto Scaling, AWS S3 buckets, and AWS RDS.

I configured and managed client nodes on cloud providers like AWS, GCE, DigitalOcean, Linode, and Vultr. I installed a Stellar test network and configured the Stellar core, bridge, and compliance servers. I also installed, configured, and managed an on-premise Atlassian stack for this project, consisting of Jira, Confluence, Bitbucket, and the Crowd server.

I designed, configured, and managed AWS infrastructure for an eCommerce firm. I also configured the development and production environment for the development team.

Technologies:
• The website works on Magento and is hosted on an AWS EC2 instance.
• RDS is used for the database, and Cloudflare is used for DNS and CDN management.
• AWS billing was optimized according to the client's budget.
• EC2 servers are configured for Magento hosting.
• RDS is configured with a multi-availability zone to eliminate single-point failures.
• DNS records are configured using Cloudflare.
• Cloudflare CDN is configured to serve static files.

I designed, configured, and managed AWS infrastructure for a mobile game project. I also configured the development, staging, and production environments to help the development team.

Technologies:
• The project is configured using EC2 instances to host a Laravel application and RDS as a database.
• ElasticCache (Redis) is used to eliminate the bottleneck of reading and writing data from a relational database.
• Redis's lazy loading strategy is used to improve the read queries, and the write-through strategy is used to improve the DB write queries.
• EC2 servers are configured with auto scale-in and scale-out policies to handle massive traffic and eliminate single-point failures.
• S3 bucket is used to store static files.
• RDS is configured with a multi-availability zone, and reading replicas to handle the traffic and eliminate single-point failures.
• An Elastic Load Balancer is used to distribute traffic among multiple servers.
• GitLab is used for version control.
• Gitlab CI/CD is used for automatic and hassle-free deployment to development, staging, and production environments.
• AWS Route 53 is used for DNS management.

I designed a fault-tolerant, highly available, and secure three-tier infrastructure on AWS using EC2, ELB, CloudFront, S3, and RDS master-slave replication. I also automated the whole infrastructure using Terraform, Packer, and Jenkins.

In addition to designing, configuring, and managing the project, I configured the development and production environments to help the development team. The project was configured with the Wowza cloud platform for video streaming and AWS infrastructure to host their application developed in PHP's CodeIgniter framework. Wowza's cloud is configured to store live streams in the AWS S3 bucket and serve as VOD content once the live streaming is completed.

Configuration details:
• Wowza cloud stores VOD files on the S3 bucket.
• S3 permission protects the VoD content.
• An EC2 instance hosts the application using PHP's CodeIgniter framework.
• EC2 servers with auto scale-in and scale-out policies handle huge traffic and eliminate single-point failures.
• RDS with a multi-availability zone and reading replicas handle the traffic and eliminate single-point failures.
• An Elastic Load Balancer is used to distribute traffic among multiple servers.
• AWS Route 53 is used for DNS management.

Configured CF in front of the WordPress website to handle more connections without increasing computing resources and improving website performance.

AWS Web Application Firewall (WAF) was configured with CloudFront to block MySQL injection and malicious requests.

Technologies Used

• AWS CloudFront to cache WordPress static files.
• Integrated WordPress with CloudFront and Varnish.
• Configured Varnish to cache static files at the server-side.
• Configured WAF rules to prevent PHP and WordPress attacks.