Integrations
AWS Bedrock Core Integration
Link your AWS Bedrock foundation models to the osmAPI orchestration layer for high-scale inference.
AWS Bedrock is Amazon's premier managed service for accessing foundation models from global AI research leaders. This guide facilitates the secure connection between your AWS IAM credentials and the osmAPI gateway.
Integration Prerequisites
- An active AWS Account with Bedrock model access enabled.
- An AWS IAM user with an Access Key ID and Secret Access Key that has permissions to invoke Bedrock models.
- An osmAPI Account with initialized workspace permissions.
Establishing the Connection
AWS Bedrock authenticates via AWS IAM Access Key credentials. You will provide your IAM Secret Access Key in the osmAPI dashboard's provider key field.
Phase 1: Model Authorization in AWS
Activate Model Subscriptions
- Log into the AWS Management Console.
- Search for and enter the AWS Bedrock service.
- Access Model Access via the primary navigation sidebar.
- Select Manage Model Access and authorize the specific model families required for your architecture (e.g., Anthropic Claude, Meta Llama).
- Confirm and wait for the "Access Granted" status to propagate.
Obtain IAM Access Key Credentials
- In the AWS Console, navigate to IAM > Users and select (or create) a user with Bedrock invoke permissions.
- Go to the Security credentials tab and select Create access key.
- Copy both the Access Key ID and the Secret Access Key. The secret key is only shown once.
- The osmAPI dashboard accepts the Secret Access Key in the provider key field, and the Access Key ID in the designated access key field.
Phase 2: Gateway Configuration
Access the Infrastructure Dashboard
- Authenticate with the osmAPI Console.
- Select the target Workspace and Project for integration.
- Access Provider Governance (Provider Keys) in the system settings.
Configure AWS Bedrock Parameters
- Select the Add Key option within the AWS Bedrock module.
- Input your IAM Access Key ID and Secret Access Key (the secret key goes in the provider key field).
- Region Affinity Selection: Define the regional residency for your model traffic:
us.- North American infrastructures (e.g., Virginia, Oregon).eu.- European data residency (e.g., Frankfurt, Ireland).global.- High-availability cross-region endpoints.
- Finalize the connection. Our engine will perform an instantaneous handshake to verify credentials.
Validation Protocol
Verify the orchestration layer is correctly processing AWS traffic with a standard completion test:
curl -X POST https://api.osmapi.com/v1/chat/completions \
-H "Authorization: Bearer ${OSM_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"model": "aws-bedrock/claude-sonnet-4-20250514",
"messages": [{ "role": "user", "content": "Confirm secure gateway connectivity." }]
}'Available Model Catalog
Upon successful integration, the following infrastructure tiers become available via the osmAPI namespace:
- Anthropic Claude 4:
aws-bedrock/claude-sonnet-4-20250514,aws-bedrock/claude-opus-4-20250514 - Anthropic Claude 4.5+:
aws-bedrock/claude-sonnet-4-5-20250929,aws-bedrock/claude-opus-4-5-20251101,aws-bedrock/claude-opus-4-1-20250805
See the full Infrastructure Browser for real-time availability.
Operational Forensics & Troubleshooting
Resource Availability Exceptions
- Ensure the selected Region Prefix matches the region where you enabled model access in AWS.
- Verify that your AWS account has passed the verification stage for specific third-party model families.
Throughput Governance (Scaling)
- AWS Bedrock enforces regional quotas (TPM/RPM). Monitor these via the AWS Service Quotas console to ensure your osmAPI workloads are not throttled at the provider level.
- High-volume users should consider requesting quota increases directly within AWS to maintain optimal performance.
How is this guide?