Data collections best practices

Purpose: This document explains best practices to keep in mind when creating a data collection.

Considerations when creating a data collection

Workbench allows you to create data collections in GCP and AWS. The pod you associate to your data collection upon creation will determine the cloud platform.

Policies

Currently, AWS data collections allow data owners to apply region and group policies only. GCP data collections allow for region, group, perimeter, and network policies.

Costs

If your organization primarily uses one cloud platform, it would make financial sense to create a data collection in that platform. Significant cross-platform egress charges can accrue if you're adding resources from a data collection in one cloud platform to a workspace in another cloud platform.

Access controls

Resources must match the cloud platform of the workspace or data collection. For example, AWS resources (such as S3 buckets) can't be added to a GCP workspace or data collection.

Potentially, you could access a data collection on one cloud platform from a workspace on another cloud platform, but this will likely be costly and slow.