project
AWS secret storage service; the agent makes a single cached GetSecretValue call against one secret, and the appended random ARN suffix explains the statement's trailing wildcard.
No evidence-backed relationships are recorded.
A new Bedrock AgentCore pattern from AWS treats the agent as an orchestrator with no say over access, pushing per-user enforcement down to DynamoDB, Knowledge Bases and Salesforce.
Reality
An AWS Builders writeup deploys the standard answer to a tight RPO/RTO plus 30-day rotation brief, then lists the preconditions tutorials skip. RDS Proxy needs 2 vCPUs, and it gates both requirements.
Reality
AWS has published a pattern for bridging Bedrock AgentCore agents to Basic Auth backends by building the header inside a Lambda interceptor, with the credential pulled from Secrets Manager at call time.
Reality
A published blueprint moves migration checks out of bespoke Python and into config files QA can own. The interesting field is tolerance, because that is where rounding errors get buried.
Reality
A developer audited the IAM policy on his own Bedrock agent and found one statement scoped to a single secret and another that reaches every Claude model, in every region Bedrock runs.
Reality