Topic.
- 2026-07-12 : Redesigned the site alongside the migration.
- 2026-07-12 : JamStack migration complete.
- 2026-07-11 : Updated DDEV environment to Tome 8.x-1.16.
- 2026-07-11 : Updated DDEV environment to Drupal 11.4.2.
- 2026-07-10 : Updated DDEV environment to Tome 8.x-1.15.
- 2026-07-04 : Updated DDEV environment to Drupal 11.4.1.
- 2026-07-02 : Updated DDEV environment to Drupal 11.4.0.
Drupal with Jamstack.
This site launched in 2024 as a hands-on learning environment for Drupal. For infrastructure, I chose AWS Lightsail with Bitnami's packaged Drupal plan and have been running it on that setup ever since.
In May 2026, AWS Lightsail ended its partnership with Bitnami, leaving further updates unsupported. That became the trigger to switch plans — and to finally implement the JamStack approach with Drupal that I had envisioned from the start.
JamStack.
The implementation is actually quite straightforward.
- Install DDEV and OrbStack on my local MacBook Pro and set up Drupal.
- Use the Tome module to convert the Drupal site into static files (HTML).
- Deploy the static files to AWS Lightsail.
- Serve them publicly via CloudFront, AWS's CDN.
The conventional approach to serving a JamStack static site is to use S3 rather than Lightsail. Since S3 has no Apache, however, the CDN has to handle all website control — which limits flexibility. With that in mind, I chose Lightsail and CloudFront for a setup that's easier to manage. (It's also simpler to configure and maintain than an S3 + CloudFront combination.)
For the Lightsail plan, I selected the OS-only Ubuntu option, configured solely for serving static files. With no programs or databases involved, the usual overhead of CMS server management simply isn't there.