remotion-dev/remotion · error · Error

Pass --s3-output-provider-endpoint when using S3 output prov

Error message

Pass --s3-output-provider-endpoint when using S3 output provider flags.

What it means

The getS3OutputProviderFromCli() helper in the Lambda CLI validates that when any S3 output provider flag (--s3-output-provider-region, --s3-output-provider-force-path-style, or --s3-output-provider-endpoint) is passed, the endpoint flag is also provided. The endpoint is the S3-compatible API URL (required), while region and forcePathStyle are optional modifiers. Without an endpoint, the other flags have nothing to apply to.

Source

Thrown at packages/lambda/src/cli/helpers/get-s3-output-provider-from-cli.ts:29

	endpoint,
	region,
	forcePathStyle,
}: {
	endpoint: string | undefined;
	region: AwsProvider['region'] | (string & {}) | undefined;
	forcePathStyle: boolean | undefined;
}): CustomCredentials<AwsProvider> | null => {
	const hasAnyS3OutputProviderFlag =
		endpoint !== undefined ||
		region !== undefined ||
		forcePathStyle !== undefined;

	if (!hasAnyS3OutputProviderFlag) {
		return null;
	}

	if (!endpoint) {
		throw new Error(
			'Pass --s3-output-provider-endpoint when using S3 output provider flags.',
		);
	}

	return {
		endpoint,
		accessKeyId:
			LambdaClientInternals.getEnvVariable(
				S3_OUTPUT_PROVIDER_ACCESS_KEY_ID_ENV_NAME,
			) ?? null,
		secretAccessKey:
			LambdaClientInternals.getEnvVariable(
				S3_OUTPUT_PROVIDER_SECRET_ACCESS_KEY_ENV_NAME,
			) ?? null,
		region,
		forcePathStyle,
	};
};

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Add the --s3-output-provider-endpoint=<url> flag, e.g. --s3-output-provider-endpoint=https://s3.example.com.
2. Remove all S3 output provider flags if you do not need a custom S3-compatible output destination.
3. Double-check the flag names against the Lambda CLI documentation to ensure all required flags are present.

Example fix

# before
npx remotion lambda render MyComp \
  --s3-output-provider-region=us-east-1 \
  --s3-output-provider-force-path-style

# after
npx remotion lambda render MyComp \
  --s3-output-provider-endpoint=https://s3.example.com \
  --s3-output-provider-region=us-east-1 \
  --s3-output-provider-force-path-style

function validateS3OutputProviderFlags(opts: {
  endpoint?: string;
  region?: string;
  forcePathStyle?: boolean;
}): void {
  const hasAny = opts.endpoint !== undefined || opts.region !== undefined || opts.forcePathStyle !== undefined;
  if (hasAny && !opts.endpoint) {
    throw new Error('--s3-output-provider-endpoint is required when using any S3 output provider flag.');
  }
}

When it happens

Trigger: Running a Lambda CLI command with --s3-output-provider-region or --s3-output-provider-force-path-style but without --s3-output-provider-endpoint. The function checks that at least one S3 flag is present, then requires the endpoint to be non-empty.

Common situations: User passes only --s3-output-provider-region=<region> expecting it to use a default endpoint; user forgets the endpoint flag when configuring a custom S3-compatible output destination (MinIO, Backblaze B2, Wasabi, etc.).

Related errors

• Pass --force-bucket-name when using S3 output provider flags
• Pass --out-name when using S3 output provider flags.
• maxRetries is NaN
• maxRetries cannot be negative but is ${maxRetries}
• maxRetries should be an integer, but is ${maxRetries}.

AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12). Data as JSON: /api/errors/5ed95886c16a30a3. Report an issue: GitHub.