Ryan Paredes

DevOps & SRE Engineer specializing in cloud infrastructure, CI/CD automation, and infrastructure as code. Building reliable systems on AWS.

Skills & Tools

Core technologies I work with daily

☁️ AWS
πŸ—οΈ Terraform
🐳 Docker
⎈ Kubernetes
βš™οΈ GitHub Actions
🐍 Python
🐧 Linux
πŸ“Š Monitoring
πŸ”„ CI/CD
πŸ“ IaC
🌐 Networking
πŸ”’ Security

Projects

Infrastructure and automation work

PersonalSite

Live

This site β€” a fully automated portfolio deployed to AWS via GitHub Actions. Infrastructure managed with Terraform, security scanning with Trivy, and built with Astro + Tailwind CSS.

AWSTerraformGitHub ActionsAstroS3CloudFront
View on GitHub β†’

More projects coming soon

CI/CD Pipeline

How this site gets built and deployed β€” fully automated with GitHub Actions

πŸ” Lint Terraform fmt + Astro check
πŸ›‘οΈ Scan Trivy IaC & dependency scan
πŸ”¨ Build Astro static site build
πŸš€ Deploy Dev S3 sync to dev bucket
βœ… Deploy Prod Approval gate + S3 sync

Pipeline Details

  • βœ“ Lint: Terraform files validated with terraform fmt -check and site checked with astro check
  • βœ“ Security Scan: Trivy scans IaC for misconfigurations and dependencies for known CVEs (pinned version to avoid supply-chain risk)
  • βœ“ Build: Astro generates optimized static HTML/CSS/JS with zero JavaScript shipped to the client by default
  • βœ“ Deploy Dev: Built artifacts synced to S3 dev bucket automatically on push to main
  • βœ“ Deploy Prod: GitHub Environment protection rules require manual approval before syncing to the production S3 bucket behind CloudFront
  • βœ“ Secrets: gitleaks pre-commit hooks + CI scanning prevent accidental credential leaks

Architecture

AWS infrastructure powering this site

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚            β”‚     β”‚              β”‚     β”‚            β”‚
β”‚  Route 53  │────▢│  CloudFront  │────▢│  S3 Bucket β”‚
β”‚  (DNS)     β”‚     β”‚  (CDN+TLS)   β”‚     β”‚  (Static)  β”‚
β”‚            β”‚     β”‚              β”‚     β”‚            β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
       β”‚                  β”‚
       β”‚           β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
       β”‚           β”‚     ACM      β”‚
       └──────────▢│ (TLS Cert)   β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

All infrastructure defined as Terraform modules β€” see the repo for full source.

Built with AI

How AI-assisted development shaped this project

πŸ€–

Planning & Architecture

AI pair programming was used to evaluate technology choices, create architecture decision records, and develop the security playbook for going public.

πŸ’»

Code Generation

Frontend components, Terraform modules, and GitHub Actions workflows were scaffolded with AI assistance using GitHub Copilot, then reviewed and customized.

πŸ”’

Security Review

AI-assisted auditing identified exposed secrets in the legacy codebase and recommended OIDC federation, pre-commit hooks, and pinned dependency versions.

Full details in the project's AI_DEVELOPMENT.md

Ongoing Security & Maintenance

How this project stays secure and up to date β€” DevSecOps practices baked in

πŸ”„

Automated Updates

Dependabot monitors three ecosystems weekly: npm packages, Terraform providers, and GitHub Actions versions. PRs are auto-created and must pass CI before merge.

πŸ›‘οΈ

Continuous Scanning

Every push runs Trivy for IaC misconfigurations and dependency CVEs, plus gitleaks for secrets detection. Critical and high findings block deployment.

πŸ“Œ

Supply Chain Integrity

All GitHub Actions are pinned to full SHA (not tags). npm uses lockfiles with npm ci for reproducible builds. Trivy is version-pinned to prevent auto-update supply chain attacks.

πŸ“‹

Review Cadence

Weekly: review Dependabot PRs and security alerts. Quarterly: full manual audit, credential rotation, and tooling version review. All documented in the repo's MAINTENANCE.md.