Migrate AWS EC2 app: Laravel · Ample Computer

Migrate AWS EC2 app: Laravel

Move Laravel compute from AWS EC2 app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Collect the process environment from the instance (systemd unit or process manager config) into an env file kept out of the repository. Move separately: cron jobs become ample job schedules, files on the instance disk move to a bucket or an Ample volume, and IAM instance roles become encrypted env credentials; Ample handles networking. Cutover: Add the custom domain with ample domain add, update DNS from the instance or load balancer, keep the instance until verified, then stop it. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

What it runs on

You need

Exact tested configuration

installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
runtimephp
sizes-1vcpu-1gb
startfrankenphp php-server --listen :$PORT --root public
templatephp-8.5

Steps

  1. Inventory the source. List what AWS EC2 app provides beyond the component you are moving. Plan these separately: cron jobs become ample job schedules, files on the instance disk move to a bucket or an Ample volume, and IAM instance roles become encrypted env credentials; Ample handles networking.

  2. Source step 1. Collect the process environment from the instance (systemd unit or process manager config) into an env file kept out of the repository.

  3. Source step 2. Replace the instance's process manager with the repository's start command; Ample supervises the process and restarts it.

  4. Source step 3. Inventory what else runs on the instance: databases, cron, reverse proxy rules, local files.

  5. Deploy on Ample in parallel. composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template. Pass the exported variables with --env; keep the source running.

   $ ample deploy . --name <app-name> --public --env-file .env.production
  1. Validate before cutover. Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).

  2. Cut over. Add the custom domain with ample domain add, update DNS from the instance or load balancer, keep the instance until verified, then stop it.

  3. Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

How it was checked

✓ destination app responds on its public URL· http get/ → “ample canary laravel patterns”
✓ configuration-secrets check from the destination example· http get/p/configuration-secrets → “see the pattern fixture checks”
✓ relational-records check from the destination example· http get/p/relational-records → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

Evidence

  1. November 6, 2026 · canary run
    Destination side verified: the Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from AWS EC2 app uses the vendor's standard tooling.

Tested examples

What it doesn’t cover