[ayushcmd]

Summary

Documents the completed CloudMonitor SSH-to-SSM migration and the AWS/GitHub setup used for production delivery.

Documentation changes

• Add docs/AWS_IAM_OIDC_SSM_PRODUCTION_SETUP.md with button-by-button AWS Console instructions for the EC2 instance role, SSM Agent/Fleet Manager, GitHub OIDC provider, GitHub deployment role, trust policy, least-privilege inline SSM policy, GitHub production Environment, workflow operations, first-host Git bootstrap, backup, verification, rollback boundaries and troubleshooting.
• Update docs/SSM_DEPLOYMENT_MIGRATION.md to reflect the completed Issue [DevOps] Migrate EC2 deployment from SSH to AWS Systems Manager #9 outcome and verified acceptance criteria.
• Update docs/CICD_SETUP_GUIDE.md to describe the current manual SSM/OIDC CD workflow rather than the retired SSH-based runner deployment.
• Update docs/AWS_DEPLOYMENT_AND_OPERATIONS.md so its deployment status and CI/CD runbook match the verified SSM production path.

Verified production facts documented

• Deployed commit: f536dad97518a761c12b83ff578ff3194e9ed04f
• Frontend HTTP 200 and backend healthy.
• PostgreSQL healthy; named volume cloudmonitor-prod_postgres_data preserved.
• Required Prometheus targets all reported up.
• CD remains manual-only via workflow_dispatch; deploy/rollback require explicit confirmation.

Safety

• Documentation-only change; no application source, workflow, IAM resource, GitHub Environment variable, AWS infrastructure or production configuration changed.
• No credentials, private keys or production secret values are added.
• No deployment will be triggered by this PR because the SSM CD workflow is manual-only.

Issue #9 was closed as completed after the successful SSM production deployment. Issue #12 remains open for broader production security work, including HTTPS/TLS and remaining telemetry/container hardening.