Skip to content

Migrate assets from GCP to AWS#407

Open
prashanthakp-setu wants to merge 3 commits intomainfrom
GCP-AWS-ASSET-MIGRATION
Open

Migrate assets from GCP to AWS#407
prashanthakp-setu wants to merge 3 commits intomainfrom
GCP-AWS-ASSET-MIGRATION

Conversation

@prashanthakp-setu
Copy link
Collaborator

Migrates documentation image/asset URLs from Google Cloud Storage (GCP) to AWS S3. All references to storage.googleapis.com/strapi-assets in the content layer are updated to the new S3 base URL.

What changed
Asset URLs
From: https://storage.googleapis.com/strapi-assets/...
To: https://docs-mdx-assets-sandbox.s3.ap-south-1.amazonaws.com/...

Content
All affected .mdx and .md files under content/ (and README.md) now point to the S3 bucket.

Docs
README.md updated with an Asset Management section that describes:

Bucket name and folder structure
New S3 URL format and examples

How to reference assets in MDX (e.g. with MainImage)
Areas touched

Data: Account Aggregator, DigiLocker, Insights, ULI

Dev tools: Bridge (overview, settings, org-settings, reports, etc.)

Payments: BBPS, BillPay, UMAP, UPI Deeplinks, WhatsApp Collect

Sample content and any other pages that used GCS asset URLs

Notes
Asset hosting is now on the docs-mdx-assets-sandbox S3 bucket (ap-south-1).
No change to doc structure or behaviour; only asset URLs and README instructions were updated.

@github-actions
Copy link

Checklist to merge a PR 🚀

To merge this pull request, please take time to complete the checklist.

What action did you perform?

Review the corresponding checklist items for the action you performed and mark them done.

Edit an existing content (MDX) page

Checklist

  • Review changes using the MDX preview option
  • If the length of content >15000 chars, use the Content preview portal to view changes
  • If a redirect is needed to the existing page, add a key, value pair in redirects.json

Edit an existing API reference page

Checklist


Add a new content (MDX) page

Checklist

  • Create a .mdx file with the path as its name in the content folder
  • Add frontmatter with all the metadata
  • Review the order of items in Sidebar using the Sidebar preview option
  • Review changes using the MDX preview option
  • If the length of content >15000 chars, use the Content preview portal to view changes
  • Created a folder with the same name, if any children were to be added to the page
  • Once all changes are done, update the menu items by using the Menu Items option
  • Add a key, and value pair in redirects.json if you wish to have a redirect to the new page

Add a new API reference page

Checklist

  • Create a .json file with the product path as its name
  • Create an api-reference.mdx file in the respective product folder inside content folder
  • Add frontmatter with all the metadata
  • Review the order of items in Sidebar using the Sidebar preview option
  • Add API reference in JSON format (OpenAPI or Swagger) into created .json file.
  • Used the Content preview portal to view changes
  • Once all changes are done, update the menu items by using the Menu Items option

@prashanthakp-setu prashanthakp-setu changed the base branch from main to staging February 12, 2026 10:18
@prashanthakp-setu prashanthakp-setu changed the base branch from staging to main March 5, 2026 06:05

<br />

<img src="https://storage.googleapis.com/strapi-assets/latest/dual-consent-approval-page/dual-consent-approval-page.png" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets give the diff to claude and ask to create abstraction for the base-url

Copy link
Contributor

@pulkit004 pulkit004 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets give the diff to claude and ask to create abstraction for the base-url

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants