NeoFS Gateways Finally Get Session Token v2, Multipart Uploads Break Free from the 300-Part Prison

The Neo SPCC crew just shipped fresh versions of both NeoFS access gateways — REST Gateway v0.17.0 and S3 Gateway v0.43.0 — because apparently "we're done" isn't in their vocabulary. The star of the show? Session token v2 support, completing the coordinated upgrade that started with NeoFS Node v0.52.0 and SDK RC18. Consider this the season finale we've been waiting for.

Session token v2, which first showed up in NeoFS Node v0.51.0, brings more granular access control for container and object operations. It's retiring the old mixed session and bearer token setup, which was basically the crypto equivalent of carrying both a house key and a car key when you're just trying to open your front door. Two tokens were just too confusing for the average developer — or apparently any developer.

REST Gateway v0.17.0 now gifts us a container attribute management API with shiny new GET and PUT endpoints. Before, managing container attributes required direct protocol interaction, like navigating a labyrinth without a map. Now, any application can handle it through REST, the way the gods intended. The update also brings comprehensive session v2 token validation and fixes a panic that occurred when invalid HTTP bearer tokens showed up uninvited, like that one friend who never RSVPs but always shows up anyway.

Some deprecated endpoints — including search and container put APIs — have been removed along with the container_ops_poll_interval and container_ops_timeout configuration options. It's like spring cleaning, but for your infrastructure. neo-go dependency bumped from v0.116.0 to v0.118.0, because staying current is apparently non-negotiable.

S3 Gateway v0.43.0 delivers a complete multipart upload object mapping redesign. This fixes a bug that prevented uploads exceeding 300 parts and resolves errors when retrieving individual parts from multipart objects. The new hierarchical structure with part-level and object-level split chains shatters the old 300-part constraint that was effectively capping maximum file sizes. It was basically a 300-part prison for your uploads, and we're breaking everyone out. Maximum single part size has been reduced from 5 GB to 4 GB to align with NeoFS capabilities, while the minimum stays at 5 MiB per S3 spec. Thems the rules.

Session token v