Skip to main content

​
Amazon Bedrock Embeddings Configuration

Amazon Bedrock Embeddings Configuration Interface The Amazon Bedrock embeddings configuration screen in Novaplan AI where you’ll enter your AWS Region, Model Name, and Provider Novaplan AI allows you to integrate with Amazon Bedrock’s foundation embedding models to enable vector search, semantic similarity, and document retrieval in your workspace. AWS Bedrock provides access to embedding models from leading AI providers including Cohere and Amazon.

​
Required Fields

​
Region *

The AWS Region where your Bedrock service is deployed. Example: us-east-1 Common regions with Bedrock availability:
  • us-east-1 (N. Virginia)
  • us-west-2 (Oregon)
  • eu-west-1 (Ireland)
  • ap-northeast-1 (Tokyo)
How to choose a region:
  • Select a region close to your users for lower latency
  • Ensure the embedding models you need are available in that region
  • Consider data residency requirements for your organisation

​
Model Name *

The Model Name field specifies the model ID you want to use with Novaplan AI. Available Amazon Bedrock embedding models:
  • cohere2.embed-multilingual-v3 - Cohere’s multilingual embedding model, supports 100+ languages
How to find model IDs:
  1. Go to the AWS Bedrock Console
  2. Navigate to “Model access” to see available models
  3. Select “Base models” to view model IDs
  4. Use the model ID exactly as shown in the console

​
Provider *

Select the provider of the embedding model you are using. This helps Novaplan AI properly format requests for the specific model. Available providers:
  • Cohere - Cohere embedding models
  • Amazon (Titan) - Amazon’s Titan embedding models
  • Other - For any other providers (requires Custom Provider Name)

​
Optional Fields

​
AWS Access Key ID

The AWS Access Key ID for authenticating requests to AWS Bedrock. Both AWS key fields can remain blank when Novaplan has configured an approved credential source for the managed backend, such as a workload role. The accessible backend then uses the Boto3 credential provider chain. Confirm which identity the deployed service uses; a login on your own computer is not automatically available to it.

​
AWS Secret Access Key

The secret portion of your AWS credentials. Use an explicit access key pair only if your AWS administrator and Novaplan agree it is needed. Define least-privilege permissions, a secure transfer method, and rotation before entering the keys. Never publish a real secret. AWS recommends temporary credentials where possible.

​
Configuration Steps

As shown in the image above:
  1. Click Configure on the Amazon Bedrock provider card
  2. Specify your AWS Region (marked with *)
  3. Enter the Model Name (model ID) (marked with *)
  4. Select the appropriate Provider from the dropdown (marked with *)
  5. (Optional) Enter the approved AWS Access Key ID only if Novaplan is using explicit keys
  6. (Optional) Enter its matching AWS Secret Access Key through the approved setup flow
  7. Click Add Model to save and validate your credentials
Region, Model Name, and Provider are required. The two key fields may be blank only when the managed backend has another approved AWS credential source.

​
IAM Permissions

The AWS identity used by the managed service needs bedrock:InvokeModel for the selected embedding model. Add bedrock:InvokeModelWithResponseStream only if the actual call path requires streaming. An inference profile may need additional permissions. Ask your AWS administrator to scope resources to the model or profile in use; do not copy an unrestricted Resource: "*" policy. See AWS’s inference prerequisites.

​
Usage Considerations

  • API usage will count against your AWS Bedrock quotas and billing
  • Different models have different pricing — check AWS Bedrock pricing for details
  • AWS Bedrock provides enterprise features including VPC endpoints, CloudTrail auditing, and data encryption

​
Troubleshooting

  • If you encounter authentication errors, verify the AWS identity configured for the managed backend or, if explicit keys were approved, the matching key pair
  • Ensure that AWS identity has the necessary Bedrock permissions
  • Verify the selected region has AWS Bedrock available and your desired model is accessible
  • Check that you have model access enabled for the specific model in the AWS Bedrock console
  • Ensure the model ID is correctly formatted as shown in the Bedrock console
For additional support, refer to the AWS Bedrock documentation or contact Novaplan AI support.