Since these assets will be uploaded to s3, we can take advantage of our existing reverse-proxy for other frontend-assets.

Our CDN will require changes for this.

• Redirecting  requests to /api/chrome-service/v1/static/* to new /apps/static/* or /config/*.
• Modify paths routed to reverse proxy as necessary.

Redirecting the assets will offer a smooth transition. Then, the chrome-frontend can update various references to the old path (for example here).

https://docs.google.com/document/d/1i39veUUrKNEQvS-4BDkONJVsMM4kOcR11_QMAbyCyxQ/edit?tab=t.0