On November 27th 2024 the IPFS experiment ended. Learn more.
Available regions :
Paris
Amsterdam
WarsawFrom November 27th 2024, IPFS Pinning and Naming services won’t host anymore new IPFS data.
We encourage you to backup your IPFS data into alternative pinning or IPNS services to keep your data available through the IPFS network. Existing blocks on our IPFS pinning will still be delivered for a few times before completely shutting down by the end of 2024.
| Type of consumption | Price | Estimated monthly cost for 100 GB | Estimated monthly cost for 2 TB |
|---|---|---|---|
| Storage | 25 GB free every month then 0.00002 €/GB/hour ~0.0146 €/GB/month | 1.09 € | 28.83 € |
| Ingress | Unmetered | Unmetered | Unmetered |
| Egress | 25 GB free every month then ~0.01 €/GB | 0.75 € | 19.75 € |
After our first experimentation on ARM Scaleway Labs is proud to unveil its latest trial, the IPFS Pinning Service, showcasing the future of the distributed internet.
This trial offers users the chance to harness the power of IPFS, a groundbreaking technology that revolutionizes how data is stored and distributed across a decentralized network.
With the IPFS Pinning Service, users can securely pin and manage their files, leveraging the advantages of decentralized storage and content distribution.
Join the trial and experience the potential of the distributed internet with Scaleway IPFS Pinning Service today.
Leverage Scaleway's IPFS Pinning Service for storing and versioning Machine Learning datasets. With IPFS's deduplication capability, redundant blocks are eliminated, optimizing dataset management.
Store and version your datasets using IPFS to minimize storage redundancy, increase resource utilization, and achieve more efficient data storage compared to traditional methods.
Choose IPFS for decentralized and content-based addressing, ensuring file availability and retrieval. Scaleway's Pinning Service is ideal for archiving, and guaranteeing node availability.
Rely on Scaleway's infrastructure and commitment to uptime for long-term accessibility and data preservation. Store and archive files confidently with the combined benefits of IPFS and Scaleway's Pinning Service.
With IPFS, you can share and distribute data across multiple nodes, ensuring redundancy and availability. This decentralized approach enhances collaboration by allowing multiple parties to access and work with the data simultaneously. Each participant can contribute to the computation and analysis of the shared data, fostering a collaborative and inclusive environment.
Leveraging IPFS enables the building of a decentralized and collaborative framework for sharing, managing, and performing computations over large datasets, providing a more secure, scalable, and transparent approach to data-driven collaboration.
IPFS's chunk-based data structure makes it ideal for streaming video content. Break video files into smaller chunks, which can be independently requested and retrieved from different nodes, improving performance and reducing latency. IPFS's content-addressed nature ensures data integrity, preventing tampering.
Leverage IPFS for efficient and decentralized video streaming, benefiting from distributed architecture, better bandwidth utilization, and resilience against single points of failure.
Host your website files on IPFS for high availability and resilience. Users can access your IPFS-hosted website using their local IPFS gateway. To reach a broader audience, leverage public gateways as intermediaries. Configure DNS settings to direct your domain to a public gateway, enabling easy access through regular web browsers.
This combination of IPFS hosting and public gateways ensures widespread accessibility to your website, reaching users worldwide.
When linking an NFT to a digital file, the method is crucial. IPFS offers a reliable solution by using a content-based identifier (CID) to link the file. The CID is independent of content localization, providing access to the file regardless of its location or changes in file paths. The CID remains constant and tamper-proof, ensuring the integrity and permanence of the NFT-file link.
IPFS establishes and maintains a robust and immutable connection between NFTs and their associated files.
This section provides concise examples on how to utilize our pinning service. For a comprehensive tutorial, please refer to our official documentation
Before pinning any content, you need first to create a regional volume (like an S3 bucket). You can do it from the Scaleway console or with the Scaleway CLI.
Create a volume with the Scaleway CLI:
scaleway labs$ export SCW_ENABLE_LABS=true
$ scw ipfs volume create name=my-volume
$ ▉
To pin a content from a CID or from an URL you have to provide your volume and the name of the pinned content.
Pin content with Scaleway CLI:
scaleway labs$ export SCW_ENABLE_LABS=true
$ scw ipfs pin create-by-cid volume-id=$VOLUME_ID cid=Qmdi7ERksspfxWXfU8ATRUt7iCjZJbEbDrUoMDtjnbdTwo name=my-file
$ ▉
You can retrieve information about any pin by using the provided pin id.
Get status of your content with Scaleway CLI:
scaleway labs$ export SCW_ENABLE_LABS=true
$ scw ipfs pin get pin-id=$PIN_ID volume-id=$VOLUME_ID
$ ▉
Kubo is the official IPFS client. Follow the installation instructions here then you can use Scaleway pinning service to store data remotely. This operation allows you to add Scaleway remote service from the kubo CLI. This operation allows you to add Scaleway remote service from the kubo CLI.
This operation allows you to add Scaleway remote service from the kubo CLI:
scaleway labs$ ipfs pin remote service add scaleway https://fr-par.ipfs.labs.scw.cloud/$VOLUME_ID/$SCW_SECRET_KEY
Then you can pin a content from a CID.
Add pin with Kubo CLI:
scaleway labs$ ipfs pin remote add --service=scaleway QmaGNR5PedL8kiTUMtsPeFFodL9HnYBMuUqAEQrv6CQH4F
$ ▉
Once your content is pinned on the Pinning Service, you can retrieve that content with its CID from any IPFS peer.
To fetch your content locally:
scaleway labs$ # via Kubo IPFS cli
$ ipfs get <YOUR_CID> > myFile
$ # via curl and cloudflare IPFS gateway
$ curl https://cloudflare-ipfs.com/ipfs/<YOUR_CID>
When you pin your files on our IPFS Pinning Service, your data is stored in the region where your IPFS volume was created. We do not handle data encryption within our service. Therefore, we advise caution when pinning files that contain private or sensitive information, as they will be accessible through the IPFS network without any access restrictions.
To ensure the security and confidentiality of your data, we recommend encrypting it yourself before pinning the files using suitable encryption methods or tools. This additional layer of encryption will help protect your data from unauthorized access while utilizing our IPFS Pinning Service.
No, IPFS is not a technology developed by Scaleway. IPFS is an open-source protocol and peer-to-peer network designed to create a distributed and decentralized file system. It was developed by Juan Benet and is maintained by Protocol Labs, an independent organization focused on building open protocols and tools for the decentralized web.
While Scaleway offers an IPFS Pinning Service that integrates with the IPFS network, IPFS itself is not specific to Scaleway and is used by various organizations and individuals worldwide.
No, by design the IPFS network does not encrypt the data.
Our IPFS Pinning Service does not provide encryption for your data. It is important to encrypt your data yourself before pinning files to ensure the security and confidentiality of your information. We recommend utilizing encryption methods or tools of your choice to protect your data prior to pinning it with our service. By taking this proactive step, you can maintain full control over the encryption process and safeguard your data according to your specific requirements.
Yes, the Scaleway pinning service is compatible with Kubo. You can use Kubo, which is an IPFS client, to interact with and manage your pinned files through the Scaleway pinning service.
Kubo provides a user-friendly interface and convenient features for accessing and controlling your IPFS content. By utilizing Kubo alongside the Scaleway pinning service, you can easily manage and work with your pinned files in a seamless and efficient manner.
In IPFS, data is identified and accessed based on its content rather than its location or traditional file paths. Content-based addressing uses a unique identifier called the Content Identifier (CID) to reference and retrieve files.
The CID is generated using cryptographic hashing algorithms, which derive a unique identifier based on the content of the file itself. This means that if the content of a file changes, its CID will also change, ensuring data integrity and facilitating efficient content distribution across the IPFS network.
Content-based addressing allows for decentralized and efficient retrieval of files in IPFS, regardless of their physical location or storage medium.
It is not possible to directly delete data from IPFS once it has been replicated on the network, you can remove the files from our IPFS Pinning Service when desired. By unpinning the files from our service, they will no longer be actively stored and distributed through our infrastructure.
To ensure data privacy and security, it is still advisable to employ encryption and access control mechanisms before adding files to IPFS. This way, even if the files are accessible through other nodes in the IPFS network, their contents remain encrypted and protected.
Please note that the lack of a built-in deletion mechanism in IPFS and the distributed nature of the network mean that removing files completely from all nodes is a complex task.
S3 (Simple Storage Service) is a centralized cloud storage system created by Amazon Web Services (AWS), while IPFS (InterPlanetary File System) is a decentralized peer-to-peer storage system created by Protocol Labs.
S3 operates on a client-server model, storing data in a centralized location (e.g. Scaleway data centers), while IPFS distributes data across a network of interconnected nodes.
S3 uses unique identifiers within the S3 service to identify objects, while IPFS uses Content Identifiers (CIDs) derived from the content of the file itself.
While IPFS (InterPlanetary File System) and BitTorrent share similarities and both utilize peer-to-peer (P2P) networking principles, IPFS is not directly based on BitTorrent.
IPFS was developed independently as a separate protocol and system. However, both IPFS and BitTorrent are decentralized P2P file-sharing technologies with the goal of improving data distribution and availability. IPFS incorporates some concepts from BitTorrent, such as the use of a distributed hash table (DHT) for content discovery and addressing, but it also introduces additional features and concepts to create a more versatile and extensible system for distributed file storage and retrieval.
IPFS CID (Content Identifier) and a BitTorrent Magnet link serve similar purposes, but they are not equivalent.
An IPFS CID is a unique identifier that represents a specific piece of content within the IPFS network. It is generated using cryptographic hashing algorithms and includes the content's hash and other metadata. The CID is used to locate and retrieve the content from the IPFS network.
On the other hand, a BitTorrent Magnet link is a URI scheme used to identify and locate a BitTorrent resource. It typically contains the hash of the torrent file, along with other optional parameters such as trackers, to enable the download and sharing of the corresponding torrent file.
While both IPFS CID and BitTorrent Magnet link are used for content identification and retrieval in their respective systems, they have different formats and serve different underlying technologies (IPFS and BitTorrent). IPFS CID is specific to IPFS and works within the IPFS ecosystem, while a BitTorrent Magnet link is specific to the BitTorrent protocol.