~I can't recall if the links were working before the migration. It is possible that AWS CloudFront automatically rewrote URLs to index.html and that the GCP equivalent does not.~ Edit: The previous setup was relying on an AWS feature called S3 website endpoint. Using that endpoint URL returns the default index document that you configure for the website. However Amazon S3 website endpoints do not support HTTPS or access points, which is why we can't use it with this GCP migration.
We could handle this by manually specifying path matching rules to enforce url rewrites, however this would mean an infrastructure re-deployment every time a new link is added. This is not an ideal fix for the issue
It would be preferable to simply change the links in this project. Links like Measurement Dashboard and Dashboard Generator already point to their HTML files.
chutten
commented
1 year ago
Description
The Data SRE team recently migrated this project's infrastructure from AWS to GCP. While assessing our migration, we've noticed some links pointing to a directory rather than an HTML file (see examples below).
~I can't recall if the links were working before the migration. It is possible that AWS CloudFront automatically rewrote URLs to
index.htmland that the GCP equivalent does not.~ Edit: The previous setup was relying on an AWS feature called S3 website endpoint. Using that endpoint URL returns the default index document that you configure for the website. However Amazon S3 website endpoints do not support HTTPS or access points, which is why we can't use it with this GCP migration.We could handle this by manually specifying path matching rules to enforce url rewrites, however this would mean an infrastructure re-deployment every time a new link is added. This is not an ideal fix for the issue
It would be preferable to simply change the links in this project. Links like Measurement Dashboard and Dashboard Generator already point to their HTML files.
Examples
Thanks!