Skip to main content

Buyer guide

Amazon Q Developer Data, Region, and Indemnity Checklist

Which tier trains on your content, where each feature stores it, how to opt an organization out, and what the AWS Service Terms indemnity covers.

Reading time
3 min read
Sources
14 cited
In this piece
Amazon Q Developer+10 Mixed

Settle six points with security and legal while Q Developer is still in use. They are content training by tier, storage location by feature, the organization opt-out, the AWS indemnity's coverage and exclusions, administrator logging, and the plugin versions on developer machines. Each item links the AWS page that states it.

When you need this

  • Some engineers use the Free tier through Builder ID next to colleagues on Pro.
  • Your data residency rules require content to stay in a named Region.
  • Legal asks what happens if Q's output infringes someone's intellectual property.
  • Audit asks who asked Q what, and what it answered.

Evaluation criteria

  1. Know which tier trains on content

    Is any of your content eligible for model training?

    Look forCheck every user's tier. AWS can use Free tier questions and generated responses or code for service improvement and model training. AWS excludes Pro content and content from the GitHub integration before general availability. Slack and Microsoft Teams run only on Free terms.

  2. Opt the organization out

    Is every Free tier surface opted out?

    Look forApply an AWS Organizations AI services opt-out policy to the console, mobile app, AWS websites, and chat apps. Have each Free IDE user disable content sharing in the plugin. Administrators cannot set that option, so put company-code users on Pro or paid Kiro seats. Organization policies and the recommended IAM Identity Center setup require the management account. A June 2025 r/aws account describes needing the reseller that owned that account to act.

  3. Map where content is stored

    Which features keep content in your Region?

    Look forMap storage by feature. For Pro users on IAM Identity Center, console chat, console error diagnosis, IDE plugins, and the command line store content in the Q Developer profile's Region. Other Pro features and all Free features store content in US Regions. Cross-region inference stays within the storage geography. Use a service control policy to block features that store content in the US.

  4. Keep the indemnity conditions

    Will the AWS indemnity apply if a claim arrives?

    Look forKeep public code suggestion suppression on and record which users hold Pro seats. Section 50.10 of the AWS Service Terms covers third-party IP claims against Amazon Q output but excludes Q Developer Free. AWS will not cover claims caused by disabled filters, customization, infringing input, or continued use after notice.

  5. Turn on logging

    Can you reconstruct who asked Q what?

    Look forEnable prompt logging to your S3 bucket. It records IDE chat prompts and responses plus accepted or rejected suggestions. Enable daily user activity reports and CloudTrail records of Pro API calls. Apply your retention policy to the buckets.

  6. Patch the plugins

    Do you know which plugin versions run on developer machines?

    Look forTrack plugin versions through device management until you remove the plugins. A malicious change reached VS Code extension 1.84.0 in July 2025. AWS says it failed to run, removed that version, and directed users to 1.85.0 under CVE-2025-8217.

Questions to ask vendors

  1. How many engineers sign in with Builder ID on the Free tier, and how do we move them to paid seats?
  2. Is an AI services opt-out policy attached at the organization root?
  3. Which Q features do we use that store content in US Regions, and is that acceptable?
  4. Who owns the prompt logs and user activity reports, and how long are they kept?

Red flags

  • Free tier sign-ins on company code with content sharing left on.
  • Legal relying on indemnity for Free tier users, whom Section 50.10 excludes.
  • Data residency claims made without checking which Q features store content in the US.
  • No record of plugin versions on developer machines.

Products in this piece

Sources

Official documentation
13
Public source
1
  1. Amazon Q Developer docs: Service improvementOfficial documentationdocs.aws.amazon.com
  2. Amazon Q Developer docs: Opt out of data sharing in the IDE and command lineOfficial documentationdocs.aws.amazon.com
  3. AWS Organizations docs: AI services opt-out policiesOfficial documentationdocs.aws.amazon.com
  4. Amazon Q Developer docs: Chatting with Amazon Q Developer in chat applicationsOfficial documentationdocs.aws.amazon.com
  5. Amazon Q Developer docs: Data storageOfficial documentationdocs.aws.amazon.com
  6. Amazon Q Developer docs: Cross-region processingOfficial documentationdocs.aws.amazon.com
  7. Amazon Q Developer docs: Amazon Q Developer for GitHub (Preview)Official documentationdocs.aws.amazon.com
  8. AWS Service Terms (Section 50, Amazon Q and Kiro)Official documentationaws.amazon.com
  9. Amazon Q Developer pricingOfficial documentationaws.amazon.com
  10. Amazon Q Developer docs: Logging users' promptsOfficial documentationdocs.aws.amazon.com
  11. Amazon Q Developer docs: Viewing the activity of specific usersOfficial documentationdocs.aws.amazon.com
  12. Amazon Q Developer docs: Logging API calls using AWS CloudTrailOfficial documentationdocs.aws.amazon.com
  13. AWS Security Bulletin AWS-2025-015: Amazon Q Developer for VS Code extension version 1.84 (Jul 23, 2025)Official documentationaws.amazon.com
  14. r/aws: setting up Q Developer when a reseller owns the management account (Jun 18, 2025)Public sourcereddit.com

Keep reading

  1. Buyer guideAmazon Q Developer Workflow Playbook: Rules, Approvals, and Reviewed ChangesHow teams still on Q Developer brief it with project rules, limit agentic chat to approved tools and read-only AWS roles, and review its changes and findings before merge.
  2. Buyer guideMoving from Amazon Q Developer to KiroWhat changes for Q Developer CLI and IDE plugin users, how Q Developer Pro seats map to Kiro tiers, and which transformation jobs to finish. Both plugins and paid subscriptions end on April 30, 2027; settle the move before then.
  3. ResearchAmazon Q Developer's End of Support: What Ends, What Stays, and WhenAWS ends Q Developer's IDE plugins and paid seats on April 30, 2027. Every dated step since the CLI moved to Kiro in November 2025, and what stays in the console and chat apps.
Read the research