4
Neo SPCC recently released updated versions of both NeoFS access gateways – REST Gateway v0.17.0 and S3 Gateway v0.43.0. Both releases introduce session token v2 support, depend on NeoFS SDK Go RC18, and require Go 1.25 or higher to build.
The gateways serve as the primary interfaces for applications interacting with NeoFS decentralized storage. The REST Gateway provides HTTP API access, while the S3 Gateway offers an Amazon S3-compatible interface. Session token v2, first introduced in NeoFS Node v0.51.0, enables more granular access control for container and object operations and replaces the previous mixed session and bearer token approach. With both gateways now supporting the new format, the coordinated upgrade that began with NeoFS Node v0.52.0 and SDK RC18 is complete across the NeoFS stack.
REST Gateway v0.17.0
The main addition in v0.17.0 is a container attribute management API, exposing new REST endpoints for GET and PUT operations on container attributes. Container attributes are key-value metadata that control container behavior and permissions – previously, managing them required direct protocol interaction. The new API brings this functionality to any application using the REST interface.
The release also includes comprehensive session v2 token validation and a fix for a production issue where invalid HTTP bearer tokens caused a panic. Several deprecated endpoints, including the search and container put APIs, have been removed, along with the container_ops_poll_interval and container_ops_timeout configuration options. Dependency updates include neo-go moving from v0.116.0 to v0.118.0.
S3 Gateway v0.43.0
S3 Gateway v0.43.0 delivers a complete redesign of multipart upload object mapping, resolving a bug that prevented uploads with more than 300 parts and fixing errors when retrieving individual parts from multipart objects. The new architecture introduces a hierarchical structure with part-level and object-level split chains, eliminating several intermediate metadata attributes used by the previous system.
The multipart redesign is significant for users working with large files through the S3 interface, as the previous 300-part ceiling effectively capped maximum file sizes. The new architecture removes that constraint while also ensuring correct metadata and payload hashes for individual parts.
Alongside the multipart overhaul, the maximum single part size has been reduced from 5 GB to 4 GB to align with NeoFS capabilities. The minimum part size remains at 5 MiB per the S3 specification. Operators planning around the difference should note that the AWS S3 specification allows up to 5 GB per part.
Session token v2 authentication support rounds out the major changes. As with the REST Gateway, the container_ops_poll_interval configuration option has been removed. Dependency updates include neo-go v0.118.0, NATS v1.49.0, and AWS SDK v2 v1.41.2.
Both gateway releases are available on GitHub at the links below:
https://github.com/nspcc-dev/neofs-rest-gw/releases/tag/v0.17.0
https://github.com/nspcc-dev/neofs-s3-gw/releases/tag/v0.43.0
en.bitcoinsistemi.com
thecryptobasic.com
1
