feat: Add documentation for S3-compatible API for network volumes

.cursor/rules/rp-styleguide.mdc

@@ -6,5 +6,5 @@ alwaysApply: true
 Always use sentence case for headings and titles.
 These are proper nouns: Pods, Serverless, Hub, Instant Clusters, Secure Cloud, Community Cloud, Tetra.
 These are generic terms: endpoint, worker, cluster, template, handler, fine-tune, network volume.
-Prefer using paragraphs to bullet points unless directly asked.
-When using bullet points, end each line with a period.
+Prefer using paragraphs to bullet points unless specifically requested.
+When using bullet points, use hyphens instead of asterisks, and end each line with a period.

docs.json

@@ -62,7 +62,8 @@
                 "group": "Storage",
                 "pages": [
                   "serverless/storage/overview",
-                  "serverless/storage/network-volumes"
+                  "serverless/storage/network-volumes",
+                  "serverless/storage/s3-api"                  
                 ]
               },
               {

hub/overview.mdx

@@ -6,7 +6,7 @@ description: "Discover, deploy, and share preconfigured AI repos."
 
 <Note>
 
-**The RunPod Hub is currently in beta**. We're actively developing features and gathering user feedback to improve the experience. Please [join our discord](https://discord.gg/runpod) if you'd like to provide feedback.
+**The RunPod Hub is currently in beta**. We're actively developing features and gathering user feedback to improve the experience. If you'd like to provide feedback, please [join our Discord](https://discord.gg/runpod).
 
 </Note>
 

serverless/pricing.mdx

@@ -55,6 +55,8 @@ Your total Serverless costs include both compute time (GPU usage) and temporary
 
 If you have many workers continuously running with high storage costs, you can utilize [network volumes](/serverless/storage/network-volumes) to reduce expenses. Network volumes allow you to share data efficiently across multiple workers, reduce per-worker storage requirements by centralizing common files, and maintain persistent storage separate from worker lifecycles.
 
+Network volumes are billed hourly at a rate of \$0.07 per GB per month for the first 1TB, and \$0.05 per GB per month for additional storage beyond that.
+
 ### Compute cost breakdown
 
 Serverless workers incur charges during these periods:

serverless/storage/network-volumes.mdx

@@ -6,10 +6,12 @@ description: "Persistent, portable storage for Serverless workers."
 
 Network volumes offer persistent storage that exists independently of the lifecycle of a [Serverless worker](/serverless/workers/overview). This means your data will be retained even if a worker is stopped or your endpoint is deleted.
 
-Network volumes can be attached to multiple Serverless endpoints, making them ideal for sharing data, or maintaining datasets between Serverless workers.
+Network volumes can be attached to multiple Serverless endpoints, making them ideal for sharing data, or maintaining datasets between workers.
 
 When attached to a Serverless endpoint, a network volume is mounted at `/runpod-volume` within the worker environment.
 
+Network volumes are billed hourly at a rate of \$0.07 per GB per month for the first 1TB, and \$0.05 per GB per month for additional storage beyond that.
+
 <Warning>
 
 If your account lacks sufficient funds to cover storage costs, your network volume may be terminated. Once terminated, the disk space is immediately freed for other users, and RunPod cannot recover lost data. Ensure your account remains funded to prevent data loss.
@@ -18,11 +20,11 @@ If your account lacks sufficient funds to cover storage costs, your network volu
 
 ## When to use a network volume
 
-Consider using a network volume when your Serverless endpoints needs:
+Consider using a network volume when your endpoints needs:
 
 *   **Persistent data that outlives individual workers:** Keep your data safe and accessible even after a worker is stopped or an endpoint is scaled to zero.
 *   **Shareable storage:** Use the same data across different workers of the same endpoint or even different endpoints. While a network volume can be *attached* to multiple Serverless endpoint configurations, ensure your application logic handles concurrent access appropriately if workers from different endpoints write to the volume to prevent data corruption.
-*   **Efficient data management:** Store frequently used models or large datasets to avoid re-downloading them for each new Serverless worker, saving time, bandwidth, and reducing cold start times.
+*   **Efficient data management:** Store frequently used models or large datasets to avoid re-downloading them for each new worker, saving time, bandwidth, and reducing cold start times.
 *   **Stateful applications:** Maintain state across multiple invocations of a Serverless function, enabling more complex, long-running tasks.
 
 ## Create a network volume
@@ -32,7 +34,7 @@ To create a new network volume:
 1.  Navigate to the [Storage page](https://www.runpod.io/console/user/storage) in the RunPod console.
 2.  Select **New Network Volume**.
 3.  **Configure your volume:**
-    *   Select a datacenter for your volume. Datacenter location does not affect pricing, but the datacenter location will determine which Serverless endpoints your network volume can be used with. Your Serverless endpoint must be in the same datacenter as the network volume.
+    *   Select a datacenter for your volume. Datacenter location does not affect pricing, but the datacenter location will determine which endpoints your network volume can be paired with. Your Serverless endpoint must be in the same datacenter as the network volume.
     *   Provide a descriptive name for your volume (e.g., "serverless-shared-models" or "project-gamma-datasets").
     *   Specify the desired size for the volume in gigabytes (GB).
 
@@ -50,7 +52,7 @@ You can edit and delete your network volumes using the [Storage page](https://ww
 
 To enable workers on an endpoint to use a network volume:
 
-1.  Navigate to the [Serverless Endpoints page](https://www.runpod.io/console/serverless/user/endpoints) in the RunPod console.
+1.  Navigate to the [Serverless page](https://www.runpod.io/console/serverless/user/endpoints) in the RunPod console.
 2.  Either create a **New Endpoint** or select an existing endpoint and choose **Edit Endpoint** from the options menu (three dots).
 3.  In the endpoint configuration, expand the **Advanced** section.
 4.  From the **Network Volume** dropdown, select the network volume you want to attach to the endpoint.
@@ -64,6 +66,10 @@ Multiple workers cannot write to a single network volume simultaneously.
 
 </Warning>
 
+## Manage files
+
+To manage files in your network volume (for example, to upload large models used by your workers), use the [RunPod S3-compatible API](/serverless/storage/s3-api).
+
 ## Architecture details
 
 Network volumes are backed by high-performance storage servers co-located with RunPod GPU servers. These are connected via high-speed networks and use NVMe SSDs for optimal performance, but data transfer speeds can vary widely based on location and network conditions (200-400MB/s, up to 10GB/s).
@@ -74,4 +80,4 @@ Using network volumes with Serverless provides significant flexibility and can l
 
 *   **Reduced cold starts:** By storing large models or datasets on a network volume, workers can access them quickly without needing to download them on each cold start.
 *   **Cost efficiency:** Network volume storage space costs less than frequently re-downloading large files or relying solely on container storage for data that needs to persist.
-*   **Simplified data management:** Centralize your datasets and models for easier updates and management across multiple Serverless workers and endpoints.
+*   **Simplified data management:** Centralize your datasets and models for easier updates and management across multiple workers and endpoints.