Magenta Domain Change Summary

Change Overview

Updated all references from analytics.comma.cm to magenta.comma.cm to align the domain name with the service name.

Files Updated

Documentation

• /docs/analytics-cleanup-summary.md
• /docs/magenta-installation-guide.md

Scripts

• /scripts/EMERGENCY-REMOVE-ANALYTICS.html
• /scripts/magenta-coming-soon-SAFE.html
• /scripts/magenta-coming-soon-snippet.html

Django Configuration

• /services/django/config/settings/magenta_staging.py
• /services/django/config/settings/magenta_production.py

Service Documentation

• /services/magenta/README.md

Infrastructure

• /infra/terraform/environments/magenta/main.tf
  • Removed analytics.comma.cm from CloudFront aliases
  • Updated API URL in outputs
• /infra/terraform/environments/magenta-prod/main.tf
  • Updated alias comment
• /infra/terraform/environments/magenta-prod/outputs.tf
  • Updated all URL references
• /infra/terraform/environments/magenta-prod/deploy.sh
  • Updated all script references
  • Removed analytics.comma.cm DNS record creation
• /infra/terraform/environments/magenta-prod/deploy-checklist.md
  • Updated all references and examples

Key Changes

1. Unified Domain: Now using magenta.comma.cm for both JavaScript delivery and API endpoints
2. CloudFront: Updated to only use magenta.comma.cm as an alias
3. DNS: Only need to configure one domain (magenta.comma.cm) instead of two
4. API Endpoints: All changed from https://analytics.comma.cm/api/v1/analytics/track/ to https://magenta.comma.cm/api/v1/analytics/track/

Next Steps

When setting up infrastructure:

1. Configure DNS for magenta.comma.cm only
2. Update SSL certificates to include magenta.comma.cm
3. Configure S3/CloudFront to serve both static assets and API requests through magenta.comma.cm