Update bedrock.md for variable consistency

[superpoussin22]

remove CUSTOM_ for consistency

Title

Standardize the variables name ( use always the same )
As the variables are also used by bedrock guardrails, remove CUSTOM_ prefix

Relevant issues

If CUSTOM_… is used bedrock guardrail don’t find the variables

Type

🐛 Bug Fix
🧹 Refactoring
📖 Documentation

Changes

@ishaan-jaff @krrishdholakia

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
litellm	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 1, 2025 8:28pm

[krrishdholakia]

Hey @superpoussin22 the key name shouldn't matter. It's just doing a os.getenv(). What exactly was the issue you ran into?

[superpoussin22]

When you try to use bedrock guardrail , it fails if variable is CUSTOM_…..
nothing in the doc about credential when using bedrock guardrail , but removing CUSTOM_ allows me to go 1step further
I was using the example from the doc to setup the bedrock models and spent time to debug guardrail, so I thing using same names of variable would be fine to avoid confusion, in particular because there’s no instruction on bedrock guardrails doc in litellm to pass such info (@krrishdholakia I sent you more details a few days ago )

[ishaan-jaff]

this makes sense, the doc should use the same env var name

[ishaan-jaff]

the doc starts with mentioning AWS_ vars, so @superpoussin22's fix makes it consistent