Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Bedrock provider doesn't work unless using bedrockOptions #3018

Open
elie222 opened this issue Sep 16, 2024 · 0 comments
Open

AWS Bedrock provider doesn't work unless using bedrockOptions #3018

elie222 opened this issue Sep 16, 2024 · 0 comments
Labels
ai/provider bug Something isn't working

Comments

@elie222
Copy link

elie222 commented Sep 16, 2024

Description

This works:

createAmazonBedrock({
          bedrockOptions: {
            region: env.BEDROCK_REGION,
            credentials: {
              accessKeyId: env.BEDROCK_ACCESS_KEY,
              secretAccessKey: env.BEDROCK_SECRET_KEY,
            },
          },
        })(model)

This works when running locally, but not when deploying to Vercel:

createAmazonBedrock({
            region: env.BEDROCK_REGION,
              accessKeyId: env.BEDROCK_ACCESS_KEY,
              secretAccessKey: env.BEDROCK_SECRET_KEY,
          },
        })(model)

I imagine the issue is that Vercel is setting a key that causes the error (https://vercel.com/docs/projects/environment-variables/reserved-environment-variables#allowed-environment-variables). But I didn't manage to track down the error. bedrockOptions worked for me though.

Code example

No response

Additional context

No response

@lgrammel lgrammel added bug Something isn't working ai/provider labels Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/provider bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants