<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oauth on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/oauth/</link><description>Recent content in Oauth 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/oauth/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></channel></rss>