AWS DevOps & Cloud Infrastructure Portfolio Project

Build an AWS Cloud Engineer Portfolio Project Using Terraform, EKS, GitOps, and Monitoring Project Overview I am looking for an experienced AWS Cloud/DevOps Engineer to help me build a professional, portfolio-ready cloud infrastructure project that demonstrates real-world Cloud Engineer skills. The project should follow industry best practices and include Infrastructure as Code, Kubernetes deployment, CI/CD automation, monitoring, security, and troubleshooting documentation. This is primarily a cloud infrastructure and automation project, not an application development project. I prefer minimal custom coding and want the infrastructure and configuration to be easy to understand and explain in technical interviews. Project Requirements 1. AWS Infrastructure with Terraform Create a VPC with public and private subnets across multiple Availability Zones. Configure networking, routing, and security groups. Provision an Amazon EKS Kubernetes cluster and the required IAM roles. Configure Amazon ECR for container image storage. Organize Terraform code into reusable, well-documented modules. Configure remote Terraform state storage and state locking using a currently supported approach. Provide clear deployment and teardown instructions. 2. CI/CD and GitOps Automation Set up a GitHub repository with a clear project structure. Use GitHub Actions to validate Terraform configuration and run formatting and security checks. Configure secure AWS authentication using GitHub OIDC rather than long-lived AWS access keys. Set up Argo CD to deploy a sample application to EKS. Demonstrate how application changes are deployed through GitOps. Include a working deployment pipeline and explain how each stage works. 3. Kubernetes Deployment and Operations Deploy a simple containerized application, such as Nginx. Configure Kubernetes Deployments, Services, health checks, and resource requests and limits. Demonstrate scaling and basic workload management. Include an example of a failed deployment and show how to troubleshoot and recover from it. 4. Monitoring and Observability Set up Prometheus and Grafana, or a suitable AWS-managed alternative if appropriate. Configure dashboards for CPU, memory, pod restarts, and application health. Demonstrate how to identify a problem and investigate it using monitoring data. Provide screenshots of the working dashboards. 5. Security and Best Practices Follow least-privilege IAM principles. Avoid hard-coded credentials and secrets in the repository. Configure encryption and appropriate access controls. Include Terraform validation and infrastructure security scanning. Document key security decisions and any known limitations. 6. Documentation and Knowledge Transfer Documentation is a major deliverable. Please include: A clear README with the architecture and project objectives. An AWS architecture diagram. Step-by-step setup and deployment instructions. Explanation of the important Terraform files and modules. Explanation of the GitHub Actions and Argo CD workflows. Troubleshooting steps for common failures. Instructions for scaling, recovering from a failed deployment, and destroying resources. Screenshots or a short recorded walkthrough of the completed project. A live knowledge-transfer session so I can understand the project and explain it in interviews. Required Deliverables Complete source code in a GitHub repository that I can access and maintain. Terraform configuration files and supporting Kubernetes manifests. Working CI/CD and GitOps configuration. Monitoring dashboards and configuration. Architecture diagram and comprehensive README. Deployment, testing, troubleshooting, and cleanup documentation. A recorded demonstration or walkthrough. A live handover session with time for questions. A list of all AWS resources created, estimated running costs, and cleanup instructions. Acceptance Criteria The project will be considered complete when: Terraform configuration passes formatting and validation checks. The infrastructure can be deployed using the documented process. The EKS cluster and sample application are operational. The GitHub Actions workflow runs successfully. Argo CD can deploy an application change. Monitoring dashboards display relevant metrics. A failed deployment can be diagnosed and recovered from. Infrastructure can be destroyed using the documented cleanup procedure. I receive the source code, documentation, and knowledge-transfer session. Please demonstrate the project in a test environment. Do not claim that components are working unless they have been tested. Required Experience Please apply only if you have hands-on experience with: AWS, especially VPC, IAM, EKS, and ECR Terraform and Infrastructure as Code Kubernetes and Helm GitHub Actions or another CI/CD platform Argo CD and GitOps Prometheus and Grafana Cloud security and infrastructure troubleshooting Proposal Requirements In your proposal, please provide: Links to two relevant projects you have personally implemented. Your experience with AWS, Terraform, EKS, Argo CD, and GitHub Actions. Your proposed architecture and implementation plan. A fixed-price quote broken down by milestones. An estimated completion timeline. What is included in the handover and knowledge-transfer session. Any additional AWS costs I should expect. Please build the project in a way that prioritizes clarity, maintainability, security, and learning—not just getting it to work.