<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elastic-Beanstalk on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/elastic-beanstalk/</link><description>Recent content in Elastic-Beanstalk on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Sep 2026 14:42:50 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/elastic-beanstalk/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Elastic Beanstalk adds Cluster Mode: multi-app shared EKS infrastructure</title><link>https://curadevops.metacog.co.kr/insights/2026-09-18-aws-elastic-beanstalk-introduces-cluster-mode-to-run-multipl/</link><pubDate>Fri, 18 Sep 2026 14:42:50 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-18-aws-elastic-beanstalk-introduces-cluster-mode-to-run-multipl/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Beanstalk Cluster Mode is EKS under the hood with AWS managing the control plane — worth understanding as an abstraction layer above raw EKS, but platform engineers already running EKS have no action to take and no deadline.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> A new official Beanstalk GitHub Action ships alongside this feature, relevant only to teams already in the Beanstalk ecosystem; no deprecation or deadline pressure makes this worth monitoring rather than scheduling.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Cluster Mode&amp;rsquo;s shared-infrastructure model could reduce per-app compute cost for orgs with many small services on Beanstalk, but there is no pricing change or strategic forcing function to act on — file for the next platform golden-path review.&lt;/li>
&lt;/ul></description></item></channel></rss>