Lambda Go SDK: upload large inputProps to S3

[iliya-vidrush]

Stacked on #8986 (merge that first). Until it lands, this PR's diff also shows the cleanup commit; it will collapse to just the S3 changes once #8986 is merged.

Motivation

The Go SDK currently rejects inputProps that exceed the inline Lambda payload limit, while the JS and PHP clients transparently upload oversized props to S3 and pass a reference. This brings the Go SDK in line with them.

Changes

• Add s3.go with the bucket and upload helpers:
  • getOrCreateBucket: lists remotionlambda- buckets in the region, errors if more than one exists (linking to the multiple-buckets docs), otherwise reuses the single bucket or creates one (with a LocationConstraint outside us-east-1).
  • SHA256 object hashing, the remotionlambda-<region>-<hash> bucket naming, the input-props/<hash>.json key, and a private application/json PutObject.
• Rewrite serializeInputProps to return a SerializedInputProps of type payload when the props fit inline, or bucket-url with the hash and bucket name after an upload. The inline threshold uses the same margin as the reference clients (200KB video, 5MB still).
• Honor forceBucketName as the user-specified bucket and forcePathStyle on the S3 client.
• Validate the render options before serializing, so an invalid request never triggers an S3 upload or bucket creation.

Testing

• Added tests for inline serialization, the upload threshold, and the bucket and key naming (all AWS-free).
• go build ./..., go vet ./..., go test ./... and gofmt -l pass. The S3 upload path itself requires live AWS credentials and was not exercised in CI.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Jul 13, 2026 3:14am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
remotion	Skipped		Jul 13, 2026 3:14am

[pullfrog]

Caution

The new S3 upload path will fail on AWS accounts using the default S3 Object Ownership setting (ACLs disabled), because the bucket is created without enabling ACLs and the object upload requests a private ACL.

Reviewed changes — added S3 bucket discovery/creation and oversized inputProps upload to the Go Lambda SDK, plus some error-handling cleanup.

• Add s3.go with bucket discovery, creation, and private object upload helpers.
• Rewrite serializeInputProps to return a SerializedInputProps payload and upload to S3 when the inline limit is exceeded.
• Move inputProps serialization after validation and remove the previous log.Fatal on serialization errors.
• Clean up pointer serialization for Crf, ColorSpace, and GopSize, and fix the version.go package statement.
• Fix the example output in lambda-go-example/main.go so it prints BucketName and RenderId.

---

Note: 1 inline comment(s) dropped because they did not anchor to lines inside the PR diff:

• packages/lambda-go/lambda_go_sdk_test.go:22 (RIGHT) — line 22 (RIGHT) is not inside a diff hunk

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏}

[pullfrog]

ℹ️ No new issues in the latest commits — the delta only resolves merge-time version/dependency drift.

Changes since last review — reviewed the merge commit from 06ba5fd to f32ea1e.

• Version alignment: package.json and go.mod versions were bumped from 4.0.486 to 4.0.487, matching version.go.
• Dependency refresh: go.mod/go.sum updated to aws-sdk-go v1.55.8, Go directive 1.26, toolchain go1.26.5, and refreshed indirect dependencies.
• Source code: the feature code is unchanged; go test, go vet, and gofmt still pass.

Note: the feedback from the previous review still needs to be addressed.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using Kimi K2 (free via Pullfrog for OSS) ｜ 𝕏}