What it is
CloudFront multi-tenant distributions are built for software-as-a-service. Instead of creating a separate distribution for every customer, a provider defines one multi-tenant distribution as a template and adds a distribution tenant for each customer domain. The tenants share the configuration, such as origins and cache behaviour, and can override parts of it where one customer needs something different.
Each tenant can carry its own domains and its own TLS certificate, managed through AWS Certificate Manager. Customers point their domain at the provider with a CNAME, and the provider adds or removes tenants through the API. Onboarding a customer becomes a few API calls rather than a new stack to maintain.
How I use it
- Each Rental Pilot company gets the app at app., customer. and cus. on its own domain, each a tenant of one multi-tenant distribution.
- The customer adds one CNAME. The certificate and the CDN are automatic.
- One build of the app reads the host name and loads that company's logo and colours.
- Lend Pilot automates it end to end: the API writes the DNS records, creates a distribution tenant with a managed certificate and switches the domain on once CloudFront is serving it.
- The white-label page traces a demo company's real domain live, from DNS to the certificate.
A multi-tenant distribution is the right tool when every customer wants your app on their own domain. A new customer becomes a new tenant, not a new stack, so the hundredth company costs the same effort as the second. That is how Rental Pilot is sold white-label.
Questions
Can my rental company use Rental Pilot on its own domain?
Yes. You add one CNAME for app., customer. or cus. on your domain, and the certificate and CDN are set up automatically.
How do you serve many customer domains from one app?
One multi-tenant CloudFront distribution with a tenant per domain, and an app build that reads the host name and loads that company's brand.