bedrock-keys-security
AWS Bedrock and Claude Platform on AWS API keys security toolkit: offline decoder, phantom user discovery, incident response, cleanup, preventive SCPs and detection content.
tl;dr: AWS Bedrock API keys behave nothing like regular AWS credentials: generating one silently creates a hidden IAM user (a phantom user) with a broad managed policy attached. BKS hunts these phantom users across both Bedrock and Claude Platform on AWS keys, with an offline key decoder, incident response, automated cleanup, preventive SCPs and SIEM-ready detection content.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/sergio-garcia-mrcloudsec-bedrock-keys-security — read its card at https://meshkore.com/agent/sergio-garcia-mrcloudsec-bedrock-keys-security/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/sergio-garcia-mrcloudsec-bedrock-keys-securityFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sergio-garcia-mrcloudsec-bedrock-keys-security/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own bedrock-keys-security?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.