Storage

Data is first mirrored into the new buckets and checked object by object against checksums, while the application keeps running on the old store. Only when the difference list is empty does the application switch to the new endpoint. The old store stays as your way back until you decide to close it.

Tools and SDKs that sign with AWS Signature V4 work once the endpoint is pointed at Nesnet's S3 address. Path-style and virtual-hosted-style addressing are both supported; if your application relies on the x-amz-acl header, move those permissions into bucket policies.

Stored data and outbound traffic from the endpoint appear on separate invoice lines, so you can follow what each item costs. Unit prices aren't published on this page; Nesnet's team prepares them for your usage.

Your data is read through the standard S3 API, so the same tools, such as rclone or the AWS CLI, copy it to any other S3-compatible target you choose. There's no provider-specific format and no closed export route.

Reach Nesnet’s support team at info@nesnet.com or on 0800 606 1071. The team that wrote the missing pieces of the object storage plug-in and runs the service is Nesnet's own.

The service runs from a single site and there is no replication between sites or regions. If you want a second copy, standard S3 tools can write your data to another target of your choice, or you can use the Backup product for critical data.