luca gil - Cloud Infrastructure Architect | ContraWork by luca gil
luca gil

luca gil

Cloud & DevOps Engineer | AWS, Terraform & CI/CD

New to Contra

luca is building their profile!

Cover image for Multi-Environment Terraform CI/CD with GitLab
Role:
Cloud
Multi-Environment Terraform CI/CD with GitLab Role: Cloud & DevOps Engineer Description: Designed and implemented multi-environment GitLab CI/CD pipelines for deploying and managing AWS infrastructure with Terraform. Infrastructure changes were managed through version control and merge request workflows. Each pipeline executed automated Terraform formatting, initialisation, validation, and environment-specific planning before any changes could be deployed. The pipelines used isolated remote states and account-specific AWS credentials for different environments. Production deployments required manual approval, ensuring that every Terraform plan could be reviewed before applying infrastructure changes. This approach improved deployment consistency, reduced manual execution, isolated infrastructure environments, and provided a clear and auditable workflow for cloud infrastructure changes. Key contributions: • Created reusable GitLab CI/CD pipeline workflows • Automated Terraform formatting and validation • Generated environment-specific Terraform plans • Implemented isolated remote states and AWS credentials • Added manual approval gates for controlled deployments • Improved infrastructure deployment traceability Skills: CI/CD · Infrastructure as Code · DevOps Tools: GitLab CI/CD · Terraform · Amazon Web Services (AWS)
1
4
Cover image for Centralized Logging Pipeline with Fluent
Centralized Logging Pipeline with Fluent Bit on AWS Role: Cloud & DevOps Engineer Description: Designed and implemented a lightweight centralized logging pipeline for Ubuntu servers hosted on AWS. Fluent Bit agents were configured to collect system and service events from journald and syslog and forward them over HTTP to a central ingestion endpoint running on AWS infrastructure. The project included Fluent Bit YAML configuration, systemd service integration, automatic startup, connectivity testing, ingestion validation, and troubleshooting of configuration and service failures. The resulting pipeline provides centralized log visibility, improves production troubleshooting, and creates an extensible foundation for future dashboards, storage, and alerting capabilities. Skills: Observability · Log Management · DevOps Tools: Fluent Bit · Amazon Web Services (AWS) · Linux
1
10
Cover image for AWS IAM Security & Access
AWS IAM Security & Access Key Visibility Role: Cloud & DevOps Engineer Description: Designed and developed a read-only IAM visibility solution for inventorying AWS users and access keys across multiple accounts. The solution uses Python and boto3 to collect IAM metadata, a FastAPI backend to expose account and scan information, SQLite to maintain historical scan records, and a web dashboard to display account summaries, access key age, activity status, and potentially unused or critical keys. The AWS integration follows a least-privilege, read-only approach, providing security visibility without modifying IAM resources. The project also establishes a foundation for future alerting, reporting, and access key rotation workflows. Skills: Identity and Access Management · Cloud Security · Automation Tools: Amazon Web Services (AWS) · Python · FastAPI
0
12
Cover image for AWS Infrastructure Migration & Standardisation
AWS Infrastructure Migration & Standardisation with Terraform Role: Cloud & DevOps Engineer Project description: An end-to-end cloud infrastructure standardisation project focused on bringing an existing AWS environment under Terraform management. I imported running resources without recreation, reorganised the infrastructure into reusable Terraform modules and isolated remote states, and implemented GitLab CI/CD workflows for formatting, validation, planning, review, and controlled deployments. The project covered core AWS networking, compute, storage, IAM, security groups, and multi-region resources. The result was a more secure, repeatable, and auditable infrastructure workflow with consistent deployments and reduced manual configuration. Key contributions: • Imported existing AWS resources into Terraform safely • Developed and adopted reusable infrastructure modules • Implemented separate remote states for infrastructure components • Built GitLab CI/CD workflows for validation, planning, and deployment • Standardised multi-account and multi-region infrastructure • Improved security, consistency, and deployment control Skills and tools: AWS, Terraform, GitLab CI/CD, Infrastructure as Code, IAM, VPC, EC2, S3, Git, Bash, Cloud Security
1
18