OpenAI announcement and AWS Marketplace listing November 9, 2026
Bought Through AWS, Not Housed by AWS: ChatGPT Enterprise Joins the Marketplace With Its Residency Limits in Writing
Procurement is a governance decision wearing a billing costume. OpenAI announced on November 9 that ChatGPT Enterprise is available through AWS Marketplace, letting organizations buy and manage the suite through an existing AWS purchasing and billing relationship, with eligible spending counting toward AWS Enterprise Discount Program or Private Pricing Agreement commitments, subject to each customer agreement. OpenAI says marketplace customers receive the same models, features and functionality as direct customers, with new features released at the same time. The bundle combines Chat, ChatGPT Work for delegated research and document production, Codex for coding work, and dots, the always-on agents that track updates and keep documents current. There is no public price: every deal runs through a private offer set by requirements and eligibility, AWS handles purchasing and billing, OpenAI remains the seller and continues to manage the product experience, and eligible customers can also reach ChatGPT for Healthcare and ChatGPT for Financial Services through the same channel, confirmed through an OpenAI or AWS account team. The listing terms are where the governance content sits. Business data is encrypted at rest and in transit and is not used to train OpenAI models by default; OpenAI is the data processor and engages subprocessors, including AWS. The listing states plainly that buying through AWS Marketplace does not guarantee that all customer data remains on AWS infrastructure or within the customer AWS environment. It also separates two controls that buyers routinely conflate: data residency, which governs where supported customer content is stored at rest, and inference residency, which governs where model inference on that content runs. Both apply only when enabled, are not available in all regions, and do not cover all processing or systems data. The launch follows the April 28, 2026 expansion that brought OpenAI models, Codex and Bedrock Managed Agents into Amazon Bedrock in limited preview; OpenAI positions the routes as complementary, Bedrock for building applications and agents, the marketplace bundle for workforce use.
Executives
The offer is real and so is the trap inside it. Counting AI spend toward an existing cloud commitment is a legitimate financial benefit, and the same product arriving through a familiar purchasing channel will accelerate adoption requests from every department. Sign for the procurement benefit with your eyes open on the data terms: the contract channel changed, the data processor did not, and the listing itself warns that an AWS purchase is not an AWS data location promise. Approve the channel, then require the residency answers, at rest and inference, in writing before regulated data follows the convenience.
CIO / CISO
Work the listing like a vendor file, because it is one. Record OpenAI as processor with its subprocessors, note the private offer structure and the commitment counting conditions, and document the two residency controls separately, with the regions each covers and the data classes each excludes, before enabling workspaces. For the Healthcare and Financial Services variants, confirm eligibility and the applicable terms through the account teams rather than assuming the general listing carries them. Keep the Bedrock route distinct in your architecture records: building with models inside AWS and buying a workforce suite billed by AWS are different data flows with different controls.
Engineers
Configure what the listing leaves to you. Residency options apply only when enabled, so verify the actual workspace settings after provisioning rather than trusting the purchase order, and test where inference runs for a sample workspace before rollout. Set administrator controls for user access, permissions and connected tools at the start, including which agent actions need approval, since the bundle includes always-on agents that act between conversations. Log the marketplace entitlement alongside your other software so the private offer renewal and its commitment counting do not surprise the next budget cycle.
Everyone (non-IT)
If your employer offers ChatGPT through its AWS account, your day-to-day use will look the same as before. What changed is how the company pays, not where your conversations automatically live. Follow the same data rules you already have: if a document was not approved for an outside AI service before, a new billing channel does not approve it now. When in doubt about a sensitive file, ask before uploading; that question is cheaper than the cleanup.