Skip to content

Project

AWS Secrets Manager

AWS Secrets Manager is a managed AWS service for storing, retrieving, and automatically rotating secrets like database credentials and API keys.

Known aliases

  • Secrets Manager

Current stories

buildConfirmed2 publishers

AgentCore's region-wide default role let one public agent's stolen credentials reach every agent in the account

Zenity Labs found that one prompt to a single public Amazon Bedrock AgentCore agent could take over every agent in the same AWS account and region. Zenity says the partial fix from AWS still leaves teams to cut each agent's role down to minimal access by hand.

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives65
Confidence55
buildOne report1 publisher

A 15-minute IAM token replaces the password Lambda keeps in its environment variables

Taking the password out of a Lambda's environment variables costs five console steps and one inline rds-db:connect policy, and buys a database credential that expires fifteen minutes after boto3 mints it.

Publishers:dev.to

Reality

Evidence44
Adoption
Not scored
Hype gap+26
Incentives28
Confidence54
buildOne report1 publisher

Elastic Beanstalk's Cluster Mode shares one EKS cluster across every app in a subnet set

AWS now says it takes full operational responsibility for Elastic Beanstalk production environments for the life of the application. Underneath, Cluster Mode puts multiple apps on one shared Amazon EKS cluster.

Publishers:aws.amazon.com

Reality

Evidence35
Adoption20
Hype gap+35
Incentives90
Confidence60
buildOne report1 publisher

AWS's Git metrics pipeline baselines AI coding tools on commit and pull request counts

AWS's walkthrough for the pattern wires GitHub and GitLab activity feeds through Step Functions into QuickSight on a schedule you set in CloudFormation, with a detector Lambda that skips the whole cycle when nothing has changed.

Publishers:aws.amazon.com

Reality

Evidence46
Adoption
Not scored
Hype gap+22
Incentives82
Confidence56
buildOne report1 publisher

AgentCore's Consent portal absorbs the five pieces of session binding you used to host

AgentCore Identity now hosts the redirect leg and keeps the tokens, and what you configure in exchange is an OIDC application in your corporate IdP, a service role, and AWS's callback URL inside your GitHub and Slack apps.

Publishers:aws.amazon.com

Reality

Evidence62
Adoption12
Hype gap+8
Incentives88
Confidence55
buildOne report1 publisher

DB_PASS slips past the five keywords Spring Boot's env sanitizer matches on

The default masking on Spring Boot's /actuator/env tests the property name against five words, so a dev.to post's DB_PASS and WEBHOOK_SIGNING examples print in plaintext, and the custom pattern it proposes covers only those examples.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+35
Incentives25
Confidence55
buildOne report1 publisher

Opting into native Git in SageMaker Unified Studio turns every save into a staging decision

Auto-sync put whatever sat on disk into Git history, notebook outputs and stray credentials included. File-level staging fixes that, and it also breaks every handoff a team built on the assumption that saving was enough.

Publishers:dev.to

Reality

Evidence32
Adoption
Not scored
Hype gap+18
Incentives52
Confidence34
buildOne report1 publisher

ECS Express Mode bakes 5% of traffic for three minutes before it shifts the rest

Express Mode turns a container image and two role ARNs into an HTTPS service on Fargate. The engineering question it leaves behind is which of its inherited defaults match your workload and which will quietly fight it.

Publishers:thenewstack.io

Reality

Evidence45
Adoption
Not scored
Hype gap+25
Incentives88
Confidence55
buildOne report1 publisher

Fitting 6.155 GB of Gemma 4 weights lands you on AWS's only Arm GPU family

The cheap fractional-GPU tiers top out at 3 GB of device memory, so the weights pick the instance and hand you a Graviton2 host with a 2018 Turing card. The interesting cost is the toolchain, not the hourly rate.

Publishers:dev.to

Reality

Evidence48
Adoption14
Hype gap−14
Incentives42
Confidence41
buildOne report1 publisher

Seven calls to a secret, with zero Secrets Manager permissions on paper

A CloudGoat walkthrough moves an API key through SNS into API Gateway and back out of Lambda. Access Analyzer and PMapper both report the user has no access.

Publishers:dev.to

Reality

Evidence52
Adoption
Not scored
Hype gap+34
Incentives72
Confidence46
buildOne report1 publisher

AWS moves agent authorization out of the agent and into the plumbing

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.

Publishers:aws.amazon.com

Reality

Evidence56
Adoption
Not scored
Hype gap+22
Incentives80
Confidence58
buildOne report1 publisher

Two mechanisms, one vCPU floor: why db.t3.micro cannot meet a 1-second RPO on RDS

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.

Publishers:dev.to

Reality

Evidence34
Adoption
Not scored
Hype gap+12
Incentives28
Confidence42
buildOne report1 publisher

Basic Auth becomes a gateway problem: AgentCore's Lambda interceptor keeps the password away from the model

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.

Publishers:aws.amazon.com

Reality

Evidence62
Adoption
Not scored
Hype gap−8
Incentives68
Confidence58
buildOne report1 publisher

The YAML file is the reconciliation script now

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.

Publishers:dev.to

Reality

Evidence26
Adoption
Not scored
Hype gap+24
Incentives52
Confidence33
buildOne report1 publisher

Two Actions, One Loose Policy: The Bedrock Wildcards That Widen A Least-Privilege Grant

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.

Publishers:dev.to

Reality

Evidence55
Adoption12
Hype gap−5
Incentives25
Confidence58