34
Views
3
Comments
How to Configure OutSystems to Serve Static Resources via CDN (CloudFront + S3)
Application Type
Reactive
Service Studio Version
11.55.4 (Build 63890)
Platform Version
11.30.0 (Build 43791)

Hi all,

I’m trying to serve static assets (CSS, JS, images, etc.) for my OutSystems application through a CDN. Here's what I've done so far:

  • Created an S3 bucket to host static files.

  • Set up an Amazon CloudFront distribution pointing to the S3 bucket.

  • Configured the origin domain in CloudFront to route through my app’s domain (via load balancer).

However, I’m unsure where in OutSystems I should configure the CDN base URL so that all static resources generated at build time (like stylesheets, scripts, and images) are served from the CDN instead of the default OutSystems path.

Is there a specific setting in Service Center or LifeTime to define the CDN base path? Or do I need to handle this differently within the app modules?

Any guidance or documentation links would be greatly appreciated.

Note: I'm currently in OutSystems Platform server version 11.30

Thanks in advance!

UserImage.jpg
Jayandhan Rajasundaram

@Pawan Parmar,

I’ve gone through forum threads you have linked in your reply, but I haven’t come across a centralized configuration option to set the CDN URL as the base path for all static assets. From what I understand, it seems like each asset might need to be handled individually — or am I missing something here?

Any clarification or guidance would be appreciated!


2025-07-22 10-30-27
Mandar Deshpande

Hi @Jayandhan Rajasundaram 

There does not seem to be any built-in configuration in Service Center / LifeTime where you can just set a “CDN base URL” and have all Outsystems static resources automatically rewritten to that CDN domain.

If you control the static assets yourself then:

  • Upload CSS/JS/images to your S3 bucket.
  • Update references in your Reactive app code to point to your CDN domain.
  • This way your app directly links to the CDN rather than the Outsystems build’s paths.

This is a manual approach for each asset reference. 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.