Neo SPCC has released updated versions of the NeoFS S3 Gateway and Send.NeoFS service.
The NeoFS S3 Gateway, which provides an API that is compatible with Amazon’s S3 cloud storage solution, was modified for compatibility with standard Neo FS nodes running version 0.45.0 or later. These changes allow the S3 gateway to be used with public Neo networks such as MainNet and TestNet.
This involved dropping the experimental tree service, which was used to retain object metadata and system information. Bucket tagging, bucket settings, CORS management, and notification configuration have each been reworked to no longer rely on the service. The new release, version 0.36.0, also received new configuration options, a subscription to S3 epoch change notifications, and various minor fixes.
Neo SPCC later released S3 Gateway v0.36.1, which fixed a performance regression caused by an incorrect settings cache and an incorrect status code given on failed object placement due to missing access permissions.
Send.NeoFS also received minor changes, including the removal of emojis from the footer, and depreciation of `react-scripts` in favor of Vite, plus an update to Node 18. The upgraded version is now available on the web app.
About The Author: Brett Rhodes
Brett is a blockchain enthusiast and freelance writer who originally began producing content for the gaming & eSports industries. Now he spends most of his time contributing in the Neo ecosystem.
More posts by Brett Rhodes