From the AWS edition of November 10, 2026
OpenAI's Daybreak Red and Daybreak Blue cyber models reach the Bedrock runtime endpoint for enrolled customers via US and Global routing
Amazon Web Services / OpenAI · Cross-SLED cybersecurity · United States and global commercial routing
- Publisher
- AWS What's New
- Original publication
- 2026-11-10
- Source retrieved
- 2026-11-11
- Event date
- 2026-11-10
What happened
AWS announced on November 10, 2026 that eligible customers can call OpenAI's Daybreak Red (GPT-5.6 Cyber) and Daybreak Blue (GPT-5.6 Sol) through the bedrock-runtime endpoint, using US and Global cross-Region inference profiles. AWS describes Blue as the starting point for defensive work and Red for authorized vulnerability research and exploit reproduction, with a lower refusal threshold matched by stronger identity verification, monitoring and access controls. Access requires enrollment in OpenAI's Daybreak program, then an access request through the AWS account team. AWS states inference data is not used for training.
Why it matters
State SOCs, university security teams and utilities that standardize on Bedrock's runtime API can now reach both Daybreak models without a separate endpoint. Daybreak Red was already in GovCloud (US-East); this change concerns commercial routing and does not add GovCloud capacity.
Evidence and measured results
Vendor announcement; no performance data. Independent capability evidence for GPT-5.6 Sol is in the Irregular item in this edition.
Limitations and uncertainty
Vendor claim. Global routing is commercial-only; GovCloud availability for Red was a separate October announcement already archived.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-11; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Security teams want AI-assisted vulnerability work on a standard Bedrock API while meeting third-party verification rules.
- Stakeholders
- CISO
- SOC manager
- Legal counsel
- University security lead
- Discovery questions
- Is the team enrolled in OpenAI's Daybreak program?
- Is Global cross-Region routing acceptable for this data?
- Who authorizes exploit-reproduction work?
- Value hypothesis
- Simpler integration for enrolled teams; security benefit unmeasured.
- Potential engagement
- An authorized Daybreak Blue pilot on one internal codebase.
- Unsupported claims
- Detection rates
- Approval timelines
- Availability of these routing profiles in GovCloud
Pre-sales engineering
Role takeaway
- Fit
- Enrolled security teams in commercial Regions.
- Architecture and integration
- bedrock-runtime with US or Global CRIS profiles.
- Prerequisites
- OpenAI enrollment
- AWS access approval
- Scoped IAM roles
- Constraints
- Enrollment required
- Global profile routes worldwide
- Red intended only for authorized tasks
- Security
- Restrict Red to named users; log all calls; treat outputs as sensitive vulnerability data.
- Proof of value
- Seeded-codebase comparison with existing scanners
- Audit of invocations by user
Delivery
Role takeaway
- Work
- Run an authorized Blue pilot with reproduction checks.
- Dependencies
- OpenAI enrollment
- AWS provisioning
- Remediation owners
- Ownership
- Security operations.
- Skills and adoption
- Analysts need skills validating AI findings.
- Governance checkpoints
- Per-target authorization
- Red access approval
- Routing residency review
- Acceptance criteria
- Proposed: all findings human-reproduced before ticketing
- Proposed: only approved users invoke Red
- Risks
- Exploit misuse
- Enrollment delays
- Residency violations
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Available through US and Global CRIS profiles on bedrock-runtime; regional availability on the bedrock-mantle endpoint is referenced separately.
Governance
Who approves, reviews and stays accountable for outcomes?
Two-stage access gate: OpenAI enrollment, then AWS provisioning. Agencies need rules of engagement for exploit-reproduction work.
Security and privacy
What data, permissions and controls need testing?
Lower refusal thresholds for Red mean misuse controls shift to identity verification and monitoring; agencies must restrict and log users.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Aimed at skilled security staff.
Procurement
What should contracts, pricing and exit terms secure?
Eligibility is decided by OpenAI and the AWS account team; no pricing in the post.
Operating model
Which teams own the service once it runs?
Findings require remediation capacity; global routing may conflict with residency rules for some workloads.
Publication history
- 2026-11-10AWS · Issue 128 resources
Stable resource ID: aws-bedrock-openai-daybreak-runtime-endpoint-20261110