Sync Pod data with cloud storage providers

Navigate to the Amazon S3 bucket creation form in your AWS console.

Provide a descriptive name for your bucket and select your preferred AWS Region (this affects data storage location and access speeds).

If you need your bucket to be publicly accessible, uncheck the Block public access option at the bottom of the form. For most use cases, keeping this checked provides better security.

Go to Security credentials in your AWS account settings. Create a new Access Key on the Security credentials page.

Your Secret Access Key will be displayed only once during creation, so make sure to save it securely.

In the Runpod console, navigate to the Pods page and select the Pod containing your data. Click Cloud Sync, then select AWS S3 from the available providers.

Enter your AWS Access Key ID and Secret Access Key in the provided fields. Specify the AWS Region where your bucket is located and provide the complete bucket path where you want to store your data.

Click Copy to/from AWS S3 to initiate the transfer. The transfer progress will be displayed in the Runpod interface. Large datasets may take time depending on your Pod’s network connection.

Access the Google Cloud Storage dashboard and click Buckets → Create to start the bucket creation process.

Choose a globally unique name for your bucket. Leave most configuration options at their default settings unless you have specific requirements.

To allow public access to your bucket contents, uncheck Enforce Public Access Prevention On This Bucket. Keep this checked for better security unless public access is required.

Create a service account specifically for Runpod access. This provides better security than using your primary account credentials.

Follow Google’s guide on creating service account keys to generate a JSON key file. This key contains all necessary authentication information.

In the Runpod console, navigate to the Pods page and select the Pod containing your data. Click Cloud Sync, then select Google Cloud Storage from the available providers.

Paste the entire contents of your Service Account JSON key into the provided field. Specify the source/destination path within your bucket and select which folders from your Pod to transfer.

Click Copy to/from Google Cloud Storage to initiate the transfer. The transfer progress will be displayed in the Runpod interface. Large datasets may take time depending on your Pod’s network connection.

Start by creating a Resource Group to organize your Azure resources. Navigate to Resource Groups in the Azure portal and click Create.

Next, set up a Storage Account under Storage Accounts. Click Create and assign it to your newly created Resource Group.

Navigate to Security + Networking → Access Keys in your storage account to retrieve the authentication key.

Create a Blob Container by going to Storage Browser → Blob Containers and clicking Add Container. Consider creating folders within the container for better organization if you plan to sync data to/from multiple Pods.

In the Runpod console, navigate to the Pods page and select the Pod containing your data. Click Cloud Sync, then select Azure Blob Storage from the available providers.

Enter your Azure Account Name and Account Key in the provided fields. Specify the source/destination path in your blob storage where you want to store your data.

Click Copy to/from Azure Blob Storage to initiate the transfer. The transfer progress will be displayed in the Runpod interface. Large datasets may take time depending on your Pod’s network connection.

Navigate to B2 Cloud Storage Buckets and click Create a Bucket.

Set the bucket visibility to Public to allow Runpod access. You can restrict access later using application keys if needed.

Visit App Keys to create a new application key. This key provides authenticated access to your bucket.

Save both the KeyID and applicationKey securely—the applicationKey cannot be retrieved after creation.

In the Runpod console, navigate to the Pods page and select the Pod containing your data. Click Cloud Sync, then select Backblaze B2 from the available providers.

Enter your Backblaze B2 Account ID, Application Key, and bucket path as shown in the Backblaze interface.

Click Copy to/from Backblaze B2 to initiate the transfer. The transfer progress will be displayed in the Runpod interface.

Go to the Dropbox App Console to create a new app.

Select Scoped Access for API options and Full Dropbox for access type. Choose a descriptive name for your app.

In the Dropbox App Console, navigate to the Permissions tab. Enable all required checkboxes for read and write access to ensure Cloud Sync can transfer files properly.

Return to the Settings tab of your app. In the OAuth2 section, click Generate under Generated Access Token.

Save this token immediately—it won’t be shown again after you leave the page. This token authenticates Runpod’s access to your Dropbox.

In the Runpod console, navigate to the Pods page and select the Pod containing your data. Click Cloud Sync, then select Dropbox from the available providers.

Paste your Dropbox Access Token and specify the remote path where you want to store the data. Creating a dedicated folder in Dropbox beforehand helps with organization.

Click Copy to/from Dropbox to initiate the transfer. The transfer progress will be displayed in the Runpod interface.