Repoint marketing distribution to www.heliumedu.com (phase 2 of 3)#57
Draft
alexdlaird wants to merge 4 commits into
Draft
Conversation
Up to standards ✅🟢 Issues
|
alexdlaird
force-pushed
the
feature/legacy-shutdown-phase-1-2026-08-01
branch
from
38eb38e to
986826f
Compare
…ding Phase 2 of August 1, 2026 legacy shutdown. Stacked on feature/legacy-shutdown-phase-1-2026-08-01 — phase 1 must apply first to release the www.heliumedu.com CloudFront alias. See MIGRATION.md for the full apply runbook. - Recreate the marketing ACM cert covering www.heliumedu.com (primary) and landing.heliumedu.com (SAN), validated via DNS - Re-alias the existing marketing CloudFront distribution from landing.heliumedu.com to www.heliumedu.com; attach a viewer-request function that 301-redirects /planner** and /settings** to https://app.heliumedu.com/ for support-article and Helium Classic links - Add a redirect-only S3+CloudFront for landing.heliumedu.com that 301s to https://www.heliumedu.com{path} for inbound legacy links - Update Route53 to point www.heliumedu.com at the marketing distribution and landing.heliumedu.com at the new redirect distribution - Use moved blocks to rename the existing landing resources to marketing in state without recreating the CloudFront distribution
Add a handler branch to catch requests whose URI ends with `.html` and return a 301 Moved Permanently redirect to the same path with the `.html` suffix removed. This complements the marketing site's static-path redirects in astro.config.ts by handling arbitrary legacy `*.html` URLs that crawlers may still have indexed.
Legacy frontend bookmark and /app convenience redirects now live in projects/www's astro.config.ts alongside /app, /status, etc. The CloudFront function and its .html-stripping rule are no longer needed since legacy `.html` URLs were never in the marketing sitemap.
alexdlaird
force-pushed
the
feature/legacy-shutdown-phase-2-2026-08-01
branch
from
c429b4d to
a44ebf3
Compare
alexdlaird
changed the title
…e/legacy-shutdown-phase-2-2026-08-01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 2 of the Aug 1, 2026 frontend-legacy shutdown. Stacked on phase 1 (#52) — phase 1 must apply first to free the
www.heliumedu.comCloudFront alias.Changes
www.heliumedu.comandlanding.heliumedu.com(DNS-validated via existing Route53 records)landing.heliumedu.comtowww.heliumedu.com; attach a CloudFront function that 301s/planner**and/settings**tohttps://app.heliumedu.com/landing.heliumedu.com→https://www.heliumedu.com{path}www.heliumedu.comA-alias; repointlanding.heliumedu.comto the new redirect distributionmovedblocks rename*.landing→*.marketingin state without recreating the CF distributionApply runbook
Apply
globalimmediately after phase 1'sprodapply to minimize downtime.Linked PRs — do not merge before Aug 1, 2026
Merge in order:
Rollback
Revert in reverse order. Note: legacy S3 buckets are gone after phase 1 apply; rollback past that requires repopulating from a snapshot.