Skip to content

Conversation

bioshazard
Copy link

@bioshazard bioshazard commented Mar 27, 2025

Closes #1561

Though I recommend y'all completely remove the pre-checks. Just catch a failed JSON parse then hand it off directly to Vercel to handle the errors anyway. Worked w/ endpoint override. And actually because setting bedrockOptions discards the others, it picked up my Env vars too! Works great as is tho!

AWS_BEDROCK_CONFIG={ ... , "bedrockOptions": { "endpoint": "https://REDACTED.vpce.amazonaws.com" } }

@bioshazard bioshazard changed the title #1561: Permit bedrockOptions in AWS_BEDROCK_CONFIG feat: Permit bedrockOptions in AWS_BEDROCK_CONFIG Mar 27, 2025
@bioshazard bioshazard changed the title feat: Permit bedrockOptions in AWS_BEDROCK_CONFIG feat: permit bedrockoptions in aws bedrock config Mar 27, 2025
@Stijnus Stijnus self-assigned this Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AWS Bedrock Config - Custom Endpoint (eg Private Link)
2 participants