<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Gateway on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/api-gateway/</link><description>Recent content in Api-Gateway on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 25 Sep 2026 15:41:44 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/api-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>Apigee hybrid v1.15.8: multiple security fixes patched</title><link>https://curadevops.metacog.co.kr/insights/2026-09-25-september-24-2026/</link><pubDate>Fri, 25 Sep 2026 15:41:44 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-25-september-24-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running Apigee hybrid on Kubernetes should schedule an upgrade to v1.15.8, which patches several security issues: JWT refresh token revocation, HTTP 103 Early Hints response desynchronization, JavaCallout policy, and SSRF in AI protection policies. No KEV listing or active exploitation reported, so no immediate emergency, but the Helm chart upgrade path is straightforward.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>GCP: Slurm security patches in Cluster Toolkit; API Gateway MCP preview</title><link>https://curadevops.metacog.co.kr/insights/2026-09-12-september-11-2026/</link><pubDate>Sat, 12 Sep 2026 13:49:10 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-12-september-11-2026/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you run Google Cluster Toolkit for HPC workloads, review the linked security bulletin and apply Slurm patches; no KEV or active exploitation signal, but a vulnerable job scheduler carries real risk. All other items (AlloyDB audit monitoring, MCP) are minor or pre-GA.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The Public Preview of MCP support in API Gateway is an early signal for orgs evaluating AI-agent integration patterns — it shows GCP moving to expose REST APIs as agent tools without backend changes, worth tracking as the feature matures toward GA.&lt;/li>
&lt;/ul></description></item><item><title>Amazon API Gateway adds 1 MB execution logs with multi-destination routing</title><link>https://curadevops.metacog.co.kr/insights/2026-09-11-amazon-api-gateway-now-supports-1-mb-execution-logs-with-con/</link><pubDate>Fri, 11 Sep 2026 14:43:59 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-11-amazon-api-gateway-now-supports-1-mb-execution-logs-with-con/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This GA feature meaningfully improves API Gateway observability: 1 KB log truncation was a real debugging blind spot, and the new ability to route up to 1 MB events to S3 (Parquet/Athena), CloudWatch, or Firehose simultaneously is worth adding to the observability platform this quarter. Plan to reconfigure API Gateway REST API logging destinations and validate cost impact under vended logs pricing.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The shift to vended logs pricing and multi-destination routing is relevant for observability cost architecture — routing long-term logs to S3/Athena instead of CloudWatch can reduce ingestion costs — but no strategic decision or vendor risk is triggered here.&lt;/li>
&lt;/ul></description></item><item><title>Amazon API Gateway adds mTLS support for backend integrations</title><link>https://curadevops.metacog.co.kr/insights/2026-09-09-amazon-api-gateway-now-supports-mutual-tls-for-backend-integ/</link><pubDate>Wed, 09 Sep 2026 14:56:08 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-09-amazon-api-gateway-now-supports-mutual-tls-for-backend-integ/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> GA feature enabling ACM-backed mTLS from API Gateway to backend services — worth adopting for any zero-trust or regulated workload this quarter; audit existing REST API integrations and plan certificate provisioning via ACM or AWS Private CA.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Closes a common compliance gap in regulated industries (finance, healthcare) by extending mTLS to the API-to-backend path; relevant context if the org is pursuing zero-trust architecture or FedRAMP/HIPAA posture.&lt;/li>
&lt;/ul></description></item></channel></rss>