Delegated Access allows you to securely and seamlessly host your unlabeled data in your preferred cloud storage provider while providing Labelbox with the limited access necessary so you can view and label your data in Labelbox. You can store your assets in an AWS S3, GCP, or Azure buckets and use native Identity and Access Management (IAM) roles and policies to control access.
Tiled imagery (Slippy maps)
Tiled imagery (COG, NITF, GeoTIFF)
You can also use delegated access to host attachments to your Data Rows.
At a high level, you will need to set up an IAM role in your cloud provider's account and grant Labelbox the ability to assume that role in order to perform certain tasks on your behalf. Then, you create a policy that defines exactly what that assumed role can do.
For example, Labelbox needs to be able to access assets stored in your AWS S3 bucket that you would like to label. So, you would grant the role the ability to perform GetObject requests on a particular S3 bucket (the setup instructions below will explain how to do this).
Delegated Access is highly flexible and allows you to control access at the granularity that you desire. You can grant Labelbox access to all of your buckets, a single bucket, or even a particular path within a bucket. You can even set up different integrations within Labelbox for different datasets or projects. Delegated Access allows you to use private cloud-hosted buckets with Labelbox, which helps to ensure that your assets are kept safe.
The Labelbox app will access assets for display in the user interface (e.g., during a labeling workflow, label review, when configuring a dataset, etc).
When the Labelbox app needs access to an asset, it will request an expiring, signed URL from the Labelbox API (the backend). The backend will assume the role that you configured in your AWS account and generate a signed URL for the asset being requested. The URL will then be returned to the frontend, which will use it to access the asset directly from your cloud storage:
The Labelbox backend also needs access to assets in order to extract metadata (e.g., image and video dimensions, video codec and length, etc.), generate thumbnails, and more advanced tools.
The backend similarly assumes the role that you configured, generates a temporary signed URL, and then uses that URL to access the asset. For example, the backend will download an asset, process it (e.g., media attribute extraction), and then release/delete it. Wherever possible, the asset will only be downloaded to memory and all processing will occur in memory. However, there may be cases where processing requires that the asset be written to a non-memory file system temporarily. In these cases, the asset will be written to some other ephemeral storage (such as a container’s file system) and deleted when processing completes.
Data processing location
Currently, all asset processing is performed in US-based datacenters.
#!pip install labelbox import labelbox organization = client.get_organization() print(organization.get_iam_integrations()) print(organization.get_default_iam_integration()) iam_integration = organization.get_iam_integrations() dataset = client.create_dataset(name="IAM manual demo", iam_integration=iam_integration) task1 = dataset.create_data_rows(datarows) task1.wait_till_done()
Currently, the expiration time is set between 15 minutes to 24 hours depending on the selected cloud provider.
Yes, simply remove the “GetObject” permission from your AWS role’s permission policy and all active signed URLs will cease to have access to your S3 bucket.
Normally, Labelbox-hosted assets are served through a CDN to improve performance; however, Delegated Access assets are served directly from customer S3 buckets, so no CDN caching occurs.
To control browser caching, you can configure various cache-related headers on your S3 bucket. See this link for details.
Yes, you might want to restrict access to your assets by only allowing requests from certain IP ranges. However, make sure to also grant the Labelbox backend (126.96.36.199) access to your assets.
No, label annotations (e.g., image segmentation masks) are still stored in Labelbox-hosted storage, even when the underlying data row is customer-hosted.
It is possible to create multiple integrations. However, it is recommended to create only a single integration and make it the default. You can control what buckets to provide access to by configuring the IAM policy within the respective cloud provider.
Every time you create a new dataset (via app or SDK), the Labelbox application will use the default IAM Delegated Access integration to access the content. This offers the best "set and forget" experience for customers who use Labelbox regularly.
Updated about 1 month ago