You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I want to connect Sourcebot with AWS bedrock, attaching a service account to the pod rather than using AWS static ACCESS_KEY and SECRET_ACCESS_KEY. Is there a way?
I'm getting the below error with this approach.
[web] | 2025-09-08T04:10:33.646Z error: [web-actions] AWS SigV4 authentication requires AWS credentials. Please provide either:
[web] | 1. Set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
[web] | 2. Provide accessKeyId and secretAccessKey in options
[web] | 3. Use a credentialProvider function
[web] | 4. Use API key authentication with AWS_BEARER_TOKEN_BEDROCK or apiKey option
[web] | Original error: AWS access key ID setting is missing. Pass it using the 'accessKeyId' parameter or the AWS_ACCESS_KEY_ID environment variable.
[web] | Error: AWS SigV4 authentication requires AWS credentials. Please provide either:
[web] | 1. Set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
[web] | 2. Provide accessKeyId and secretAccessKey in options
[web] | 3. Use a credentialProvider function
[web] | 4. Use API key authentication with AWS_BEARER_TOKEN_BEDROCK or apiKey option
[web] | Original error: AWS access key ID setting is missing. Pass it using the 'accessKeyId' parameter or the AWS_ACCESS_KEY_ID environment variable.
[web] | at /app/packages/web/.next/server/chunks/5676.js:93:54278
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I want to connect Sourcebot with AWS bedrock, attaching a service account to the pod rather than using AWS static ACCESS_KEY and SECRET_ACCESS_KEY. Is there a way?
I'm getting the below error with this approach.
[web] | 2025-09-08T04:10:33.646Z error: [web-actions] AWS SigV4 authentication requires AWS credentials. Please provide either:
[web] | 1. Set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
[web] | 2. Provide accessKeyId and secretAccessKey in options
[web] | 3. Use a credentialProvider function
[web] | 4. Use API key authentication with AWS_BEARER_TOKEN_BEDROCK or apiKey option
[web] | Original error: AWS access key ID setting is missing. Pass it using the 'accessKeyId' parameter or the AWS_ACCESS_KEY_ID environment variable.
[web] | Error: AWS SigV4 authentication requires AWS credentials. Please provide either:
[web] | 1. Set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
[web] | 2. Provide accessKeyId and secretAccessKey in options
[web] | 3. Use a credentialProvider function
[web] | 4. Use API key authentication with AWS_BEARER_TOKEN_BEDROCK or apiKey option
[web] | Original error: AWS access key ID setting is missing. Pass it using the 'accessKeyId' parameter or the AWS_ACCESS_KEY_ID environment variable.
[web] | at /app/packages/web/.next/server/chunks/5676.js:93:54278
Beta Was this translation helpful? Give feedback.
All reactions