FAQ — secops sts v2 feed migration checklist

Domain questions for the 2026-11-01 window. Not a vendor console. Not affiliated.

When do v1 SecOps cloud storage connectors lose support vs permanently stop?

Answer from official docs for secops-sts-v2-feed-migration-checklist: verify dates on the linked sources (https://docs.cloud.google.com/chronicle/docs/deprecations · https://docs.cloud.google.com/chronicle/docs/administration/upgrade-data-feeds-v2). Local tool only helps you structure the work — it never calls the vendor. For secops-admin, treat 2026-11-01 as the hard gate and keep residue owners visible. Domain detail: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain).

What service-account permissions does STS auto-migration need on GCS?

Answer from official docs for secops-sts-v2-feed-migration-checklist: verify dates on the linked sources (https://docs.cloud.google.com/chronicle/docs/deprecations · https://docs.cloud.google.com/chronicle/docs/administration/upgrade-data-feeds-v2). Local tool only helps you structure the work — it never calls the vendor. For secops-admin, treat 2026-11-01 as the hard gate and keep residue owners visible. Domain detail: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain).

Which IP ranges must S3 or Azure Blob allow for Storage Transfer Service?

Answer from official docs for secops-sts-v2-feed-migration-checklist: verify dates on the linked sources (https://docs.cloud.google.com/chronicle/docs/deprecations · https://docs.cloud.google.com/chronicle/docs/administration/upgrade-data-feeds-v2). Local tool only helps you structure the work — it never calls the vendor. For secops-admin, treat 2026-11-01 as the hard gate and keep residue owners visible. Domain detail: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain).

Can one SQS queue serve multiple S3 buckets during v2 migration?

Answer from official docs for secops-sts-v2-feed-migration-checklist: verify dates on the linked sources (https://docs.cloud.google.com/chronicle/docs/deprecations · https://docs.cloud.google.com/chronicle/docs/administration/upgrade-data-feeds-v2). Local tool only helps you structure the work — it never calls the vendor. For secops-admin, treat 2026-11-01 as the hard gate and keep residue owners visible. Domain detail: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain).

What if a feed is stuck with failed credentials during the migration wave?

Answer from official docs for secops-sts-v2-feed-migration-checklist: verify dates on the linked sources (https://docs.cloud.google.com/chronicle/docs/deprecations · https://docs.cloud.google.com/chronicle/docs/administration/upgrade-data-feeds-v2). Local tool only helps you structure the work — it never calls the vendor. For secops-admin, treat 2026-11-01 as the hard gate and keep residue owners visible. Domain detail: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain).

Does this wizard call Google SecOps or change my feeds for me?

Answer from official docs for secops-sts-v2-feed-migration-checklist: verify dates on the linked sources (https://docs.cloud.google.com/chronicle/docs/deprecations · https://docs.cloud.google.com/chronicle/docs/administration/upgrade-data-feeds-v2). Local tool only helps you structure the work — it never calls the vendor. For secops-admin, treat 2026-11-01 as the hard gate and keep residue owners visible. Domain detail: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain).

More: how-to · use cases. Re-check official pages before cutover.