Support Passing X-Amzn-Bedrock-Request-Metadata headers for cost allocation within AWS Bedrock

[m4x1202]

Before posting

• I searched existing discussions and issues for similar requests.
• I checked the documentation to confirm this is not already supported.
• This is a product idea or enhancement request, not a support question.
• I removed or anonymized sensitive details from examples and screenshots.

Product area

Dashboard / Admin UI

Problem or use case

Although it is great to see the costs of AI of our users in the Netbird Web UI, it would be awesome to have a similar details directly in the AWS Cost Management.
As far as I know this is possible using Cost-allocation tags.

Proposed solution

I found the this header X-Amzn-Bedrock-Request-Metadata, that seems to, when forwarded as part of the AI requests to Bedrock, should solve the Use case described above:
https://docs.aws.amazon.com/bedrock/latest/userguide/cost-mgmt-request-metadata.html#cost-mgmt-request-metadata-how-it-works

Alternatives or workarounds considered

No response

Community impact and priority

• Deployment type: self-hosted
• I assume a fairly limited group of people is affected, since i don't know how many customers are actually using Bedrock only
• Priority: Low-Medium

Examples from other tools or products

No response

Security, privacy, and compatibility considerations

No response

Implementation ideas

No response

Are you willing to help?

Yes, I can test or validate a proposed implementation.

Additional context

Thanks a lot in advance for the help

[mlsmaycon]

@m4x1202, thanks for submitting the request.

The support is feasible, but I wonder what kind of information you would like to see there? Following current support for different gateways on our platform, we are usually sending users and groups, so potentially the upstream request could have the following:

X-Amzn-Bedrock-Request-Metadata: {"group": "orchestrator", "user": "user@example.com"}

[m4x1202]

Hi @mlsmaycon, thanks a lot for the quick answer.

user and group should be perfect to start with.

I was considering if the policy name that is used would be useful to have as metadata in AWS, but not sure what i would use it for.
The used provider can probably be derived from the used API key.
It might be useful to know what guardrails are applied to a request (e.g. "prompt capture"), especially if you plan to extend the guardrails that can be applied.

[mlsmaycon]

Thanks for the feedback @m4x1202 . Currently we are passing groups and users to the proxy only. We will check in regards the other fields, but it might come in a different PR with metadata customization support for all providers.

[m4x1202]

An extension to this request that would be awesome to have for cost efficiency optimization is the X-Amzn-Bedrock-Service-Tier header (https://docs.aws.amazon.com/bedrock/latest/userguide/service-tiers-inference.html). Not sure how this could be added to the UI of Netbird, but it would be super cool to have.
If needed, i can also add it as a separate discussion. Please let me know 🙂

[mlsmaycon]

Interesting, let me take a look