Neo SPCC launched NeoFS S3 Gateway v0.46.0 on Sept. 2, introducing an Authbox service that points S3 credentials over HTTP alongside routing optimizations, operational enhancements, and dependency updates for the S3-compatible interface to NeoFS decentralized storage.
The discharge follows v0.45.1, which delivered learn and write efficiency enhancements in early August, and v0.45.0, which added bucket namespacing and eliminated legacy options in July.
Authbox credential service
The headline addition is Authbox, a brand new service that provisions S3 credentials over HTTP. Beforehand, producing credentials for the S3 Gateway required utilizing the neofs-s3-authmate command-line software immediately. Authbox wraps this performance in an HTTP-accessible service, making it simpler for functions and platform operators to programmatically provision entry to NeoFS storage via the S3-compatible protocol with out direct CLI interplay.
The characteristic ships as a brand new neofs-s3-authmatesrv binary alongside the present gateway and authmate instruments, with prebuilt binaries obtainable for Linux, macOS, and Home windows throughout each AMD64 and ARM64 architectures.
Routing, logging, entry key modifications
Request routing was optimized to match decoded URL paths quite than uncooked encoded strings, addressing pointless reminiscence allocations that have been noticed underneath heavy learn load. The change improves each correctness in path dealing with and useful resource consumption throughout high-throughput operations, notably for object retrieval workflows.
Entry key objects are actually capped at 64 KB when studying, introducing a safeguard in opposition to outsized or malformed key information that might in any other case devour extreme assets. The discharge additionally reduces verbose logging output generated by batched operations, chopping log noise for operators operating the gateway at scale and making it simpler to establish significant entries in manufacturing environments.
Dependency updates
The gateway now requires Go 1.26 or later as its minimal toolchain model, up from the earlier requirement. Core ecosystem dependencies have been up to date to align with the most recent NeoFS infrastructure releases, with the NeoFS SDK shifting to RC22 and the NeoGo blockchain toolkit up to date to v0.123.0.
A number of upstream Go libraries have been additionally refreshed as a part of the toolchain replace, together with the AWS SDK for Go v2, gRPC, Protocol Buffers, and the Zap structured logging framework.
The total launch notes may be discovered on the hyperlink under:
https://github.com/nspcc-dev/neofs-s3-gw/releases/tag/v0.46.0
