devops-infra

Provide infrastructure and DevOps guidance for Docker, AWS, Kubernetes, CI/CD, and messaging systems.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill devops-infra-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-infra
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/devops-infra
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill devops-infra-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces the risk, toil, and uncertainty of designing, deploying, and operating containerized and cloud infrastructure by providing concrete best practices, architecture patterns, and pipeline templates that enforce reliability, security, and cost efficiency.

Core Features & Use Cases

  • Docker & Containerization: Guidance for multi-stage builds, non-root containers, health checks, .dockerignore optimization, and image scanning for production readiness.
  • AWS Architecture & Infrastructure: Opinionated patterns for ECS/Fargate, Lambda, VPC design, RDS and caching, storage lifecycle, and cost-aware instance selection.
  • CI/CD & Deployment Strategy: Complete GitHub Actions pipeline patterns for test, security scans, image build/push, canary and full rollouts, and automated rollback on failed health checks.
  • Messaging & Reliability: Kafka partitioning and replication decisions, SNS→SQS fan-out, DLQ handling, visibility timeouts, idempotency strategies, and retry/backoff patterns.
  • Monitoring & Observability: Metrics, logs, and tracing priorities with thresholds, alerts, and runbook-oriented checks for operational excellence.
  • Use Case: Use this Skill to review a Dockerfile and GitHub Actions workflow, produce a hardened production pipeline that scans images and deploys a 10% canary to ECS with automatic rollback, and design messaging DLQs and idempotency for reliable background processing.

Quick Start

Generate a production-ready GitHub Actions workflow that builds and scans a Docker image, deploys a 10% canary to ECS, monitors health checks for five minutes, and automatically rolls back on failure.

Frequently Asked Questions about devops-infra

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a production-ready GitHub Actions workflow for ECS canary deployments?

A production-ready GitHub Actions workflow for ECS deploys a 10% canary, monitors health checks for five minutes, and automatically rolls back on failure. It includes stages for testing, security scans, and Docker image building.

What are the best practices for securing Docker containers in production?

Securing Docker containers in production requires multi-stage builds, non-root user execution, health checks, and .dockerignore optimization. Production readiness also mandates automated image scanning within your CI/CD pipeline.

How do I design SNS to SQS fan-out with Dead Letter Queue handling?

SNS to SQS fan-out with Dead Letter Queue handling requires configuring visibility timeouts, idempotency strategies, and retry/backoff patterns. DLQ handling captures failed messages to ensure reliable background processing.

What is needed for a secure AWS VPC and autoscaling architecture?

A secure AWS VPC and autoscaling architecture needs opinionated patterns for ECS/Fargate, Lambda, RDS caching, and storage lifecycle. Cost-aware instance selection ensures efficient scaling and operational reliability.

How do I configure monitoring alerts and tracing for Kubernetes?

Configuring monitoring alerts and tracing for Kubernetes involves prioritizing metrics, logs, and tracing thresholds. It establishes alert routing and runbook-oriented checks to achieve operational excellence and observability.

Does this DevOps guidance include Kafka partitioning and replication strategies?

This DevOps guidance includes Kafka partitioning and replication decisions for messaging reliability. It pairs these decisions with SNS to SQS fan-out, visibility timeouts, and idempotency strategies for robust background processing.