← All posts
Managing Multiple Apps with Subdomains
DNSinfrastructuredeploymentarchitecture
As I built more applications, I needed a cleaner structure than keeping everything on one domain path.
The model
I use a consistent pattern:
app.strong.fm - Landing page
app.strong.fm/app - The application itself
Examples:
aired.strong.fmandaired.strong.fm/apptrips.strong.fmandtrips.strong.fm/app
Why this works
1. Clear structure
Each product has its own space and URL identity.
2. Better product messaging
Each app can have its own landing page and value proposition.
3. Independent releases
Apps can be deployed separately without affecting each other.
4. More professional URLs
Subdomains make the portfolio easier to understand.
Technical setup
With AWS Amplify, setup is straightforward:
- Add custom domain in Amplify
- Add required DNS records
- Wait for SSL provisioning
- Go live
What I learned
- Lower DNS TTL during migrations for quicker rollback
- Validate on preview URLs first
- Keep DNS records documented to avoid operational drift