CuraDevOps

tag: Data-Residency · 4 items

2026-08-21 · GitLab Blog · source ↗ #gitlab#ai-gateway#data-residency
  • Platform/SRE — Plan: If your org runs GitLab Dedicated, the AI Gateway for Duo Agent Platform is now deployable inside your single-tenant environment, keeping AI-processed data in your chosen AWS region. Evaluate this quarter whether to enable it as part of your agentic DevOps rollout.
  • CI/CD — Skip
  • Leader — Learn: Organizations using GitLab Dedicated for compliance or data-residency reasons can now extend that boundary to AI agent workloads — shapes thinking on how to pursue agentic DevOps without relaxing data-sovereignty requirements.
2026-08-21 · AWS What's New · source ↗ #aws-outposts#ec2-ami#data-residency
  • Platform/SRE — Plan: For teams running workloads on AWS Outposts with data residency requirements, this GA capability enables AMI and backup lifecycle workflows to keep snapshots fully on-Outpost without specifying an ARN manually — worth integrating into Outposts image-management processes this quarter.
  • CI/CD — Skip
  • Leader — Skip
2026-08-19 · AWS What's New · source ↗ #aws-bedrock#ai-ml#data-residency
  • Platform/SRE — Skip
  • CI/CD — Skip
  • Leader — Learn: Relevant if the org operates in India with data-residency requirements and uses Bedrock — this expands the compliant model options available without leaving AWS, worth noting for AI strategy reviews.
  • Platform/SRE — Learn: Relevant only if you have workloads targeting Greece or EMEA data-residency requirements; no action needed unless expanding into that region.
  • CI/CD — Skip
  • Leader — Learn: Worth noting if the org has Greek or EMEA in-country data-residency obligations; no strategic decision required unless expansion into that market is on the roadmap.
  • Signals: GA announcement