gcloud transfer jobs create/update accepts storage class inclusion flags

Introduced 2026-09-15 · score 0.93

HOW TO USE IT

For a transfer job sourced from Amazon S3, set `--include-storage-classes` to the classes to transfer; use `gcloud transfer jobs update <job-name> --clear-include-storage-classes` to remove the filter.

WHY THIS HELPS

Configure a transfer job to include selected storage classes.

REQUIREMENTS AND LIMITATIONS

• SOURCE (required): Source location; use `s3://<bucket>` for an Amazon S3 source.
• DESTINATION (required): Destination location; Google Cloud Storage uses `gs://<bucket>`.
• NAME (required): Name of the transfer job to update.
• --include-storage-classes: Comma-separated Amazon S3 storage classes to include; objects in other classes are skipped. Example values: `STANDARD,GLACIER`.
• --clear-include-storage-classes: Removes the storage class filter from the object conditions.
• Prerequisite: Storage class filtering applies to transfers from Amazon S3. Valid values are Amazon S3 storage class names.
• Prerequisite: Restore S3 Glacier Deep Archive (`DEEP_ARCHIVE`) and Glacier Flexible Retrieval (`GLACIER`) objects before transferring them.
• Docs conflict: The Google filtering guide, last updated 2026-09-30, says storage class filtering is not supported in gcloud CLI. This conflicts with the release note and current gcloud create/update references, which document the flags; the conflicting guide statement is not used.

FIRST-PARTY EVIDENCE

• https://docs.cloud.google.com/sdk/docs/release-notes#58500_2026-09-15
• https://docs.cloud.google.com/sdk/gcloud/reference/transfer/jobs/create
• https://docs.cloud.google.com/sdk/gcloud/reference/transfer/jobs/update
• https://docs.cloud.google.com/storage-transfer/docs/filtering-by-storage-class

Check the installed version and the source before using it. Entry JSON

Report a problem with this card