01
Availability
Verify us-gov-west-1 access, APIs, quotas, account eligibility, and current documentation.
Browser-local planning aid · Source checked August 9, 2026
Check the control path before the GovCloud pilot
Turn the August AgentCore Memory, Policy, and Harness launch into explicit availability, data, identity, enforcement, deployment, and approval questions. The result identifies missing evidence; it never certifies compliance.
Planning result
Current stage
Discovery
Resolve the highlighted evidence gaps before a bounded pilot.
Unresolved gates
- Verify service access and supported APIs in the authorized account.
- Record the launch, Region, and GovCloud differences evidence.
- Complete the data-flow, authority, failure-test, and rollback review.
This local checklist does not access AWS, validate a configuration, prove data residency, determine control inheritance, certify compliance, estimate cost, or authorize production.
Five gates
Service availability is the start of readiness
02
Data paths
Map memory, model, tool, identity, log, file, support, and external endpoint traffic.
03
Authority
Separate caller, actor, session, harness role, Gateway identity, Policy, and downstream authorization.
04
Failure tests
Test cross-tenant denial, stale memory, LOG_ONLY drift, enforcement changes, and cleanup.
05
Approval
Keep technical readiness separate from compliance, records, security, and production approval.
Continue by control decision
Launch and architecture
Separate the Memory, Policy, and Harness boundaries and GovCloud-specific differences.
Memory decision
Choose raw session events, extracted cross-session records, both, or no persistence.
Cedar and Gateway Policy
Review generated Cedar, observe LOG_ONLY decisions, and protect enforcement changes.
Security, cost, and cleanup
Plan execution roles, network paths, observability, budget controls, and teardown.
AgentCore GovCloud readiness questions
It turns selected planning facts into a local list of unresolved availability, data, memory, policy, and deployment gates. It does not inspect an AWS account or determine compliance.
No. The form runs in the browser and sends no AWS request. Verify service access, APIs, quotas, logs, and configurations in the authorized account using approved procedures.
No. The output is a planning aid. Security, compliance, privacy, records, procurement, model, data-owner, and change-management approvals remain separate decisions.
AWS documents customer-configured Gateway targets, identity providers, browser destinations, and Code Interpreter internet access as paths that may send traffic to customer-selected endpoints outside GovCloud.
Official references: AWS launch announcement, AgentCore release notes, and AgentCore in AWS GovCloud. Recheck current Region support, APIs, differences, infrastructure-as-code coverage, quotas, pricing, and data paths.