The complete checklist for containerisation : what to verify before, during, and after | clickmasters: what to verify before starting, during development, before launch, and after launch. Every item is specific and binary it is done or it is not.
Real-time completion tracker
Start completing tasks to track your progress.

The complete checklist for containerisation: what to verify before starting, during development, before launch, and after launch. Every item is specific and binary it is done or it is not. No ambiguity, no interpretation required.
All infrastructure defined in Terraform or CDK (no console-only resources)
Resource tagging policy applied (Project, Environment, Owner, CostCentre)
CloudTrail enabled in all regions
AWS Security Hub enabled with CIS Benchmark findings reviewed
GuardDuty enabled
No IAM users with console access and no MFA
No security groups with 0.0.0.0/0 inbound on port 22 or 3389
S3 buckets: Block Public Access enabled at account level
RDS instances: encryption at rest enabled, no public accessibility
Secrets in AWS Secrets Manager (not environment variables or .env files)
VPC: private subnets for application and database tiers
AWS Budgets configured with alert at 80% and 100% of monthly target
GitHub Actions (or equivalent) running on every PR
Automated tests running in CI and blocking merge on failure
Snyk or Dependabot configured for dependency CVE scanning
GitHub secret scanning enabled
Deployment to staging automated on merge to main
Deployment to production requires manual approval gate
Rollback procedure documented and tested
All acceptance criteria verified by ClickMasters QA in staging
End-to-end tests passing in CI for all critical user journeys
Load test at 2x expected peak: P95 < 500ms, error rate < 1%
OWASP Top 10 review: no critical or high severity findings open
All environment variables set in production (not copied from dev)
Database backups enabled and tested (restore to staging verified)
SSL certificate installed and renewing automatically
Error tracking (Sentry) configured and receiving events from staging
Analytics events verified firing in staging before production deploy
Feature flags configured for all new user-facing features
Monitoring alerts configured (error rate, P95 latency, disk, memory)
On-call rotation defined for launch week
CloudWatch dashboard with P95 latency, error rate, database connections
Auto-scaling configured and tested (verified scales up on load)
Multi-AZ deployment for production workloads (not single-AZ)
Industry-standard compliance and best practice implementation.
Industry-standard compliance and best practice implementation.
Industry-standard compliance and best practice implementation.
Industry-standard compliance and best practice implementation.
ClickMasters runs this checklist on every engagement. Fixed-price.