Securely upload videos from AWS, GCP, or Azure using direct cloud integration or signed URLs.
There are three primary ways to provide video files to NomadicML:
This page covers the two cloud-native methods in detail below.
To avoid exchanging keys, we offer direct integration with your cloud storage. This approach is ideal for continuous data ingestion pipelines. We support secure, read-only access for the following providers:
Cloud Provider | Integration Method | Details |
---|---|---|
AWS S3 | Bucket Policy | Grant our IAM role (arn:aws:iam::xxxx:role/xxxx-readonly-role ) read-only access to your S3 bucket |
Google Cloud Storage | IAM Policy | Grant the Storage Object Viewer role to our service account (xxxx@our.iam.gserviceaccount.com ) on your GCS bucket. |
Azure Blob Storage | Role Assignment | Please contact us to get the correct Service Principal for role assignment. |
This method avoids exchanging secret keys and gives you full control to manage access from your cloud console. Please contact our support team to configure a direct integration.
If your videos are stored privately in Amazon S3 or Google Cloud Storage, you can provide NomadicML with a pre-signed URL. The SDK will download the file directly.
In Azure, you can generate a Shared Access Signature (SAS) token to create a temporary, secure URL.
If you have many URLs you can pass them as a list or organize them in folders. See SDK Usage Examples for full workflows.
After configuring your cloud storage, you can explore these topics:
Deploy and manage NomadicML within your own Virtual Private Cloud.
Learn how to analyze videos and manage the results.
Securely upload videos from AWS, GCP, or Azure using direct cloud integration or signed URLs.
There are three primary ways to provide video files to NomadicML:
This page covers the two cloud-native methods in detail below.
To avoid exchanging keys, we offer direct integration with your cloud storage. This approach is ideal for continuous data ingestion pipelines. We support secure, read-only access for the following providers:
Cloud Provider | Integration Method | Details |
---|---|---|
AWS S3 | Bucket Policy | Grant our IAM role (arn:aws:iam::xxxx:role/xxxx-readonly-role ) read-only access to your S3 bucket |
Google Cloud Storage | IAM Policy | Grant the Storage Object Viewer role to our service account (xxxx@our.iam.gserviceaccount.com ) on your GCS bucket. |
Azure Blob Storage | Role Assignment | Please contact us to get the correct Service Principal for role assignment. |
This method avoids exchanging secret keys and gives you full control to manage access from your cloud console. Please contact our support team to configure a direct integration.
If your videos are stored privately in Amazon S3 or Google Cloud Storage, you can provide NomadicML with a pre-signed URL. The SDK will download the file directly.
In Azure, you can generate a Shared Access Signature (SAS) token to create a temporary, secure URL.
If you have many URLs you can pass them as a list or organize them in folders. See SDK Usage Examples for full workflows.
After configuring your cloud storage, you can explore these topics:
Deploy and manage NomadicML within your own Virtual Private Cloud.
Learn how to analyze videos and manage the results.