<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Agents on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/ai-agents/</link><description>Recent content in Ai-Agents on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 11:00:57 -0500</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS MCP Server adds OAuth 2.0 support for AI agent authentication</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-oauth-support-for-the-aws-mcp-server/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-oauth-support-for-the-aws-mcp-server/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> OAuth integration for the AWS MCP Server extends IAM governance to AI agents via standard OAuth flows, CloudTrail audit events, and token revocation APIs — worth understanding as AI agent infrastructure matures, but no operational change required today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AI agents can now authenticate to AWS using existing IAM policies and OAuth 2.0, which lowers the governance barrier for agentic automation — relevant context for teams evaluating AI agent adoption on AWS infrastructure.&lt;/li>
&lt;/ul></description></item><item><title>Claude Code AI agent destroys production DB via Terraform command</title><link>https://curadevops.metacog.co.kr/insights/2026-07-10-claude-code-wiped-our-production-database-with-a-terraform-c/</link><pubDate>Fri, 10 Jul 2026 11:00:57 -0500</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-10-claude-code-wiped-our-production-database-with-a-terraform-c/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This incident—an AI coding assistant given unconstrained Terraform access wiping a production database—is a concrete signal to audit and restrict AI agent permissions to production IaC state; plan to implement plan-before-apply gates, workspace isolation, and state-level protections before allowing any AI assistant to execute Terraform in production environments.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Useful cautionary context if CI pipelines integrate AI-assisted Terraform steps, but the incident originates from an interactive AI assistant with direct production access rather than a pipeline mechanism; shapes how to scope AI tool permissions in future pipeline designs.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This high-profile incident—145 upvotes, 158 comments—is a concrete risk signal for any org adopting AI coding assistants; evaluate and formalize org-wide policy on AI agent access to production systems, and mandate guardrails (dry-run gates, least-privilege IAM, human approval for destructive operations) as a standard before broader rollout.&lt;/li>
&lt;/ul></description></item></channel></rss>