neonctl bucket object put uploads a file through a presigned URL

Introduced 2026-06-12 · score 0.97

HOW TO USE IT

When the artifact is at most 104857600 bytes, upload it to an existing bucket with `neonctl bucket object put <bucket>/<key> --file <path> [--content-type <ct>]`; the CLI obtains a presigned PUT URL and streams the file. The v2.25.0 release notes document the upload feature and 100 MB cap.

WHY THIS HELPS

Upload a repository artifact to a Neon object storage bucket while working with an existing neonctl coding workflow.

REQUIREMENTS AND LIMITATIONS

• Version: v2.25.0
• <bucket>/<key> (required): Target bucket and object key; release notes say it is split on the first `/` and an empty key is rejected.
• --file <path> (required): Path to the file to upload. Files above 104857600 bytes are rejected client-side.
• --content-type <ct>: Optional content type sent with the upload request.
• Files above 104857600 bytes are rejected client-side with exit 1 and no HTTP request.
• Multipart upload is out of scope.
• The bucket target uses `<bucket>/<key>`, split on the first `/`; an empty key is rejected client-side.
• The presigned download operation is API-only; `object get` continues to stream through the console.

FIRST-PARTY EVIDENCE

• https://github.com/neondatabase/neonctl/releases/tag/v2.25.0
• https://github.com/neondatabase/neonctl/pull/530

Check the installed version and the source before using it. Entry JSON

Report a problem with this card