<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/deployment/</link><description>Recent content in Deployment on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Jul 2026 12:23:02 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon ECS Action Logs adds deployment and daemon operation visibility</title><link>https://curadevops.metacog.co.kr/insights/2026-07-22-amazon-ecs-now-provides-action-logs-for-deployment-and-orche/</link><pubDate>Wed, 22 Jul 2026 12:23:02 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-22-amazon-ecs-now-provides-action-logs-for-deployment-and-orche/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This GA feature surfaces previously opaque ECS service-side deployment events — state transitions, circuit-breaker rollbacks, Managed Daemon updates — directly into CloudWatch, S3, or Firehose. Platform teams running ECS should evaluate opting in at the cluster level to reduce MTTR on deployment incidents without waiting on AWS Support.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> ECS Action Logs expose service-side operations that can help diagnose failures in pipeline-triggered deployments, but no pipeline changes are required — this is an opt-in ECS console/CloudWatch feature, not a build or artifact system change.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>