Repository navigation
Add Neon Object Storage profile - #205
Merged
Merged
Conversation
dkocher
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a connection profile for Neon Object Storage, the S3 compatible storage included with Neon projects. Each Neon branch has its own endpoint, like
br-<branch>.storage.c-<n>.<region>.aws.neon.tech.Service documentation: https://neon.com/docs/storage/s3-compatibility
Notes on the profile:
s3.bucket.virtualhost.disableis set.auto. The service accepts any region in the SigV4 scope. Without a region set, creating a bucket fails becauseGetBucketLocationis not supported.STANDARDis the only storage class. Versioning and transfer acceleration are disabled because the service stores but does not enforce versioning and does not support acceleration.Tested with Cyberduck CLI 9.5.4 against a branch in us-east-2: ListBuckets, CreateBucket, DeleteBucket, ListObjectsV2, PutObject, CopyObject, GetObject, DeleteObject.
Known limitation: renaming a file fails with
501 Not Implementedbecause ACLs are read only andPutObjectAclis rejected after the copy.Documentation: iterate-ch/docs#
Replaces iterate-ch/cyberduck#18672.
Disclosure: I'm a contractor at Neon.