Reuse a provider’s automatic encryption
S3-managed encryption
ServerSideEncryption=AES256. Use only a provider that
supports this API. Unsupported/rejected requests fail; there is no unencrypted
retry fallback. Explicit SSE profiles require HTTPS with certificate verification.
S3 with a customer-managed KMS key
driver => 'dsse-kms'
and omit bucket_key, which is not supported for that profile.
Native parameters are enforced at SDK write initialization, covering ordinary
uploads, SDK copies and multipart initiation. Studio’s direct multipart pipeline
also propagates existing Laravel SSE options when mode is off, binds encryption
options into the session target identity and checks encryption metadata before
publication. Changing encryption parameters during a direct upload invalidates
that session’s target; do not rotate configuration mid-session.
The policy compiles internally to fms-s3-native, preserving Laravel’s S3 adapter,
streaming, HTTP ranges and temporary URLs. It does not download/re-encrypt large
files in PHP. Provider-side settings and real storage behavior must still be
verified in the deployment. Tests use the real AWS SDK with mocked responses,
not a live AWS/KMS account.