page:guides:laravel:private file access

Enforce Private-File Authorization for Laravel

Summary

Private file access for a Laravel app on Ample. Verified on Laravel: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: 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.

Representative Queries

Framework

Laravel

Workload

Enforce private-file authorization

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

Tested Configuration

Workflows Steps

  1. Build and start
    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; the server must bind 0.0.0.0 on PORT.

  2. Create the bucket and pass its credentials
    Create it once with ample bucket create, then pass endpoint, region, bucket and keys with --env; use path-style addressing.
    Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

  3. Authorize before touching storage
    Return 401 for unauthenticated requests and 403 for the wrong role; keep the bucket unpublished and stream objects through the app.

  4. Verify
    Fetch the live URL and /p/private-document-library on the example; on failure read the build and runtime logs.
    Command: ample logs --kind build

Examples

Success Checks

Limitations

Cost Estimate

Evidence Summary

Next Actions