AWS Archives - Page 4 of 23

AWS PrivateLink for Bedrock: Keep Coding-Agent Model Calls Off the Public Internet

Create interface VPC endpoints for Amazon Bedrock, restrict them with endpoint policies and aws:SourceVpce, and prove agent model calls skip the NAT.

AI AWS Machine Learning

Amazon Bedrock Knowledge Bases: RAG Over Your Monorepo for Coding Agents

Build a Bedrock knowledge base over a monorepo: export code as Markdown, add metadata, sync from CI, and retrieve with filters in a Converse tool loop.

AI AWS Debugging

AWS Secrets Manager Rotation for Coding-Agent Tool Credentials: Short-Lived Tokens That Can’t Leak Forever

Secrets Manager rotation for coding-agent tools: four-step rotation Lambda tested with moto, GitHub App installation tokens, tag-based access, and keeping secrets out of model context.

AI AWS System Design

Amazon EFS: Shared Workspaces Across Multi-Turn Coding-Agent Tasks

Multi-turn coding agents that re-clone the same monorepo on every Lambda, Fargate, or CodeBuild step waste minutes and burn git forge rate limits. Amazon EFS gives a shared workspace mount across those steps — pick throughput mode wisely, lock security groups and POSIX, and never treat EFS as a substitute for durable artifact stores.

AI AWS System Design

AWS Fargate Spot: Cheap Ephemeral Sandboxes for Coding Agents

Always-on Fargate and long CodeBuild fleets burn money while coding-agent sandboxes sit idle between clone/test/apply bursts. Fargate Spot gives cheap ephemeral capacity for short-lived agent sandboxes — handle SIGTERM interruptions, keep task defs thin, and pair IAM with SCPs so Spot savings do not become Spot blast radius.

AI AWS System Design

AWS Organizations SCPs: Hard Caps on What Coding-Agent Accounts Can Call

Per-tenant coding-agent AWS accounts still blow up when an over-permissioned tool role gets iam:CreateUser or organizations:LeaveOrganization. Service Control Policies at the Organizations OU hard-cap what agent accounts can call even if the role policy is wrong — complementing Verified Permissions and IAM condition keys.

AI AWS Debugging

AWS CodeArtifact: Private Package Mirrors Inside Coding-Agent Sandboxes

Coding-agent sandboxes that npm/pip/go fetch from the public internet are slow, flaky, and supply-chain risky — one compromised package and your agent applies malware as a “fix.” AWS CodeArtifact gives private package mirrors with upstreams, domain policies, and IAM so CodeBuild/Fargate/Lambda sandboxes resolve only approved registries.

AI AWS System Design

MemoryDB vs ElastiCache for Coding-Agent Session State: Durable Cursors and Tool-Result Caches

MemoryDB vs ElastiCache for AI coding agents: durable session cursors, Valkey durability options, cluster-mode hash tags, Lua compare-and-advance, claim-based tool-result cache and DynamoDB ledgers.

AI AWS System Design

AWS Lambda SnapStart for Coding-Agent Tools: Faster Cold Starts on Java, Python and .NET

Lambda SnapStart for coding-agent tools: how snapshots work, Java and Python runtime hooks, uniqueness, pricing, limits and restore metrics.

AI AWS System Design

AWS Budgets + Cost Anomaly Detection: Cap Runaway Coding-Agent Spend

Multi-tenant coding agents can burn Bedrock tokens, Lambda GB-seconds, and Batch vCPU overnight before dashboards catch up. AWS Budgets plus Cost Anomaly Detection give hard caps and intelligent alerts on runaway agent spend — wired to SNS, AppConfig kill switches, and per-tenant EMF metrics.