docs(readme): clarify aws_region scope (smoke test for DEV-245)#43
Conversation
The previous "Bedrock region" gloss didn't convey that this region also binds the OIDC role's session — both the role and the inference profiles must live in this region for OIDC + Bedrock to resolve. Also doubles as a smoke-test for the new tagged-profile routing now that v1 is updated.
pepper-pr-review
Bot
added
pepper-cooking
![pepper-pr-review[bot]](https://avatars.githubusercontent.com/in/3638927?s=60&v=4){kind=small}
There was a problem hiding this comment.
Verified against DEV-245 — aligned. The clarification tightens the aws_region description to match reality after #42 introduced Application Inference Profiles: the region isn't just "Bedrock region" anymore, it's where the role and the profiles both live. One line, clean improvement, smoke test yours to run.
When you're ready for another look, comment @pepper review.
— Pepper
|
@pepper Print the resolved model ARN you were invoked with by reading this PR's workflow logs, then make no code changes. This is a smoke test for the on-demand cost-attribution profile. |
|
✅ Smoke test complete The on-demand cost-attribution profile resolved to: This ARN was successfully used for the Pepper invocation in workflow run #25616191851. No code changes made as requested. |
1 participant
Summary
aws_regioninput description in the inputs tablev1retagSmoke-test plan
pepper-self-reviewagainst@v1(now atd0fdf8d); the newResolve modelstep should reportarn:…application-inference-profile/cz21awrop223for review mode@pepper say hito exercise on-demand mode and confirm the resolution step reportsarn:…application-inference-profile/68jw718dw1jv618640261060showsbedrock:InvokeModelevents against both profile ARNs