Option C satisfies both the enterprise routing requirement and sound application architecture. Claude is available through Amazon Bedrock, and Anthropic provides Bedrock-specific SDK integration rather than requiring applications to call api.anthropic.com directly. Current Anthropic documentation describes Claude in Amazon Bedrock as operating through AWS-managed infrastructure with AWS-native authentication, billing, and security boundaries. Newer Bedrock integrations use the Messages API shape, allowing substantial application logic to remain consistent across provider environments.
Anthropic SDKs also provide dedicated Bedrock clients—for example, Python includes AnthropicBedrockMantle for current Bedrock deployments. Keeping business logic separated from provider-specific authentication, endpoints, model identifiers, and transport configuration reduces migration and maintenance risk.
A violates architectural simplicity by duplicating every call unnecessarily. B knowingly violates the enterprise requirement until migration occurs. D directly ignores the contractual routing constraint and is therefore invalid regardless of technical feasibility.
The correct approach is to make Bedrock the configured inference provider while keeping higher-level application and agent behavior decoupled from provider-specific implementation details. Relevant Claude Developer topics are Claude API mechanics, cloud-provider integrations, Amazon Bedrock, SDK configuration, authentication boundaries, model invocation, and provider abstraction.
===============
