How to: secops sts v2 feed migration checklist

Use this local guide before 2026-11-01. Re-check official vendor documentation for authoritative dates. This site does not call vendor APIs or store tokens.

1. Step 1. Confirm Nov 1 2026 EOS and Mar 15 2027 EOL on Product deprecations + upgrade-data-feeds-v2
2. Step 2. List active feeds still on GOOGLE_CLOUD_STORAGE / AMAZON_S3 / AMAZON_SQS / AZURE_BLOBSTORE v1
3. Step 3. Grant the new STS-related service account on each GCS bucket before auto-migration wave
4. Step 4. Allowlist STS IP ranges on S3 and Azure Blob network controls
5. Step 5. Ensure each SQS queue maps to one S3 bucket with matching credentials
6. Step 6. Clear or rotate feeds stuck on failed credentials that block migration
7. Step 7. Optionally self-replace v1 feeds with v2 connectors per the upgrade guide
8. Step 8. Export Markdown checklist with deprecations + upgrade URLs into the SecOps ticket

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates. Export your Markdown pack into the change ticket with the official URLs listed on the home page.

Context for operators: Google SecOps v1 Cloud Storage/S3/SQS/Azure Blob connectors EOS Nov1 2026 / EOL Mar15 2027 (STS auto-migration domain). The gap this wedge fills: deprecations+upgrade 双源；缺本地可勾选 SA/IP/凭据前置闸。不做 Chronicle/SecOps SaaS。 Keep owners assigned on every residue row so nothing silently slips past the deadline. When in doubt, re-open the official source pages rather than trusting a cached screenshot.