feat(region): add ap-southeast-5/7, eu-south-1/2 to AgentCore regions

[jariy17]

What

Add the 4 newly-launched AgentCore Regions to AgentCoreRegionSchema:

Region	AWS code
Bangkok	ap-southeast-7
Malaysia	ap-southeast-5
Milan	eu-south-1
Spain	eu-south-2

Why

AgentCore is now GA in these 4 Regions with runtime, identity/access control, policy, gateway, built-in tools, and observability. The CLI's AgentCoreRegionSchema is a hard z.enum allowlist and is the single source of truth for region detection (detectRegion) and deployment-target validation — so until these are added, the CLI rejects them as unsupported.

Changes

• Add the 4 region codes to AgentCoreRegionSchema (src/schema/schemas/aws-targets.ts)
• Update the enumerates all supported regions unit test to match

Testing

vitest run src/schema/schemas/__tests__/aws-targets.test.ts → 22 passed. Lint, prettier, and typecheck pass via pre-commit hooks.

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[github-actions]

Package Tarball

aws-agentcore-0.23.0.tgz

How to install

gh release download pr-1722-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-0.23.0.tgz

[agentcore-cli-automation]

Thanks for adding these — the region set matches the official AgentCore supported regions doc (Bangkok = ap-southeast-7 corresponds to "Asia Pacific (Thailand)", and Malaysia/Milan/Spain are all listed there too).

One blocker before merging: the LLM-compacted schema at src/schema/llm-compacted/aws-targets.ts is a manually-maintained mirror of AgentCoreRegionSchema and wasn't updated. Per src/schema/llm-compacted/AGENTS.md, this file must stay in sync with the Zod schema — otherwise AI coding assistants reading agentcore/.llm-context/ after agentcore init will still think these 4 regions are unsupported and generate invalid configs (or refuse to write them). The prior region-addition PR (#833) by the same author updated both files together, so this looks like an oversight.

Separately (out of scope, just flagging): aws/agentcore-l3-cdk-constructs maintains its own copy of AgentCoreRegionSchema at src/schema/schemas/aws-targets.ts + src/schema/llm-compacted/aws-targets.ts. Those will need a matching PR before the new regions actually work end-to-end via agentcore create, since the vended CDK project uses the constructs' schema to validate deployment targets at synth time.

[agentcore-cli-automation]

The sibling LLM-compacted mirror src/schema/llm-compacted/aws-targets.ts needs the same 4 additions. Per src/schema/llm-compacted/AGENTS.md:

When Zod schemas in schemas/ are updated, manually update the corresponding file here
| aws-targets.ts | schemas/aws-targets.ts |

That file is embedded as text at build time and written to agentcore/.llm-context/ during agentcore init — it's what AI coding assistants read when editing agentcore/aws-targets.json. If left as-is, agents will treat ap-southeast-5/7 and eu-south-1/2 as invalid even though the Zod validator now accepts them.

Please add the same 4 entries to the AgentCoreRegion union in that file (alphabetical order, matching the placement here).