chore(tests): re-migrate Bedrock CI to AWS account 941277531214

[mateo-berri]

Relevant issues

Slack context: https://berriaillm.slack.com/archives/C09NFLCD8FP/p1782416661022059?thread_ts=1782403968.400269&cid=C09NFLCD8FP

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Screenshots / Proof of Fix

The agentcore transformation tests pass (32 passed) and the reasoning-effort-grid opus-4-7 xfail behavior is confirmed (11 xfailed, no live calls). The live Bedrock CI jobs themselves will exercise the new account 941277531214 once this runs in CI

Type

🧹 Refactoring
✅ Test

Changes

This undoes the revert PR #29326 (Revert "chore(tests): migrate Bedrock CI to AWS account 941277531214 (#28728)") and brings Bedrock CI back onto the new AWS account 941277531214, re-applying the original migration #28728

It was produced by reverse-applying the revert commit f11c12d off litellm_internal_staging, then hand-resolving three drifted files. tests/batches_tests/test_bedrock_files_and_batches.py was already back on 941277531214 via #29477, so it stays as-is. tests/llm_translation/reasoning_effort_grid/grid_spec.py keeps the base's evolved opus-4-7 cell while re-adding the migration's fail_reason xfail. tests/litellm_utils_tests/test_litellm_overhead.py was rewritten to mocked transports upstream, so the migration hunk no longer applies and that file is unchanged

The net effect is 20 files changed, swapping the old account 888602223428 and its associated resources (S3 buckets, guardrail IDs, SageMaker endpoint, knowledge base / vector store id, AgentCore runtime ARN, live-call model strings, image-gen mocks) back to the 941277531214 equivalents. Verified no stray 888602223428 references remain in the migrated files

---

Generated by Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[devin-ai-integration]

🚅 Hi, thanks for the PR! I'm Agent Shin, the automated triage bot for this repository. What's this and why am I getting it?

I read the description against our contribution rubric. Here's how it lined up:

What you got right:

• ✅ Clear problem description
• ✅ Expected vs. actual behavior

What's still missing:

• linked GitHub issue or clear issue reference
• end-to-end QA proof with screenshots, video, or real commands plus output

The PR body explains the migration and what changed, so it satisfies context, but it does not include any acceptable end-to-end proof. The only evidence is test/status claims and mocked/unit-test results, which do not count as QA proof for triage.

If the description isn't updated in the next 24 hours, I'll auto-close this PR. That's not us saying we don't care about the change; we want the open-PR list to mirror what a maintainer can act on right now, so contributors don't get lost in a backlog. A closed PR is a soft "park this for later," not a rejection. Take your time; everything below still works after the close.

During the grace period: just update the PR description with the missing pieces. No need to ping me; I'll re-check on the next sweep and skip the auto-close if it now passes. See what counts as QA proof for the full rubric (a linked issue alone isn't enough; it covers context, not proof).

If the PR does get auto-closed in 24 hours, you still have easy recovery paths:

• Comment @agent-shin reconsider after updating the description. I'll re-evaluate and reopen the PR if it now passes.
• Comment @greptileai to request a fresh Greptile review; that still works even after the PR is closed, and a stronger score is one of the signals that lifts the PR back into the queue. So a low Greptile score isn't a blocker either.

Internal BerriAI contributors: this rubric doesn't apply to you; ping a maintainer.

(I'm an LLM, so I'm not infallible. If you think I got this wrong, ping a maintainer; they'll override me.)