Idigicode

Cloud Architect

Amaris • Freelance

Oct 2025 - Nov 2025 • 1 mo

What I worked on: • Designed and reviewed AWS infrastructure using custom VPCs. • Implemented public and private subnets with proper route table associations. • Configured Internet Gateway for controlled public access. • Launched EC2 instances with security groups and IAM role-based access. • Ensured network isolation and secure traffic flow following AWS best practices. Alongside compute and networking, I also worked with AWS-managed data and storage services, including: • Amazon S3 — for object storage and application data. • Amazon DynamoDB — for serverless NoSQL workloads. • Amazon RDS — deployed within a dedicated VPC for database isolation and security.

DevOps Engineer

Idigi • Freelance

May 2024 - Nov 2024 • 6 mos

𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝗖𝗜/𝗖𝗗 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝘄𝗶𝘁𝗵 𝗝𝗲𝗻𝗸𝗶𝗻𝘀, 𝗚𝗶𝘁𝗛𝘂𝗯 & 𝗗𝗼𝗰𝗸𝗲𝗿 (𝗩𝗲𝗿𝘀𝗶𝗼𝗻𝗶𝗻𝗴 + 𝗥𝗼𝗹𝗹𝗯𝗮𝗰𝗸): This led to the design and implementation of a complete CI/CD pipeline using Jenkins, GitHub, and Docker, with built-in versioning and rollback to support real-world deployment scenarios. • Designed an end-to-end CI/CD pipeline using Jenkins and GitHub, triggered automatically on every code push. • Dockerized a Node.js web application with a functional dashboard UI and API endpoints. • Created a private Docker Hub repository to centrally store and manage versioned application images. • Integrated Docker Hub authentication via Jenkins Credentials Manager to securely push and pull images. • Implemented Docker image versioning using semantic tags (v1.0, v2.0, v45) to enable traceability and controlled releases. • Automated deployments across multiple EC2 instances using Docker with dynamic port mapping. • Enabled controlled rollback by redeploying any previous Docker image version from Docker Hub when required. • Automated Docker installation and configuration on EC2 instances as part of the deployment workflow. • Applied a zero-downtime deployment approach by cleanly replacing running containers during releases. • Demonstrated the full delivery sequence: code commit → build → image push → pull → deployment → live application. Outcome: This setup establishes a scalable delivery foundation where application releases are predictable, versioned, and reversible — a critical requirement for larger systems and enterprise environments.

Consultant Engineer

Amaris tech • Freelance

Apr 2024 - May 2024 • 1 mo

Its one of my projects: (for more info please write me) 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺 – 𝗙𝗿𝗼𝗺 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝘁𝗼 𝗦𝗰𝗮𝗹𝗮𝗯𝗹𝗲 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁: After designing the AWS infrastructure foundation, I automated the environment using Terraform and extended it to support scalable, multi-EC2 deployments with automated configuration. The focus was not only on provisioning resources, but also on ensuring that instances were deployment-ready immediately after creation. • Automated provisioning of multiple EC2 instances using Terraform. • Defined AMI, instance family, subnets, and security groups as code. • Deployed EC2 instances across subnets to support scalability. • Applied configuration directly from main.tf to bootstrap instances. • Automated Docker installation on all EC2 instances during provisioning. • Ensured consistent configuration across environments without manual access. 𝗧𝗵𝗶𝘀 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 𝗲𝗹𝗶𝗺𝗶𝗻𝗮𝘁𝗲𝗱 𝗽𝗼𝘀𝘁-𝗹𝗮𝘂𝗻𝗰𝗵 𝗺𝗮𝗻𝘂𝗮𝗹 𝘀𝗲𝘁𝘂𝗽 𝗮𝗻𝗱 𝗲𝗻𝗮𝗯𝗹𝗲𝗱 𝗮 𝗿𝗲𝗽𝗲𝗮𝘁𝗮𝗯𝗹𝗲, 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻-𝗿𝗲𝗮𝗱𝘆 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲. • Infrastructure created and managed entirely via code. • Consistent EC2 configuration across multiple instances. • Faster readiness for containerized workloads. • Reduced configuration drift and operational overhead. This automated infrastructure now serves as a solid base for CI/CD pipelines, containerized deployments, and monitoring.