Skill

devops-platform-patterns

Platform-specific IaC checklists for DigitalOcean, Hetzner, AWS, and Cloudflare.

From majestic-devops
Install
1
Run in your terminal
$
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-devops
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

DevOps Platform Patterns

Platform-specific verification checklists for infrastructure code.

DigitalOcean

CheckPassFail
VPC used for private networkingPrivate network configuredPublic networking only
Reserved IPs for productionStatic IPs assignedEphemeral IPs for critical services
Managed database in same regionCo-located DBCross-region latency
Spaces for state backendRemote state in SpacesLocal state only
Firewall attached to all dropletsFirewall rules appliedNo firewall

Best Practices:

  • Use digitalocean_vpc for internal communication
  • Attach firewalls via digitalocean_firewall with inbound rules
  • Store Terraform state in DigitalOcean Spaces with versioning

Hetzner

CheckPassFail
Private network configuredNetwork createdNo private networking
Firewall rules definedRules restrict accessOpen to internet
SSH keys managed via resourcehcloud_ssh_key usedKeys in user_data only
Placement groups for HAServers distributedSingle point of failure

Best Practices:

  • Use hcloud_network + hcloud_network_subnet for internal traffic
  • Apply hcloud_firewall to all servers
  • Use placement groups with spread type for critical workloads

AWS

CheckPassFail
VPC with private subnetsMulti-AZ VPCDefault VPC usage
Security groups least-privilegeSpecific ports/IPs0.0.0.0/0 ingress
IAM roles over access keysInstance profilesHardcoded credentials
KMS encryption for dataCustomer-managed keysNo encryption
CloudTrail enabledAudit logging onNo audit trail

Best Practices:

  • Never use default VPC for production
  • Prefer aws_iam_role with instance profiles over access keys
  • Enable S3 bucket versioning and encryption by default
  • Use aws_kms_key for sensitive data encryption

Cloudflare

CheckPassFail
API tokens over global keyScoped tokensGlobal API key
WAF rules configuredProtection enabledNo WAF
SSL mode is strictFull (strict) modeFlexible SSL
Rate limiting on endpointsRules appliedNo rate limiting

Best Practices:

  • Create scoped API tokens per environment/purpose
  • Set SSL mode to strict for origin protection
  • Apply rate limiting to authentication endpoints
  • Enable Bot Management if available

Cross-Platform Checks

CheckApplies ToVerification
Private networkingAllInternal services not exposed
Firewall/security groupsAllExplicit allow rules only
State backend remoteAllNot in local tfstate
Encryption at restAllData encrypted
Audit loggingAWS, CloudflareActivity tracked
Stats
Parent Repo Stars31
Parent Repo Forks6
Last CommitFeb 15, 2026