<?xml version="1.0" encoding="UTF-8" standalone="no"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" version="2.0">

<channel>
	<title>AWS Compute Blog</title>
	<atom:link href="https://aws.amazon.com/blogs/compute/feed/" rel="self" type="application/rss+xml"/>
	<link>https://aws.amazon.com/blogs/compute/</link>
	<description/>
	<lastBuildDate>Thu, 19 Nov 2026 21:20:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Handling large volume of transactions with AWS Lambda Managed Instances</title>
		<link>https://aws.amazon.com/blogs/compute/handling-large-volume-of-transactions-with-aws-lambda-managed-instances/</link>
		
		<dc:creator><![CDATA[Mythili Annamalai Sekar]]></dc:creator>
		<pubDate>Thu, 19 Nov 2026 21:20:28 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">7f1d2cdf5645ba0be07912dd5d51a797f826b751</guid>

					<description>AWS Lambda Managed Instances keeps compute capacity warm before a predictable traffic burst and scales it back down afterward. This post walks through a concert-ticketing reference implementation that sustains 40,000 transactions per second for 120 seconds, with a deployable sample you can run, test, and clean up.</description>
										<content:encoded>&lt;p&gt;Pre-scheduled events like concert ticket on-sales and product launches can drive a load spike 100 times higher than the baseline. The spike persists for a few hours while the inventory clears, then traffic returns to normal. If you miss the first minute of the on-sales, customers experience errors while competitors keep selling, and the event’s reputation takes a hit. Over-provision for the burst, and you pay for peak capacity 24 hours a day, 365 days a year. The actual peak lasts 10 minutes and happens 10 times a year.&lt;/p&gt; 
&lt;p&gt;In this post, you will see how &lt;a href="https://aws.amazon.com/lambda/lambda-managed-instances/" target="_blank" rel="noopener"&gt;AWS Lambda Managed Instances&lt;/a&gt;, a capability of &lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener"&gt;AWS Lambda&lt;/a&gt;, handles predictable traffic bursts. It keeps compute capacity warm before the on-sales event opens and scales it back down afterward. You will see a reference ticketing implementation that sustains &lt;strong&gt;40,000 transactions per second (TPS) for 120 seconds&lt;/strong&gt;.&lt;/p&gt; 
&lt;h2 id="understanding-lambda-managed-instances"&gt;Understanding Lambda Managed Instances&lt;/h2&gt; 
&lt;p&gt;Lambda Managed Instances runs your Lambda functions on &lt;a href="https://aws.amazon.com/pm/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (EC2)&lt;/a&gt; instances in your account, including Graviton4 and memory-optimized instance types. AWS handles the underlying infrastructure lifecycle (provisioning, scaling, patching, and routing), while you benefit from EC2 pricing including Compute Savings Plans and Reserved Instances.&lt;/p&gt; 
&lt;p&gt;Lambda Managed Instances provides several benefits. With pre-provisioned execution environments (EE), capacity is already warm before traffic arrives, so there are no cold starts when a burst hits. Scaling bounds are configurable with &lt;code&gt;MinExecutionEnvironments&lt;/code&gt; and &lt;code&gt;MaxExecutionEnvironments&lt;/code&gt; for each function, and each new EE comes online in 1–2 seconds. With multi-concurrent invocations, one EE handles multiple requests at once, which improves utilization for I/O-heavy handlers. You also get EC2 pricing, so Compute Savings Plans and Reserved Instances apply instead of per-request Lambda pricing.&lt;/p&gt; 
&lt;p&gt;Lambda Managed Instances is well suited for predictable, spike-shaped workloads that need sustained compute capacity during the peak and can scale back down when traffic returns to the baseline.&lt;/p&gt; 
&lt;h2 id="predictable-burst-workloads-work-best-with-lambda-managed-instances"&gt;Predictable burst workloads work best with Lambda Managed Instances&lt;/h2&gt; 
&lt;p&gt;This post focuses on one of the key capabilities of Lambda Managed Instances: absorbing scheduled traffic bursts without provisioning for peak year-round. Some of the use cases where Lambda Managed Instances helps are ticket and event on-sales (concerts, sports, festivals), live streaming and voting events, and scheduled batch and report generation nightly or hourly jobs that consume steady compute during a defined window.&lt;/p&gt; 
&lt;h2 id="use-case-high-throughput-ticket-booking-with-lambda-managed-instances"&gt;Use case: High-throughput ticket booking with Lambda Managed Instances&lt;/h2&gt; 
&lt;p&gt;To demonstrate Lambda Managed Instances handling predictable traffic bursts, we built a &lt;strong&gt;concert ticketing backend&lt;/strong&gt;. The solution implements the industry-standard queue-plus-hold-and-confirm booking flow, a pattern that ticketing platforms, airlines, and hotels use to prevent overselling during large traffic spikes. It separates user traffic management from the critical database transactions required to lock inventory.&lt;/p&gt; 
&lt;p&gt;The following diagram presents the detailed architecture of the solution we built.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2784-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2784-1.png" alt="Architecture of the ticketing solution: API Gateway routes to three Lambda Managed Instances handlers backed by ElastiCache and DynamoDB" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Architecture of the concert ticketing solution across two AWS CloudFormation stacks&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;The solution deploys two &lt;a href="https://aws.amazon.com/cloudformation/" target="_blank" rel="noopener"&gt;AWS CloudFormation&lt;/a&gt; stacks in a single AWS Region. In the first stack, &lt;a href="https://aws.amazon.com/api-gateway/" target="_blank" rel="noopener"&gt;Amazon API Gateway&lt;/a&gt; routes public HTTPS traffic through three ticketing handlers hosted in Lambda Managed Instances on a shared capacity provider. &lt;a href="https://aws.amazon.com/elasticache/" target="_blank" rel="noopener"&gt;Amazon ElastiCache Serverless for Valkey&lt;/a&gt; holds the atomic queue counter. &lt;a href="https://aws.amazon.com/dynamodb/" target="_blank" rel="noopener"&gt;Amazon DynamoDB&lt;/a&gt; holds durable per-seat state across a write-sharded inventory table (500 shards) and a bookings table. &lt;code&gt;WarmThroughput&lt;/code&gt; is pre-provisioned to absorb the burst without waiting for adaptive capacity. A separate simulation stack drives synthetic load through a three-tier Lambda fan-out, reproducing the on-sales burst shape at any target TPS.&lt;/p&gt; 
&lt;p&gt;Public traffic and load-generation traffic take completely separate code paths, so the load generator’s own scaling behavior does not affect measurements on the ticketing stack. Each successful booking traverses three Lambda handlers. Handler &lt;code&gt;queue-position&lt;/code&gt; assigns an atomic virtual queue number using an &lt;code&gt;INCR&lt;/code&gt; on a single ElastiCache key. Handler &lt;code&gt;inventory-lock&lt;/code&gt; places a time-bounded hold on a specific seat through a DynamoDB conditional &lt;code&gt;UpdateItem&lt;/code&gt;, moving it from &lt;code&gt;AVAILABLE&lt;/code&gt; to &lt;code&gt;HELD&lt;/code&gt; with a time to live (TTL) of 180 seconds. Handler &lt;code&gt;booking-confirm&lt;/code&gt; executes a single &lt;code&gt;TransactWriteItems&lt;/code&gt; call that atomically transitions the seat from &lt;code&gt;HELD&lt;/code&gt; to &lt;code&gt;CONFIRMED&lt;/code&gt; and writes a durable booking record. Either both writes succeed or neither does.&lt;/p&gt; 
&lt;p&gt;All three handlers are stateless, because each request they receive is treated as an independent, standalone transaction. The mutable state lives in ElastiCache and DynamoDB, stored with safety features like conditional writes and atomic operations to avoid collisions, race conditions, and overwrites. This is why the multi-concurrent EE model of Lambda Managed Instances can serve thousands of simultaneous invocations per instance safely.&lt;/p&gt; 
&lt;h2 id="what-makes-this-solution-better-with-lambda-managed-instances"&gt;What makes this solution better with Lambda Managed Instances&lt;/h2&gt; 
&lt;p&gt;With Lambda Managed Instances, you keep the same Lambda programming model, one function per handler, and the same deployment story, while Lambda Managed Instances handles the fleet. Raise &lt;code&gt;MinExecutionEnvironments&lt;/code&gt; a few minutes before an on-sales opens, let it burst inside the &lt;code&gt;Min&lt;/code&gt; to &lt;code&gt;Max&lt;/code&gt; range while traffic is live, and scale back down when the window closes.&lt;/p&gt; 
&lt;h2 id="deploy-the-application"&gt;Deploy the application&lt;/h2&gt; 
&lt;p&gt;For the full deployment instructions, refer to the README file in the &lt;a href="https://github.com/aws-samples/sample-aws-lambda-managed-instances-large-transactions-volume" target="_blank" rel="noopener"&gt;GitHub repository&lt;/a&gt; after you have cloned it.&lt;/p&gt; 
&lt;h3 id="prerequisites"&gt;Prerequisites&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface (CLI)&lt;/a&gt; version 2 configured with credentials.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/serverless/sam/" target="_blank" rel="noopener"&gt;AWS Serverless Application Model (SAM)&lt;/a&gt; CLI installed.&lt;/li&gt; 
 &lt;li&gt;Python 3.13+ with &lt;code&gt;boto3&lt;/code&gt; installed.&lt;/li&gt; 
 &lt;li&gt;An existing &lt;a href="https://aws.amazon.com/vpc/" target="_blank" rel="noopener"&gt;Amazon Virtual Private Cloud (VPC)&lt;/a&gt; with at least two subnets in different Availability Zones, plus either a NAT Gateway or VPC endpoints for DynamoDB and &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; Logs.&lt;/li&gt; 
 &lt;li&gt;AWS Service Quotas – the initial deployment works with an AWS account’s default service quota. Peak-load testing requires EC2 vCPU and API Gateway throttle quotas increase.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="run-the-application"&gt;Run the application&lt;/h2&gt; 
&lt;p&gt;Once deployed, all test traffic goes through the simulation API. The sample includes an optional single-page web user interface (UI) (see the &lt;code&gt;demo-ui/&lt;/code&gt; folder in the repository) that wraps the same endpoints and renders the per-burst results interactively.&lt;/p&gt; 
&lt;p&gt;Read the “Cost considerations” section before running a simulation to understand the cost you will incur in the process.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;1. Smoke test –&lt;/strong&gt; low TPS to verify the pipeline end-to-end:&lt;/p&gt; 
&lt;p&gt;By default, &lt;code&gt;deploy.sh&lt;/code&gt; provisions a cost-safe baseline of three warm EEs (&lt;code&gt;Min=1&lt;/code&gt;, &lt;code&gt;Max=3&lt;/code&gt; per handler). The following smoke test works on this baseline.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;curl -X POST https://&amp;lt;sim-api&amp;gt;/v1/simulation/start \
-H 'Content-Type: application/json' \
-d '{"run_id": "smoke-1", "target_tps": 50, "ramp_duration_seconds": 10, "sustain_duration_seconds": 60}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;2. Peak-load test&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;To reproduce the headline result, scale the Lambda handlers to the per-handler &lt;code&gt;Min&lt;/code&gt; and &lt;code&gt;Max&lt;/code&gt; values before firing the peak-load test. Refer to the Peak-load testing section of the &lt;a href="https://github.com/aws-samples/sample-aws-lambda-managed-instances-large-transactions-volume.git" target="_blank" rel="noopener"&gt;GitHub repository&lt;/a&gt; before firing the burst. This also requires an EC2 vCPU and an API Gateway account-throttle quotas increase above the default.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;3. View results&lt;/strong&gt;&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;curl “https://&amp;lt;sim-api&amp;gt;/v1/dashboard?run_id=onsale-1”&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The response includes total requests, total bookings written to DynamoDB, delivered peak TPS, and end-to-end latency percentiles.&lt;/p&gt; 
&lt;h2 id="interactive-demo-ui"&gt;Interactive demo UI&lt;/h2&gt; 
&lt;p&gt;The sample repository ships an optional single-page web UI (in the &lt;code&gt;demo-ui/&lt;/code&gt; folder) that wraps the same simulation and dashboard endpoints as the preceding &lt;code&gt;curl&lt;/code&gt; examples. Point it at your simulation API endpoint, then fire bursts and view results interactively without leaving the browser.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Configure and start the UI:&lt;/strong&gt;&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# In demo-ui/config.js, set SIMULATION_API_URL to your simulation endpoint.
cd demo-ui &amp;amp;&amp;amp; python3 serve.py
# Serving on http://localhost:8000/&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Fire a burst.&lt;/strong&gt; Choose a target load (a preset button or a custom TPS value), set the sustain duration and ramp, then choose &lt;strong&gt;Start burst&lt;/strong&gt;. The UI sends a POST request to &lt;code&gt;/simulation/start&lt;/code&gt; and stores the returned &lt;code&gt;run_id&lt;/code&gt; and &lt;code&gt;event_id&lt;/code&gt;, so you can query DynamoDB directly if you want to drill deeper.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;View results.&lt;/strong&gt; After the burst completes, choose &lt;strong&gt;View results&lt;/strong&gt;. The UI queries API Gateway metrics, DynamoDB, CloudWatch Logs Insights, and CloudWatch Lambda metrics in parallel to reconstruct the run: total requests received, durable bookings written, and a per-handler table showing EEs used, Lambda throttles, and p95/p99 latency.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2784-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2784-2.png" alt="Demo UI results panel showing 4,804,200 API Gateway requests and 1,750,886 durable bookings with per-handler latency" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: Demo UI results panel from a 40,000 TPS, 120-second run&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;The panel shows 4,804,200 API Gateway requests and 1,750,886 durable bookings, plus a per-handler table with the baseline EE pool (50/100/150 for &lt;code&gt;queue-position&lt;/code&gt;, &lt;code&gt;inventory-lock&lt;/code&gt;, and &lt;code&gt;booking-confirm&lt;/code&gt;). During the burst, 36 additional EEs are pre-emptively warmed on &lt;code&gt;booking-confirm&lt;/code&gt;, with zero Lambda throttles and p99 latencies of 4.7, 15.8, and 39.8 ms.&lt;/p&gt; 
&lt;p&gt;The identifiers panel at the top exposes the burst’s &lt;code&gt;run_id&lt;/code&gt; (the partition key in the simulation metrics table) and &lt;code&gt;event_id&lt;/code&gt; (used in both the inventory and bookings tables), so you can locate them directly in DynamoDB or CloudWatch Logs Insights for the specific burst you ran.&lt;/p&gt; 
&lt;h2 id="what-we-measured"&gt;What we measured&lt;/h2&gt; 
&lt;p&gt;Across a load range from 5,000 to 40,000 requests per second, the pre-warmed EE pool served every burst without cold-start impact. Key results from the headline 40,000 TPS × 120-second burst:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Metric&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Value&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Delivered peak throughput&lt;/td&gt; 
   &lt;td&gt;40,035 req/sec&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Total HTTP requests&lt;/td&gt; 
   &lt;td&gt;4,804,200&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Durable bookings written to Amazon DynamoDB&lt;/td&gt; 
   &lt;td&gt;1,750,886&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;End-to-end p50 / p99 latency&lt;/td&gt; 
   &lt;td&gt;44 ms / 121 ms&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;AWS Lambda errors&lt;/td&gt; 
   &lt;td&gt;0&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;AWS Lambda concurrency throttles&lt;/td&gt; 
   &lt;td&gt;0&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon DynamoDB write throttles&lt;/td&gt; 
   &lt;td&gt;0&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;The tested range spanned 5,000 to 40,000 requests per second, an 8× spread in delivered load. Across it, p99 latency stayed within a 3 ms band. Doubling sustained throughput from 20,000 to 40,000 requests per second held at exactly 121 ms, which confirms that the pre-warmed pool had substantial headroom throughout the tested range.&lt;/p&gt; 
&lt;h2 id="observability"&gt;Observability&lt;/h2&gt; 
&lt;p&gt;Lambda Managed Instances automatically publishes metrics to CloudWatch and structured logs to CloudWatch Logs, giving you visibility into function performance and capacity utilization without additional code. During a burst, the metrics that matter most are:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Duration percentiles&lt;/strong&gt; per handler to confirm p99 latency stays flat as load rises.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;ConcurrencyThrottles&lt;/strong&gt; to detect if any handler hits its &lt;code&gt;MaxExecutionEnvironments&lt;/code&gt; ceiling.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Errors&lt;/strong&gt; for handler-side failures.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;EE count&lt;/strong&gt; (log-derived) to observe how quickly Lambda Managed Instances adds warm capacity above &lt;code&gt;Min&lt;/code&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;The sample repository includes a demo dashboard endpoint that queries CloudWatch metrics, CloudWatch Logs Insights, and DynamoDB in parallel to reconstruct a per-burst report, API Gateway request count, durable bookings landed, distinct EEs used, and per-handler latency percentiles. Reconciling the simulation-side counts against the AWS ground truth catches load-generator artifacts and confirms the system-under-test numbers.&lt;/p&gt; 
&lt;h2 id="cost-considerations"&gt;Cost considerations&lt;/h2&gt; 
&lt;p&gt;Lambda Managed Instances uses EC2 instance pricing plus a 15% management fee. Compute Savings Plans and Reserved Instances apply to the underlying instance cost.&lt;/p&gt; 
&lt;p&gt;The Lambda Managed Instances configuration runs a small always-on baseline and uses a scaling script to pre-warm to 50/100/150 EEs in the minutes leading up to each event, then scales back down to baseline afterward.&lt;/p&gt; 
&lt;p&gt;To simulate a peak load under controlled conditions, the fleet is pre-warmed for a 7-minute window (5-minute ramp and 2-minute burst) then scaled back down. The cost breakdown can be as follows.&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Component&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Volume&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Rate&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Cost&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;API Gateway requests&lt;/td&gt; 
   &lt;td&gt;4.8 M&lt;/td&gt; 
   &lt;td&gt;$3.50 per 1 M&lt;/td&gt; 
   &lt;td&gt;$16.80&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;DynamoDB writes&lt;/td&gt; 
   &lt;td&gt;8.8 M WCU&lt;/td&gt; 
   &lt;td&gt;$1.25 per 1 M&lt;/td&gt; 
   &lt;td&gt;$11.00&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Lambda Managed Instances compute (peak window)&lt;/td&gt; 
   &lt;td&gt;75 × c7i.4xlarge × 7 min&lt;/td&gt; 
   &lt;td&gt;$0.821 / instance-hr&lt;/td&gt; 
   &lt;td&gt;$7.18&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Lambda Managed Instances request charges&lt;/td&gt; 
   &lt;td&gt;4.8 M&lt;/td&gt; 
   &lt;td&gt;$0.20 per 1 M&lt;/td&gt; 
   &lt;td&gt;$0.96&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;CloudWatch Logs (~2 GB)&lt;/td&gt; 
   &lt;td&gt;ingestion&lt;/td&gt; 
   &lt;td&gt;$0.50 per GB&lt;/td&gt; 
   &lt;td&gt;$1.00&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon ElastiCache Serverless for Valkey&lt;/td&gt; 
   &lt;td&gt;4.8 M &lt;code&gt;INCR&lt;/code&gt; operations&lt;/td&gt; 
   &lt;td&gt;ECPU-based&lt;/td&gt; 
   &lt;td&gt;$0.30&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Total per burst&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;~$37.00&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;The estimated cost for simulating each burst is around $37.&lt;/p&gt; 
&lt;h2 id="best-practices"&gt;Best practices&lt;/h2&gt; 
&lt;p&gt;Based on experience building this solution, here are key recommendations:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Pre-warm before scheduled events.&lt;/strong&gt; Raise &lt;code&gt;MinExecutionEnvironments&lt;/code&gt; using an &lt;a href="https://aws.amazon.com/eventbridge/scheduler/" target="_blank" rel="noopener"&gt;Amazon EventBridge Scheduler&lt;/a&gt; rule or a manual scaling script when you expect major spikes, giving Lambda Managed Instances enough time to scale the underlying instances. Restore the low baseline after the event.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Set MaxExecutionEnvironments aggressively.&lt;/strong&gt; Lambda Managed Instances adds new EEs to your capacity provider. A high &lt;code&gt;MaxExecutionEnvironments&lt;/code&gt; value costs nothing while idle but absorbs unexpected demand during the burst.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Write-shard hot DynamoDB tables.&lt;/strong&gt; For workloads writing thousands of items per second to one logical entity (a single event, a single product SKU), spread writes across a synthetic sharded partition key. This sample uses 500 shards per event.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Use WarmThroughput on DynamoDB tables.&lt;/strong&gt; Pre-provision physical partitions before the burst rather than waiting for adaptive capacity to expand during the first minute of the on-sales.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Keep hot atomic counters out of DynamoDB.&lt;/strong&gt; Single-row atomic increments in DynamoDB cap at approximately 1,000 operations per second.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Make write endpoints idempotent.&lt;/strong&gt; The sample uses a caller-provided &lt;code&gt;booking_id&lt;/code&gt; on the confirmation endpoint so that retries produce the same booking record instead of duplicates.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="clean-up"&gt;Clean up&lt;/h2&gt; 
&lt;p&gt;When you are done exploring the solution, remove the provisioned resources to avoid ongoing charges. For the full cleanup commands and exact steps, refer to the &lt;a href="https://github.com/aws-samples/sample-aws-lambda-managed-instances-large-transactions-volume" target="_blank" rel="noopener"&gt;GitHub repository&lt;/a&gt; README file.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;Lambda Managed Instances brings the same Lambda programming model to workloads that need sustained, pre-provisioned compute during predictable bursts: ticket on-sales, product launches, registration windows, and other scheduled surge patterns. The concert ticketing example shows how a queue-plus-hold-and-confirm pattern built on Lambda Managed Instances can sustain 40,000 requests per second while costing less than an always-on EC2 fleet sized for the same peak.&lt;/p&gt; 
&lt;p&gt;Explore the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances.html" target="_blank" rel="noopener"&gt;Lambda Managed Instances documentation&lt;/a&gt; and try building your own predictable-burst serverless application. You can find the complete code for this example in the &lt;a href="https://github.com/aws-samples/sample-aws-lambda-managed-instances-large-transactions-volume" target="_blank" rel="noopener"&gt;GitHub repository&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2784-3.jpg" alt="Mythili Annamalai Sekar" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Mythili Annamalai Sekar&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Mythili Sekar is a Solutions Architect at Amazon Web Services (AWS) working with Independent Software Vendors (ISVs), where she guides customers in designing secure, enterprise-scale architectures built on AWS best practices. Her work centers on serverless and generative AI, helping software companies turn new cloud capabilities into real, production-ready outcomes for their businesses.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2784-4.jpg" alt="Guy Haddad" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Guy Haddad&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Guy is a Senior Technical Account Manager at AWS where he assists customers with leveraging their AWS entitlements and adhering to architectural and operational best practices. He specializes in AI/ML and serverless technologies and has a deep background in software development, telecommunications and complex program deliveries.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Announcing 30-minute timeout for on-demand AWS Lambda Event Functions</title>
		<link>https://aws.amazon.com/blogs/compute/announcing-30-minute-timeout-for-on-demand-aws-lambda-event-functions/</link>
		
		<dc:creator><![CDATA[Tarun Rai Madan]]></dc:creator>
		<pubDate>Thu, 19 Nov 2026 19:28:52 +0000</pubDate>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<guid isPermaLink="false">f5b95467ff9ae3b413bb5bbe04fadd5b126ca0b7</guid>

					<description>AWS Lambda now supports a 30-minute function timeout for on-demand Event Functions and for synchronous invocations on Lambda Managed Instances, doubling the previous 15-minute limit. You can run AI inference, media transcoding, and other long-running jobs without re-architecting your applications.</description>
										<content:encoded>&lt;p&gt;AWS Lambda now supports a 30-minute function timeout for &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-functions-chapter.html" target="_blank" rel="noopener"&gt;Event Functions&lt;/a&gt; that run on demand, doubling the previous 15-minute limit for synchronous, asynchronous, and event source mapping (ESM) invocations. On &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances.html" target="_blank" rel="noopener"&gt;Lambda Managed Instances&lt;/a&gt;, synchronous invocations also support up to 30 minutes, while asynchronous and ESM invocations keep the &lt;a href="https://aws.amazon.com/blogs/compute/announcing-90-minute-function-timeout-on-aws-lambda-managed-instances/" target="_blank" rel="noopener"&gt;90-minute timeout&lt;/a&gt; we announced in September 2026. You can now run AI inference, media transcoding, and financial calculations on Lambda for spiky or steady-state traffic without re-architecting your applications. The new timeout also applies when you use &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-functions.html" target="_blank" rel="noopener"&gt;Lambda durable functions&lt;/a&gt; or invoke your functions from &lt;a href="https://docs.aws.amazon.com/step-functions/latest/dg/choosing-workflow-type.html" target="_blank" rel="noopener"&gt;AWS Step Functions Standard workflows&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="evolution-of-function-timeout-on-lambda"&gt;Evolution of function timeout on Lambda&lt;/h2&gt; 
&lt;p&gt;Lambda launched in 2014 with a 60-second function timeout, which we extended to 5 minutes in 2015 and to 15 minutes in 2018.&lt;/p&gt; 
&lt;p&gt;Lambda now offers three form factors: Event Functions, &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/web-functions.html" target="_blank" rel="noopener"&gt;Web Functions&lt;/a&gt;, and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html" target="_blank" rel="noopener"&gt;MicroVMs&lt;/a&gt;. Event Functions process events from more than 200 AWS event sources through synchronous, asynchronous, and ESM invocations. With Web Functions, you can run HTTP servers on Lambda with an HTTP-native, multi-concurrent programming model and opt-in multi-Region endpoints. MicroVMs give each user or session an isolated environment for running user-generated or AI-generated code.&lt;/p&gt; 
&lt;p&gt;By default, all three form factors run on demand, with Lambda provisioning compute as requests arrive. For steady-state traffic, Event Functions can also run on the Lambda Managed Instances capacity provider. With Lambda Managed Instances, you can process multiple concurrent requests per instance and choose specialized compute configurations, without managing infrastructure. You can also use EC2 pricing options such as AWS Savings Plans and Reserved Instances. Figure 1 shows the form factors.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-1.png" alt="The three Lambda form factors: Event Functions, Web Functions, and MicroVMs" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Lambda form factors&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Each form factor has its own duration limit (Table 1). Until today, Event Functions had a 15-minute timeout, except for asynchronous and ESM invocations on Lambda Managed Instances, which we extended to 90 minutes in September 2026.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-functions.html" target="_blank" rel="noopener"&gt;Lambda durable functions&lt;/a&gt; run on demand and on Lambda Managed Instances, and provide application-level checkpointing and workflow-as-code. Your code saves execution state with &lt;code&gt;step()&lt;/code&gt; and &lt;code&gt;wait()&lt;/code&gt; operations and resumes from the last checkpoint after a failure. A durable execution (the complete lifecycle of a durable function) can run for up to 1 year, but each invocation within it is bound by the function timeout.&lt;/p&gt; 
&lt;p&gt;Customers told us that 15 minutes was still too short for many Event Functions workloads that run on demand, and for synchronous invocations on Lambda Managed Instances. Agentic AI requests that chain model calls and tool invocations can take longer than 15 minutes to return a result. Media transcoding and file conversion jobs often run past 15 minutes when input files are large. Financial calculations such as Monte Carlo simulations, bond pricing, and portfolio risk analysis are memory-intensive and need more continuous execution time. Report generation across multiple data sources can also exceed 15 minutes during peak volumes. ETL steps triggered by Amazon Simple Queue Service (Amazon SQS) or Amazon Simple Storage Service (Amazon S3) events can run just as long. Many of these workloads have spiky traffic that doesn’t justify steady-state capacity on Lambda Managed Instances.&lt;/p&gt; 
&lt;p&gt;With today’s launch, Event Functions support up to 30 minutes for synchronous, asynchronous, and ESM invocations, and up to 90 minutes for asynchronous and ESM invocations on Lambda Managed Instances. Table 1 shows the maximum durations across Lambda form factors.&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Duration&lt;/strong&gt;&lt;/td&gt; 
   &lt;td colspan="2"&gt;&lt;strong&gt;Event Functions&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Web Functions&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;MicroVMs&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;On demand (default)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Lambda Managed Instances&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Without durable execution&lt;/td&gt; 
   &lt;td&gt; &lt;p&gt;Synchronous: 30 minutes&lt;/p&gt; &lt;p&gt;Asynchronous: 30 minutes&lt;/p&gt; &lt;p&gt;ESM: 30 minutes&lt;/p&gt;&lt;/td&gt; 
   &lt;td&gt; &lt;p&gt;Synchronous: 30 minutes&lt;/p&gt; &lt;p&gt;Asynchronous: 90 minutes&lt;/p&gt; &lt;p&gt;ESM: 90 minutes&lt;/p&gt;&lt;/td&gt; 
   &lt;td&gt;15 minutes&lt;/td&gt; 
   &lt;td&gt;8 hours (running and suspended)&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;With durable execution&lt;/td&gt; 
   &lt;td&gt; &lt;p&gt;Synchronous: 30 minutes&lt;/p&gt; &lt;p&gt;Asynchronous: 1 year&lt;/p&gt; &lt;p&gt;ESM: 30 minutes&lt;/p&gt;&lt;/td&gt; 
   &lt;td&gt; &lt;p&gt;Synchronous: 30 minutes&lt;/p&gt; &lt;p&gt;Asynchronous: 1 year&lt;/p&gt; &lt;p&gt;ESM: 90 minutes&lt;/p&gt;&lt;/td&gt; 
   &lt;td&gt;–&lt;/td&gt; 
   &lt;td&gt;–&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;strong&gt;Table 1: Supported durations on Lambda form factors&lt;/strong&gt;&lt;/p&gt; 
&lt;h2 id="configuring-the-30-minute-function-timeout"&gt;Configuring the 30-minute function timeout&lt;/h2&gt; 
&lt;p&gt;You can configure any Event Function with a timeout of up to 30 minutes (1,800 seconds). For asynchronous and ESM invocations on Lambda Managed Instances, you can configure up to 90 minutes (5,400 seconds). Lambda rejects higher values with a validation error. Your function runs exactly as before, with the same runtime, handler, IAM execution role, and virtual private cloud (VPC) configuration. The &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtime-environment.html" target="_blank" rel="noopener"&gt;Init phase&lt;/a&gt; keeps its existing limits of 10 seconds for functions that run on demand and 15 minutes on Lambda Managed Instances. &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/provisioned-concurrency.html" target="_blank" rel="noopener"&gt;Provisioned concurrency&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html" target="_blank" rel="noopener"&gt;Lambda SnapStart&lt;/a&gt;, which aren’t available on Lambda Managed Instances, keep their 15-minute initialization limit.&lt;/p&gt; 
&lt;p&gt;To set the timeout, update your function configuration using the AWS Command Line Interface (AWS CLI):&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda update-function-configuration \
--function-name my-demo-function \
--timeout 1800 \
--region us-east-1&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;To set the timeout in an AWS Serverless Application Model (AWS SAM) template, use the Timeout property:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;MyFunction:
  Type: AWS::Serverless::Function
  Properties:
    FunctionName: my-demo-function
    Runtime: python3.14
    Handler: app.handler
    Timeout: 1800
    MemorySize: 2048&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You can also update the timeout in the Lambda console under Configuration &amp;gt; General configuration (Figure 2), where synchronous test invocations now run for up to 30 minutes. If you use an AI coding assistant such as Kiro, Claude Code, or Codex, you can install the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/agent-setup-guide.html" target="_blank" rel="noopener"&gt;Agent Toolkit for AWS&lt;/a&gt; and configure the timeout with natural language prompts.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-2.png" alt="Lambda console General configuration page with the function timeout set to 30 minutes" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: Configuring Lambda function timeout&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;The new timeout applies to invocations that start after you update the function. For event source mappings, allow a few minutes for the change to propagate. Amazon CloudWatch metrics, AWS CloudTrail, and AWS X-Ray continue to capture the full invocation lifecycle. For details, see &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-monitoring.html" target="_blank" rel="noopener"&gt;monitoring Lambda functions&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-monitoring.html" target="_blank" rel="noopener"&gt;monitoring durable functions&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For Event Functions that run on demand, the 30-minute timeout is available in all commercial &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/" target="_blank" rel="noopener"&gt;AWS Regions&lt;/a&gt;. For synchronous invocations on Lambda Managed Instances, it is available in all AWS Regions where Lambda Managed Instances is available. Standard &lt;a href="https://aws.amazon.com/lambda/pricing/" target="_blank" rel="noopener"&gt;AWS Lambda pricing&lt;/a&gt; applies.&lt;/p&gt; 
&lt;h2 id="minute-timeout-and-durable-functions"&gt;30-minute timeout and durable functions&lt;/h2&gt; 
&lt;p&gt;The 30-minute function timeout and durable functions are complementary. The &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/configuration-timeout.html" target="_blank" rel="noopener"&gt;function timeout&lt;/a&gt; (&lt;code&gt;--timeout&lt;/code&gt;) controls how long each individual invocation can run, whereas the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-configuration.html" target="_blank" rel="noopener"&gt;durable execution timeout&lt;/a&gt; (&lt;code&gt;ExecutionTimeout&lt;/code&gt; in &lt;code&gt;--durable-config&lt;/code&gt;) controls the total elapsed time from execution start to completion. On replay after a failure, the function re-executes from the beginning and skips completed steps.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Functions that run on demand:&lt;/strong&gt; Each durable function invocation can run for up to 30 minutes, whether you invoke it synchronously, asynchronously, or through an event source mapping. When you invoke the function asynchronously, the durable execution can run for up to 1 year. When you invoke it synchronously through the Invoke API or a function URL, the durable execution is limited to 30 minutes, and Lambda rejects higher values. ESM invocations have the same 30-minute limit.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Lambda Managed Instances:&lt;/strong&gt; Synchronous invocations can run for up to 30 minutes, and asynchronous and ESM invocations can run for up to 90 minutes. When you invoke the function asynchronously, the durable execution can run for up to 1 year. The durable execution is limited to 30 minutes for synchronous invocations and 90 minutes for ESM invocations.&lt;/p&gt; 
&lt;p&gt;For idempotent jobs, such as an ETL step triggered by Amazon SQS, the extended timeout alone might be enough. A failed invocation returns the message to the queue for a fresh attempt. For jobs where re-execution is expensive, combine the extended timeout with durable functions. A 25-minute inference run that fails at minute 22 restarts from zero without checkpoints, but resumes from its last checkpoint with durable functions.&lt;/p&gt; 
&lt;h2 id="invocation-behavior-synchronous-asynchronous-and-event-source-mappings"&gt;Invocation behavior: Synchronous, asynchronous, and event source mappings&lt;/h2&gt; 
&lt;p&gt;&lt;strong&gt;Synchronous invocations (up to 30 minutes):&lt;/strong&gt; Synchronous invocations now support up to 30 minutes, whether the function runs on demand or on Lambda Managed Instances. If another AWS service invokes your function synchronously, that service applies its own timeout, so verify that it supports the longer duration before you raise the function timeout. Set your client’s read and socket timeouts longer than the function timeout. For example, increase the read timeout of your AWS SDK client when you call the Invoke API. On Lambda Managed Instances, Lambda applies the 30-minute limit to synchronous invocations even if the function timeout is higher, and the &lt;a href="https://docs.aws.amazon.com/cli/latest/reference/lambda/get-function-configuration.html" target="_blank" rel="noopener"&gt;GetFunctionConfiguration API&lt;/a&gt; reports the configured value.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Asynchronous invocations (up to 30 minutes, or up to 90 minutes on Lambda Managed Instances):&lt;/strong&gt; If the function fails or times out, Lambda applies your configured retry policy (up to two retries by default). It then routes failed events to your dead-letter queue or on-failure destination.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Event source mappings (up to 30 minutes, or up to 90 minutes on Lambda Managed Instances):&lt;/strong&gt; For SQS, set the queue’s visibility timeout to &lt;a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-lambda-function-trigger.html" target="_blank" rel="noopener"&gt;at least six times&lt;/a&gt; the function timeout, so at least 3 hours for a 30-minute function. This gives Lambda enough time to retry if a function is throttled while it processes a previous batch. Lambda validates this when you create the event source mapping, but it doesn’t prevent later changes to queue or function settings that create a mismatch.&lt;/p&gt; 
&lt;p&gt;For &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html" target="_blank" rel="noopener"&gt;Amazon Kinesis Data Streams&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-ddb.html" target="_blank" rel="noopener"&gt;Amazon DynamoDB Streams&lt;/a&gt;, Lambda processes one batch per shard at a time by default, so longer invocations slow how quickly each shard is read. Monitor the &lt;code&gt;IteratorAge&lt;/code&gt; metric and increase the parallelization factor if records start to back up. Longer invocations also mean that a failure late in a batch wastes more work. Enable partial batch failure reporting so that Lambda retries only the failed records. You can use it with SQS, Amazon Kinesis, DynamoDB Streams, Amazon Managed Streaming for Apache Kafka (Amazon MSK), and self-managed Apache Kafka event source mappings.&lt;/p&gt; 
&lt;p&gt;Invocations from &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-mq.html" target="_blank" rel="noopener"&gt;Amazon MQ&lt;/a&gt; (ActiveMQ and RabbitMQ) and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-documentdb.html" target="_blank" rel="noopener"&gt;Amazon DocumentDB&lt;/a&gt; (with MongoDB compatibility) event source mappings remain limited to 14 minutes. The same limit applies to Kafka event source mappings that were created before November 19, 2026, and don’t use provisioned mode. To use the 30-minute timeout with Kafka, create a new event source mapping or turn on provisioned mode for your existing one. For these mappings, keep the function timeout at 14 minutes (840 seconds) or less.&lt;/p&gt; 
&lt;h2 id="considerations-and-best-practices"&gt;Considerations and best practices&lt;/h2&gt; 
&lt;p&gt;Longer-running functions need extra care with concurrency and components that can expire mid-invocation, such as network connections and credentials.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Concurrency:&lt;/strong&gt; Concurrency equals requests per second multiplied by average duration in seconds. At the same request rate, a function that runs for 30 minutes instead of 15 needs twice the concurrency. For example, 1 request per second at 30 minutes each needs 1,800 concurrent executions. Check your account concurrency quota and reserved concurrency settings before you raise the timeout. On Lambda Managed Instances, check the maximum scaling limits of your capacity provider.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Networking:&lt;/strong&gt; Make sure idle connection timeouts on downstream services such as Amazon Relational Database Service (Amazon RDS), Amazon ElastiCache, and external APIs accommodate the full function duration. If your function routes traffic through a NAT gateway, which drops idle connections after 350 seconds, send keep-alive packets. For long synchronous invocations, also turn on TCP keep-alive on the calling client. DNS caching depends on your runtime and HTTP client. For example, the AWS SDK for Java relies on the JVM DNS cache, which on some configurations never refreshes. Set a short DNS TTL, such as 5 seconds for the JVM, and configure custom HTTP clients to re-resolve hostnames.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Credentials:&lt;/strong&gt; If your function acquires temporary credentials or tokens, verify they remain valid for the full execution duration or refresh them in the background.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Idempotency:&lt;/strong&gt; Lambda does not guarantee exactly-once processing, and longer-running functions widen the window for retries and duplicate deliveries. Use &lt;a href="https://docs.aws.amazon.com/powertools/python/latest/utilities/idempotency/" target="_blank" rel="noopener"&gt;Powertools for AWS Lambda&lt;/a&gt; to make operations such as payments or database writes idempotent. In durable functions, steps have at-least-once execution semantics by default. The SDK skips completed steps during replay, but steps that fail before checkpointing might re-execute. You can use &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-execution-idempotency.html" target="_blank" rel="noopener"&gt;execution names&lt;/a&gt; as idempotency keys for durable functions.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;The 30-minute function timeout brings longer continuous execution to Event Functions that run on demand and to synchronous invocations on Lambda Managed Instances. It complements the &lt;a href="https://aws.amazon.com/blogs/compute/announcing-90-minute-function-timeout-on-aws-lambda-managed-instances/" target="_blank" rel="noopener"&gt;90-minute timeout&lt;/a&gt; for asynchronous and ESM invocations on Lambda Managed Instances that we launched in September 2026. Workloads such as AI inference, media transcoding, and report generation that exceed 15 minutes can now run on Lambda without architectural workarounds, for spiky or steady-state traffic. If your workloads need a longer timeout, let us know on the &lt;a href="https://github.com/aws/aws-lambda-roadmap" target="_blank" rel="noopener"&gt;AWS Lambda Roadmap GitHub page&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To get started, update your function’s timeout configuration and deploy. For details, see &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/configuration-timeout.html" target="_blank" rel="noopener"&gt;Configure Lambda function timeout&lt;/a&gt; in the AWS Lambda Developer Guide. For sample code that shows long-running functions with durable checkpointing, see &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-examples.html" target="_blank" rel="noopener"&gt;durable functions examples&lt;/a&gt;. To learn more, visit the &lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener"&gt;AWS Lambda product page&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-3.jpg" alt="Tarun Rai Madan" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Tarun Rai Madan&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Tarun is a Principal Product Manager at Amazon Web Services (AWS), where he leads product areas across AWS Serverless Compute, including developer and agentic experiences, event-driven data ingestion, orchestration, and compute for data-intensive workloads. His work centers on removing infrastructure complexity so developers can concentrate on their differentiated business logic. Before joining AWS, he was an engineering leader in the semiconductor industry, where he developed high-performance processors for data center, wireless, and automotive applications.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-4.jpg" alt="Dan Slusariuc" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Dan Slusariuc&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Dan is a Software Development Manager at AWS, where he leads the Lambda Frontend team. His team builds the backend services that receive and route Lambda function invocations. He also leads compliance and availability for Lambda. In his prior role, Dan was a Software Development Engineer in Amazon Advertising, where he helped build the engine that generates banners for products listed on Amazon.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/19/ComputeBlog-2833-5.jpg" alt="Snehil Ameta" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Snehil Ameta&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Snehil is a Software Development Engineer at AWS, where he works on AWS Lambda. He focuses on Lambda scalability and availability, and leads capabilities such as Lambda response streaming and Lambda Managed Instances. In his prior role, Snehil worked in Amazon seller services, where he helped build its recommendation service.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>AWS Lambda Durable Functions observability with OpenTelemetry</title>
		<link>https://aws.amazon.com/blogs/compute/aws-lambda-durable-functions-observability-with-opentelemetry/</link>
		
		<dc:creator><![CDATA[Ricardo Marques]]></dc:creator>
		<pubDate>Thu, 19 Nov 2026 19:09:43 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Best Practices]]></category>
		<guid isPermaLink="false">f22d8e87cb305c81af1dda9b381ae2df11ef4742</guid>

					<description>A single AWS Lambda Durable Functions workflow can span many invocations, fragmenting its traces. This post shows how the OpenTelemetry plugin for the AWS Durable Execution SDK generates deterministic trace IDs that unify every invocation into one distributed trace, and how to set it up, read the traces, and apply best practices.</description>
										<content:encoded>&lt;p&gt;Gaining observability into &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/durable-functions.html" target="_blank" rel="noopener"&gt;AWS Lambda Durable Functions&lt;/a&gt;, a capability of AWS Lambda, can be challenging. A single workflow can span multiple invocations, queues, and downstream services, with no persistent host or centralized log file to inspect. With &lt;a href="https://opentelemetry.io/" target="_blank" rel="noopener"&gt;OpenTelemetry&lt;/a&gt;, you can close that gap by generating and correlating traces, metrics, and logs through an open specification. You can instrument once and export anywhere, which avoids vendor lock-in and establishes a baseline for operating serverless systems at scale.&lt;/p&gt; 
&lt;p&gt;With AWS Lambda Durable Functions, you can construct resilient workflows with multiple steps, which save their state and automatically recover from errors by replaying. A single durable execution can persist across several Lambda calls. It can continue after pauses, recover from errors, and restart from saved checkpoints. Although this model delivers fault tolerance, it introduces an observability challenge. Each invocation generates its own trace, fragmenting the end-to-end view of a single logical workflow.&lt;/p&gt; 
&lt;p&gt;This post introduces the &lt;a href="https://docs.aws.amazon.com/durable-execution/sdk-reference/observability/opentelemetry/" target="_blank" rel="noopener"&gt;OpenTelemetry plugin for the AWS Durable Execution SDK&lt;/a&gt; (&lt;code&gt;aws-durable-execution-sdk-python-otel&lt;/code&gt;). With this plugin, you can generate deterministic trace IDs that unify all invocations of a single durable execution into one coherent distributed trace. In this post, you learn how to set up the plugin, see the traces it produces for the happy-path workflow, and apply foundational best practices.&lt;/p&gt; 
&lt;p&gt;The complete application code is available in our &lt;a href="https://s12d.com/DurableFunctions-Otel" target="_blank" rel="noopener"&gt;GitHub repository&lt;/a&gt;, so this post uses code snippets to illustrate the examples.&lt;/p&gt; 
&lt;h2 id="the-problem-fragmented-traces-across-invocations"&gt;The problem: fragmented traces across invocations&lt;/h2&gt; 
&lt;p&gt;Consider a document review workflow with a human approval gate:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-python"&gt;import json

from aws_durable_execution_sdk_python import (
    DurableContext,
    durable_execution,
    durable_step,
)
from aws_durable_execution_sdk_python.types import WaitForCallbackContext


@durable_step
def extract_text(step_context, doc_id):
    step_context.logger.info(f"Extracting text from document: {doc_id}")
    return {"doc_id": doc_id, "text": "extracted content"}


@durable_step
def summarize(step_context, extracted):
    step_context.logger.info(f"Summarizing document: {extracted['doc_id']}")
    return {"summary": "Document summary here"}


@durable_step
def publish(step_context, summary, approval):
    step_context.logger.info(f"Publishing with approval from: {approval.get('reviewer')}")
    return {"status": "published"}


@durable_execution
def handler(event: dict, context: DurableContext) -&amp;gt; dict:
    extracted = context.step(extract_text(event["doc_id"]), name="extract-text")
    summary = context.step(summarize(extracted), name="summarize")

    def submit_for_review(callback_id: str, ctx: WaitForCallbackContext) -&amp;gt; None:
        notify_reviewer(callback_id, summary)

    approval = context.wait_for_callback(submitter=submit_for_review, name="human-review")
    if isinstance(approval, str):
        approval = json.loads(approval)

    if not approval.get("approved"):
        return {"status": "rejected", "reason": approval.get("feedback")}

    context.step(publish(summary, approval), name="publish")
    return {"status": "published"}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;This workflow runs across at least two Lambda invocations. The first invocation executes &lt;code&gt;extract-text&lt;/code&gt; and &lt;code&gt;summarize&lt;/code&gt;, then suspends at &lt;code&gt;human-review&lt;/code&gt; with zero compute cost while waiting. Hours later, when the reviewer responds, Lambda invokes the function again. It replays the completed steps and executes &lt;code&gt;publish&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;The following diagram illustrates the difference between the default behavior and the plugin’s unified tracing. On the left side, two independent traces are generated: Trace A captures the first invocation (totaling 2.69 seconds), while Trace B captures the second invocation after the callback resumes (replaying and publishing in 0.37 seconds). These traces have different trace IDs and no correlation between them. On the right side, with the OTel plugin, all operations appear under a single deterministic trace ID. The &lt;code&gt;human-review&lt;/code&gt; wait (6 hours and 8 minutes at zero compute cost) is represented as a continuous span connecting both invocations, giving operators a complete timeline from start to finish. You can compare the total wall-clock duration of 152 seconds against only 0.019 seconds of actual compute time billed.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;img loading="lazy" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/09/03/ComputeBlog-2716-1.png" alt="Figure 1. race comparison of fragmented traces without the plugin (left) versus a single unified trace with the OTel plugin." width="800" height="887"&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1. Trace comparison of fragmented traces without the plugin (left) versus a single unified trace with the OTel plugin (right), showing how the Durable Execution SDK merges multiple Lambda invocations into one end-to-end trace.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;The plugin achieves this through:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Capability&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;What it does&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Deterministic trace IDs&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Derives a stable trace ID from the AWS X-Ray header, so all invocations share one trace&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Span-per-operation&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Each step, wait, or &lt;code&gt;wait_for_callback&lt;/code&gt; gets its own span with real timing&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Continuation spans&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Operations completing in a later invocation link back to the original span&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Log correlation&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Stamps &lt;code&gt;traceId&lt;/code&gt; and &lt;code&gt;spanId&lt;/code&gt; onto every log record automatically&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Configurable sampling&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Standard OpenTelemetry sampling to control trace volume&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/09/03/ComputeBlog-2716-2.png" alt="Figure 2. Amazon CloudWatch Application Signals Traces view. The durable execution appears as a single trace with OK status. The Duration column (152s) reflects the total wall-clock time including the human-review wait, while Response Time (0.019s) shows only the compute time." width="800"&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2. Amazon CloudWatch Application Signals Traces view. The durable execution appears as a single trace with OK status. The Duration column (152s) reflects the total wall-clock time including the human-review wait, while Response Time (0.019s) shows only the compute time.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Choose &lt;b&gt;execution view&lt;/b&gt; to see all operations grouped under the &lt;code&gt;Workflow&lt;/code&gt; span. Use this view when the full execution, including waits and retries, finishes within your tracing vendor’s span ingestion window. For example, if your vendor rejects spans that started more than 8 hours ago, use execution view only for workflows that reliably finish well under 8 hours.&lt;br aria-hidden="true"&gt;Choose &lt;b&gt;invocation view&lt;/b&gt; if an execution might exceed your vendor’s ingestion window, or if you want to see progress as each function execution terminates. Operations appear under the invocation that ran them. A wait’s first segment appears under the invocation that started it, even while the wait is still pending.&lt;br aria-hidden="true"&gt;In both views, the &lt;code&gt;Workflow&lt;/code&gt; span covers the full execution, so the vendor’s ingestion window still applies to it. If an execution runs longer than the window, your vendor might reject the &lt;code&gt;Workflow&lt;/code&gt; span even in invocation view.&lt;/p&gt; 
&lt;p&gt;The plugin sends Workflow as one span when the execution succeeds or fail. It doesn’t send that span in pieces. The vendor can, however, accept earlier spans from the same trace.&lt;/p&gt; 
&lt;p&gt;Why do we recommend someone to use invocation view for long running ones?&lt;br aria-hidden="true"&gt;Suppose a workflow waits 10 hours and the vendor rejects spans that started more than 8 hours ago. In invocation view, the invocation that starts the wait can export the wait’s initial span before the wait finishes. The invocation that resumes the workflow can later export the wait’s completion span. Those short spans can be accepted even if the vendor rejects the final &lt;code&gt;Workflow&lt;/code&gt; span.&lt;/p&gt; 
&lt;h2 id="getting-started"&gt;Getting started&lt;/h2&gt; 
&lt;p&gt;In the following walkthrough, you configure your Lambda durable function to trace requests end-to-end.&lt;/p&gt; 
&lt;h3 id="prerequisites"&gt;Prerequisites&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;Python 3.11 or later.&lt;/li&gt; 
 &lt;li&gt;An existing Lambda durable function (or a new one you want to instrument).&lt;/li&gt; 
 &lt;li&gt;An AWS account with permissions to enable &lt;a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Signals-Enable-LambdaMain.html" target="_blank" rel="noopener"&gt;Amazon CloudWatch Application Signals&lt;/a&gt; tracing and add Lambda layers.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="step-1-install-the-plugin"&gt;Step 1: Install the plugin&lt;/h3&gt; 
&lt;p&gt;Add the plugin to your function’s dependencies:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;pip install aws-durable-execution-sdk-python-otel&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Or in your &lt;code&gt;requirements.txt&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;div class="hide-language"&gt; 
  &lt;div class="hide-language"&gt; 
   &lt;div class="hide-language"&gt; 
    &lt;pre&gt;&lt;code class="lang-python"&gt;aws-durable-execution-sdk-python==3.0.2 
aws-durable-execution-sdk-python-otel==2.1.0&lt;/code&gt;&lt;/pre&gt; 
   &lt;/div&gt; 
  &lt;/div&gt; 
 &lt;/div&gt; 
&lt;/div&gt; 
&lt;h3 id="step-2-add-the-adot-lambda-layer"&gt;Step 2: Add the ADOT Lambda layer&lt;/h3&gt; 
&lt;p&gt;With the &lt;a href="https://aws-otel.github.io/docs/getting-started/lambda" target="_blank" rel="noopener"&gt;AWS Distro for OpenTelemetry (ADOT) Lambda layer&lt;/a&gt;, you can export traces from your function.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;MyDurableFunction:
  Type: AWS::Serverless::Function
  Properties:
    Runtime: python3.13
    Handler: index.handler
    Architectures:
      - x86_64
    DurableConfig:
      ExecutionTimeout: 31622400
    Layers:
      - !Sub arn:aws:lambda:us-east-1:615299751070:layer:AWSOpenTelemetryDistroPython:33
    Environment:
      Variables:
        AWS_LAMBDA_EXEC_WRAPPER: /opt/otel-instrument&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The examples in this post use AWS Serverless Application Model (AWS SAM) for brevity. You can achieve the same configuration using the AWS Command Line Interface (AWS CLI), AWS Cloud Development Kit (AWS CDK), Terraform, or &lt;a href="https://aws.amazon.com/cloudformation/" target="_blank" rel="noopener"&gt;AWS CloudFormation&lt;/a&gt; directly. Refer to the &lt;a href="https://aws-otel.github.io/docs/getting-started/lambda#adot-lambda-layer-arns" target="_blank" rel="noopener"&gt;ADOT Lambda Layer ARNs page&lt;/a&gt; for the latest layer version and supported architectures. Pin the layer version in production deployments to avoid unexpected behavior from automatic version changes.&lt;/p&gt; 
&lt;h3 id="step-3-turn-on-x-ray-active-tracing"&gt;Step 3: Turn on X-Ray active tracing&lt;/h3&gt; 
&lt;p&gt;The plugin uses the &lt;code&gt;_X_AMZN_TRACE_ID&lt;/code&gt; environment variable to derive deterministic trace IDs. Turn on active tracing on your function:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;MyDurableFunction:
  Type: AWS::Serverless::Function
  Properties:
    Tracing: Active&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Also verify your function’s execution role includes the &lt;code&gt;AWSXRayDaemonWriteAccess&lt;/code&gt; managed policy (or equivalent &lt;code&gt;xray:PutTraceSegments&lt;/code&gt; and &lt;code&gt;xray:PutTelemetryRecords&lt;/code&gt; permissions).&lt;/p&gt; 
&lt;h3 id="step-4-add-the-otel-plugin-to-your-handler"&gt;Step 4: Add the OTel plugin to your handler&lt;/h3&gt; 
&lt;p&gt;Import &lt;code&gt;InvocationOtelPlugin&lt;/code&gt; and pass it to the &lt;code&gt;plugins&lt;/code&gt; parameter of &lt;code&gt;@durable_execution&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;div class="hide-language"&gt; 
  &lt;pre&gt;&lt;code class="lang-python"&gt;from aws_durable_execution_sdk_python import DurableContext, durable_execution
from aws_durable_execution_sdk_python.config import Duration
from aws_durable_execution_sdk_python_otel import create_otel_plugin_factory
@durable_execution(plugins=[create_otel_plugin_factory()])
def handler(event: dict, context: DurableContext) -&amp;gt; str:
    data = context.step(lambda ctx: event["id"], name="fetch-data")
    context.wait(Duration.from_seconds(5), name="cooldown")
    return context.step(lambda ctx: f"processed {data}", name="process")&lt;/code&gt;&lt;/pre&gt; 
 &lt;/div&gt; 
&lt;/div&gt; 
&lt;p&gt;The plugin handles &lt;code&gt;Tracer Provider&lt;/code&gt; setup, deterministic ID generation, and span lifecycle internally.&lt;/p&gt; 
&lt;h2 id="testing-and-results"&gt;Testing and results&lt;/h2&gt; 
&lt;p&gt;After you configure the plugin, deploy the function, invoke it, and confirm the unified trace appears in Amazon CloudWatch.&lt;/p&gt; 
&lt;h3 id="testing-the-setup"&gt;Testing the setup&lt;/h3&gt; 
&lt;p&gt;Build and deploy your function:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;sam build
sam deploy --guided&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Then publish a function version (durable functions require a qualified ARN, not &lt;code&gt;$LATEST&lt;/code&gt;):&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda publish-version --function-name my-durable-function --region us-east-1&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Invoke the function asynchronously (required when using &lt;code&gt;wait_for_callback&lt;/code&gt;, since the function suspends mid-execution):&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda invoke \
    --function-name my-durable-function \
    --qualifier 1 \
    --invocation-type Event \
    --region us-east-1 \
    --cli-binary-format raw-in-base64-out \
    --payload '{"doc_id": "test-doc-001"}' \
    response.json&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Monitor the logs to get the callback ID:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws logs tail /aws/lambda/my-durable-function --follow --region us-east-1&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Wait 2-3 minutes (so the &lt;code&gt;human-review&lt;/code&gt; span has visible duration in the trace), then send the callback:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda send-durable-execution-callback-success \
    --cli-binary-format raw-in-base64-out \
    --callback-id "&amp;lt;CALLBACK_ID_FROM_LOGS&amp;gt;" \
    --region us-east-1 \
    --result '{"approved": true, "reviewer": "alice"}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The &lt;code&gt;send-durable-execution-callback-success&lt;/code&gt; command does not require &lt;code&gt;--function-name&lt;/code&gt;. The callback ID already contains the reference to the execution.&lt;/p&gt; 
&lt;h3 id="what-you-see-in-amazon-cloudwatch-application-signals"&gt;What you see in Amazon CloudWatch Application Signals&lt;/h3&gt; 
&lt;p&gt;After you invoke this function, open the &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; console and choose &lt;strong&gt;Application Signals (APM)&lt;/strong&gt;, then &lt;strong&gt;Traces&lt;/strong&gt;. You see a single unified trace containing:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;&lt;strong&gt;One root span&lt;/strong&gt; representing the entire durable execution.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Child spans&lt;/strong&gt; for each named operation: &lt;code&gt;extract-text&lt;/code&gt;, &lt;code&gt;summarize&lt;/code&gt;, &lt;code&gt;human-review&lt;/code&gt;, and &lt;code&gt;publish&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Accurate timing&lt;/strong&gt;: each span reflects the actual wall-clock time of the operation, not replay time.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Continuation links&lt;/strong&gt;: if &lt;code&gt;human-review&lt;/code&gt; completes in a different invocation (after the reviewer approves hours later), the span is linked back to the original trace.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/09/03/ComputeBlog-2716-3.png" alt="Figure 3. Trace details view. The service map shows the flow: Client to Lambda Context (first invocation), then Lambda Function (second invocation after callback resume). Both invocations appear under a single trace ID with total duration of 4.55 sec." width="800"&gt;
 &lt;p class="wp-caption-text"&gt;Figure 3. Trace details view. The service map shows the flow: Client to Lambda Context (first invocation), then Lambda Function (second invocation after callback resume). Both invocations appear under a single trace ID with total duration of 4.55 sec.&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="correlated-logs"&gt;Correlated logs&lt;/h3&gt; 
&lt;p&gt;Because the plugin sets &lt;code&gt;enrich_logger=True&lt;/code&gt; by default, your application logs are automatically stamped with &lt;code&gt;traceId&lt;/code&gt; and &lt;code&gt;spanId&lt;/code&gt;.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/09/08/compute-2716-fig-4.png" alt="Figure 4. Expanded log entry in CloudWatch. Each log record includes traceId, spanId, and otelTraceSampled: true, which lets you correlate logs across all invocations of the same execution." width="800"&gt;
 &lt;p class="wp-caption-text"&gt;Figure 4. Expanded log entry in CloudWatch. Each log record includes traceId, spanId, and otelTraceSampled set to true, which lets you correlate logs across all invocations of the same execution.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;You can combine the plugin’s log correlation with structured JSON logging to run powerful queries in Amazon CloudWatch Logs Insights:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-plaintext"&gt;fields @timestamp, @message, traceId, spanId
| filter traceId = "abcd1234567890abcdef1234567890ab"
| sort @timestamp asc&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;This returns logs from all invocations in chronological order, correlated to their respective spans.&lt;/p&gt; 
&lt;h2 id="best-practices"&gt;Best practices&lt;/h2&gt; 
&lt;p&gt;When you run the OTel plugin in production, keep the following performance, operational, and cost considerations in mind.&lt;/p&gt; 
&lt;h3 id="performance-considerations"&gt;Performance considerations&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Cold start impact:&lt;/strong&gt; The ADOT layer adds overhead to cold starts and memory consumption. Measure the impact for your workload using &lt;a href="https://github.com/alexcasalboni/aws-lambda-power-tuning" target="_blank" rel="noopener"&gt;Lambda Power Tuning&lt;/a&gt;. For latency-sensitive functions, consider using &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/provisioned-concurrency.html" target="_blank" rel="noopener"&gt;provisioned concurrency&lt;/a&gt; to keep warm environments available.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Memory overhead:&lt;/strong&gt; The plugin and ADOT layer &lt;a href="https://aws-observability.github.io/aws-otel-collector/benchmark/report" target="_blank" rel="noopener"&gt;consume approximately 40–60 MB&lt;/a&gt; of additional memory. Verify your function has sufficient memory allocated.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Replay efficiency:&lt;/strong&gt; During replay, the plugin correctly identifies replayed operations and does not emit duplicate spans. Only new operations generate new spans.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="operational-guidelines"&gt;Operational guidelines&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Name your operations:&lt;/strong&gt; Always pass the &lt;code&gt;name&lt;/code&gt; parameter to &lt;code&gt;context.step()&lt;/code&gt;, &lt;code&gt;context.wait_for_callback()&lt;/code&gt;, and other durable operations. These names appear as span names in your traces, making them human-readable.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Use structured logging:&lt;/strong&gt; Combine the plugin’s log correlation with structured JSON logging to unlock powerful Amazon CloudWatch Logs Insights queries.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Monitor trace gaps:&lt;/strong&gt; If you see traces with missing spans, check that X-Ray active tracing is enabled and the ADOT layer is correctly configured.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="cost-management"&gt;Cost management&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Amazon CloudWatch Application Signals pricing:&lt;/strong&gt; You are charged per trace recorded and per trace scanned. At high volumes, configure sampling to control costs. See &lt;a href="https://aws.amazon.com/cloudwatch/pricing/" target="_blank" rel="noopener"&gt;Amazon CloudWatch Application Signals pricing&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Log volume:&lt;/strong&gt; With &lt;code&gt;enrich_logger=True&lt;/code&gt;, every log record includes trace context fields, slightly increasing log volume. This overhead is typically negligible but worth noting for high-throughput functions.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="pricing"&gt;Pricing&lt;/h2&gt; 
&lt;p&gt;The plugin is open source (Apache 2.0). Costs come from AWS X-Ray traces recorded and the ADOT Lambda layer overhead. The layer increases both the memory consumption and the cold start duration of your function. Lambda pricing is based on GB-seconds, so the additional memory allocated (rounded up to the nearest MB) multiplied by the additional execution time per invocation determines the cost impact. Each durable execution produces one trace regardless of invocation count, so X-Ray cost scales with executions, not invocations. Measure the overhead for your workload using &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html#configuration-memory-use-cases" target="_blank" rel="noopener"&gt;Lambda Power Tuning&lt;/a&gt; and see &lt;a href="https://aws.amazon.com/cloudwatch/pricing/" target="_blank" rel="noopener"&gt;AWS X-Ray pricing&lt;/a&gt; for current rates.&lt;/p&gt; 
&lt;h2 id="beyond-this-post"&gt;Beyond this post&lt;/h2&gt; 
&lt;p&gt;This post focused on a single, representative workflow (sequential steps plus a human-approval callback) to keep the walkthrough concrete. It is not an exhaustive tour of the SDK. The Durable Execution SDK offers many other primitives that also produce spans and are worth exploring: durable timers (&lt;code&gt;context.wait&lt;/code&gt;), condition polling (&lt;code&gt;context.wait_for_condition&lt;/code&gt;), durable Lambda-to-Lambda calls (&lt;code&gt;context.invoke&lt;/code&gt;), parallel and fan-out execution (&lt;code&gt;context.parallel&lt;/code&gt;, &lt;code&gt;context.map&lt;/code&gt;), nested child contexts, and automatic retries (&lt;code&gt;with_retry&lt;/code&gt; and &lt;code&gt;StepConfig&lt;/code&gt;), where each attempt and each parallel branch surfaces as its own span. We also did not cover failure paths, such as step errors and failure callbacks, which is where unified tracing is often most valuable.&lt;/p&gt; 
&lt;p&gt;Likewise, the OTel plugin exposes configuration we did not exercise here: toggling log enrichment &lt;code&gt;(InvocationOtelPlugin(OtelPluginConfig(enrich_logger=False)))&lt;/code&gt;, supplying a custom Tracer Provider&lt;code&gt; via OtelPluginConfig(tracer_provider=...)&lt;/code&gt;, and controlling trace volume through standard OpenTelemetry sampling (&lt;code&gt;OTEL_TRACES_SAMPLER&lt;/code&gt;). This walkthrough sampled 100% of traces. Consult the &lt;a href="https://docs.aws.amazon.com/durable-functions/" target="_blank" rel="noopener"&gt;SDK documentation&lt;/a&gt; for the full surface area, or access the &lt;a href="https://github.com/aws/aws-durable-execution-sdk-python/tree/main/packages/aws-durable-execution-sdk-python-otel" target="_blank" rel="noopener"&gt;GitHub repository&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;b&gt;Sending Lambda durable functions traces to Observability partners. &lt;/b&gt;&lt;br aria-hidden="true"&gt;The OpenTelemetry plugin exports telemetry data to Amazon CloudWatch and can work with any observability solution that supports OpenTelemetry. &lt;b&gt;&lt;u&gt;&lt;a href="https://dash0.com/" target="_blank" rel="noopener noreferrer"&gt;Dash0&lt;/a&gt;&lt;/u&gt;&lt;/b&gt;&amp;nbsp;is an OpenTelemetry-native observability platform that supports Lambda durable functions without custom configuration. Dash0 worked with AWS to validate the OpenTelemetry plugin for the AWS Durable Execution SDK for JavaScript prior to launch, &lt;b&gt;Dash0 coordinates logs and spans. &lt;/b&gt;In Dash0, spans for the durable execution, each invocation, and each durable operation appear alongside the function’s inputs and outputs and the payloads of its AWS SDK calls. To learn more, visit &lt;u&gt;&lt;a href="https://www.dash0.com/docs/dash0/infrastructure/aws/aws-lambda/overview" target="_blank" rel="noopener noreferrer"&gt;About AWS Lambda Monitoring&lt;/a&gt;&lt;/u&gt;.&lt;/p&gt; 
&lt;h2 id="clean-up"&gt;Clean up&lt;/h2&gt; 
&lt;p&gt;To avoid ongoing charges, delete the resources created in this walkthrough:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;sam delete --stack-name &amp;lt;your-stack-name&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;This removes the Lambda function, AWS Identity and Access Management (IAM) roles, and any associated resources created by the SAM template.&lt;/p&gt; 
&lt;p&gt;If you manually added the ADOT Lambda layer or X-Ray tracing policies outside of your SAM template, remove those separately using the AWS CLI or console.&lt;/p&gt; 
&lt;p&gt;Trace data retained in X-Ray does not incur storage charges and expires automatically after 30 days.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;In this post, we showed how to unify fragmented traces across multiple Lambda invocations using the OpenTelemetry plugin for the Durable Execution SDK. To explore the full SDK surface area, including parallel execution, durable timers, and failure-path tracing, see the &lt;a href="https://docs.aws.amazon.com/durable-execution/sdk-reference/observability/opentelemetry/" target="_blank" rel="noopener"&gt;AWS Durable Execution SDK Developer Guide&lt;/a&gt;. For more observability patterns, visit the &lt;a href="https://aws-observability.github.io/observability-best-practices/" target="_blank" rel="noopener"&gt;AWS Observability Best Practices guide&lt;/a&gt;.&lt;/p&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Monitor the efficiency and availability of accelerated computing instances with Amazon EC2 Detailed Monitoring and performance status checks</title>
		<link>https://aws.amazon.com/blogs/compute/monitor-the-efficiency-and-availability-of-accelerated-computing-instances-with-amazon-ec2-detailed-monitoring-and-performance-status-checks/</link>
		
		<dc:creator><![CDATA[Caroline Frost]]></dc:creator>
		<pubDate>Thu, 19 Nov 2026 18:34:57 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Announcements]]></category>
		<guid isPermaLink="false">f98e2ce13e6d4081337568150c1e378fe2ae3343</guid>

					<description>Amazon EC2 now reports one-minute per-GPU metrics through Detailed Monitoring and surfaces recoverable hardware conditions with a new performance status check, giving infrastructure teams agentless visibility into accelerated computing efficiency and availability across their fleet.</description>
										<content:encoded>&lt;p&gt;Amazon Elastic Compute Cloud (Amazon EC2) &lt;a href="https://aws.amazon.com/ec2/instance-types/accelerated-computing/" target="_blank" rel="noopener"&gt;accelerated computing instances&lt;/a&gt; run some of the most demanding workloads customers operate, from large model training and distributed fine-tuning to high-throughput, live inference. These customers seek high availability and performance to make sure their training and inference run efficiently. To meet their performance goals, customers require visibility into the efficiency and performance of each accelerated computing chip in their fleet.&lt;/p&gt; 
&lt;p&gt;For example, central infrastructure or machine learning teams often operate accelerated computing capacity for many application teams. These infrastructure teams need a clear view of utilization and health across every instance in their fleet even if they don’t develop the applications running on those instances. They are often responsible for how efficiently that capacity is used and for hardware health, while application teams own the workload. Customers asked us to provide foundational telemetry for their accelerated computing efficiency and status that doesn’t require setup within the instance and complements their in-guest tooling.&lt;/p&gt; 
&lt;p&gt;Amazon EC2 now reports one-minute graphics processing unit (GPU) metrics through Detailed Monitoring and surfaces recoverable conditions with performance status checks. One-minute GPU metrics in Amazon EC2 Detailed Monitoring report per-GPU utilization and thermal data to Amazon CloudWatch, so you can identify underused capacity and tune workloads for cost and throughput. Performance status checks report recoverable hardware conditions, such as a GPU memory error, to help you manage GPU performance.&lt;/p&gt; 
&lt;h2 id="feature-overviews"&gt;Feature overviews&lt;/h2&gt; 
&lt;p&gt;Amazon EC2 reports GPU metrics and performance status checks without an in-guest agent and without using instance compute. These capabilities are available on supported NVIDIA GPU-based accelerated computing instance types. For the metrics supported on each instance family, see the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html#accelerator-metrics" target="_blank" rel="noopener"&gt;Amazon EC2 Detailed Monitoring documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;One-minute accelerated computing metrics extend EC2 Detailed Monitoring and are published to CloudWatch as OpenTelemetry Metrics or CloudWatch Metrics. The metric name you add to a category determines which one CloudWatch publishes: include &lt;code&gt;GPUUtilization&lt;/code&gt; for a CloudWatch Metric, &lt;code&gt;instance.gpu.utilization&lt;/code&gt; for an OpenTelemetry Metric, or both names to publish both. Amazon EC2 publishes each metric to CloudWatch at two levels: one series for the instance, identified by &lt;code&gt;InstanceId&lt;/code&gt;, and one series for each GPU, identified by &lt;code&gt;InstanceId&lt;/code&gt; and &lt;code&gt;GpuId&lt;/code&gt;. &lt;code&gt;GpuId&lt;/code&gt; is the GPU UUID, which you can match to a device by running &lt;code&gt;nvidia-smi -L&lt;/code&gt; on the instance.&lt;/p&gt; 
&lt;p&gt;Performance status checks add a fifth status check to the existing Amazon EC2 product check suite of system, instance, attached EBS, and application status checks. The check reports recoverable hardware issues that affect accelerated computing performance while the instance might remain running and reachable. It surfaces through the EC2 console, through &lt;code&gt;DescribeInstanceStatus&lt;/code&gt;, and in CloudWatch metrics.&lt;/p&gt; 
&lt;h2 id="evaluating-accelerated-computing-utilization-and-performance-with-ec2-detailed-monitoring"&gt;Evaluating accelerated computing utilization and performance with EC2 Detailed Monitoring&lt;/h2&gt; 
&lt;p&gt;Amazon EC2 Detailed Monitoring reports per-GPU measurements, including compute activity, memory use, temperature, and data movement.&lt;/p&gt; 
&lt;p&gt;GPU utilization metrics report different aspects of GPU use. &lt;code&gt;GPUPowerUtilization&lt;/code&gt; is available by default and reports active power use. Power utilization scales with the depth of work the GPU performs. Compare it with more granular utilization metrics to see how efficiently your workload uses the GPUs. GPU utilization shows the percentage of time the GPU was running work. Because a busy GPU might use only a fraction of its streaming multiprocessors (SMs), compare it with SM utilization to see how much of the compute capacity the workload uses. Memory utilization shows how much of the GPU’s memory capacity is in use, helping you assess memory headroom. Context accumulated time is a running total of the time a process has held the GPU open, whether or not it ran work. Use the CloudWatch &lt;a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/using-metric-math.html#metric-math-syntax-functions-list" target="_blank" rel="noopener"&gt;metric math&lt;/a&gt; expression &lt;code&gt;RATE(m1)/1000000&lt;/code&gt;, where &lt;code&gt;m1&lt;/code&gt; is &lt;code&gt;GPUContextAccumulatedTime&lt;/code&gt;, to compare context activity with GPU utilization. A result close to 1 with low GPU utilization indicates that a GPU context is held open but idle.&lt;/p&gt; 
&lt;p&gt;GPU temperature is reported as a percentage of the GPU’s thermal throttle limit, and memory temperature as a percentage of the memory’s critical temperature. Both metrics can report values above 100 percent when a GPU or its memory runs above the limit. A GPU reduces its clocks when it reaches its throttle limit, so a value at or above 100 percent can explain a drop in throughput. You can correlate these measurements with GPU and interconnect utilization metrics to understand workload performance.&lt;/p&gt; 
&lt;p&gt;Interconnect utilization metrics show how much of the available bandwidth a workload uses for data movement. Each value reports the busier direction, either send or receive. NVLink utilization measures GPU-to-GPU traffic, such as collective operations in distributed training. It reports all of the GPU’s links together. PCIe utilization measures traffic between the host and the GPU.&lt;/p&gt; 
&lt;h2 id="getting-started-with-ec2-detailed-monitoring"&gt;Getting started with EC2 Detailed Monitoring&lt;/h2&gt; 
&lt;p&gt;Amazon EC2 Detailed Monitoring publishes instance metrics to Amazon CloudWatch at one-minute intervals without running an agent in the guest operating system. You can publish these as OpenTelemetry Metrics or CloudWatch Metrics.&lt;/p&gt; 
&lt;p&gt;To get started, create a metric category, an Amazon EC2 resource containing the metrics you want to collect. Next, associate the category with one or more instances. For an existing instance, provide the category ID when you enable Detailed Monitoring with the &lt;code&gt;MonitorInstances&lt;/code&gt; API. For a new instance, provide the category ID in the &lt;code&gt;Monitoring&lt;/code&gt; object when you call &lt;code&gt;RunInstances&lt;/code&gt; or configure a launch template.&lt;/p&gt; 
&lt;p&gt;The following example creates a metric category for GPU utilization, SM utilization, and memory utilization.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 create-metric-category --metrics instance.gpu.utilization instance.gpu.sm_utilization instance.gpu.memory_utilization&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The response includes a metric category ID. To associate the category with an existing instance, use &lt;code&gt;MonitorInstances&lt;/code&gt;.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 monitor-instances --instance-ids &amp;lt;instance-id&amp;gt; --metric-category-ids &amp;lt;metric-category-id&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;To associate the category when you launch an instance, include the category ID in the &lt;code&gt;Monitoring&lt;/code&gt; object.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 run-instances --image-id &amp;lt;ami-id&amp;gt; --instance-type &amp;lt;instance-type&amp;gt; --count 1 --monitoring Enabled=true,MetricCategoryIds=&amp;lt;metric-category-id&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;To apply a category to every instance launched from a launch template, include the category ID in the &lt;code&gt;Monitoring&lt;/code&gt; object in the launch template data.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 create-launch-template --launch-template-name accelerated-computing-monitoring --launch-template-data '{"Monitoring":{"Enabled":true,"MetricCategoryIds":["&amp;lt;metric-category-id&amp;gt;"]}}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Categories apply to many instances at once, unlike per-instance metric settings. Define the metric set once and associate it wherever it applies. Every associated instance then reports the same set of metrics. Changing a category updates the metric set for every associated instance. The change is eventually consistent across running instances. Add the category to a launch template to apply the same metrics to new instances. This gives you one metric definition per workload type instead of one configuration per host. Metrics apply under &lt;a href="https://aws.amazon.com/cloudwatch/pricing/" target="_blank" rel="noopener"&gt;standard Amazon CloudWatch pricing&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="managing-accelerated-computing-availability-with-performance-status-checks"&gt;Managing accelerated computing availability with performance status checks&lt;/h2&gt; 
&lt;p&gt;Accelerated computing hardware can experience non-terminal issues that affect performance and can be resolved with a GPU reset or an instance reboot. For example, when a GPU encounters an uncorrectable memory error, it schedules a repair that remaps the affected row to a spare. The repair takes effect the next time the GPU is reset or the instance is rebooted.&lt;/p&gt; 
&lt;p&gt;Amazon EC2 performance status checks surface these recoverable hardware conditions. For example, when Amazon EC2 detects a pending GPU memory row remap, the instance’s performance status check reports an impaired status and identifies reboot as the recommended remediation.&lt;/p&gt; 
&lt;p&gt;You can view performance status checks on the Amazon EC2 console or through &lt;code&gt;DescribeInstanceStatus&lt;/code&gt;. Amazon EC2 also publishes the &lt;code&gt;StatusCheckFailed_Performance&lt;/code&gt; metric to CloudWatch. A failed performance status check also increments the combined &lt;code&gt;StatusCheckFailed&lt;/code&gt; metric. The following example uses the EC2 &lt;code&gt;DescribeInstanceStatus&lt;/code&gt; API:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 describe-instance-status --instance-ids i-0123456789abcdef0&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The following response shows the system, instance, attached EBS, and configured application status checks passing while the performance status check is impaired:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
  "InstanceStatuses": [
    {
      "AvailabilityZone": "us-east-1a",
      "InstanceId": "i-0123456789abcdef0",
      "InstanceState": {
        "Code": 16,
        "Name": "running"
      },
      "InstanceStatus": {
        "Details": [
          {
            "Name": "reachability",
            "Status": "passed"
          }
        ],
        "Status": "ok"
      },
      "SystemStatus": {
        "Details": [
          {
            "Name": "reachability",
            "Status": "passed"
          }
        ],
        "Status": "ok"
      },
      "AttachedEbsStatus": {
        "Details": [
          {
            "Name": "reachability",
            "Status": "passed"
          }
        ],
        "Status": "ok"
      },
      "ApplicationStatus": {
        "Status": "ok"
      },
      "PerformanceStatus": {
        "Status": "impaired",
        "ImpairedSince": "2026-10-18T14:32:00Z",
        "Remediation": "reboot"
      }
    }
  ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Amazon EC2 sends a scheduled event for the instance if the condition requires further action after a reboot.&lt;/p&gt; 
&lt;p&gt;To act on these conditions across your accelerated computing instances, create a CloudWatch alarm on &lt;code&gt;StatusCheckFailed_Performance&lt;/code&gt;.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;The alarm on &lt;code&gt;StatusCheckFailed_Performance&lt;/code&gt; fires for an instance in a training cluster.&lt;/li&gt; 
 &lt;li&gt;You confirm the condition and the recommended action with &lt;code&gt;DescribeInstanceStatus&lt;/code&gt;, which returns a status of impaired and a remediation of reboot.&lt;/li&gt; 
 &lt;li&gt;You checkpoint the job if applicable, then drain the node and reboot the instance at a planned point. On Amazon Elastic Kubernetes Service (Amazon EKS), cordon and drain the node. In Slurm, set the node to &lt;code&gt;DRAIN&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;After the reboot completes, the performance status check returns to ok.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;The following command creates that alarm for a single instance.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws cloudwatch put-metric-alarm --alarm-name performance-status-impaired-&amp;lt;instance-id&amp;gt; --namespace AWS/EC2 --metric-name StatusCheckFailed_Performance --dimensions Name=InstanceId,Value=&amp;lt;instance-id&amp;gt; --statistic Maximum --unit Count --period 60 --evaluation-periods 2 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --alarm-actions &amp;lt;sns-topic-arn&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;A CloudWatch Metrics Insights alarm evaluates a single query across all matching instances, so one alarm can cover a large fleet. To drive automation without an alarm, poll the &lt;code&gt;DescribeInstanceStatus&lt;/code&gt; API.&lt;/p&gt; 
&lt;p&gt;Rebooting the instance is the recommended remediation. Alternatively, you can reset the affected GPU while keeping the other GPUs running. On the affected instance, run &lt;code&gt;nvidia-smi -q -d ROW_REMAPPER&lt;/code&gt; and find the GPU that reports &lt;code&gt;Pending: Yes&lt;/code&gt;. Stop all processes using that GPU, then use root permissions to run &lt;code&gt;nvidia-smi -r -i &amp;lt;GPU_UUID&amp;gt;&lt;/code&gt;. The performance status check returns to ok shortly after the reset completes.&lt;/p&gt; 
&lt;h2 id="bringing-it-all-together"&gt;Bringing it all together&lt;/h2&gt; 
&lt;p&gt;Accelerated computing metrics and performance status checks address complementary questions. Detailed Monitoring metrics help you find idle or underused capacity and tune workloads for cost and throughput. Performance status checks surface recoverable conditions and recommend remediation. Together, these EC2 signals report utilization and status across the capacity infrastructure teams manage, while in-guest tooling provides workload-specific analysis.&lt;/p&gt; 
&lt;p&gt;For example, a central infrastructure team monitors how efficiently workloads use the accelerated computing instances it manages for several application teams. It finds that one team’s GPUs report lower GPU utilization and power utilization than comparable workloads run by other teams. The infrastructure team shares the finding and relevant workload-tuning practices with the application team. After the application team updates that workload, the infrastructure team uses the same CloudWatch metrics to evaluate the change. The infrastructure team also monitors &lt;code&gt;StatusCheckFailed_Performance&lt;/code&gt; across the fleet. When a check reports an impaired status and recommends a reboot, the orchestrator saves the active job, stops placing new work on the instance, and reboots it. After the check returns to ok, the orchestrator makes the instance available for new jobs. Together, these workflows help the team improve GPU utilization, protect job progress, and return affected capacity to service.&lt;/p&gt; 
&lt;p&gt;Amazon EC2 Detailed Monitoring reports accelerated computing metrics once per minute at the instance and GPU levels. Performance status checks report recoverable conditions at the instance level. Infrastructure teams can use these EC2 signals to monitor utilization and status across the capacity they manage. In-guest tools add process, container, Kubernetes pod, and sub-minute detail.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon EC2&lt;/a&gt; Detailed Monitoring reports metrics for your instances, including GPU utilization metrics reported per GPU. Performance status checks tell you when accelerated computing hardware needs attention. These capabilities help you evaluate utilization and manage the efficiency of your accelerated computing fleets. To learn more, see the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/manage-detailed-monitoring.html#detailed-monitoring-metric-categories" target="_blank" rel="noopener"&gt;Amazon EC2 Detailed Monitoring documentation&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-system-instance-status-check.html" target="_blank" rel="noopener"&gt;EC2 status checks documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the author&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/17/ComputeBlog-2815-1.jpg" alt="Caroline Frost" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Caroline Frost&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Caroline is an Amazon EC2 Senior Product Manager – Technical, focusing on the EC2 instance lifecycle. She is passionate about building capabilities that improve the developer experience and create operational ease and simplicity.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Control your AWS Lambda runtimes with customer-managed runtimes</title>
		<link>https://aws.amazon.com/blogs/compute/control-your-aws-lambda-runtimes-with-customer-managed-runtimes/</link>
		
		<dc:creator><![CDATA[Jonathan Tuliani]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 18:53:02 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<guid isPermaLink="false">5315aad48b621eed88c470a184edb89f041d3f34</guid>

					<description>AWS Lambda customer-managed runtimes give you full control over the contents, updates, access, and lifecycle of the runtime your Lambda Event Functions use. Package a runtime once, share it across your organization, and roll out updates centrally. Functions pick up the change automatically, keeping the same .zip deployment experience.</description>
										<content:encoded>&lt;p&gt;With AWS Lambda &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/runtimes-customer-managed.html" target="_blank" rel="noopener"&gt;customer-managed runtimes&lt;/a&gt; for Lambda Event Functions (formerly called Lambda functions), you get full control over Lambda runtime contents, updates, access, and lifecycle. You package your runtime once, share it across your organization, and when you update it, Event Functions pick up the change automatically. You can test, schedule, stagger, and monitor the runtime update rollout. If necessary, you can roll back.&lt;/p&gt; 
&lt;p&gt;In this post, we will explain why you might use a customer-managed runtime, and the core concepts of Lambda runtime management. This includes the runtime publisher and consumer roles, resource model, and update process. We will also cover cross-organization runtime sharing, deletion guardrails, and pricing.&lt;/p&gt; 
&lt;h2 id="lambda-managed-runtimes"&gt;Lambda managed runtimes&lt;/h2&gt; 
&lt;p&gt;Until now, AWS Lambda Event Functions (formerly Lambda functions) ran only on runtimes that Lambda manages. You choose a language, deploy your code, and Lambda takes care of the runtime, including patching and lifecycle management. This model works well, and remains the right choice for many Lambda customers, especially those who are new to serverless.&lt;/p&gt; 
&lt;p&gt;However, for more advanced customers managing thousands of Event Functions, the Lambda managed runtime can be restrictive. For example, suppose your organization has a standardized security or monitoring extension, enterprise certificates, or even wants to use Lambda with an additional language such as PHP. These components need to be included in each Event Function in an application or organization, in addition to the function code.&lt;/p&gt; 
&lt;p&gt;With Lambda managed runtimes, you have two options. You can use Lambda layers to distribute shared libraries. These must be deployed with every function, as shown in the diagram:&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-1.png" alt="Boxes-and-arrows diagram showing each Lambda function repeating three components (function code, PHP runtime, and monitoring extension), all connected to a single Lambda runtime that contains only the OS libraries" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Using PHP and a monitoring extension with a Lambda managed runtime&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Layers follow a pull model, so when you update a layer, you must redeploy every Event Function that uses it to pick up the change. Alternatively, you can use container image packaging to get full control over the runtime contents. But this shifts complexity to every developer on every team. Developers need to understand Dockerfiles, image registries, and container builds, and need to rebuild and redeploy every function to roll out a shared component update. You also lose the simplicity of .zip-based deployment and automatic runtime updates.&lt;/p&gt; 
&lt;h2 id="how-customer-managed-runtimes-solve-this"&gt;How customer-managed runtimes solve this&lt;/h2&gt; 
&lt;p&gt;With customer-managed runtimes you can package your language runtime, certificates, security tools, and monitoring agents into a centrally managed runtime resource, shared by any number of functions.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-2.png" alt="Boxes-and-arrows diagram showing each Lambda function with a single component, the function code, all connected to one customer-managed runtime that contains the PHP runtime, monitoring extension, and OS libraries" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: Using PHP and a monitoring extension with a customer-managed runtime&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Application developers reference your runtime in their Event Function configuration, the same way they would reference a Lambda-managed runtime like &lt;code&gt;python3.14&lt;/code&gt;. They deploy their code as .zip files, use the same AWS Command Line Interface (AWS CLI) and tools, and receive runtime updates automatically.&lt;/p&gt; 
&lt;p&gt;When you update the runtime, you update it once. Event Functions pick up the new version at their next cold start, with no per-function redeployments. You can stage the rollout across environments, roll out Region by Region, monitor function invocation success rates, and roll back if something goes wrong.&lt;/p&gt; 
&lt;p&gt;This model supports a range of scenarios:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Standardize shared components at scale –&lt;/strong&gt;&amp;nbsp;Give teams in your organization a runtime with your approved security and monitoring tools built in. Update those tools centrally.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Use languages Lambda doesn’t support –&lt;/strong&gt;&amp;nbsp;Package languages or runtimes such as PHP, Bun, R, or any other language into a customer-managed runtime. Developers use it with the same .zip deployment experience as Python or Node.js.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Control your patching cadence –&lt;/strong&gt;&amp;nbsp;Apply runtime patches on your schedule, immediately for critical issues or during planned maintenance windows for routine updates. You can also stage the updates, for example across development, test, and production environments.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Extend runtime lifetime –&lt;/strong&gt;&amp;nbsp;If Lambda deprecates a managed runtime before your organization is ready to migrate, fork it into a customer-managed runtime. Now you can apply your own security patches and deprecate on your own timeline.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="publishers-and-consumers"&gt;Publishers and consumers&lt;/h2&gt; 
&lt;p&gt;Customer-managed runtimes introduce two roles: &lt;em&gt;runtime publisher&lt;/em&gt; and &lt;em&gt;runtime consumer&lt;/em&gt;.&lt;/p&gt; 
&lt;p&gt;The &lt;em&gt;runtime publisher&lt;/em&gt; owns the runtime. That includes its contents, updates, access control, and lifecycle. The publisher builds runtime images, publishes versions, rolls out updates, and decides who can use the runtime. In an enterprise, this could be a central cloud platform team. Alternatively, an application team could operate an application-specific runtime built on base images from their platform team, or from Lambda.&lt;/p&gt; 
&lt;p&gt;The &lt;em&gt;runtime consumer&lt;/em&gt; is the function developer. Consumers reference the runtime in their Event Function configuration, deploy their code as .zip files, and receive updates automatically. They don’t use or manage the underlying container images. They only write application code.&lt;/p&gt; 
&lt;p&gt;This separation creates a clean boundary. The runtime publisher focuses on runtime management: patching, security tooling, and compliance. Developers consume the runtime and focus on their business logic.&lt;/p&gt; 
&lt;h2 id="resource-model"&gt;Resource model&lt;/h2&gt; 
&lt;p&gt;Customer-managed runtimes use three resource types that work together.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Runtime&lt;/strong&gt;: The top-level resource representing the runtime as a whole, for example, a PHP 8 runtime for your organization. A runtime has a name, an Amazon Resource Name (ARN), and a description. You control access at the runtime level using a resource-based policy. To create a runtime:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda-core create-runtime \
    --name my-runtime \
    --description "Describe or link to runtime description" \
    --license-info "None"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Runtime version&lt;/strong&gt;: Represents the contents of the runtime at a point in time. Each version is backed by a container image in Amazon Elastic Container Registry (Amazon ECR) and is immutable, so once created it can’t be changed. To update the runtime, you create a new version. To create a runtime version, reference the ECR image that defines the runtime contents:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda-core create-runtime-version \
    --runtime-name my-runtime \
    --name v1 \
    --image-uri 111122223333.dkr.ecr.us-east-1.amazonaws.com/my-runtime:v1&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Runtime images contain the operating system libraries, language support, a bootstrap script, and the runtime interface client (code that retrieves invoke requests from the Lambda service and calls your function handler). You must grant the Lambda service principal read access to your ECR repository. For details, refer to the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/cmr-building-images.html" target="_blank" rel="noopener"&gt;runtime image building documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Runtime alias&lt;/strong&gt;: A named pointer to a runtime version. Event Functions consume the runtime through an alias. When you update an alias to point to a new version, functions using that alias pick up the change at their next cold start. To create a runtime alias:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda-core create-runtime-alias \
    --runtime-name my-runtime \
    --name production \
    --runtime-version v1&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;How you structure your aliases depends on your release process, for example, separate aliases per environment (dev, test, prod), per release track (latest, stable), or semantic version (php8.3, php8.4). Refer to &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/cmr-aliases.html#cmr-aliases-strategies" target="_blank" rel="noopener"&gt;alias strategies&lt;/a&gt; in the documentation for common patterns.&lt;/p&gt; 
&lt;p&gt;Runtimes are Regional resources. You must create a runtime, its versions, and its aliases in each AWS Region where you need them. We recommend using consistent names across Regions so that ARNs differ only in the Region component. Use ECR cross-Region replication to distribute your images, and roll out alias updates one Region at a time to limit the impact of a faulty version.&lt;/p&gt; 
&lt;h2 id="consuming-a-runtime"&gt;Consuming a runtime&lt;/h2&gt; 
&lt;p&gt;For function developers, the only change is how you specify the runtime source. In the Lambda console, specify whether the runtime is in the function’s account or shared from a different account, and provide the runtime alias ARN:&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-3.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-3.png" alt="AWS Lambda console Create Event Function page with a red box highlighting the runtime selection, where the ‘Your runtimes’ option is chosen instead of ‘AWS-managed runtimes’ and a customer-managed runtime alias ARN is entered" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 3: The Lambda console Create Event Function page with customer-managed runtime selection&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;In the AWS CLI (and similarly in AWS CloudFormation), instead of specifying a Lambda runtime identifier like &lt;code&gt;python3.14&lt;/code&gt;, you set the runtime to &lt;code&gt;custom&lt;/code&gt; and provide the runtime ARN and alias name:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda create-function \
    --function-name my-function \
    --runtime custom \
    --runtime-config RuntimeArn=arn:aws:lambda:us-east-1:111122223333:runtime/my-runtime,RuntimeAlias=production \
    --handler index.handler \
    --zip-file fileb://function.zip \
    --role arn:aws:iam::111122223333:role/my-lambda-role&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Everything else works the same, including function configuration, invocation, logging, monitoring, layers, and infrastructure-as-code tools. Developers deploy .zip files, use the same CLI, and don’t need to learn containers or new tooling.&lt;/p&gt; 
&lt;h2 id="runtime-updates-and-monitoring"&gt;Runtime updates and monitoring&lt;/h2&gt; 
&lt;p&gt;As a runtime publisher, you own the update process. Lambda doesn’t patch customer-managed runtimes for you. If you build your runtime from a Lambda base image, you get the operating system, language runtime, and Lambda runtime interface client as a starting point. AWS regularly updates the base images with security patches. You can also build your runtime image from scratch for maximum control.&lt;/p&gt; 
&lt;p&gt;To patch your runtime, first rebuild your runtime image from the updated base image. You then publish a new runtime version referencing the new image, test it, and roll out the new version by updating your runtime aliases. To create a new runtime version and update an alias:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda-core create-runtime-version \
    --runtime-name my-runtime \
    --name v2 \
    --image-uri 111122223333.dkr.ecr.us-east-1.amazonaws.com/my-runtime:v2

aws lambda-core update-runtime-alias \
    --runtime-name my-runtime \
    --name production \
    --runtime-version v2&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Lambda publishes two Amazon CloudWatch metrics in the runtime publisher’s account: &lt;code&gt;RuntimeInvocations&lt;/code&gt; (total invocations of functions using the runtime) and &lt;code&gt;RuntimeInvocationErrors&lt;/code&gt; (invocations that result in errors). You can view these by runtime, runtime version, or runtime alias.&lt;/p&gt; 
&lt;p&gt;Your runtime updates need to be backward-compatible with existing functions. Lambda strives to provide backward-compatible updates to its base images, which you can use as your starting point. However, as with any change, there’s always the possibility of an unexpected compatibility issue. During a rollout, you can compare the error rate of the new runtime version against the previous version. If the new version shows a higher error rate under similar traffic, it’s a signal to pause or roll back by re-pointing the alias to the previous runtime version. You can also track rollout progress as Lambda replaces execution environments, shifting invocations from the old version to the new one. We recommend creating a CloudWatch alarm on the error rate of each alias and configuring your deployment pipeline to halt when an alarm fires.&lt;/p&gt; 
&lt;h2 id="cross-account-sharing-and-trust"&gt;Cross-account sharing and trust&lt;/h2&gt; 
&lt;p&gt;For customer-managed runtimes, we expect most usage to be cross-account: the runtime publisher shares a runtime with runtime consumer accounts by applying a resource-based policy on the runtime. You can share with individual AWS accounts, an AWS Organizations organization or organizational unit, or publicly. Consumers in shared accounts also need an identity-based policy granting &lt;code&gt;lambda:AssociateRuntimeAlias&lt;/code&gt; permission. Both the resource-based and identity-based policies must allow the action for cross-account access to work. To allow consumers to use &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html#runtime-management-controls" target="_blank" rel="noopener"&gt;runtime management controls&lt;/a&gt; to roll back a function to a specific runtime version, they also need &lt;code&gt;lambda:AssociateRuntimeVersion&lt;/code&gt; permission. For details and example policies, refer to &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/cmr-permissions.html" target="_blank" rel="noopener"&gt;Sharing and controlling access to customer-managed runtimes&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;A runtime publisher can push code into the execution environments of every function that uses their runtime. This is by design. It’s how runtime updates work. The runtime publisher can also ship updates that break your functions, or delete the runtime causing your functions to fail. This means you must trust the runtime publisher the same way you would trust anyone managing your application or running code with your permissions.&lt;/p&gt; 
&lt;p&gt;Organization administrators can use service control policies (SCPs) to govern which runtimes are allowed in their organization. For example, allowing only runtimes from specific trusted accounts, or blocking all external runtimes entirely. To consume a third-party runtime, you may wish to retain control by using their container images to build a customer-managed runtime that you manage. The image-centric model means you can use standard container tooling for vulnerability scanning, compliance checks, and supply chain security. These are the same tools you already use for your other container workloads.&lt;/p&gt; 
&lt;h2 id="deletion-guardrails"&gt;Deletion guardrails&lt;/h2&gt; 
&lt;p&gt;Deleting a runtime resource can break many functions, including functions in other accounts. Because of this, Lambda enforces built-in guardrails to help prevent and recover from accidental deletion:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Deletion isn’t immediate. Lambda schedules the runtime, version, or alias for deletion with a waiting period you choose, from 7–30 days (default 30). During this period, you can restore the resource.&lt;/li&gt; 
 &lt;li&gt;You can’t delete a runtime version while an alias points to it.&lt;/li&gt; 
 &lt;li&gt;You can’t delete a runtime while it has versions or aliases that aren’t scheduled for deletion. You must delete aliases first, then versions, then the runtime.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;When a runtime alias or version is deleted (or scheduled for deletion), functions that use it enter the &lt;code&gt;Inactive&lt;/code&gt; state and invocations fail on cold start. If you restore the resource during the waiting period, functions recover automatically, with no redeployment needed.&lt;/p&gt; 
&lt;p&gt;Before deleting any runtime resource, check the &lt;code&gt;RuntimeInvocations&lt;/code&gt; metric to verify usage. You can monitor runtime metrics during the scheduled for deletion window to check whether the pending deletion is causing function invocations to fail.&lt;/p&gt; 
&lt;p&gt;To manage the runtime lifecycle, you can set a release lifecycle stage (&lt;code&gt;Preview&lt;/code&gt;, &lt;code&gt;GenerallyAvailable&lt;/code&gt;, or &lt;code&gt;Deprecated&lt;/code&gt;) and optionally block new function creation or function updates after a specified date. Refer to &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/cmr-lifecycle.html" target="_blank" rel="noopener"&gt;runtime lifecycle management&lt;/a&gt; in the documentation for details.&lt;/p&gt; 
&lt;h2 id="pricing"&gt;Pricing&lt;/h2&gt; 
&lt;p&gt;There’s no additional charge for customer-managed runtimes. Event Functions that use a customer-managed runtime cost the same as functions that use a Lambda-managed runtime. There’s no charge for creating runtime versions or aliases. However, runtime publishers must keep the container image for each runtime version in Amazon ECR for as long as the version exists. Standard Amazon ECR storage pricing applies to these images.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;With customer-managed runtimes, platform teams have central control over the Lambda runtimes used across their organization. As runtime publishers, they control the runtime contents, updates, access, and lifecycle. Alternatively, they can publish base images that application teams use to build and manage their own runtimes. Developers keep the .zip deployment experience they’re familiar with and receive runtime updates automatically.&lt;/p&gt; 
&lt;p&gt;To get started, visit the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/runtimes-customer-managed.html" target="_blank" rel="noopener"&gt;customer-managed runtimes documentation&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/runtimes-custom-managed-tutorial.html" target="_blank" rel="noopener"&gt;step-by-step tutorial&lt;/a&gt;. Customer-managed runtimes are available today across commercial AWS Regions through the Lambda console, AWS Command Line Interface, and AWS CloudFormation.&lt;/p&gt; 
&lt;p&gt;We would love to hear how you use customer-managed runtimes. Share your feedback in the comments, in the &lt;a href="https://github.com/aws/aws-lambda-roadmap/issues/54" target="_blank" rel="noopener"&gt;Lambda public roadmap&lt;/a&gt;, or reach out through &lt;a href="https://repost.aws/" target="_blank" rel="noopener"&gt;AWS re:Post&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the author&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/16/ComputeBlog-2832-4.jpg" alt="Jonathan Tuliani" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Jonathan Tuliani&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Jonathan is a Principal Product Manager for AWS Lambda in Amazon Web Services, where he leads product strategy for runtimes and programming models. He is passionate about serverless computing, having previously delivered systems on cloud, virtualized, and bare-metal infrastructure.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Securing REST APIs with JWT authorizers in Amazon API Gateway</title>
		<link>https://aws.amazon.com/blogs/compute/securing-rest-apis-with-jwt-authorizers-in-amazon-api-gateway/</link>
		
		<dc:creator><![CDATA[Giedrius Praspaliauskas]]></dc:creator>
		<pubDate>Tue, 17 Nov 2026 18:39:16 +0000</pubDate>
				<category><![CDATA[Amazon API Gateway]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<guid isPermaLink="false">5e0b583c60e6e1200437358ec5bb9a461c32397f</guid>

					<description>Amazon API Gateway REST APIs now support JWT authorizers, which validate tokens from any OIDC-compatible identity provider in API Gateway itself, with no Lambda authorizer required. Learn how JWT authorizers work, then build a REST API that accepts machine-to-machine tokens with per-method scopes and adds an Amazon Cognito user pool as a second issuer.</description>
										<content:encoded>&lt;p&gt;Many teams already run an OpenID Connect (OIDC) identity provider and want their &lt;a href="https://aws.amazon.com/api-gateway/" target="_blank" rel="noopener"&gt;Amazon API Gateway&lt;/a&gt; REST APIs to accept its security tokens. Until now, the built-in authorizer for API Gateway REST APIs accepted only Amazon Cognito tokens. For other identity providers, you wrote an &lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener"&gt;AWS Lambda&lt;/a&gt; authorizer that downloaded the provider’s signing keys, verified each token, and returned an &lt;a href="https://aws.amazon.com/iam/" target="_blank" rel="noopener"&gt;AWS Identity and Access Management (IAM)&lt;/a&gt; policy.&lt;/p&gt; 
&lt;p&gt;Today, AWS announced JSON Web Token (JWT) authorizers for API Gateway REST APIs, which validate tokens in API Gateway itself. You declare the issuers you trust, the audiences you accept from each, the signing algorithms you permit, and any additional claims you require the token to carry. JWT authorizers work on Regional, edge-optimized, and private REST APIs.&lt;/p&gt; 
&lt;p&gt;In this post, you learn how JWT authorizers work. You then build a REST API that accepts machine-to-machine tokens from your own identity provider and enforces different scopes on read and write operations. Finally, you add an Amazon Cognito user pool as a second trusted issuer on the same authorizer.&lt;/p&gt; 
&lt;h2 id="solution-overview"&gt;Solution overview&lt;/h2&gt; 
&lt;p&gt;Lambda authorizers remain the right choice when authorization needs custom logic, token introspection, or credentials that are not JWTs. For token validation alone, a JWT authorizer validates the token in API Gateway itself, with no function to maintain and no invocation in the request path, as the following diagram shows.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/ComputeBlog-2825-1-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/ComputeBlog-2825-1-1.png" alt="A client calls API Gateway, which validates the token and passes only authorized requests to the backend integration." width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: New architecture. API Gateway validates the token inline and forwards only authorized requests to the integration&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Each request goes through the following steps:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;The client sends a security token as a bearer token in the header that the identity source names, typically &lt;code&gt;Authorization&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;API Gateway matches the token’s &lt;code&gt;iss&lt;/code&gt; claim to a configured issuer and rejects a token from an unknown issuer before any network call.&lt;/li&gt; 
 &lt;li&gt;API Gateway checks that the token’s signing algorithm is one you configured, then validates the signature against the issuer’s public keys, which it locates through OIDC discovery and caches.&lt;/li&gt; 
 &lt;li&gt;API Gateway checks the audience and the expiry and not-before times.&lt;/li&gt; 
 &lt;li&gt;If the method requires authorization scopes, you must use an access token that carries at least one of them in its &lt;code&gt;scope&lt;/code&gt; or &lt;code&gt;scp&lt;/code&gt; claim.&lt;/li&gt; 
 &lt;li&gt;API Gateway checks any additional claim rules you configured for that issuer.&lt;/li&gt; 
 &lt;li&gt;API Gateway passes the validated claims to the integration, and the request proceeds.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;API Gateway stops processing the request at the first failed check. API Gateway returns &lt;code&gt;401 Unauthorized&lt;/code&gt; for a missing, malformed, expired, or untrusted token. It returns &lt;code&gt;403 Forbidden&lt;/code&gt; for a valid token that lacks a required scope or fails a claim rule. If API Gateway cannot reach an issuer’s key endpoint and has no cached keys, it returns a &lt;code&gt;5xx&lt;/code&gt; response rather than letting the request through.&lt;/p&gt; 
&lt;h2 id="walkthrough"&gt;Walkthrough&lt;/h2&gt; 
&lt;p&gt;In this walkthrough, you create an &lt;code&gt;orders&lt;/code&gt; REST API in which &lt;code&gt;GET /orders&lt;/code&gt; requires the &lt;code&gt;orders:read&lt;/code&gt; scope and &lt;code&gt;POST /orders&lt;/code&gt; requires &lt;code&gt;orders:write&lt;/code&gt;.&lt;/p&gt; 
&lt;h3 id="prerequisites"&gt;Prerequisites&lt;/h3&gt; 
&lt;p&gt;To follow this walkthrough, you need:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;An AWS account and an IAM principal with permissions to manage API Gateway resources, and &lt;a href="https://aws.amazon.com/cognito/" target="_blank" rel="noopener"&gt;Amazon Cognito&lt;/a&gt; resources for step 7. Follow the principle of least privilege.&lt;/li&gt; 
 &lt;li&gt;An OIDC-compatible identity provider that supports the OAuth 2.0 client credentials flow and publishes a discovery document at &lt;code&gt;/.well-known/openid-configuration&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;The latest version of the &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;curl&lt;/code&gt; and &lt;code&gt;jq&lt;/code&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="step-1-prepare-your-identity-provider"&gt;Step 1: Prepare your identity provider&lt;/h3&gt; 
&lt;p&gt;In your identity provider, create an API (or resource server) for the orders service with two scopes, &lt;code&gt;orders:read&lt;/code&gt; and &lt;code&gt;orders:write&lt;/code&gt;. Then create two machine-to-machine applications: a reporting application with only &lt;code&gt;orders:read&lt;/code&gt; and a fulfillment application with both scopes.&lt;/p&gt; 
&lt;p&gt;Then collect the following values, shown here for three common providers.&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Value&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Okta&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Auth0&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Microsoft Entra ID&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;code&gt;ISSUER&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;https://{yourOktaDomain}/oauth2/default&lt;/code&gt; for the default custom authorization server&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;https://{yourTenant}.auth0.com/&lt;/code&gt;, including the trailing slash. &lt;em&gt;Note that URL might include country code.&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;https://login.microsoftonline.com/{tenantId}/v2.0&lt;/code&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;code&gt;AUDIENCE&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;The authorization server’s &lt;strong&gt;Audience&lt;/strong&gt;, for example &lt;code&gt;api://default&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;The &lt;strong&gt;API Identifier&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;The application ID URI or client ID of the API app registration&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;code&gt;TOKEN_URL&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;{ISSUER}/v1/token&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;https://{yourTenant}.auth0.com/oauth/token&lt;/code&gt; &lt;em&gt;Note that URL might include country code.&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;https://login.microsoftonline.com/{tenantId}/oauth2/v2.0/token&lt;/code&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Scopes&lt;/td&gt; 
   &lt;td&gt;Custom scopes on the authorization server&lt;/td&gt; 
   &lt;td&gt;Permissions on the API, granted to each application&lt;/td&gt; 
   &lt;td&gt;See Considerations. Client credentials tokens carry app roles, not scopes.&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;For the example walkthrough, set the values as environment variables (production clients can load client secrets from &lt;a href="https://aws.amazon.com/secrets-manager/" target="_blank" rel="noopener"&gt;AWS Secrets Manager&lt;/a&gt; or an equivalent store).&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;REGION=&amp;lt;your AWS Region, for example us-east-1&amp;gt;
ISSUER=&amp;lt;issuer URL, exactly as it appears in the token's iss claim&amp;gt;
AUDIENCE=&amp;lt;audience value&amp;gt;
TOKEN_URL=&amp;lt;token endpoint&amp;gt;
READER_ID=&amp;lt;reporting application client ID&amp;gt;
READER_SECRET=&amp;lt;reporting application client secret&amp;gt;
WRITER_ID=&amp;lt;fulfillment application client ID&amp;gt;
WRITER_SECRET=&amp;lt;fulfillment application client secret&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The issuer must match the token’s &lt;code&gt;iss&lt;/code&gt; claim exactly, including any trailing slash, so copy it from a decoded token.&lt;/p&gt; 
&lt;h3 id="step-2-create-the-jwt-authorizer"&gt;Step 2: Create the JWT authorizer&lt;/h3&gt; 
&lt;p&gt;Create a REST API, then describe the authorizer in a file that lists the trusted issuers, the audiences accepted from each, and the signing algorithms you configure on your issuer:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;API_ID=$(aws apigateway create-rest-api \
  --name orders \
  --region "$REGION" \
  --query 'id' --output text)

cat &amp;gt; jwt-config.json &amp;lt;&amp;lt;EOF
{
  "issuers": [
    {
      "issuer": "${ISSUER}",
      "audiences": ["${AUDIENCE}"]
    }
  ],
  "defaultAlgorithms": ["RS256"]
}
EOF

AUTHORIZER_ID=$(aws apigateway create-authorizer \
  --rest-api-id "$API_ID" \
  --name orders-jwt \
  --type JWT \
  --identity-source method.request.header.Authorization \
  --jwt-configuration file://jwt-config.json \
  --region "$REGION" \
  --query 'id' --output text)&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;When you create or update the authorizer, API Gateway reads each issuer’s discovery document and checks that its &lt;code&gt;issuer&lt;/code&gt; value matches. If your provider signs with an elliptic curve key, add &lt;code&gt;ES256&lt;/code&gt; or another supported algorithm to &lt;code&gt;defaultAlgorithms&lt;/code&gt;. Keep &lt;code&gt;jwt-config.json&lt;/code&gt; for step 7.&lt;/p&gt; 
&lt;h3 id="step-3-attach-the-authorizer-to-methods-with-different-scopes"&gt;Step 3: Attach the authorizer to methods with different scopes&lt;/h3&gt; 
&lt;p&gt;Create the &lt;code&gt;/orders&lt;/code&gt; resource and two methods that share the authorizer but require different scopes. A mock integration returns the issuer and subject from the validated token:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;ROOT_ID=$(aws apigateway get-resources --rest-api-id "$API_ID" \
  --region "$REGION" --query 'items[?path==`/`].id' --output text)

RESOURCE_ID=$(aws apigateway create-resource --rest-api-id "$API_ID" \
  --parent-id "$ROOT_ID" --path-part orders \
  --region "$REGION" --query 'id' --output text)

add_method () {
  aws apigateway put-method --rest-api-id "$API_ID" --resource-id "$RESOURCE_ID" \
    --http-method "$1" \
    --authorization-type JWT \
    --authorizer-id "$AUTHORIZER_ID" \
    --authorization-scopes "$2" \
    --region "$REGION"

  aws apigateway put-integration --rest-api-id "$API_ID" --resource-id "$RESOURCE_ID" \
    --http-method "$1" --type MOCK \
    --request-templates '{"application/json":"{\"statusCode\": 200}"}' \
    --region "$REGION"

  aws apigateway put-method-response --rest-api-id "$API_ID" --resource-id "$RESOURCE_ID" \
    --http-method "$1" --status-code 200 --region "$REGION"

  aws apigateway put-integration-response --rest-api-id "$API_ID" --resource-id "$RESOURCE_ID" \
    --http-method "$1" --status-code 200 \
    --response-templates '{"application/json":"{\"issuer\":\"$context.authorizer.claims.iss\",\"subject\":\"$context.authorizer.claims.sub\"}"}' \
    --region "$REGION"
}

add_method GET  orders:read
add_method POST orders:write&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="step-4-deploy-the-api"&gt;Step 4: Deploy the API&lt;/h3&gt; 
&lt;p&gt;Deploy the API to a stage named &lt;code&gt;test&lt;/code&gt; and record the invoke URL:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws apigateway create-deployment --rest-api-id "$API_ID" \
  --stage-name test --region "$REGION"

API_URL="https://${API_ID}.execute-api.${REGION}.amazonaws.com/test/orders"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="step-5-test-the-failure-cases-first"&gt;Step 5: Test the failure cases first&lt;/h3&gt; 
&lt;p&gt;Call the API without a token:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;curl -s -o /dev/null -w "%{http_code}\n" "$API_URL"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The request returns &lt;code&gt;401&lt;/code&gt;, because API Gateway rejects it before the integration runs.&lt;/p&gt; 
&lt;p&gt;Next, use a token for the reporting application, which has only &lt;code&gt;orders:read&lt;/code&gt;, to create an order. The &lt;code&gt;get_token&lt;/code&gt; helper sends an OAuth 2.0 client credentials request:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;get_token () {
   local url="$1" client_id="$2" client_secret="$3" scope="$4" audience="$5"
   local args=(
      -sS -X POST "$url"
      -u "$client_id:$client_secret"
      -H "Content-Type: application/x-www-form-urlencoded"
      --data-urlencode "grant_type=client_credentials"
    )
   [[ -n "$scope"    ]] &amp;amp;&amp;amp; args+=(--data-urlencode "scope=$scope")
   [[ -n "$audience" ]] &amp;amp;&amp;amp; args+=(--data-urlencode "audience=$audience")

   curl "${args[@]}" | jq -r .access_token
}

# Auth0 requires the audience parameter. Okta ignores it.
READER_TOKEN=$(get_token "$TOKEN_URL" "$READER_ID" "$READER_SECRET" "orders:read" "$AUDIENCE")

curl -s -o /dev/null -w "%{http_code}\n" -X POST \
  -H "Authorization: Bearer $READER_TOKEN" "$API_URL"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The request returns &lt;code&gt;403&lt;/code&gt;. The token is valid, but &lt;code&gt;POST /orders&lt;/code&gt; requires &lt;code&gt;orders:write&lt;/code&gt;.&lt;/p&gt; 
&lt;h3 id="step-6-test-the-successful-cases"&gt;Step 6: Test the successful cases&lt;/h3&gt; 
&lt;p&gt;Read orders with the reporting token, then request a token for the fulfillment application and create an order:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;curl -s -H "Authorization: Bearer $READER_TOKEN" "$API_URL"

WRITER_TOKEN=$(get_token "$TOKEN_URL" "$WRITER_ID" "$WRITER_SECRET" "orders:write" "$AUDIENCE")
curl -s -X POST -H "Authorization: Bearer $WRITER_TOKEN" "$API_URL"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Both calls return &lt;code&gt;200&lt;/code&gt; with the issuer and subject that the integration received:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{"issuer":"https://example.us.auth0.com/","subject":"0oa1b2c3d4EXAMPLE"}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="step-7-add-amazon-cognito-as-a-second-issuer"&gt;Step 7: Add Amazon Cognito as a second issuer&lt;/h3&gt; 
&lt;p&gt;An authorizer can trust up to 10 issuers, for example while you migrate between identity providers. In this step, you add a Cognito user pool to the same authorizer.&lt;/p&gt; 
&lt;p&gt;Create a user pool, a domain for its token endpoint, a resource server with the two scopes, and one machine-to-machine client:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;DOMAIN_PREFIX=&amp;lt;a globally unique prefix, for example orders-demo-1234&amp;gt;

POOL_ID=$(aws cognito-idp create-user-pool --pool-name orders-demo \
  --region "$REGION" --query 'UserPool.Id' --output text)

aws cognito-idp create-user-pool-domain --user-pool-id "$POOL_ID" \
  --domain "$DOMAIN_PREFIX" --region "$REGION"

aws cognito-idp create-resource-server --user-pool-id "$POOL_ID" \
  --identifier orders --name orders \
  --scopes ScopeName=orders:read,ScopeDescription="Read orders" \
           ScopeName=orders:write,ScopeDescription="Create orders" \
  --region "$REGION"

read -r COGNITO_ID COGNITO_SECRET &amp;lt;&amp;lt;&amp;lt; "$(aws cognito-idp create-user-pool-client \
  --user-pool-id "$POOL_ID" --client-name legacy-reporting --generate-secret \
  --allowed-o-auth-flows client_credentials --allowed-o-auth-flows-user-pool-client \
  --allowed-o-auth-scopes orders/orders:read \
  --region "$REGION" \
  --query 'UserPoolClient.[ClientId,ClientSecret]' --output text)"

COGNITO_ISSUER="https://cognito-idp.${REGION}.amazonaws.com/${POOL_ID}"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Add the user pool to &lt;code&gt;jwt-config.json&lt;/code&gt; and send the full file back, because an update replaces the whole configuration. Cognito access tokens carry the app client ID in &lt;code&gt;client_id&lt;/code&gt; rather than &lt;code&gt;aud&lt;/code&gt;, so use the client ID as the audience:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;jq --arg iss "$COGNITO_ISSUER" --arg aud "$COGNITO_ID" \
  '.issuers += [{issuer: $iss, audiences: [$aud]}]' \
  jwt-config.json &amp;gt; jwt-config.tmp &amp;amp;&amp;amp; mv jwt-config.tmp jwt-config.json

aws apigateway update-authorizer \
  --rest-api-id "$API_ID" \
  --authorizer-id "$AUTHORIZER_ID" \
  --patch-operations "$(jq -n --rawfile v jwt-config.json \
      '[{op:"replace",path:"/jwtConfiguration",value:$v}]')" \
  --region "$REGION"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The following screenshot shows the updated authorizer in the API Gateway console, with the key set that API Gateway resolved for each issuer.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/ComputeBlog-2825-2-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/ComputeBlog-2825-2-1.png" alt="API Gateway console authorizer page listing two trusted issuers with the key set resolved for each." width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: JWT authorizer with two trusted issuers&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;If you no longer have the &lt;code&gt;jwt-config.json&lt;/code&gt; file, rebuild it from &lt;code&gt;get-authorizer&lt;/code&gt; and remove the &lt;code&gt;jwksUri&lt;/code&gt; fields, because API Gateway rejects an update that includes them:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws apigateway get-authorizer --rest-api-id "$API_ID" --authorizer-id "$AUTHORIZER_ID" \
  --query jwtConfiguration --output json --region "$REGION" \
  | jq 'del(.issuers[].jwksUri)' &amp;gt; jwt-config.json&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Cognito names scopes &lt;code&gt;{resource server}/{scope}&lt;/code&gt;, so its token carries &lt;code&gt;orders/orders:read&lt;/code&gt; rather than &lt;code&gt;orders:read&lt;/code&gt;. Add that form to &lt;code&gt;GET /orders&lt;/code&gt;, then redeploy, because authorizer and method changes take effect only in a new deployment:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws apigateway update-method --rest-api-id "$API_ID" --resource-id "$RESOURCE_ID" \
  --http-method GET \
  --patch-operations op=add,path=/authorizationScopes,value=orders/orders:read \
  --region "$REGION"

aws apigateway create-deployment --rest-api-id "$API_ID" \
  --stage-name test --region "$REGION"

COGNITO_TOKEN=$(get_token "https://${DOMAIN_PREFIX}.auth.${REGION}.amazoncognito.com/oauth2/token" \
  "$COGNITO_ID" "$COGNITO_SECRET" "orders/orders:read")

curl -s -H "Authorization: Bearer $COGNITO_TOKEN" "$API_URL"&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The request returns &lt;code&gt;200&lt;/code&gt; with the Cognito issuer, and tokens from your original provider keep working. For Cognito issuers, a method with scopes accepts only access tokens and a method without scopes accepts only ID tokens. Give each method that client credentials callers use at least one scope.&lt;/p&gt; 
&lt;p&gt;To finish a migration, remove the retired issuer from &lt;code&gt;jwt-config.json&lt;/code&gt;, send the same &lt;code&gt;replace&lt;/code&gt; operation (using &lt;code&gt;aws apigateway update-authorizer --patch-operations&lt;/code&gt; command), and redeploy.&lt;/p&gt; 
&lt;h3 id="optional-require-an-additional-claim"&gt;Optional: Require an additional claim&lt;/h3&gt; 
&lt;p&gt;To accept only tokens whose &lt;code&gt;department&lt;/code&gt; claim equals &lt;code&gt;eng&lt;/code&gt;, add a claim rule to the issuer entry. Matching is exact and case-sensitive, and API Gateway returns a &lt;code&gt;403&lt;/code&gt; for other tokens:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
  "issuer": "https://example.auth0.com/",
  "audiences": ["api://default"],
  "additionalClaims": [
    { "claimName": "department", "format": "SINGLE_STRING", "required": true, "expectedValues": ["eng"] }
  ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="defining-jwt-authorizers-as-infrastructure-as-code"&gt;Defining JWT authorizers as infrastructure as code&lt;/h2&gt; 
&lt;p&gt;In &lt;a href="https://aws.amazon.com/cloudformation/" target="_blank" rel="noopener"&gt;AWS CloudFormation&lt;/a&gt;, the &lt;code&gt;AWS::ApiGateway::Authorizer&lt;/code&gt; resource has a &lt;code&gt;JwtConfiguration&lt;/code&gt; property that mirrors the API, and methods set &lt;code&gt;AuthorizationType: JWT&lt;/code&gt; and &lt;code&gt;AuthorizationScopes&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;Parameters:
  IdpIssuer:
    Type: String
    Description: Issuer URL exactly as it appears in the token's iss claim
  IdpAudience:
    Type: String

Resources:
  OrdersAuthorizer:
    Type: AWS::ApiGateway::Authorizer
    Properties:
      RestApiId: !Ref OrdersApi
      Name: orders-jwt
      Type: JWT
      IdentitySource: method.request.header.Authorization
      JwtConfiguration:
        DefaultAlgorithms: [RS256]
        Issuers:
          - Issuer: !Ref IdpIssuer
            Audiences: [!Ref IdpAudience]

  GetOrders:
    Type: AWS::ApiGateway::Method
    Properties:
      RestApiId: !Ref OrdersApi
      ResourceId: !Ref OrdersResource
      HttpMethod: GET
      AuthorizationType: JWT
      AuthorizerId: !GetAtt OrdersAuthorizer.AuthorizerId
      AuthorizationScopes: [orders:read]
      Integration:
        Type: MOCK
        RequestTemplates:
          application/json: '{"statusCode": 200}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;In OpenAPI 3.0 and Swagger 2.0 definitions, use the &lt;code&gt;x-amazon-apigateway-authorizer&lt;/code&gt; extension with &lt;code&gt;type: jwt&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;components:
  securitySchemes:
    orders-jwt:
      type: apiKey
      name: Authorization
      in: header
      x-amazon-apigateway-authtype: jwt
      x-amazon-apigateway-authorizer:
        type: jwt
        jwtConfiguration:
          issuers:
            - issuer: https://example.auth0.com/
              audiences: [ "api://default" ]
            - issuer: https://login.microsoftonline.com/{tenantId}/v2.0
              audiences: [ "00000000-0000-0000-0000-000000000000" ]
          defaultAlgorithms: [ "RS256", "ES256" ]
paths:
  /orders:
    get:
      security:
        - orders-jwt: [ "orders:read" ]&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You can also convert an existing Lambda or Cognito authorizer in place with one &lt;code&gt;update-authorizer&lt;/code&gt; command that changes &lt;code&gt;/type&lt;/code&gt;, replaces &lt;code&gt;/jwtConfiguration&lt;/code&gt;, and clears the old type’s fields. Clear Lambda fields with a &lt;code&gt;replace&lt;/code&gt; that has no value, and remove each Cognito provider ARN with &lt;code&gt;remove&lt;/code&gt;. Then switch each method that uses the authorizer to &lt;code&gt;authorizationType: JWT&lt;/code&gt;, add its scopes, and redeploy.&lt;/p&gt; 
&lt;h2 id="using-claims-in-your-integration"&gt;Using claims in your integration&lt;/h2&gt; 
&lt;p&gt;API Gateway passes every JWT claim to your backend as JSON as it appeared in the token. Strings stay quoted and escaped, numbers stay numbers, and arrays and objects stay intact, so your backend never has to guess what was sent. Mapping templates read validated claims as &lt;code&gt;$context.authorizer.claims.name&lt;/code&gt;, as with Cognito authorizers, and Lambda proxy integrations receive them in &lt;code&gt;event.requestContext.authorizer.claims&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;HTTP proxy integrations don’t forward claims automatically, so map the ones you need to headers, for example &lt;code&gt;integration.request.header.x-caller&lt;/code&gt; to &lt;code&gt;context.authorizer.claims.sub&lt;/code&gt;.&lt;/p&gt; 
&lt;h2 id="observability-and-troubleshooting"&gt;Observability and troubleshooting&lt;/h2&gt; 
&lt;p&gt;When API Gateway rejects a request, the response body is &lt;code&gt;Unauthorized&lt;/code&gt; or &lt;code&gt;The incoming token has expired&lt;/code&gt; for a &lt;code&gt;401&lt;/code&gt;, and &lt;code&gt;Access Denied&lt;/code&gt; for a &lt;code&gt;403&lt;/code&gt;. A &lt;code&gt;WWW-Authenticate&lt;/code&gt; header that follows &lt;a href="https://www.rfc-editor.org/info/rfc6750/" target="_blank" rel="noopener"&gt;RFC 6750&lt;/a&gt; carries the details, such as the failed check or, for a missing scope, the scopes the method accepts.&lt;/p&gt; 
&lt;p&gt;With execution logging on, API Gateway logs a claims summary for each request, without the raw token. Data trace logging masks the &lt;code&gt;Authorization&lt;/code&gt; header but not custom headers, so if your identity source is a header such as &lt;code&gt;X-Token&lt;/code&gt;, keep data trace logging off for that stage.&lt;/p&gt; 
&lt;p&gt;To test an authorizer before you deploy, choose &lt;strong&gt;Test authorizer&lt;/strong&gt; on the authorizer page or run &lt;code&gt;test-invoke-authorizer&lt;/code&gt;. The test skips method scopes and accepts Cognito identity tokens, so call the deployed method to test scopes.&lt;/p&gt; 
&lt;h2 id="considerations"&gt;Considerations&lt;/h2&gt; 
&lt;p&gt;Before you add a JWT authorizer, consider the following:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;An authorizer trusts 1–10 issuers. Each issuer accepts 1–100 audiences and up to 10 additional claim rules, each with at most one expected value.&lt;/li&gt; 
 &lt;li&gt;Supported signing algorithms are RS256, RS384, RS512, ES256, ES384, and ES512, and API Gateway rejects HMAC and &lt;code&gt;alg: none&lt;/code&gt; tokens. The token header must carry a &lt;code&gt;kid&lt;/code&gt;, which some providers omit by default.&lt;/li&gt; 
 &lt;li&gt;API Gateway allows 60 seconds of clock skew when it checks &lt;code&gt;exp&lt;/code&gt;, &lt;code&gt;nbf&lt;/code&gt;, and &lt;code&gt;iat&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;API Gateway caches each issuer’s signing keys for about 60 minutes, so a key your provider removes can still verify tokens for that long. If the key endpoint is unavailable, API Gateway keeps using the last key set for up to 1 hour.&lt;/li&gt; 
 &lt;li&gt;A token passes a method’s scope check when its &lt;code&gt;scope&lt;/code&gt; or &lt;code&gt;scp&lt;/code&gt; claim carries one of the method’s scopes. Microsoft Entra ID client credentials tokens carry permissions in &lt;code&gt;roles&lt;/code&gt; instead, so use a dedicated audience per caller or a Lambda authorizer for role checks.&lt;/li&gt; 
 &lt;li&gt;An authorizer reads the token from a single request header.&lt;/li&gt; 
 &lt;li&gt;JWT authorizers don’t check revocation, so a token stays valid until it expires. Use short token lifetimes for sensitive operations.&lt;/li&gt; 
 &lt;li&gt;The issuer URL must be publicly accessible.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="clean-up"&gt;Clean up&lt;/h2&gt; 
&lt;p&gt;To avoid incurring future charges, delete the resources you created:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws apigateway delete-rest-api --rest-api-id "$API_ID" --region "$REGION"

aws cognito-idp delete-user-pool-domain --user-pool-id "$POOL_ID" \
  --domain "$DOMAIN_PREFIX" --region "$REGION"

aws cognito-idp delete-user-pool --user-pool-id "$POOL_ID" --region "$REGION"

rm -f jwt-config.json&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;In your identity provider, delete the two applications and the orders API or resource server if you no longer need them.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;With JWT authorizers, you can validate tokens from OIDC-compatible identity providers in API Gateway REST APIs without a function in the request path. In this post, you built an API that accepted machine-to-machine tokens from your own provider, enforced separate read and write scopes, and added a Cognito user pool as a second issuer. Lambda authorizers remain the right tool for custom authorization logic. For token validation alone, we recommend the JWT authorizer.&lt;/p&gt; 
&lt;p&gt;JWT authorizers for REST APIs are available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions. To get started, refer to &lt;a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/rest-api-jwt-authorizer.html" target="_blank" rel="noopener"&gt;Controlling access to a REST API using JWT authorizers&lt;/a&gt; in the Amazon API Gateway Developer Guide. To learn more about serverless architectures, visit &lt;a href="https://serverlessland.com/" target="_blank" rel="noopener"&gt;Serverless Land&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/ComputeBlog-2825-3-1.jpg" alt="Giedrius Praspaliauskas" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Giedrius Praspaliauskas&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Giedrius is a Specialist Solutions Architect at Amazon Web Services, focusing on helping customers modernize their infrastructure and adopt cloud-native architectures. He has extensive experience with API management, microservices, serverless, developer experience, and application modernization.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/ComputeBlog-2825-4-1.jpg" alt="Srijan Bhattacharya" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Srijan Bhattacharya&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Srijan Bhattacharya is a Senior Product Manager – Technical at AWS on the Amazon API Gateway team, based in Toronto. He works with customers to shape features across API security, observability, traffic management, integrations, and extensibility.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Per-customer invoice management with Amazon EventBridge Scheduler</title>
		<link>https://aws.amazon.com/blogs/compute/per-customer-invoice-management-with-amazon-eventbridge-scheduler/</link>
		
		<dc:creator><![CDATA[Rana Kiziltoprak German]]></dc:creator>
		<pubDate>Thu, 12 Nov 2026 20:26:38 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EventBridge]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">30e239de52fd594fe04cacdb96d4cacfb26a9b81</guid>

					<description>Many SaaS platforms bill each customer on their own cycle from their signup date, which turns into millions of precisely timed invoice and reminder events. Learn how to use Amazon EventBridge Scheduler as the time-aware backbone of a per-customer billing system, with recurring invoice schedules, one-time reminders, and no scheduling infrastructure to run.</description>
										<content:encoded>&lt;p&gt;Many software as a service (SaaS) platforms need to bill each customer on their unique billing cycle, based on the date they signed up. This creates a complex scheduling problem: an individually timed invoice generation event per customer, each followed by precisely timed payment reminders. On a large platform, that adds up to millions of events.&lt;/p&gt; 
&lt;p&gt;In this post, we show you how to use &lt;a href="https://docs.aws.amazon.com/scheduler/latest/UserGuide/what-is-scheduler.html" target="_blank" rel="noopener"&gt;Amazon EventBridge Scheduler&lt;/a&gt; as the time-aware backbone of a per-customer billing system. You learn how to create recurring schedules for invoice generation, spawn one-time schedules for payment reminders, and manage the full customer billing lifecycle, all without building or operating scheduling infrastructure.&lt;/p&gt; 
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt; 
&lt;p&gt;This solution uses the following AWS services:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/scheduler/latest/UserGuide/what-is-scheduler.html" target="_blank" rel="noopener"&gt;Amazon EventBridge Scheduler&lt;/a&gt;: Manages the per-customer recurring and one-time schedules.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/welcome.html" target="_blank" rel="noopener"&gt;AWS Lambda&lt;/a&gt;: Runs the invoice generation and reminder logic.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/ses/latest/dg/Welcome.html" target="_blank" rel="noopener"&gt;Amazon Simple Email Service (Amazon SES)&lt;/a&gt;: Sends the invoice and reminder email.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html" target="_blank" rel="noopener"&gt;Amazon DynamoDB&lt;/a&gt;: Stores the reminder log that makes reminder delivery idempotent.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html" target="_blank" rel="noopener"&gt;Amazon Simple Queue Service (Amazon SQS)&lt;/a&gt;: Provides the dead-letter queue for failed invocations.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt; 
&lt;p&gt;To follow along with this post, you need:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;An &lt;a href="https://signup.aws.amazon.com/billing/signup" target="_blank" rel="noopener"&gt;AWS account&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;The &lt;a href="https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html" target="_blank" rel="noopener"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt; configured with appropriate credentials.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://www.python.org/downloads/" target="_blank" rel="noopener"&gt;Python 3.12 or later&lt;/a&gt; with &lt;a href="https://boto3.amazonaws.com/v1/documentation/api/latest/index.html" target="_blank" rel="noopener"&gt;Boto3&lt;/a&gt;. Python 3.9 has reached end of support as a Lambda runtime, so use a current runtime for new functions.&lt;/li&gt; 
 &lt;li&gt;An AWS Identity and Access Management (IAM) role with permissions to create Amazon EventBridge Scheduler schedules and invoke Lambda functions.&lt;/li&gt; 
 &lt;li&gt;A DynamoDB table named &lt;code&gt;billing-reminder-log&lt;/code&gt; with &lt;code&gt;idempotency_key&lt;/code&gt; as its partition key, and time to live (TTL) enabled on the &lt;code&gt;ttl&lt;/code&gt; attribute so that old reminder records expire on their own.&lt;/li&gt; 
 &lt;li&gt;A &lt;a href="https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html" target="_blank" rel="noopener"&gt;verified sending identity&lt;/a&gt; in Amazon SES. If your account is still in the SES sandbox, request production access before you send to arbitrary customer addresses, because the sandbox only allows sending to verified addresses.&lt;/li&gt; 
 &lt;li&gt;An SQS queue to use as the dead-letter queue for failed schedule invocations.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt; 
&lt;p&gt;You run a SaaS platform. Each customer signs up on a different day, and their billing cycle starts from that signup date. Customer A signed up on March 3, so they get invoiced on the 3rd of every month. Customer B signed up on the 17th, and they get invoiced on the 17th. You have 500,000 customers, each with their own billing anchor date.&lt;/p&gt; 
&lt;p&gt;Now layer on payment reminders: 7 days before the invoice is due, 3 days before, and the day it is due. That is four scheduled actions per customer per billing cycle, which comes to millions of events every month.&lt;/p&gt; 
&lt;p&gt;How do you build this?&lt;/p&gt; 
&lt;h3 id="the-traditional-approach-and-why-it-breaks"&gt;The traditional approach (and why it breaks)&lt;/h3&gt; 
&lt;p&gt;Most teams consider one of these patterns:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;&lt;strong&gt;A cron job that scans the database every hour&lt;/strong&gt;: Query all customers, check whether anyone is due for an invoice or a reminder, and process them. This works at small scale but becomes a bottleneck fast. The job takes longer as your customer base grows. If it crashes mid-run, you miss invoices. If it runs slowly, reminders arrive late.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;A queue with delayed messages&lt;/strong&gt;: An appealing idea at first glance, but Amazon SQS caps &lt;code&gt;DelaySeconds&lt;/code&gt; at 15 minutes (900 seconds), which rules it out for billing events scheduled days or weeks ahead.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;Both approaches share the same drawback: you are building and operating scheduling infrastructure instead of focusing on your billing product.&lt;/p&gt; 
&lt;h2 id="the-building-block-amazon-eventbridge-scheduler"&gt;The building block: Amazon EventBridge Scheduler&lt;/h2&gt; 
&lt;p&gt;Amazon EventBridge Scheduler is purpose-built for this problem. It is a fully managed scheduling service that handles billions of one-time and recurring invocations. You create a schedule, tell it when to fire and what to invoke, and walk away. There is no infrastructure to manage, no polling, and no worker fleets.&lt;/p&gt; 
&lt;p&gt;For per-customer billing, Scheduler becomes the time-aware backbone of your invoicing system:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Each customer gets their own recurring schedule for invoice generation.&lt;/li&gt; 
 &lt;li&gt;Each billing cycle spawns one-time schedules for payment reminders.&lt;/li&gt; 
 &lt;li&gt;Scheduler handles the timing, and your application handles the business logic.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="architecture"&gt;Architecture&lt;/h2&gt; 
&lt;p&gt;The following diagram shows the end-to-end flow, from customer signup through invoice generation and payment reminders.&lt;/p&gt; 
&lt;p&gt;At signup, the application creates a recurring monthly schedule for the customer’s signup day. On each billing day, this schedule invokes the invoice generation Lambda function. The function sends the invoice through Amazon SES and sets up three one-time payment reminders: 7 days before the due date, 3 days before, and on the due date. Each reminder invokes the Send Payment Reminder Lambda function, which notifies the customer only if the invoice is still unpaid. When a payment arrives, a separate handler deletes any outstanding reminders so no further messages go out.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/12/ComputeBlog-2711-1-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/12/ComputeBlog-2711-1-1.png" alt="Architecture diagram showing customer signup creating a recurring invoice schedule, which invokes the invoice generation Lambda function, which creates one-time reminder schedules that invoke the payment reminder Lambda function and send email through Amazon SES." width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Invoice generation and payment reminders with Amazon EventBridge Scheduler&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="implementation"&gt;Implementation&lt;/h2&gt; 
&lt;p&gt;The complete implementation is available in the &lt;a href="https://github.com/aws-samples/sample-per-customer-invoice-generation-and-payment-reminders-with-amazon-eventbridge-scheduler" target="_blank" rel="noopener"&gt;accompanying GitHub repository&lt;/a&gt;. The AWS Serverless Application Model (AWS SAM) template provisions the DynamoDB tables, SQS dead-letter queue, Amazon EventBridge Scheduler groups, AWS Key Management Service (AWS KMS) key, and AWS Lambda functions described in this section. The rest of this section walks through the design of each component.&lt;/p&gt; 
&lt;h3 id="step-1-create-schedule-groups"&gt;Step 1: Create schedule groups&lt;/h3&gt; 
&lt;p&gt;Before creating any schedules, make sure the schedule groups exist. The sample declares them in the AWS SAM template so they are provisioned once at stack deploy time.&lt;/p&gt; 
&lt;h3 id="step-2-create-a-recurring-invoice-schedule-at-signup"&gt;Step 2: Create a recurring invoice schedule at signup&lt;/h3&gt; 
&lt;p&gt;When a customer signs up, the signup handler creates a recurring schedule based on their signup date. For customers who sign up on the 29th, 30th, or 31st, the sample clamps the billing day to the last day of each month using the &lt;code&gt;L&lt;/code&gt; cron special character, so no customer is skipped in February or in 30-day months. The handler is idempotent: if the schedule already exists (for example, after a retry), it updates the schedule instead of failing.&lt;/p&gt; 
&lt;h3 id="step-3-generate-the-invoice-and-schedule-reminders"&gt;Step 3: Generate the invoice and schedule reminders&lt;/h3&gt; 
&lt;p&gt;The invoice generation Lambda function, &lt;code&gt;GenerateInvoice&lt;/code&gt;, does the billing work and then creates one-time schedules for the payment reminders. It includes an idempotency check to prevent duplicate invoices if Scheduler delivers the event more than once.&lt;/p&gt; 
&lt;h3 id="step-4-send-reminders-with-idempotency"&gt;Step 4: Send reminders with idempotency&lt;/h3&gt; 
&lt;p&gt;The reminder Lambda function, &lt;code&gt;SendPaymentReminder&lt;/code&gt;, checks whether the invoice is still outstanding and whether this specific reminder was already sent, which prevents duplicate reminders on retry.&lt;/p&gt; 
&lt;h3 id="step-5-cancel-reminders-on-payment-event-driven"&gt;Step 5: Cancel reminders on payment (event-driven)&lt;/h3&gt; 
&lt;p&gt;Instead of checking payment status only when a reminder fires, a payment handler cancels outstanding reminders immediately when a payment is received. Your payment processing system triggers this handler (for example, through an Amazon EventBridge event or an SQS message from your payment gateway).&lt;/p&gt; 
&lt;h3 id="step-6-handle-customer-lifecycle-changes"&gt;Step 6: Handle customer lifecycle changes&lt;/h3&gt; 
&lt;p&gt;When a customer cancels, upgrades, or changes their billing cycle, update or delete their schedule accordingly. One thing to be careful of: &lt;code&gt;UpdateSchedule&lt;/code&gt; replaces the entire schedule configuration rather than merging changes, so any field you leave out is lost. Always read the existing schedule first, then apply your changes and write it back in full.&lt;/p&gt; 
&lt;h2 id="why-scheduler-is-the-right-building-block"&gt;Why Scheduler is the right building block&lt;/h2&gt; 
&lt;p&gt;The following table compares the do-it-yourself (DIY) approach with Amazon EventBridge Scheduler for each operational concern.&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Concern&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;DIY Approach&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;With Scheduler&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Per-customer timing&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Complex database queries to find who is due&lt;/td&gt; 
   &lt;td&gt;Each customer has their own schedule, so no queries are needed&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Reminder precision&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Polling interval determines accuracy&lt;/td&gt; 
   &lt;td&gt;Fires at the minute you specify, within the flexible time window you configure&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Scale&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;More customers = more polling load, more workers&lt;/td&gt; 
   &lt;td&gt;Scheduler handles millions of schedules natively&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Missed executions&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Crashed cron host = missed invoices&lt;/td&gt; 
   &lt;td&gt;Fully managed, built-in retries with a dead-letter queue&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Early payment&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Reminders fire anyway, or you build cancellation logic into your poller&lt;/td&gt; 
   &lt;td&gt;Delete the schedule and it does not fire&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Lifecycle changes&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Update database records, hope the poller picks up the change&lt;/td&gt; 
   &lt;td&gt;Update or delete the schedule directly&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Operational overhead&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;Manage worker fleets, monitor queue depth, handle clock skew&lt;/td&gt; 
   &lt;td&gt;Zero infrastructure to manage&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;h2 id="operational-considerations"&gt;Operational considerations&lt;/h2&gt; 
&lt;p&gt;Before you run this design in production, consider the following operational factors.&lt;/p&gt; 
&lt;h3 id="schedule-groups-for-organization"&gt;Schedule groups for organization&lt;/h3&gt; 
&lt;p&gt;Use schedule groups to organize and manage schedules by function:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;code&gt;billing-invoices&lt;/code&gt;: All recurring invoice generation schedules.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;billing-reminders&lt;/code&gt;: All one-time payment reminder schedules.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;With schedule groups, you can tag a set of schedules for organization and access control, list schedules by category, and delete all schedules in a group if needed (for example, during testing).&lt;/p&gt; 
&lt;h3 id="quotas-and-request-rates-at-scale"&gt;Quotas and request rates at scale&lt;/h3&gt; 
&lt;p&gt;Service quotas matter once you move past a test account. One quota is the number of schedules. The default limit is 10 million schedules per account per Region, and it is adjustable through Service Quotas. The &lt;code&gt;CreateSchedule&lt;/code&gt; and &lt;code&gt;UpdateSchedule&lt;/code&gt; APIs also have request rate quotas, which matters if you backfill existing customers in a single migration. Spread that backfill over time if you do not need to backfill immediately.&lt;/p&gt; 
&lt;p&gt;Scheduler also throttles invocations, with a default of 500–1,000 transactions per second (TPS) depending on the Region and adjustable to tens of thousands of TPS. To deal with an invocation spike (for example, the majority of your customers having invoices due at the same time), we recommend using the Flexible Time Window feature. In this post, we use it to spread each burst over 15 minutes, which smooths the load on your downstream Lambda functions and on Amazon SES without changing what the customer sees on their invoice.&lt;/p&gt; 
&lt;h3 id="monitoring"&gt;Monitoring&lt;/h3&gt; 
&lt;p&gt;Monitor schedule health with Amazon CloudWatch metrics, and capture any failed invocations in a dead-letter queue.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;CloudWatch metrics&lt;/strong&gt;: Monitor &lt;code&gt;InvocationAttemptCount&lt;/code&gt;, &lt;code&gt;InvocationDroppedCount&lt;/code&gt;, &lt;code&gt;InvocationThrottleCount&lt;/code&gt;, and &lt;code&gt;TargetErrorCount&lt;/code&gt; per schedule group.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Dead-letter queue&lt;/strong&gt;: Configure a dead-letter queue on your schedules to capture failed invocations that exhaust retries, and alarm on the &lt;code&gt;InvocationsSentToDeadLetterCount&lt;/code&gt; metric so a failed delivery pages you instead of sitting silent in the queue.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Invoice audit trail&lt;/strong&gt;: Log every invoice generation and reminder send to an Amazon DynamoDB table or Amazon CloudWatch Logs for compliance.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="retry-policy"&gt;Retry policy&lt;/h3&gt; 
&lt;p&gt;The retry policy and dead-letter queue are applied to every schedule target the sample creates. This retries transient Lambda failures up to three times over 1 hour, and permanently failed invocations land in the SQS dead-letter queue for investigation.&lt;/p&gt; 
&lt;h3 id="cost-at-scale"&gt;Cost at scale&lt;/h3&gt; 
&lt;p&gt;Amazon EventBridge Scheduler pricing is based on invocations, and the AWS Free Tier covers 14 million invocations per month. The 500,000-customer example in this post generates four scheduled events per customer per month (one invoice and three reminders), which is 2 million invocations, so the scheduling layer costs nothing at that scale. Scale the same design to 10 million customers and you generate 40 million invocations per month, of which 26 million are billable at $1.00 per million, so the scheduling layer costs roughly $26 per month.&lt;/p&gt; 
&lt;p&gt;The costs that grow with this design sit in the targets rather than in the scheduling:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;AWS Lambda charges for each invocation and its duration.&lt;/li&gt; 
 &lt;li&gt;Amazon SES charges per email, so the three reminders per customer per cycle are the largest line item in this workload.&lt;/li&gt; 
 &lt;li&gt;Amazon DynamoDB charges for the reminder log writes and reads, which the TTL setting keeps from accumulating.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Check the pricing page for each service for current rates in your AWS Region.&lt;/p&gt; 
&lt;h2 id="cleanup"&gt;Cleanup&lt;/h2&gt; 
&lt;p&gt;To avoid incurring charges, delete the resources you created. If you deployed the accompanying SAM sample, run &lt;code&gt;sam delete --stack-name &amp;lt;stack-name&amp;gt;&lt;/code&gt;, which removes the Lambda functions, DynamoDB tables, SQS queue, KMS key, and IAM roles in one command. Before deleting the stack, delete any schedules the sample created at runtime, because schedule groups cannot be deleted while they still contain schedules. If you deployed the resources manually, delete them in this order:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Delete the schedule groups. Deleting a group also deletes the schedules it contains.&lt;/li&gt; 
 &lt;li&gt;Delete the Lambda functions (&lt;code&gt;GenerateInvoice&lt;/code&gt; and &lt;code&gt;SendPaymentReminder&lt;/code&gt;).&lt;/li&gt; 
 &lt;li&gt;Delete the IAM roles (&lt;code&gt;SchedulerInvoiceRole&lt;/code&gt; and &lt;code&gt;SchedulerReminderRole&lt;/code&gt;).&lt;/li&gt; 
 &lt;li&gt;Delete the SQS dead-letter queue.&lt;/li&gt; 
 &lt;li&gt;Delete the &lt;code&gt;billing-reminder-log&lt;/code&gt; DynamoDB table.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;Billing is inherently time-driven. Every customer has a cycle, every invoice has a due date, and every reminder has a send time. When you build billing infrastructure, you are building scheduling infrastructure whether you set out to or not.&lt;/p&gt; 
&lt;p&gt;With Amazon EventBridge Scheduler, you can stop building scheduling infrastructure and focus on your billing logic. Each customer’s billing lifecycle becomes a set of schedules, created at signup, updated when plans change, and deleted at cancellation. The timing is managed for you, the service scales to millions of schedules per Region, and the operational burden of running the scheduler moves to AWS.&lt;/p&gt; 
&lt;p&gt;If your application has per-customer timing, Scheduler is the building block that makes it straightforward.&lt;/p&gt; 
&lt;p&gt;To deploy this solution, use the accompanying &lt;a href="https://github.com/aws-samples/sample-per-customer-invoice-generation-and-payment-reminders-with-amazon-eventbridge-scheduler" target="_blank" rel="noopener"&gt;AWS SAM project on GitHub&lt;/a&gt;, which provisions the Lambda functions, DynamoDB tables, Amazon EventBridge Scheduler groups, and SQS dead-letter queue described in this post. For more information about the service, see the &lt;a href="https://docs.aws.amazon.com/scheduler/latest/UserGuide/what-is-scheduler.html" target="_blank" rel="noopener"&gt;Amazon EventBridge Scheduler documentation&lt;/a&gt; and the &lt;a href="https://aws.amazon.com/eventbridge/scheduler/" target="_blank" rel="noopener"&gt;Amazon EventBridge Scheduler product page&lt;/a&gt;. For more serverless learning resources, visit &lt;a href="https://serverlessland.com/" target="_blank" rel="noopener"&gt;Serverless Land&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/12/ComputeBlog-2711-2-1.jpg" alt="Rana Kiziltoprak German" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Rana Kiziltoprak German&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Rana is a Senior Technical Account Manager at Amazon Web Services, where she supports the Enterprise Support customers to build scalable, cost-optimized, resilience and secure architectures to prepare the workloads to the production scale. She specializes on the AWS Serverless services and Event-Driven Architecture.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/12/ComputeBlog-2711-3-1.jpg" alt="Oluwaseun Ademuwagun" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Oluwaseun Ademuwagun&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Oluwaseun is a Software Development Manager at Amazon Web Services, where he leads engineering teams responsible for event-driven and scheduled applications. Outside of work, he loves traveling, cooking, and playing football.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/12/ComputeBlog-2711-4-1.jpg" alt="Tugce Konuklar Dogantekin" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Tugce Konuklar Dogantekin&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Tugce is a Technical Account Manager at Amazon Web Services based in Germany. She brings more than a decade of software development experience to this work, and her technical focus is serverless, AIOps and observability.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Monitor application health with Amazon EC2 application status checks</title>
		<link>https://aws.amazon.com/blogs/compute/monitor-application-health-with-amazon-ec2-application-status-checks/</link>
		
		<dc:creator><![CDATA[Caroline Frost]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 15:48:19 +0000</pubDate>
				<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">dfc0d801a157733012d997f8e23784bb9554217d</guid>

					<description>Amazon EC2 application status checks detect application-layer failures with an HTTP or HTTPS health check, publish the result to Amazon CloudWatch, and let Amazon EC2 Auto Scaling replace impaired instances. Catch a stuck application without running a separate monitoring system.</description>
										<content:encoded>&lt;p&gt;&lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/a&gt; application status checks monitor application health and responsiveness alongside instance, system, and Amazon Elastic Block Store (Amazon EBS) status checks. You can use them to identify a web server that has stopped accepting requests, a Docker daemon that is not running, an incorrect networking configuration, or a network interface that is no longer passing traffic. Amazon EC2 reports application, instance, system, and Amazon EBS status checks through the DescribeInstanceStatus API and &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt;, so you can monitor application health through these EC2 signals rather than publish a custom health metric.&lt;/p&gt; 
&lt;p&gt;Application status checks can monitor an EC2 instance whether it is launched using &lt;code&gt;RunInstances&lt;/code&gt;, Amazon EC2 Fleet, or Amazon EC2 Auto Scaling. For &lt;code&gt;RunInstances&lt;/code&gt; and EC2 Fleet, launch the instance with the tag used by the check association. EC2 reports the application status, and you choose how to respond. Amazon EC2 Auto Scaling monitors instance health and can use included application status checks to automate recovery by replacing an instance when its application status is impaired. When Auto Scaling launches a replacement with the &lt;code&gt;app=database&lt;/code&gt; tag, the existing tag-based association includes it, so the application status check monitors the new instance without another association call. This walkthrough uses an Auto Scaling group and also covers CloudWatch alarms, staged onboarding, and application maintenance.&lt;/p&gt; 
&lt;p&gt;For additional details about the feature and pricing, you can refer to the &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/amazon-ec2-application-status-checks/" target="_blank" rel="noopener"&gt;What’s New post&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/application-status-checks.html" target="_blank" rel="noopener"&gt;application status checks&lt;/a&gt; in the Amazon EC2 User Guide.&lt;/p&gt; 
&lt;h2 id="solution-overview"&gt;Solution overview&lt;/h2&gt; 
&lt;p&gt;Application status checks report through the DescribeInstanceStatus API and Amazon CloudWatch, so you can consume the result in more than one way. You can poll the status from your own tooling, alarm on the CloudWatch metric and run your own remediation, or rely on Amazon EC2 Auto Scaling to replace an instance whose application status is impaired.&lt;/p&gt; 
&lt;p&gt;In this example, we use the feature with EC2 Auto Scaling groups. Auto Scaling groups help you manage the instance lifecycle across launching, monitoring, and refreshing instances, and they maintain the number of running instances you specify by replacing an instance that fails a health check. For simplicity, we assume the group is a fixed size, with its desired, minimum, and maximum capacity set to the same value, so replacing an instance keeps capacity steady. We assume we have already set up application monitoring for an application running on EC2 instances in an Amazon EC2 Auto Scaling group. Our goal is to replace an impaired application quickly.&lt;/p&gt; 
&lt;p&gt;The walkthrough adds one application status check across your instances, surfaces the result in CloudWatch, and configures Auto Scaling to replace an instance whose application status is impaired.&lt;/p&gt; 
&lt;p&gt;You configure the protocol, port, path, accepted response codes, and failure and success thresholds. EC2 evaluates the endpoint every 60 seconds. A matching response code passes. A different response code, a refused or reset connection, or a timeout counts as a failure. The check reports &lt;code&gt;failed&lt;/code&gt; after &lt;code&gt;FailureThreshold&lt;/code&gt; consecutive failures and &lt;code&gt;passed&lt;/code&gt; after &lt;code&gt;SuccessThreshold&lt;/code&gt; consecutive successes. Both thresholds default to 2.&lt;/p&gt; 
&lt;p&gt;The application status of the instance is separate from the result of any single check. It is the aggregation of the checks associated with the instance that have &lt;code&gt;Aggregation&lt;/code&gt; set to &lt;code&gt;included&lt;/code&gt;. It reports impaired when at least one included check has a failed result. This is the value that appears as &lt;code&gt;ApplicationStatus&lt;/code&gt; in &lt;code&gt;describe-instance-status&lt;/code&gt; and that Amazon EC2 Auto Scaling acts on. An initialization grace period delays evaluation after launch, so an application that is still starting is not reported impaired before it is ready. You can associate more than one check with an instance, for example a liveness path and a readiness path, and include or exclude each one from the aggregated instance-level status.&lt;/p&gt; 
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt; 
&lt;p&gt;Before you start, you need the following:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;An application running on EC2 instances in an Auto Scaling group. If you need to create a group for this walkthrough, see &lt;a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-launch-template.html" target="_blank" rel="noopener"&gt;Create an Auto Scaling group using a launch template&lt;/a&gt;. Configure the Amazon Machine Image (AMI) or user data in the launch template to install and start the application on each instance.&lt;/li&gt; 
 &lt;li&gt;A tag on those instances that you can target, for example &lt;code&gt;app=database&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Instances reachable on the health check port from within your virtual private cloud (VPC). With AWS-managed network paths, EC2 matches the health check source to the subnet and security group combinations used by the associated instances. Before creating the check, add an inbound rule to each instance security group that allows health check traffic on the check port from the same security group. The host firewall must also allow the port. The instances do not need public IP addresses.&lt;/li&gt; 
 &lt;li&gt;An &lt;a href="https://aws.amazon.com/iam/" target="_blank" rel="noopener"&gt;AWS Identity and Access Management (IAM)&lt;/a&gt; principal with permissions for the EC2 application status check actions and EC2 Auto Scaling.&lt;/li&gt; 
 &lt;li&gt;Make sure your AWS Command Line Interface (AWS CLI) is up to date. Older releases might not include the application status check commands. If the CLI does not recognize &lt;code&gt;create-application-status-check&lt;/code&gt;, follow &lt;a href="https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html" target="_blank" rel="noopener"&gt;Installing or updating to the latest version of the AWS CLI&lt;/a&gt; before continuing.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;If you do not have an application on a health path yet, add a lightweight endpoint that returns a success code when the instance is ready (most web frameworks expose one), or point the check at an existing readiness path. You need at least &lt;a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-launch-template.html" target="_blank" rel="noopener"&gt;one running instance in the Auto Scaling group&lt;/a&gt; that is reachable on the check port and serving that endpoint to see a passing result.&lt;/p&gt; 
&lt;p&gt;To add a lightweight endpoint for an instance running Amazon Linux 2023, install nginx and serve a path that returns 200:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;sudo dnf install -y nginx
sudo tee /etc/nginx/conf.d/health.conf &amp;gt;/dev/null &amp;lt;&amp;lt;'EOF'
server {
    listen 8080;
    location = /health {
        access_log off;
        default_type text/plain;
        return 200 'ok';
    }
}
EOF
sudo nginx -t
sudo systemctl enable --now nginx
curl -I http://127.0.0.1:8080/health&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The final curl command confirms that nginx is listening locally and returning a 200 response. Before you create the application status check, configure the instance security group to allow health check traffic on port 8080 from the same security group. For instructions, see &lt;a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html#security-group-referencing" target="_blank" rel="noopener"&gt;Security group referencing&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="create-an-application-status-check"&gt;Create an application status check&lt;/h2&gt; 
&lt;p&gt;Create a check that requests &lt;code&gt;/health&lt;/code&gt; on port 8080 over HTTP and treats 200 as healthy. Keep the default thresholds and set an initialization grace period so that newly launched instances have time to start.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 create-application-status-check \
  --protocol http \
  --port 8080 \
  --path /health \
  --status-code-matcher "200" \
  --initialization-grace-period-seconds 300 \
  --tag-specifications 'ResourceType=application-status-check,Tags=[{Key=Name,Value=database-health}]'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The response returns an application status check ID, for example &lt;code&gt;asc-0123456789abcdef0&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;code&gt;Name=database-health&lt;/code&gt; identifies the application status check. The &lt;code&gt;app=database&lt;/code&gt; tag used in the next step selects the instances to monitor.&lt;/p&gt; 
&lt;p&gt;The status code matcher defaults to 200 and accepts a comma-separated list of individual codes or ranges, for example &lt;code&gt;"200,204"&lt;/code&gt;, up to 64 characters.&lt;/p&gt; 
&lt;h2 id="associate-the-check-with-your-instances"&gt;Associate the check with your instances&lt;/h2&gt; 
&lt;p&gt;Use the application status check ID returned by the create step to associate the check with every instance that carries the &lt;code&gt;app=database&lt;/code&gt; tag. Tag-based association covers instances that already carry the tag and instances that launch with it later, which suits an Auto Scaling group where replacement instances launch with the tag.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 associate-application-status-check \
  --application-status-check-id asc-0123456789abcdef0 \
  --target-tag-associations Key=app,Value=database&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You can also associate specific instances with &lt;code&gt;--instance-ids&lt;/code&gt; instead of &lt;code&gt;--target-tag-associations&lt;/code&gt;.&lt;/p&gt; 
&lt;h2 id="view-the-application-status"&gt;View the application status&lt;/h2&gt; 
&lt;p&gt;The &lt;code&gt;describe-instance-status&lt;/code&gt; call returns the application status alongside the instance and system status checks, so a query you already run surfaces it without a new API call.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 describe-instance-status --instance-ids i-0abc123def4567890&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The following example response shows a case where the system and instance status checks pass, while the application status reports &lt;code&gt;impaired&lt;/code&gt;.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
    "InstanceStatuses": [
        {
            "AvailabilityZone": "us-east-1d",
            "InstanceId": "i-0abc123def4567890",
            "InstanceState": {
                "Code": 16,
                "Name": "running"
            },
            "SystemStatus": {
                "Status": "ok",
                "Details": [
                    {
                        "Name": "reachability",
                        "Status": "passed"
                    }
                ]
            },
            "InstanceStatus": {
                "Status": "ok",
                "Details": [
                    {
                        "Name": "reachability",
                        "Status": "passed"
                    }
                ]
            },
            "ApplicationStatus": {
                "Status": "impaired",
                "ImpairedSince": "2026-08-07T14:32:10.000Z"
            }
        }
    ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;code&gt;describe-instance-status&lt;/code&gt; returns the aggregation of the included application status checks associated with an instance. For details on every application status check associated with an instance, use &lt;code&gt;describe-application-status&lt;/code&gt;, which returns each associated check’s individual result, the reason code, and the HTTP status code your application returned. Use &lt;code&gt;describe-instance-status&lt;/code&gt; to see the aggregated application health next to other status checks, and &lt;code&gt;describe-application-status&lt;/code&gt; for details on which check failed and why.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 describe-application-status --instance-ids i-0abc123def4567890&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;A failed check includes a reason that explains the outcome. For example:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
    "ApplicationStatuses": [
        {
            "InstanceId": "i-0abc123def4567890",
            "ApplicationStatus": {
                "Status": "impaired",
                "Details": [
                    {
                        "ApplicationStatusCheckId": "asc-0123456789abcdef0",
                        "Aggregation": "included",
                        "Status": "failed",
                        "Reason": {
                            "Code": "ResponseCodeMismatch",
                            "StatusCode": 503,
                            "Protocol": "HTTP"
                        }
                    }
                ]
            }
        }
    ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;For &lt;code&gt;ResponseCodeMatched&lt;/code&gt; and &lt;code&gt;ResponseCodeMismatch&lt;/code&gt;, the &lt;code&gt;Reason&lt;/code&gt; includes the returned &lt;code&gt;StatusCode&lt;/code&gt; and the &lt;code&gt;Protocol&lt;/code&gt;, so you can distinguish a 500 from a 503. Connection reasons such as &lt;code&gt;ConnectionTimeout&lt;/code&gt;, &lt;code&gt;ConnectionRefused&lt;/code&gt;, and &lt;code&gt;ConnectionReset&lt;/code&gt; indicate that the application did not complete a response at all, and do not include a &lt;code&gt;StatusCode&lt;/code&gt;.&lt;/p&gt; 
&lt;h2 id="replace-instances-with-an-impaired-status-check"&gt;Replace instances with an impaired status check&lt;/h2&gt; 
&lt;p&gt;When an application status check reports impaired, the right response depends on what failed, and not every impairment calls for terminating the instance. Common responses include rebooting the instance, rolling back a recent deployment, or terminating the instance and replacing it, and your workload may call for others. A transient fault may clear with a reboot, a bad deployment may call for a rollback, and a crashed or wedged instance usually calls for termination and replacement.&lt;/p&gt; 
&lt;p&gt;Amazon EC2 Auto Scaling evaluates the aggregated application status as part of its EC2 health checks. When the status is impaired, the group marks the instance unhealthy, terminates it, and attempts to launch a replacement from the group’s launch template. Auto Scaling does not copy the application from the terminated instance. Configure the AMI, user data, or deployment system for the group to install and start the application on each replacement. Because the group has fixed capacity in this example, it replaces the impaired instance rather than changing capacity. Auto Scaling includes application status checks in the group’s EC2 health checks by default, so no separate Auto Scaling health check configuration is required.&lt;/p&gt; 
&lt;p&gt;Terminate and replace is the default an Auto Scaling group gives you. If your remediation is a reboot or a rollback instead, keep the same impaired signal and act on it yourself, using the CloudWatch alarm in the next section to trigger your own automation.&lt;/p&gt; 
&lt;p&gt;Set the check’s &lt;code&gt;InitializationGracePeriodSeconds&lt;/code&gt; to at least the time your application needs to start, and make sure the Auto Scaling group’s health check grace period is no shorter. Then neither the check nor the group acts on an instance that is still initializing. Detection and remediation then run without a separate monitoring system.&lt;/p&gt; 
&lt;h2 id="alarm-on-the-application-status-in-amazon-cloudwatch"&gt;Alarm on the application status in Amazon CloudWatch&lt;/h2&gt; 
&lt;p&gt;EC2 publishes the application status to CloudWatch, so you can alarm on it without a custom metric. This step is optional. Auto Scaling replaces an impaired instance whether or not you create an alarm. Add one when you want notification or a dashboard alongside the replacement. The following alarm notifies an operations topic when the application status check fails for an instance.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws cloudwatch put-metric-alarm \
  --alarm-name database-impaired \
  --namespace AWS/EC2 \
  --metric-name StatusCheckFailed_Application \
  --dimensions Name=InstanceId,Value=i-0abc123def4567890 \
  --statistic Maximum \
  --period 60 \
  --evaluation-periods 3 \
  --threshold 1 \
  --comparison-operator GreaterThanOrEqualToThreshold \
  --alarm-actions arn:aws:sns:us-east-1:111122223333:ops-notifications&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The alarm enters the ALARM state when the application status is impaired for three consecutive minutes. &lt;code&gt;StatusCheckFailed_Application&lt;/code&gt; aggregates across every associated check whose aggregation is &lt;code&gt;included&lt;/code&gt;. EC2 also publishes a per-check metric named &lt;code&gt;StatusCheckFailed_Application_{application-status-check-id}&lt;/code&gt;, so you can alarm on an individual check when an instance has more than one associated.&lt;/p&gt; 
&lt;p&gt;To see the behavior end to end, stop the application process on one instance without stopping the instance. After the configured thresholds are met, the application status can turn impaired, the CloudWatch alarm can enter the ALARM state, and the Auto Scaling group can replace the instance while the remaining healthy instances can continue to serve traffic.&lt;/p&gt; 
&lt;h2 id="rollout-and-maintenance-strategies"&gt;Rollout and maintenance strategies&lt;/h2&gt; 
&lt;p&gt;Use the following strategies to stage deployment across your instances and suppress reporting during planned application maintenance.&lt;/p&gt; 
&lt;h3 id="onboard-checks-across-your-instances"&gt;Onboard checks across your instances&lt;/h3&gt; 
&lt;p&gt;Roll application status checks out to a large number of instances in stages. An excluded check does not contribute to replacement decisions while you validate it.&lt;/p&gt; 
&lt;h3 id="start-in-observe-only-mode"&gt;Start in observe-only mode&lt;/h3&gt; 
&lt;p&gt;Create the check with &lt;code&gt;Aggregation&lt;/code&gt; set to &lt;code&gt;excluded&lt;/code&gt;. An excluded check still runs and reports its result through &lt;code&gt;describe-application-status&lt;/code&gt; and CloudWatch, but it does not contribute to the instance-level application status and does not cause Auto Scaling to replace an instance. Watch it for a representative period, confirm it returns the codes you expect, and tune the &lt;code&gt;StatusCodeMatcher&lt;/code&gt;, &lt;code&gt;FailureThreshold&lt;/code&gt;, &lt;code&gt;SuccessThreshold&lt;/code&gt;, and initialization grace period. When you are confident, move the check to &lt;code&gt;included&lt;/code&gt; with &lt;code&gt;ModifyApplicationStatusCheck&lt;/code&gt;, and the result begins contributing to the instance-level status and to Auto Scaling replacement.&lt;/p&gt; 
&lt;h3 id="associate-by-tag"&gt;Associate by tag&lt;/h3&gt; 
&lt;p&gt;Associate the check with a tag rather than a list of instance IDs. A tag-based association also covers a new instance when it launches with the tag, without another API call. This fits an Auto Scaling group, an instance refresh, or any workflow that replaces instances over time.&lt;/p&gt; 
&lt;h3 id="amazon-eks-and-karpenter"&gt;Amazon EKS and Karpenter&lt;/h3&gt; 
&lt;p&gt;Application status checks can monitor an application endpoint on an EC2 worker node, including nodes launched for Amazon Elastic Kubernetes Service (Amazon EKS) managed node groups or by Karpenter. Each associated node must expose the HTTP or HTTPS health path on the configured port and carry the tag used by the check association. For an EKS managed node group, apply the tag to the EC2 instances through its custom launch template. For Karpenter, apply the tag through &lt;code&gt;spec.tags&lt;/code&gt; in the EC2NodeClass. Application status checks monitor the endpoint on the EC2 instance, not a Kubernetes Service or an individual pod.&lt;/p&gt; 
&lt;h3 id="manage-checks-as-code"&gt;Manage checks as code&lt;/h3&gt; 
&lt;p&gt;Define the check, its thresholds, and its tag association in the same infrastructure-as-code templates you use for your instances, so you can apply the same definition across environments and use your review process for changes. Roll the same definition out one Auto Scaling group or one Region at a time, and use a CloudWatch dashboard on the &lt;code&gt;StatusCheckFailed_Application&lt;/code&gt; metric and the per-check &lt;code&gt;StatusCheckFailed_Application_{application-status-check-id}&lt;/code&gt; metric to compare behavior before and after you switch a check to &lt;code&gt;included&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;The following template creates the check and its tag association. The template creates the check with &lt;code&gt;Aggregation&lt;/code&gt; set to &lt;code&gt;excluded&lt;/code&gt; so that it reports without contributing to the instance-level status, and you change it to &lt;code&gt;included&lt;/code&gt; when you are ready.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;Resources:
  DatabaseHealthCheck:
    Type: AWS::EC2::ApplicationStatusCheck
    Properties:
      Protocol: http
      Port: 8080
      Path: /health
      StatusCodeMatcher: "200"
      FailureThreshold: 2
      SuccessThreshold: 2
      InitializationGracePeriodSeconds: 300
      Aggregation: excluded
      Tags:
        - Key: Name
          Value: database-health

  DatabaseHealthCheckTagAssociation:
    Type: AWS::EC2::ApplicationStatusCheckTagAssociation
    Properties:
      ApplicationStatusCheckId: !GetAtt DatabaseHealthCheck.ApplicationStatusCheckId
      TagKey: app
      TagValue: database&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The association takes the check ID, which the check exposes as an Fn::GetAtt attribute. To target named instances instead of a tag, use AWS::EC2::ApplicationStatusCheckInstanceAssociation with ApplicationStatusCheckId and InstanceId. Every ID property on both association resources is create-only, so changing the target replaces the association.&lt;/p&gt; 
&lt;h3 id="run-more-than-one-check"&gt;Run more than one check&lt;/h3&gt; 
&lt;p&gt;You can associate more than one check with an instance, for example a liveness path and a readiness path, and include or exclude each from the aggregated instance-level status. Create a new check and exclude it from the aggregated count, confirm it behaves, then include it. The application status appears alongside the instance, system, and Amazon EBS status checks in &lt;code&gt;describe-instance-status&lt;/code&gt;, so you can adopt it without changing the queries and alarms you already run.&lt;/p&gt; 
&lt;h3 id="perform-application-maintenance"&gt;Perform application maintenance&lt;/h3&gt; 
&lt;p&gt;Planned maintenance, such as a rolling configuration change or a version upgrade, can make an application stop responding on its health path for a short time. Without a pause, the check reports the instance impaired and Auto Scaling can replace an instance that is healthy and only briefly offline. Pause reporting for the duration, then resume it.&lt;/p&gt; 
&lt;p&gt;The direct control is &lt;code&gt;EnableApplicationStatusCheckSuppression&lt;/code&gt;. While suppression is in effect, the check does not mark instances impaired, so Auto Scaling does not act on it. Reporting resumes when you call &lt;code&gt;DisableApplicationStatusCheckSuppression&lt;/code&gt;, or at the resume time set for the suppression. The following patterns wire that pause into common maintenance workflows.&lt;/p&gt; 
&lt;h3 id="ec2-auto-scaling-instance-refresh-and-standby"&gt;EC2 Auto Scaling instance refresh and standby&lt;/h3&gt; 
&lt;p&gt;An instance refresh rolls a new launch template through the group in batches and waits for each new instance to pass its health checks, including the application status check, before it continues. Set the check’s &lt;code&gt;InitializationGracePeriodSeconds&lt;/code&gt;, and the group’s instance warmup, to at least the time your application needs to start, so the refresh does not act on an instance that is still initializing. For one-off manual work on a single instance, move it to standby with &lt;code&gt;EnterStandby&lt;/code&gt;. The group stops health-checking and replacing it until you call &lt;code&gt;ExitStandby&lt;/code&gt;.&lt;/p&gt; 
&lt;h3 id="aws-codedeploy"&gt;AWS CodeDeploy&lt;/h3&gt; 
&lt;p&gt;Suppression is not tied to any one deployment tool. If you deploy with &lt;a href="https://aws.amazon.com/codedeploy/" target="_blank" rel="noopener"&gt;AWS CodeDeploy&lt;/a&gt;, a deployment that restarts your application fails its health path until the new version is serving, so suppress the instance in a lifecycle hook before the deployment and resume it after. Suppress in a &lt;code&gt;BeforeInstall&lt;/code&gt; hook and resume in an &lt;code&gt;ApplicationStart&lt;/code&gt; hook in your &lt;code&gt;appspec.yml&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;version: 0.0
os: linux
hooks:
  BeforeInstall:
    - location: scripts/suppress_status_check.sh
      timeout: 60
  ApplicationStart:
    - location: scripts/resume_status_check.sh
      timeout: 60&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;code&gt;scripts/suppress_status_check.sh&lt;/code&gt; suppresses the instance before the new version installs:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;#!/bin/bash
set -euo pipefail
aws ec2 enable-application-status-check-suppression \
  --instance-ids i-0abc123def4567890 \
  --duration-seconds 600&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;code&gt;scripts/resume_status_check.sh&lt;/code&gt; resumes reporting once the new version is up:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;#!/bin/bash
set -euo pipefail
aws ec2 disable-application-status-check-suppression \
  --instance-ids i-0abc123def4567890&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The &lt;code&gt;--duration-seconds&lt;/code&gt; value is a safety net: If the deployment fails before the resume hook runs, suppression lifts on its own rather than leaving the instance unmonitored. Omit it to suppress until you call disable. Grant the instance role &lt;code&gt;ec2:EnableApplicationStatusCheckSuppression&lt;/code&gt; and &lt;code&gt;ec2:DisableApplicationStatusCheckSuppression&lt;/code&gt;. After reporting resumes, the check evaluates the application again and returns the instance to healthy once it passes, so a routine deployment does not trigger a replacement.&lt;/p&gt; 
&lt;h3 id="aws-systems-manager-maintenance-windows"&gt;AWS Systems Manager maintenance windows&lt;/h3&gt; 
&lt;p&gt;For scheduled maintenance such as patching, run the work inside an &lt;a href="https://aws.amazon.com/systems-manager/" target="_blank" rel="noopener"&gt;AWS Systems Manager&lt;/a&gt; maintenance window and bracket it with the suppression calls: an automation step that enables suppression before the patch task and disables it after. Reporting stays paused for the window and resumes on its own at the suppression resume time if a step does not complete.&lt;/p&gt; 
&lt;h2 id="clean-up-resources"&gt;Clean up resources&lt;/h2&gt; 
&lt;p&gt;Application status checks incur charges while they are associated with instances. AWS charges for each managed elastic network interface (ENI) AWS creates in your VPC, per Availability Zone, and standard Amazon CloudWatch rates apply to the metrics the checks publish. AWS creates one endpoint per combination of source subnet and security group, so the count does not scale per instance or per check. Delete the resources you created so that you do not incur further charges. Delete the application status check and the CloudWatch alarm, and delete the Auto Scaling group if you created it only for this walkthrough.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 delete-application-status-check --application-status-check-id asc-0123456789abcdef0
aws cloudwatch delete-alarms --alarm-names database-impaired&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="quotas"&gt;Quotas&lt;/h2&gt; 
&lt;p&gt;Application status checks are subject to service quotas that cap how many checks you create, how many associations you make, and how many instances you monitor. Review the current defaults before you roll out to a large number of instances, because a tag-based association covers instances that launch later. A growing number of instances can reach a quota without any change to your configuration. Once you pass a quota, the instances beyond it stop being checked and report no status. Use the &lt;a href="https://console.aws.amazon.com/servicequotas/" target="_blank" rel="noopener"&gt;Service Quotas console&lt;/a&gt; to view usage and request increases. For the current quotas and how each one is counted, see &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/application-status-checks.html" target="_blank" rel="noopener"&gt;Application status checks&lt;/a&gt; in the Amazon EC2 User Guide.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;In this post, we showed how to monitor application health on Amazon EC2 with application status checks. You created an HTTP check, associated it with your instances by tag, viewed the status alongside your existing status checks, alarmed on it in Amazon CloudWatch, and relied on Amazon EC2 Auto Scaling to replace an impaired instance. You can use EC2 status checks and Auto Scaling to detect and respond to application failures rather than operate a separate monitoring system.&lt;/p&gt; 
&lt;p&gt;If you use another deployment mechanism, apply the association tag to each EC2 instance and make sure the application exposes the configured health path and port. Contact your AWS account team if you need help adapting this pattern to your deployment process.&lt;/p&gt; 
&lt;p&gt;To learn more, see &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/application-status-checks.html" target="_blank" rel="noopener"&gt;Application status checks&lt;/a&gt; in the Amazon EC2 User Guide and &lt;a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-health-checks.html" target="_blank" rel="noopener"&gt;Health checks for instances in an Auto Scaling group&lt;/a&gt; in the Amazon EC2 Auto Scaling User Guide. As a next step, add a second check for a readiness path and exclude it from aggregation to see how per-check status contributes to the instance-level result.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the author&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2718-1.jpg" alt="Caroline Frost" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Caroline Frost&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Caroline is an Amazon EC2 Senior Product Manager – Technical, focusing on the EC2 instance lifecycle. She is passionate about building capabilities that improve the developer experience and create operational ease and simplicity.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Building a GPU workstation for visual effects with Amazon EC2: Part 5 – Security</title>
		<link>https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-5-security/</link>
		
		<dc:creator><![CDATA[Andy Hayes]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 15:27:23 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">1d9b93b2cce997236b51b4f5906b3969aed098e2</guid>

					<description>The final post in our GPU workstation series covers security for visual effects workstations on Amazon EC2: controlling who can reach the desktop, protecting the Amazon DCV session in transit, and safeguarding credentials, images, and storage, plus IAM, encryption, monitoring, and patch management best practices for production VFX environments.</description>
										<content:encoded>&lt;p&gt;For many years Amazon Web Services (AWS) has been guiding users in the deployment of powerful NVIDIA GPU backed workstations for graphics intensive workloads. With the recent expansion of our G-series &lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/a&gt; graphics-based instances, we’re excited to introduce new instance families that deliver enhanced performance and capabilities. We’re also refreshing our comprehensive guidance on choosing and configuring these powerful virtual workstations.&lt;/p&gt; 
&lt;p&gt;This is the fifth post in a five-part series, exploring security practices related to the deployment of visual effects (VFX) workstations: how to secure these workstations by controlling who can reach the desktop, protecting the session in transit, and safeguarding the credentials, images, and storage behind it. The following screen capture shows these GPU-powered workstations in use, in a real production environment.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-1.jpeg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-1.jpeg" alt="Rocky Linux-based GPU workstations in use by artists in a studio, each with two monitors" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Amazon EC2 GPU-powered workstations, used in a Studio-in-the-Cloud courtesy of Outpost VFX&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="before-you-begin"&gt;Before you begin&lt;/h2&gt; 
&lt;p&gt;This post builds upon topics covered earlier in the series, regarding Linux and Windows EC2 instances, configured for the purposes of creating GPU workstations.&lt;/p&gt; 
&lt;p&gt;If you want to understand more about GPU accelerated Amazon EC2 G graphics instances, go to Part 1 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/build-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-1-setup/"&gt;Build a GPU workstation for visual effects on Amazon EC2: Part 1 – Setup&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For deployment instructions for creating a Rocky Linux graphics workstation, go to Part 2 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-2-linux/"&gt;Building a GPU workstation for visual effects on Amazon EC2: Part 2 – Linux&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For creating a Windows Server 2025 graphics workstation, go to Part 3 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 3 – Windows&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Finally, for methods to standardize and optimize instances, for rapid re-use at scale, go to Part 4 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="security-considerations"&gt;Security considerations&lt;/h2&gt; 
&lt;p&gt;When deploying EC2 instance workloads on Amazon EC2, security hardening isn’t only a best practice but also essential for protecting your infrastructure, data, and applications from evolving threats. AWS provides secure cloud infrastructure, but the responsibility for securing the operating system and applications running on your EC2 instances falls squarely on you as part of the &lt;a href="https://aws.amazon.com/compliance/shared-responsibility-model/" target="_blank" rel="noopener"&gt;AWS Shared Responsibility Model&lt;/a&gt;. While AWS secures the underlying infrastructure (the physical servers, networking equipment, and hypervisor layer), you’re responsible for everything from the guest operating system upward. This includes patching, configuration management, access controls, and monitoring. A misconfigured EC2 instance can become an entry point for unauthorized users, potentially impacting more than that single instance in your AWS environment through lateral movement.&lt;/p&gt; 
&lt;p&gt;Throughout this post series, we’ve implemented security best practices aligned with the AWS documentation on &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-best-practices.html" target="_blank" rel="noopener"&gt;Best practices for Amazon EC2&lt;/a&gt;. As we conclude, let’s revisit the key security principles we’ve applied and explore additional considerations for production environments.&lt;/p&gt; 
&lt;h3 id="amazon-dcv-connection-security"&gt;Amazon DCV connection security&lt;/h3&gt; 
&lt;p&gt;Amazon DCV provides immediate out-of-the-box encryption of pixels and end-user inputs, and to do so it creates a self-signed certificate. As previously mentioned, the browser issues a security warning when you connect by default. This is expected because the browser can’t verify the certificate’s authenticity in terms of domain or validity by a Certificate Authority (CA). Amazon DCV doesn’t immediately know your domain requirements for servers or clients. You elect to accept the risk based on your knowledge of the IP in question that you are connecting to.&lt;/p&gt; 
&lt;p&gt;Amazon DCV itself has further configurations that can mitigate potential security risks. For example, the DCV server can perform administrator-defined regex filtering on origin and host names to protect against WebSocket hijacking, and Host Header attacks. On Linux, add the following to &lt;code&gt;dcv.conf&lt;/code&gt;, typically found at &lt;code&gt;/etc/dcv/dcv.conf&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-ini"&gt;# Under [security] add the following line:
allowed-ws-origin-regex = ^https://(www\.)?example\.com(:443)?$
allowed-http-host-regex = ^(www\.)?example\.com$&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;On Windows, you add the respective string values for each parameter subkey within the &lt;code&gt;Computer\HKEY_USERS\S-1-5-18\Software\GSettings\com\nicesoftware\dcv\security&lt;/code&gt; registry key. The following screen capture shows this registry key open in Registry Editor, with the connectivity-restriction values in place. In this example, two values are defined under the security key (allowed-ws-origin-regex and allowed-http-host-regex) each set to a regular expression that limits connections to a specific domain.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-2.png" alt="Windows Registry Editor showing the Amazon DCV security key with allowed-ws-origin-regex and allowed-http-host-regex subkeys limiting connectivity to one domain" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: The Amazon DCV registry security key, with subkeys limiting host and origin connectivity&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;For more information about security parameters with Amazon DCV, see security parameter reference of the &lt;a href="https://docs.aws.amazon.com/dcv/latest/adminguide/config-param-ref.html#security" target="_blank" rel="noopener"&gt;Amazon DCV Administrator Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Amazon DCV clients requesting connections to the Amazon DCV server can be restricted through fundamental network-level controls that allow requests from specific IP addresses and ports:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html" target="_blank" rel="noopener"&gt;&lt;strong&gt;AWS Network Access Control List&lt;/strong&gt;&lt;/a&gt; (ACLs) restrict inbound and outbound traffic at the subnet level on the VPC.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/vpc/latest/userguide/vpc-security-groups.html" target="_blank" rel="noopener"&gt;&lt;strong&gt;AWS Security Groups&lt;/strong&gt;&lt;/a&gt; (as already mentioned and used in this post) apply another layer of restrictions on incoming IP addresses and ports to the server instance.&lt;/li&gt; 
 &lt;li&gt;Firewall rules can further restrict incoming IP addresses and ports.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;To extend both the functionality and security of Amazon DCV, an &lt;a href="https://docs.aws.amazon.com/dcv/latest/gw-admin/what-is-gw.html" target="_blank" rel="noopener"&gt;Amazon DCV Connection Gateway&lt;/a&gt; can also be used as part of a more extensive infrastructure, to act as an intermediary between clients and servers. From a security point of view, it adds a single point of entry, hiding the servers behind the gateway, mitigating load, but also implementing a token-based authentication system to resolve server sessions for clients.&lt;/p&gt; 
&lt;p&gt;Whilst these steps prevent unauthorized access attempts from unexpected sources, it doesn’t solve the certificate trust warning. To improve both the user experience (to resolve the warning, and the general question of &lt;em&gt;is this secure?&lt;/em&gt;) as well as strengthen your security defenses, consider using your own certificate from a trusted CA. This is beyond the scope of this post, but services such as &lt;a href="https://www.amazonaws.cn/en/private-ca/getting-started/" target="_blank" rel="noopener"&gt;AWS Private Certificate Authority&lt;/a&gt; provide the ability to create certificates that encapsulate your domain and can be trusted by the browser as a legitimate CA. Not only does this simplify the user experience but it also provides cryptographic verification of server identity and protection against man-in-the-middle attacks.&lt;/p&gt; 
&lt;h3 id="network-security"&gt;Network security&lt;/h3&gt; 
&lt;p&gt;We have repeatedly applied the principle of least privilege, using &lt;strong&gt;Security Group&lt;/strong&gt; rules to restrict access to known IP addresses only. As detailed in Part 1 of this series, the choice of connectivity method significantly impacts your security architecture, and while this post uses internet connectivity for simplicity, production environments should evaluate additional security layers based on their requirements. &lt;strong&gt;Network Access Control Lists&lt;/strong&gt; (NACLs) can also be used for subnet-level traffic filtering as an additional defense layer to security groups, and &lt;a href="https://aws.amazon.com/network-firewall/" target="_blank" rel="noopener"&gt;AWS Network Firewall&lt;/a&gt; offers advanced threat protection and intrusion detection.&lt;/p&gt; 
&lt;p&gt;For enhanced security postures &lt;a href="https://aws.amazon.com/vpn/site-to-site-vpn/"&gt;AWS Site-to-Site VPN&lt;/a&gt; adds network-layer IPsec encryption on top of the application-layer security of Amazon DCV, protecting against man-in-the-middle attacks, traffic analysis, and DNS hijacking while allowing workstations to reside in private subnets. &lt;strong&gt;AWS Direct Connect&lt;/strong&gt; further strengthens security by bypassing the public internet entirely through dedicated fiber connections, reducing exposure to internet-based DDoS attacks, ISP-level surveillance, and routing attacks.&lt;/p&gt; 
&lt;p&gt;If you have strict compliance requirements, also consider deploying Amazon DCV servers in private subnets with &lt;a href="https://aws.amazon.com/privatelink/" target="_blank" rel="noopener"&gt;AWS PrivateLink&lt;/a&gt; endpoints for fully private connectivity. For comprehensive guidance on these connectivity options and additional firewall and protection services that enhance protection against exploits such as ransomware and DDoS, see &lt;a href="https://aws.amazon.com/products/security/" target="_blank" rel="noopener"&gt;Security, Identity and Compliance on AWS&lt;/a&gt; (refer back to Part 1’s detailed comparison of connectivity architectures).&lt;/p&gt; 
&lt;h3 id="aws-identity-and-access-management-iam"&gt;AWS Identity and Access Management (IAM)&lt;/h3&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/iam" target="_blank" rel="noopener"&gt;IAM&lt;/a&gt; securely controls access to AWS. With IAM, you can manage authentication and authorization and grant your identities only the least-privilege permissions required for their tasks, reducing the risk of mistakes or unauthorized behavior. Throughout this post series, we’ve applied this principle of least privilege to IAM roles and policies. For example, we attached IAM roles to EC2 instances rather than using long-lived static credentials, eliminating the risk of exposed access keys.&lt;/p&gt; 
&lt;p&gt;For example, for the purposes of this post, we used read-only policies for S3. For production environments, we recommend taking this further by prescribing:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Access to &lt;em&gt;specific&lt;/em&gt; S3 buckets using resource-level permissions. 
  &lt;ul&gt; 
   &lt;li&gt;For example, &lt;code&gt;arn:aws:s3:::amzn-s3-demo-bucket/*&lt;/code&gt;.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;Limiting actions to &lt;em&gt;only&lt;/em&gt; what’s required. 
  &lt;ul&gt; 
   &lt;li&gt;For example, &lt;code&gt;s3:GetObject&lt;/code&gt; instead of &lt;code&gt;s3:*&lt;/code&gt;.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="credential-security"&gt;Credential security&lt;/h3&gt; 
&lt;p&gt;As a best practice, we recommend changing default passwords immediately and aligning them with your organization’s password quality requirements, such as 16 or more characters with mixed case, numbers, and symbols. Any SSH key pairs should be rotated regularly in line with your organizational requirements.&lt;/p&gt; 
&lt;h3 id="monitoring-and-logging"&gt;Monitoring and logging&lt;/h3&gt; 
&lt;p&gt;You can use a number of tools and services to monitor activity within an AWS account. For example, use &lt;a href="https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-user-guide.html" target="_blank" rel="noopener"&gt;AWS CloudTrail&lt;/a&gt; to audit IAM actions and API calls for compliance and security, and implement &lt;a href="https://www.amazonaws.cn/en/cloudwatch" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; alarms to warn about specific security events. &lt;a href="https://aws.amazon.com/iam/access-analyzer/" target="_blank" rel="noopener"&gt;AWS Identity and Access Management Access Analyzer&lt;/a&gt; can be used to identify resources shared with external entities and validate that your IAM policies grant only intended access, whilst &lt;a href="https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html" target="_blank" rel="noopener"&gt;VPC Flow Logs&lt;/a&gt; monitor and allow you to audit network traffic patterns within your network. For vulnerability detection, &lt;a href="https://aws.amazon.com/inspector/" target="_blank" rel="noopener"&gt;Amazon Inspector&lt;/a&gt; can scan EC2 instances for software and network exposure, whilst &lt;a href="https://aws.amazon.com/guardduty/" target="_blank" rel="noopener"&gt;Amazon GuardDuty&lt;/a&gt; can continuously monitor for threat detection across your infrastructure, looking for suspicious or malicious behavior.&lt;/p&gt; 
&lt;h3 id="encryption"&gt;Encryption&lt;/h3&gt; 
&lt;p&gt;Encrypting your data at rest, and in transit helps protect against unauthorized access even if storage media is compromised or network traffic is intercepted. In these posts we made sure that Amazon Elastic Block Store (Amazon EBS) volumes for our instances were all encrypted using &lt;a href="https://docs.aws.amazon.com/kms/latest/developerguide/overview.html" target="_blank" rel="noopener"&gt;AWS Key Management Service (KMS)&lt;/a&gt; for encryption key management, providing cryptographic verification and centralized key rotation capabilities. We explored Transport Layer Security (TLS) encryption for Amazon DCV, which helps protect your desktop pixels and user inputs during transmission using TLS v1.2 or greater with strong cipher suites.&lt;/p&gt; 
&lt;h3 id="patch-management"&gt;Patch management&lt;/h3&gt; 
&lt;p&gt;Consider build-time hardening services such as &lt;a href="https://aws.amazon.com/image-builder/" target="_blank" rel="noopener"&gt;EC2 Image Builder&lt;/a&gt; to automate the creation of Amazon Machine Images (AMIs) that apply the latest security patches, remove unnecessary components, and install anti-malware protection.&lt;/p&gt; 
&lt;p&gt;For lifecycle management, &lt;a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager.html" target="_blank" rel="noopener"&gt;AWS Systems Manager Patch Manager&lt;/a&gt; can automate patching across your fleets. It uses patching policies that scan for and install approved updates on a schedule you define (weekly is recommended). Patch Manager is particularly valuable for fleet-wide VFX workstations because it centralises patching control across multiple accounts and AWS Regions. It supports custom patch baselines, so you can define what counts as compliant for your organisation. It also integrates with &lt;a href="https://aws.amazon.com/security-hub/" target="_blank" rel="noopener"&gt;AWS Security Hub CSPM (Cloud Security Posture Management)&lt;/a&gt; and &lt;a href="https://aws.amazon.com/config/" target="_blank" rel="noopener"&gt;AWS Config&lt;/a&gt; for greater visibility, and it maintains audit trails through &lt;a href="https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-user-guide.html" target="_blank" rel="noopener"&gt;AWS CloudTrail&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="backup-and-recovery"&gt;Backup and recovery&lt;/h3&gt; 
&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html" target="_blank" rel="noopener"&gt;Amazon EBS&lt;/a&gt; snapshots represent a cost-effective, encrypted, point-in-time backup of your instance data (such as the operating system and applications) residing on EBS volumes. They’re stored in Amazon Simple Storage Service (Amazon S3). Incremental versions only store the deltas in data from previously stored volumes (deletions of snapshots only remove unique data associated with that volume). With snapshots, you can retrieve a prior state (snapshot) of an instance and resume work or even turn a snapshot into an AMI for more permanent use. Whilst many companies using VFX workstations on AWS tend to regularly launch new daily instances for their artists (avoiding ‘stopped’ state charges overnight and ensuring artists are using up-to-date AMIs), long-term use of Amazon EC2 instances can use EBS snapshots to instigate disaster recovery preparation against accidents, corruption, or ransomware. It’s vital when using disaster recovery processes such as EBS snapshots, that testing is done to confirm that recovery procedures work when needed.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;This post has covered essential security practices including network controls, IAM policies, encryption, monitoring, and threat detection, which are all foundational elements of a comprehensive security strategy. For production deployments, we strongly recommend consulting the &lt;a href="https://aws.amazon.com/architecture/security-identity-compliance/" target="_blank" rel="noopener"&gt;AWS Security Best Practices documentation&lt;/a&gt; and the &lt;a href="https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/welcome.html" target="_blank" rel="noopener"&gt;AWS Well-Architected Framework Security Pillar&lt;/a&gt; to explore additional security services, compliance frameworks, and industry-specific guidance tailored to your organization’s requirements.&lt;/p&gt; 
&lt;p&gt;For more information contact us at &lt;a class="email" href="mailto:aws-visual-compute-interest@amazon.com"&gt;aws-visual-compute-interest@amazon.com&lt;/a&gt;.&lt;/p&gt; 
&lt;p style="clear: both"&gt; &lt;/p&gt;
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-3.jpg" alt="Andy Hayes" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Andy Hayes&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Andy is a Senior Visual Computing Solutions Architect at AWS. With 20 years’ experience in Visual Effects and Animation, Andy has led CG divisions and departments and added supervision to film projects, earning both Annie and Visual Effects Society Awards along the way. At AWS, he partners with studios and creative technology companies across the Media &amp;amp; Entertainment industry, spanning VFX and animation to rendering, virtual production, and games, helping them design and scale the cloud infrastructure and workflows behind their content pipelines. Drawing on his production background, Andy bridges the worlds of artists and engineers, guiding customers as they adopt technologies like high-performance rendering, GPU compute, and increasingly AI and machine learning to solve real creative and technical challenges. He remains passionate about the marriage of art and science that leads to the creation of compelling imagery, and about aligning technology to the evolving needs of the industry.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-4.jpg" alt="Alex Waddell" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Alex Waddell&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Alex is a Principal Security Specialist SA at AWS, specialising in security within the Worldwide Specialist Organisation (WWSO) GTM Specialists team for EMEA. Based in Scotland, he helps enterprise customers design and build secure, scalable cloud architectures, with a focus on security strategy, identity, threat detection and application security at scale, helping organisations move faster without trading away security. Alex is a regular contributor to the security community and speaks on the real-world challenges of securing modern cloud environments. Alex has been with AWS since 2021 and works across the region to bring security best practice into customer engagements.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2763-5.jpg" alt="Mike Owen" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Mike Owen&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Mike is a Principal Visual Computing Solutions Architect at AWS, where he has spent many years helping studios move their creative work to the cloud. He focuses on the architecture behind high-end content creation: cloud workstations, render farm scaling and storage that spans multiple sites. Mike works with studios and creative technology companies across Media &amp;amp; Entertainment, from VFX and animation to finishing and colour. He has pioneered the concept of “Studio in the Cloud” and helped bring industry tools such as Autodesk Flame to AWS, and has contributed to a range of AWS Thinkbox Deadline improvements. Most recently he has led development of KNFSD File Cache, an open-source NFS caching solution from AWS. It lets studios burst large render workloads into the cloud whilst their data stays on existing on-premises storage. He cares about giving artists the same seamless, colour-accurate experience in the cloud that they expect on-premises, and about removing the cost and complexity that usually come with building a global studio.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations</title>
		<link>https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/</link>
		
		<dc:creator><![CDATA[Andy Hayes]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 15:27:19 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">9180756e298712f8a08e18acd5fb3ec3c83aafe9</guid>

					<description>Part 4 of our series on building GPU workstations for visual effects on Amazon EC2. This post covers standardizing VFX workstation configurations with custom AMIs and launch templates, GPU performance optimizations such as disabling ECC, and security considerations when sharing machine images.</description>
										<content:encoded>&lt;p&gt;For many years, Amazon Web Services (AWS) has been guiding customers in deploying powerful workstations backed by NVIDIA graphics processing units (GPUs) for graphics-intensive workloads. With the recent expansion of our G-series &lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/a&gt; graphics-based instances, we’re excited to introduce new instance families that deliver enhanced performance and capabilities. We’re also refreshing our comprehensive guidance on choosing and configuring these powerful virtual workstations.&lt;/p&gt; 
&lt;p&gt;This is the fourth post in a five-part series, exploring optimizations to support the ready deployment of visual effects (VFX) workstations, using &lt;a href="https://docs.aws.amazon.com/dcv/latest/adminguide/what-is-dcv.html" target="_blank" rel="noopener"&gt;Amazon DCV&lt;/a&gt; as a performant desktop display protocol. The screen capture that follows shows one such workstation running a live visual-effects workload.&lt;/p&gt; 
&lt;blockquote&gt;
 &lt;p&gt;&lt;em&gt;“First there were rocks… Humanity made wheels. Those wheels ground flour and we made progress to sliced bread. Amazon DCV is the best thing since sliced bread.”&lt;/em&gt;&lt;/p&gt; 
 &lt;p&gt;— Chris Coupe, CG Supervisor, Outpost VFX&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-1.png" alt="Rocky Linux workstation running SideFX Houdini, with an internal render shown above the desktop background" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: A screen capture of a Rocky Linux-based workstation&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;This post focuses on several key aspects:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;The consolidation and standardization of VFX workstation instance configurations, to allow simpler launching mechanisms, also facilitating deployments at larger scale (for example, a team of people).&lt;/li&gt; 
 &lt;li&gt;Optimizations to improve performance beyond out-of-the-box setups, with emphasis on GPU acceleration.&lt;/li&gt; 
 &lt;li&gt;Analysis and discussion of security considerations when implementing a VFX workstation on AWS.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt; 
&lt;p&gt;This post assumes that you have deployed a Linux or Windows EC2 instance, for the purposes of creating a GPU workstation.&lt;/p&gt; 
&lt;p&gt;If you want to understand more about GPU-accelerated Amazon EC2 G graphics instances, go to Part 1 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/build-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-1-setup/"&gt;Build a GPU workstation for visual effects on Amazon EC2: Part 1 – Setup&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For deployment instructions for creating a Rocky Linux graphics workstation, go to Part 2 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-2-linux/"&gt;Building a GPU workstation for visual effects on Amazon EC2: Part 2 – Linux&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Finally, for deployment instructions for creating a Windows Server 2025 graphics workstation, go to Part 3 in this series: &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 3 – Windows&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="amazon-machine-images-and-launch-templates"&gt;Amazon Machine Images and launch templates&lt;/h2&gt; 
&lt;p&gt;You have used existing base &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html" target="_blank" rel="noopener"&gt;Amazon Machine Images (AMIs)&lt;/a&gt; as a source for your OS and software, customizing them to your needs. The next step is to produce your own AMIs from these customizations so that you can quickly launch one or more instances from this state in the future. Furthermore, you want to avoid replicating the work that you have just done, while also maintaining a standard environment across the teams that use these instances.&lt;/p&gt; 
&lt;p&gt;Moreover, when you initiated the workstation instances, you also stipulated the networking, security, permissions, and instance type that define the complete instance alongside the AMI. You can wrap all of this information into an &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html" target="_blank" rel="noopener"&gt;Amazon EC2 launch template&lt;/a&gt; to standardize the whole instance, so you can launch it without issues.&lt;/p&gt; 
&lt;p&gt;Note the current size of the &lt;a href="https://aws.amazon.com/ebs/" target="_blank" rel="noopener"&gt;Amazon Elastic Block Store (Amazon EBS)&lt;/a&gt; volume that you are using for your OS and applications on your workstation. When you create an AMI you stipulate the size of the volume to associate with it. Keeping the storage size of the AMI efficient makes sure that your (relatively small) storage costs are optimized and any movement and startup using that AMI are as quick as possible.&lt;/p&gt; 
&lt;p&gt;On Windows, review the size of the C: drive in Windows Explorer by looking at the drive properties, and in a shell in Linux you can use &lt;code&gt;df -h&lt;/code&gt; to review filesystem disk space usage.&lt;/p&gt; 
&lt;h3 id="preparing-a-linux-ami"&gt;Preparing a Linux AMI&lt;/h3&gt; 
&lt;p&gt;To prepare Linux, first stop the instance, if it is running:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;In the Amazon EC2 console, choose &lt;strong&gt;Amazon EC2 Dashboard&lt;/strong&gt; in the top left.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Instances (running)&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose the &lt;code&gt;my_linux_workstation&lt;/code&gt;&amp;nbsp;instance in the top pane.&lt;/li&gt; 
 &lt;li&gt;Open the context menu for the instance, and choose &lt;strong&gt;Stop instance&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Wait for the &lt;strong&gt;Instance state&lt;/strong&gt; to move from &lt;strong&gt;Running&lt;/strong&gt; to &lt;strong&gt;Stopped&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="preparing-a-windows-ami"&gt;Preparing a Windows AMI&lt;/h3&gt; 
&lt;p&gt;Windows Server 2025 uses the agent &lt;strong&gt;EC2Launchv2&lt;/strong&gt; on bootup to perform system tasks. You must configure the agent before shutting down the instance, prior to making an AMI, through the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launch-v2-settings.html" target="_blank" rel="noopener"&gt;Amazon EC2LaunchSettings&lt;/a&gt; application. The following screen capture shows the EC2Launch Settings application, where you set the boot-time behavior of the agent. In this example, the General tab is open. This tab controls launch-time options for the instance, such as setting the instance name and configuring the administrator username and password.&lt;/p&gt; 
&lt;div style="width: 455px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-2.png" alt="Amazon EC2Launch Settings application open on the General tab, showing instance launch options" width="445"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: A screen capture of the Amazon EC2Launch Settings application, used to configure the EC2Launch agent on bootup&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;On your Windows instance, open the &lt;strong&gt;Amazon EC2Launch settings&lt;/strong&gt; application.&lt;/p&gt; 
&lt;p&gt;This application controls which tasks the agent performs on boot. Pertinent options to enable are as follows:&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Host name&lt;/strong&gt;:&lt;/p&gt; 
&lt;ol type="a"&gt; 
 &lt;li&gt;Turn on “Set the compute name of the instance”, and set it to &lt;code&gt;ip-&amp;lt;hex primary IP address&amp;gt;&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Turn on “Reboot after setting Computer Name”.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;This makes sure that the compute host name is unique upon booting for future considerations toward Active Directory, render farms, and so on.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Password&lt;/strong&gt;&lt;/p&gt; 
&lt;ol start="3" type="a"&gt; 
 &lt;li&gt;Turn on &lt;strong&gt;Set the administrator account&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Set the &lt;strong&gt;Administrator username&lt;/strong&gt; (for example, Administrator).&lt;/li&gt; 
 &lt;li&gt;Specify the &lt;strong&gt;Administrator password&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;This can be the same as what you previously set before, or you can change it.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Wallpaper&lt;/strong&gt; (on the third tab)&lt;/p&gt; 
&lt;p&gt;You can specify the custom Windows wallpaper and stat burn-in of various instance parameters.&lt;/p&gt; 
&lt;ol start="6" type="a"&gt; 
 &lt;li&gt;When you have made your changes, choose &lt;strong&gt;Save&lt;/strong&gt; at the bottom of the screen to save your configuration changes.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;You have two choices to shut down based on &lt;strong&gt;Sysprep&lt;/strong&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Shut down without Sysprep&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;This option is useful if you have embedded information on the image that you want to retain (for example, local users for processes) that would otherwise be removed by Sysprep.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Shut down with Sysprep&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;For removing PC-specific information for future AMI consideration:&lt;/p&gt; 
&lt;ol start="7" type="a"&gt; 
 &lt;li&gt;Shut down with Sysprep on this occasion. The machine automatically shuts down.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;Wait for the &lt;strong&gt;Instance state&lt;/strong&gt; to move from &lt;strong&gt;Running&lt;/strong&gt; to &lt;strong&gt;Stopped&lt;/strong&gt;.&lt;/p&gt; 
&lt;p&gt;You can find more information about Amazon EC2 Launch in the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launch-v2.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="creating-the-ami"&gt;Creating the AMI&lt;/h3&gt; 
&lt;p&gt;When your instances are in the &lt;strong&gt;Stopped&lt;/strong&gt; state, you can proceed with making your &lt;strong&gt;AMI&lt;/strong&gt;.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;In the Amazon EC2 console, choose &lt;strong&gt;Instances&lt;/strong&gt; in the top left.&lt;/li&gt; 
 &lt;li&gt;Choose your workstation instance by selecting the checkbox next to its name.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Actions&lt;/strong&gt; from the top right of the pane, and choose &lt;strong&gt;Image and templates&lt;/strong&gt;, &lt;strong&gt;Create image&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;In the &lt;strong&gt;Create image&lt;/strong&gt; page, specify the options for your AMI:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Give your &lt;strong&gt;AMI&lt;/strong&gt; an Image name. You might want to consider versions in the &lt;strong&gt;AMI&lt;/strong&gt; name. 
  &lt;ol type="a"&gt; 
   &lt;li&gt;For example, &lt;code&gt;VFX_Workstation_Linux_v001&lt;/code&gt;.&lt;/li&gt; 
  &lt;/ol&gt; &lt;/li&gt; 
 &lt;li&gt;Give your &lt;strong&gt;AMI&lt;/strong&gt; a relevant Image description. 
  &lt;ol type="a"&gt; 
   &lt;li&gt;For example, &lt;code&gt;base build, with GPU, WACOM, CLI&lt;/code&gt;.&lt;/li&gt; 
  &lt;/ol&gt; &lt;/li&gt; 
 &lt;li&gt;The &lt;strong&gt;Size&lt;/strong&gt; of your storage can be specified. As mentioned previously, consider reducing this down to something that is more aligned with your actual usage, such as usage + 20 percent.&lt;/li&gt; 
 &lt;li&gt;Consider adding a new tag to give your AMI a discernible name. 
  &lt;ol type="a"&gt; 
   &lt;li&gt;For example, add a &lt;strong&gt;Name&lt;/strong&gt; tag key, and paste the &lt;strong&gt;Image name&lt;/strong&gt; as the value.&lt;/li&gt; 
  &lt;/ol&gt; &lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create image&lt;/strong&gt; to make the AMI. This can take several minutes to complete.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;Amazon EC2 AMIs can be shared across accounts and Regions, which lets teams standardize workstation configurations and deploy them quickly. Because a VFX workstation AMI often bakes in licensed digital content creation (DCC) tools, render plugins, studio tooling, and credentials, treat it as a controlled asset rather than something to share broadly.&lt;/p&gt; 
&lt;p&gt;Share each AMI only with the specific accounts that need it and prefer sharing with named AWS account IDs over making an AMI public. Before you share, confirm the image contains no embedded secrets such as application API keys, license tokens, or SSH keys baked in during the build. Audit your sharing configuration periodically so access does not outlive its purpose and revoke it when a team or project no longer needs the image.&lt;/p&gt; 
&lt;h2 id="creating-a-launch-template"&gt;Creating a launch template&lt;/h2&gt; 
&lt;p&gt;When you launched the EC2 instance, as well as the AMI to use, you also stipulated other options that were important to define how the machine launched, such as the network, security groups, and roles. Rather than do this each time that you want to start an instance, you can combine all this information, and more, into an &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-launch-template.html" target="_blank" rel="noopener"&gt;Amazon EC2 launch template&lt;/a&gt;. You can then quickly launch machines in the future, or combine them with other brokering and scaling mechanisms to control larger usage of the machines. This is useful for studios with multiple artists, or render farms with multiple machines, all using standardized environments.&lt;/p&gt; 
&lt;p&gt;You can build a launch template through the Amazon EC2 console:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;In the Amazon EC2 console, choose &lt;strong&gt;Launch Templates&lt;/strong&gt; under the &lt;strong&gt;Instances&lt;/strong&gt; section on the left.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create launch template&lt;/strong&gt; on the right side of the pane.&lt;/li&gt; 
 &lt;li&gt;Provide a &lt;strong&gt;Launch template name&lt;/strong&gt; and &lt;strong&gt;description&lt;/strong&gt; in the relevant boxes.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;blockquote&gt;
 &lt;p&gt;Launch templates are versioned, so there is no need to add a version number to its name.&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;ol start="4" type="1"&gt; 
 &lt;li&gt;For the AMI, choose &lt;strong&gt;My AMIs&lt;/strong&gt; and choose the relevant AMI that you made in the previous steps.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Instance type&lt;/strong&gt; choose &lt;strong&gt;g6.4xlarge&lt;/strong&gt;. This is the default size for your template (but this and all values can be overridden at launch time if you wish).&lt;/li&gt; 
 &lt;li&gt;Provide your &lt;code&gt;ec2_test_keypair&lt;/code&gt;&amp;nbsp;in the &lt;strong&gt;Key pair (login)&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Edit the &lt;strong&gt;Network settings&lt;/strong&gt; to adjust security and network placement: 
  &lt;ol type="a"&gt; 
   &lt;li&gt;Leave the &lt;strong&gt;Subnet&lt;/strong&gt; to &lt;strong&gt;Don’t include in launch template&lt;/strong&gt;.&lt;/li&gt; 
   &lt;li&gt;Under the &lt;strong&gt;Firewall (security groups)&lt;/strong&gt; section of the &lt;strong&gt;Network Settings&lt;/strong&gt;, choose &lt;strong&gt;Select existing security group&lt;/strong&gt;, and choose the “ec2_test_sg” that you made earlier to set up the firewall for the machine.&lt;/li&gt; 
  &lt;/ol&gt; &lt;/li&gt; 
 &lt;li&gt;In &lt;strong&gt;Resource tags&lt;/strong&gt;, add a &lt;strong&gt;Name&lt;/strong&gt; key tag, with a value of &lt;code&gt;my_workstation&lt;/code&gt;&amp;nbsp;or another suitable name.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Advanced details&lt;/strong&gt;, specify the &lt;code&gt;basic_workstation_role&lt;/code&gt; that you made previously through the &lt;strong&gt;IAM instance profile&lt;/strong&gt; list, to allow your workstation to access more services.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;There are many other options that you can explore in launch templates. A useful feature is found at the bottom of the Advanced details: the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html" target="_blank" rel="noopener"&gt;User data&lt;/a&gt;. With user data, you can enter Windows PowerShell or Linux shell commands to run on boot, adding configurations or modifications on top of the AMI. This circumvents the need to publish new AMIs for certain kinds of change. An example of this can be found in the following GPU performance optimization section, but for now you can finish making the launch template.&lt;/p&gt; 
&lt;ol start="10" type="1"&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create launch template&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;When you return to the &lt;strong&gt;Launch templates&lt;/strong&gt; dashboard, your newly created template appears in the list. Select the template, then choose &lt;strong&gt;Launch instance from template&lt;/strong&gt; from the &lt;strong&gt;Actions&lt;/strong&gt; menu to open a dialog for launching a new instance from it. The dialog shows the template’s values and lets you adjust any setting before launch. You can also modify a template to create new versions and set a default version. This way, you can keep multiple versions for comparison while clearly marking which one to use by default. The following screen capture shows the dialog, where you confirm the source template and version and optionally override its settings before launching.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-3.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-3.png" alt="Amazon EC2 launch template dialog showing the source template and version, with options to override settings before launching an instance" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 3: The Amazon EC2 launch template UI can be used to quickly start an instance, with options to override existing parameters&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Launch templates can be used in other services to streamline and control instance starting mechanisms at scale, such as &lt;a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/auto-scaling-groups.html" target="_blank" rel="noopener"&gt;Amazon EC2 Auto Scaling groups&lt;/a&gt;, as well as third-party services listed in the Further reading section.&lt;/p&gt; 
&lt;blockquote&gt;
 &lt;p&gt;This post demonstrates how to build an AMI in manual steps. There are alternate services to create an AMI that can cater to larger scaling mechanisms to support productions. For example, &lt;a href="https://docs.aws.amazon.com/imagebuilder/latest/userguide/what-is-image-builder.html" target="_blank" rel="noopener"&gt;Amazon EC2 Image Builder&lt;/a&gt; allows you to define recipes and schedules for automating the creation of AMIs.&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;h2 id="gpu-performance-optimization"&gt;GPU performance optimization&lt;/h2&gt; 
&lt;p&gt;There’s dedicated AWS documentation in the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/optimize_gpu.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt; regarding GPU optimizations. This includes initializing the persistent driver kernel on Linux, to keep GPU states initialized regardless of client connections:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;sudo nvidia-persistenced&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;It also includes documenting how to turn off GPU autoboost, for slightly more efficient GPU usage. This option should be considered and evaluated on a per-application basis to ascertain positive or negative impact on performance. Go to the preceding documentation for more information.&lt;/p&gt; 
&lt;p&gt;Outside of the official documentation on AWS, for VFX-specific workloads a further optimization can be made regarding NVIDIA Error Correction Code (ECC). Amazon EC2 G instance family types use NVIDIA data center cards, designed for high performance computing. These differ from the consumer-style cards typically found in individual workstations in offices. On data center cards, ECC is provisioned and enabled as a method to introspectively look for potential pixel errors because of bit flipping through phenomena such as cosmic ray interaction, and fix any errors found.&lt;/p&gt; 
&lt;p&gt;You should consider deactivating this feature to reduce the overhead of memory checking on the GPU, to gain performance. ECC isn’t typically available on consumer GPU cards, so many customers’ workloads haven’t relied on this error-correction feature in the first place. If debugging requires it, the feature can be quickly re-enabled.&lt;/p&gt; 
&lt;p&gt;ECC is activated on every fresh start of an EC2 instance, and disabling necessitates a reboot. You can automate turning it off with a traditional startup script, or with the previously mentioned &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html" target="_blank" rel="noopener"&gt;User data&lt;/a&gt; script as part of the launch template.&lt;/p&gt; 
&lt;p&gt;For a Windows instance, you can add the User data script by inserting it between leading and trailing &lt;code&gt;powershell&lt;/code&gt; elements to define a PowerShell script, with the &lt;code&gt;persist&lt;/code&gt; element added so the script runs again on each reboot cycle, and not only on the first boot.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;&amp;lt;powershell&amp;gt;
Write-Host 'ECC Checking'
if (&amp;amp;'nvidia-smi.exe' -q -d ECC | Select-String "Enabled")
{
    &amp;amp;'nvidia-smi.exe' -e 0
    Write-Host 'ECC Enabled: Turning off ECC'
    Restart-Computer
} else {
    Write-Host 'ECC Disabled: Nothing to do.'
}
&amp;lt;/powershell&amp;gt;
&amp;lt;persist&amp;gt;true&amp;lt;/persist&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;For a Linux instance, you can enter a shell script:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;#!/bin/sh
if ( /usr/bin/nvidia-smi -q -d ECC | grep -q 'Enabled')
then
    echo "ECC Enabled: Turning off ECC"
    sudo nvidia-smi -e 0
    sudo reboot
else
    echo "ECC Disabled: Nothing to do."
fi&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;User data is a mechanism to make changes to EC2 instances, without reverting to changing the underlying AMI. However, you should avoid hardcoding and storing sensitive data in it, that might pose a visible compliance or security risk. &lt;a href="https://aws.amazon.com/secrets-manager/" target="_blank" rel="noopener"&gt;AWS Secrets Manager&lt;/a&gt; can be used to obfuscate sensitive data, as it stores and manages the lifecycle of secrets, and provides robust mechanisms to pass that data programmatically into process within a user data context.&lt;/p&gt; 
&lt;h2 id="cleaning-up"&gt;Cleaning up&lt;/h2&gt; 
&lt;p&gt;Remember to turn off your instances when not in use. You can turn them off either through the &lt;a href="https://aws.amazon.com/console/" target="_blank" rel="noopener"&gt;AWS Management Console&lt;/a&gt;, or through other programmatic methods such as the &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;. You incur costs associated with a running machine, so deactivating machines when not in use reduces your expenditure.&lt;/p&gt; 
&lt;p&gt;There are two different options for deactivating an EC2 instance: &lt;strong&gt;stopping&lt;/strong&gt; and &lt;strong&gt;terminating&lt;/strong&gt;.&lt;/p&gt; 
&lt;h3 id="stopping"&gt;Stopping&lt;/h3&gt; 
&lt;p&gt;When you stop an instance, its Amazon EBS volumes remain attached and their data is retained, so your work on the EBS volume persists while the instance is deactivated. Data held in memory (RAM) is not preserved, and neither is any data on the instance store (NVMe) volumes (that data is lost when the instance stops).&lt;/p&gt; 
&lt;p&gt;You perform this operation by choosing the instance from the Amazon EC2 console, and under the &lt;strong&gt;Instance state&lt;/strong&gt; options you can elect to &lt;strong&gt;Stop instance&lt;/strong&gt;. The instance remains in your console, with a “Stopped” state, but the persistent volumes enable you to restart the instance and resume your session when you want, retaining any changes that you made to the main volume. You can restart an instance by using the &lt;strong&gt;Start instance&lt;/strong&gt; operation under the &lt;strong&gt;Instance state&lt;/strong&gt; options.&lt;/p&gt; 
&lt;p&gt;When an instance is “Stopped”, you don’t pay for the instance itself but incur a &lt;a href="https://aws.amazon.com/ebs/pricing/" target="_blank" rel="noopener"&gt;smaller charge&lt;/a&gt; for the storage of the volume.&lt;/p&gt; 
&lt;h3 id="terminating"&gt;Terminating&lt;/h3&gt; 
&lt;p&gt;This operation deactivates the instance and does not retain any information locally stored. You can’t restart a terminated instance.&lt;/p&gt; 
&lt;p&gt;To terminate an instance, choose &lt;strong&gt;Terminate instance&lt;/strong&gt; from the &lt;strong&gt;Instance state&lt;/strong&gt; options on the Amazon EC2 console. The instance shuts down and reports a “Terminated” state on the console, and automatically disappears after a short time.&lt;/p&gt; 
&lt;p&gt;For more information about Amazon EC2 lifecycles, options, and billing, go to the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-lifecycle.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;This post has demonstrated how existing base AMIs can be used as a source for creating a custom VFX workstation, with further GPU optimizations applied to increase performance. These customizations can be published as new AMIs themselves for quick redeployment of that machine setup. Then, you integrated this AMI into a launch template to specify the complete array of startup requirements needed for a workstation, for quick and standardized deployment of machines.&lt;/p&gt; 
&lt;p&gt;We recommend that you continue to the final Part 5 of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-5-security/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 5 – Security&lt;/a&gt;, to explore security practices related to the deployment of visual effects (VFX) workstations. This post examines how to secure these workstations by controlling who can reach the desktop, protecting the session in transit, and safeguarding the credentials, images, and storage behind it.&lt;/p&gt; 
&lt;p&gt;For more information, contact us at &lt;a class="email" href="mailto:aws-visual-compute-interest@amazon.com"&gt;aws-visual-compute-interest@amazon.com&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="further-reading"&gt;Further reading&lt;/h2&gt; 
&lt;p&gt;If you want to augment a VFX workstation environment with a dedicated render farm, then consider the managed service &lt;a href="https://aws.amazon.com/deadline-cloud/" target="_blank" rel="noopener"&gt;AWS Deadline Cloud&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;EC2 instance metrics, such as CPU and memory usage, are readily sent to &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; logs, allowing you to access this data through the console and AWS CLI. This information can be pertinent to discern if an EC2 instance is being over-provisioned or under-provisioned for the work at hand. For example, it has excessive CPU, memory, and networking resources for the current tasks and could be optimized for price, or the alternative where it has not been allocated enough resources to cope. For more information, visit the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring_ec2.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Windows instances can be lengthy to boot. &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/win-ami-config-fast-launch.html" target="_blank" rel="noopener"&gt;Amazon EC2 Fast Launch for Windows&lt;/a&gt; is an AWS facility for quicker launching of Windows machines through smart snapshots of the AMI.&lt;/p&gt; 
&lt;p&gt;The following post shows &lt;a href="https://aws.amazon.com/blogs/compute/managing-domain-membership-of-dynamic-fleet-of-ec2-instances/" target="_blank" rel="noopener"&gt;how to programmatically configure a Windows EC2 instance as part of a domain&lt;/a&gt;. This is particularly useful when the instances are used ephemerally, for example as part of a fleet of instances that spool up and down for the purposes of rendering, and you need methods to bind and remove instances quickly.&lt;/p&gt; 
&lt;p&gt;Commercial options also exist to perform artist/instance brokering, using Amazon DCV and Amazon EC2 launch templates. An example of this offering is &lt;a href="https://leostream.com/" target="_blank" rel="noopener"&gt;Leostream&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-4.jpg" alt="Andy Hayes" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Andy Hayes&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Andy is a Senior Visual Computing Solutions Architect at AWS. With 20 years’ experience in Visual Effects and Animation, Andy has led CG divisions and departments and added supervision to film projects, earning both Annie and Visual Effects Society Awards along the way. At AWS, he partners with studios and creative technology companies across the Media &amp;amp; Entertainment industry, spanning VFX and animation to rendering, virtual production, and games, helping them design and scale the cloud infrastructure and workflows behind their content pipelines. Drawing on his production background, Andy bridges the worlds of artists and engineers, guiding customers as they adopt technologies like high-performance rendering, GPU compute, and increasingly AI and machine learning to solve real creative and technical challenges. He remains passionate about the marriage of art and science that leads to the creation of compelling imagery, and about aligning technology to the evolving needs of the industry.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2762-5.jpg" alt="Mike Owen" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Mike Owen&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Mike is a Principal Visual Computing Solutions Architect at AWS, where he has spent many years helping studios move their creative work to the cloud. He focuses on the architecture behind high-end content creation: cloud workstations, render farm scaling and storage that spans multiple sites. Mike works with studios and creative technology companies across Media &amp;amp; Entertainment, from VFX and animation to finishing and colour. He has pioneered the concept of “Studio in the Cloud” and helped bring industry tools such as Autodesk Flame to AWS, and has contributed to a range of AWS Thinkbox Deadline improvements. Most recently he has led development of KNFSD File Cache, an open-source NFS caching solution from AWS. It lets studios burst large render workloads into the cloud whilst their data stays on existing on-premises storage. He cares about giving artists the same seamless, colour-accurate experience in the cloud that they expect on-premises, and about removing the cost and complexity that usually come with building a global studio.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Building a GPU workstation for visual effects with Amazon EC2: Part 3 – Windows</title>
		<link>https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows/</link>
		
		<dc:creator><![CDATA[Andy Hayes]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 15:27:16 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">1b57ce2ac1c6a59b35ad2afd2c9234fe114161b9</guid>

					<description>The third post in a five-part series on building GPU-backed VFX workstations on Amazon EC2. This post walks through deploying a Windows Server 2025 workstation with NVIDIA GPU drivers, Amazon DCV as the remote display protocol, and Wacom stylus support for a high-performance remote creative environment.</description>
										<content:encoded>&lt;p&gt;For many years Amazon Web Services (AWS) has been guiding customers in the deployment of powerful NVIDIA GPU-backed workstations for graphics-intensive workloads. With the recent expansion of our G-series &lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/a&gt; graphics-based instances, we are excited to introduce new instance families that deliver enhanced performance and capabilities. We are also refreshing our comprehensive guidance on choosing and configuring these powerful virtual workstations.&lt;/p&gt; 
&lt;p&gt;This is the third post in a five-part series, focusing on the deployment of a Windows Server 2025 visual effects (VFX) workstation, using &lt;a href="https://docs.aws.amazon.com/dcv/latest/adminguide/what-is-dcv.html" target="_blank" rel="noopener"&gt;Amazon DCV&lt;/a&gt; as a performant desktop display protocol.&lt;/p&gt; 
&lt;blockquote&gt;
 &lt;p&gt;&lt;em&gt;“Amazon DCV has unlocked previously unrealised playback performance, that has massively increased my productivity. Amazon DCV is performant on a range of systems and where other solutions have failed, I have been able to continue working and most importantly, continue delivering”&lt;/em&gt;&lt;/p&gt; 
 &lt;p&gt;— Chris Coupe, CG Supervisor, Outpost VFX&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt; 
&lt;p&gt;This post assumes that you have configured the following:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;An active AWS account with increased GPU Amazon EC2 service quota limits.&lt;/li&gt; 
 &lt;li&gt;A valid key pair in your &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regions_az/" target="_blank" rel="noopener"&gt;AWS Region&lt;/a&gt; of choice.&lt;/li&gt; 
 &lt;li&gt;A configured virtual firewall security group, with open TCP/UDP ports 22, 443, 8443, and 3389 limited to only your own IP address.&lt;/li&gt; 
 &lt;li&gt;An &lt;a href="https://aws.amazon.com/iam/" target="_blank" rel="noopener"&gt;AWS Identity and Access Management (IAM)&lt;/a&gt; profile with least-permissions &lt;a href="https://aws.amazon.com/s3/" target="_blank" rel="noopener"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt; read access.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;We strongly recommend that you follow Part 1 of the series, &lt;a href="https://aws.amazon.com/blogs/compute/build-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-1-setup/"&gt;Build a GPU workstation for visual effects on Amazon EC2: Part 1 – Setup&lt;/a&gt;, which goes through the preceding steps in detail.&lt;/p&gt; 
&lt;h2 id="launching-the-windows-workstation"&gt;Launching the Windows workstation&lt;/h2&gt; 
&lt;p&gt;We use the latest AWS provided Windows Server 2025 &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html" target="_blank" rel="noopener"&gt;Amazon Machine Image (AMI)&lt;/a&gt; for our deployment, and install the NVIDIA, Amazon DCV, and Wacom components to create a fully functioning VFX Windows desktop environment.&lt;/p&gt; 
&lt;p&gt;Follow these steps to launch a g6.4xlarge instance in your chosen AWS Region. If you want to use multiple GPU cards (for example, by using the 12xlarge, 24xlarge, or 48xlarge instance types), then Windows requires you to have that number of GPU cards present when setting up the GPU driver. In this case, we recommend starting the relevant multiple GPU instance size when making your AMI.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Log in to the &lt;strong&gt;AWS Management Console&lt;/strong&gt; and choose &lt;strong&gt;EC2 Dashboard&lt;/strong&gt; in the top left.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Launch instances&lt;/strong&gt; to start the prompt to launch a new instance.&lt;/li&gt; 
 &lt;li&gt;Give the instance a name, for example &lt;code&gt;my_windows_workstation&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Windows&lt;/strong&gt; under the &lt;strong&gt;Quick Start AMI&lt;/strong&gt; and use the default &lt;strong&gt;Microsoft Windows Server Base Image 2025&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Instance type&lt;/strong&gt;, choose &lt;strong&gt;g6.4xlarge&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Key pair name&lt;/strong&gt;, choose the menu and choose your key pair. In the previous post we called it &lt;code&gt;ec2_test_keypair&lt;/code&gt; to specify the password security credentials.&lt;/li&gt; 
 &lt;li&gt;Edit the &lt;strong&gt;Network settings&lt;/strong&gt; to adjust security and network placement: 
  &lt;ol type="a"&gt; 
   &lt;li&gt;Leave the &lt;strong&gt;Subnet&lt;/strong&gt; to &lt;strong&gt;No preference&lt;/strong&gt;.&lt;/li&gt; 
   &lt;li&gt;Make sure that &lt;strong&gt;Auto-assign public IP&lt;/strong&gt; is set to &lt;strong&gt;Enable&lt;/strong&gt;, so that you can access the instance through the internet.&lt;/li&gt; 
  &lt;/ol&gt; &lt;/li&gt; 
 &lt;li&gt;Under the &lt;strong&gt;Firewall (security groups)&lt;/strong&gt; section of the &lt;strong&gt;Network Settings&lt;/strong&gt;, choose &lt;strong&gt;Select existing security group&lt;/strong&gt;, and specify your security group. In the previous post we named it &lt;code&gt;ec2_test_sg&lt;/code&gt; to set up the firewall for the machine.&lt;/li&gt; 
 &lt;li&gt;In Configuration storage, expand the default root volume from 10 GiB to 50 GiB of gp3 storage.&lt;strong&gt;Important&lt;/strong&gt;: Turn on encryption in the Advanced options by selecting the Encrypted option and selecting the default AWS managed key (aws/ebs) or a customer-managed KMS key for enhanced control. Amazon Elastic Block Store (Amazon EBS) encryption protects your VFX project files, renders, and application data at rest. Encryption uses industry-standard AES-256 encryption and is transparent to applications with minimal performance impact.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Advanced details&lt;/strong&gt;, specify the role that you created for workstation usage. In the previous post we called it &lt;code&gt;basic_workstation_role&lt;/code&gt; through the &lt;strong&gt;IAM instance profile&lt;/strong&gt; menu, so your workstation can access more services.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Launch instance&lt;/strong&gt; on the right-hand side, as shown in the following figure.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;Choose the link to the EC2 instance that has been launched, or view it through the &lt;strong&gt;Instances&lt;/strong&gt; pane in the &lt;strong&gt;Amazon EC2 Service&lt;/strong&gt; page. The following screen capture shows the newly launched workstation in the EC2 Instances list, where you can confirm it is ready to use. Wait until the &lt;code&gt;my_windows_workstation&lt;/code&gt; instance shows an Instance state of &lt;strong&gt;Running&lt;/strong&gt; and a Status check of 3/3 checks passed. Once both conditions are met, you can continue.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-1.png" alt="EC2 Instances page showing the my_windows_workstation instance with an Instance state of Running and a Status check of 3/3 checks passed" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: A screen capture of the EC2 Instances page, showing the my_windows_workstation in a ready state&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="configuring-the-windows-workstation"&gt;Configuring the Windows workstation&lt;/h2&gt; 
&lt;p&gt;In the last part of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations&lt;/a&gt;, we show how to add scripting capabilities to the boot sequence of EC2 instances. This runs processes such as the NVIDIA GPU driver and Wacom tablet driver automatically during the startup of a machine. For the purposes of this post, we take a more manual approach, showing how you can remote into the machine to perform setup tasks.&lt;/p&gt; 
&lt;p&gt;You initially connect to the instance through the &lt;strong&gt;Windows Remote Desktop Protocol (RDP)&lt;/strong&gt;. In the Amazon EC2 Service page browser tab with the list of EC2 instances running, again choose the &lt;code&gt;my_windows_workstation&lt;/code&gt; and choose &lt;strong&gt;Connect&lt;/strong&gt;.&lt;/p&gt; 
&lt;p&gt;Choose the &lt;strong&gt;RDP client&lt;/strong&gt; tab to connect to the machine through RDP with the following steps:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Choose the &lt;strong&gt;Get password&lt;/strong&gt; option to retrieve the Administrator password for the machine through your key pair credential.&lt;/li&gt; 
 &lt;li&gt;Upload the private &lt;code&gt;ec2_test_keypair&lt;/code&gt; .pem key file that you downloaded previously and choose &lt;strong&gt;Decrypt password&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;The password is now displayed. Copy the password into the clipboard memory by choosing the copy icon, and choose &lt;strong&gt;OK&lt;/strong&gt;, as shown in the following figure.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;div style="width: 469px" class="wp-caption aligncenter"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-2.png" target="_blank" rel="noopener"&gt;&lt;img loading="lazy" class="" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-2.png" alt="Get Windows Password page showing the instance ID, the private IP address, the username, and a redacted password" width="459" height="164"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: A screen capture of the Get Windows Password retrieval options available to EC2 instances&lt;/p&gt;
&lt;/div&gt; 
&lt;ol start="4" type="1"&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Download remote desktop file&lt;/strong&gt; to download the &lt;strong&gt;.rdp&lt;/strong&gt; file to your local machine.&lt;/li&gt; 
 &lt;li&gt;Run the &lt;strong&gt;.rdp&lt;/strong&gt; file with your &lt;strong&gt;Remote Desktop Application&lt;/strong&gt; of choice.&lt;/li&gt; 
 &lt;li&gt;When prompted, paste the previously copied &lt;code&gt;Administrator&lt;/code&gt; password and choose &lt;strong&gt;OK&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Yes&lt;/strong&gt; to trust the machine, and the session is authenticated and opened.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="security"&gt;Security&lt;/h3&gt; 
&lt;p&gt;We recommend setting a new, private password when you first start the fresh instance.&lt;/p&gt; 
&lt;p&gt;Open a &lt;strong&gt;Windows PowerShell&lt;/strong&gt; to configure and make changes to the workstation. In the shell, configure that change and store your new password in a safe place.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-powershell"&gt;net user Administrator &amp;lt;&amp;lt;NewPassword&amp;gt;&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="tools"&gt;Tools&lt;/h3&gt; 
&lt;p&gt;To install the &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt; enter the following into the shell, and follow the on-screen prompts:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-powershell"&gt;msiexec.exe /i https://awscli.amazonaws.com/AWSCLIV2.msi&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="graphics"&gt;Graphics&lt;/h3&gt; 
&lt;p&gt;You must use AWS approved NVIDIA GPU drivers, issued through Amazon S3, not only for optimal compatibility and performance, but also to make sure that the necessary professional GRID drivers are automatically provisioned. You can always find the latest instructions in the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html#nvidia-GRID-driver" target="_blank" rel="noopener"&gt;Amazon EC2 Windows User Guide&lt;/a&gt;. At the time of writing, you can download the latest version to your desktop by running the following in a new Windows PowerShell:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-powershell"&gt;$Bucket = "ec2-windows-nvidia-drivers"
$KeyPrefix = "latest"
$LocalPath = "$home\Desktop\NVIDIA"
$Objects = Get-S3Object -BucketName $Bucket -KeyPrefix $KeyPrefix -Region us-east-1
foreach ($Object in $Objects) {
    $LocalFileName = $Object.Key
    if ($LocalFileName -ne '' -and $Object.Size -ne 0) {
        $LocalFilePath = Join-Path $LocalPath $LocalFileName
        Copy-S3Object -BucketName $Bucket -Key $Object.Key -LocalFile $LocalFilePath -Region us-east-1
    }
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;When it is downloaded, navigate to your Desktop, open the &lt;strong&gt;NVIDIA&lt;/strong&gt; folder, then the &lt;strong&gt;latest&lt;/strong&gt; folder inside, and run the NVIDIA installer executable, following the instructions.&lt;/p&gt; 
&lt;h3 id="wacom-support-and-wacom-bridge"&gt;Wacom support and Wacom Bridge&lt;/h3&gt; 
&lt;p&gt;To add Wacom stylus support on the workstation, open &lt;strong&gt;Microsoft Edge&lt;/strong&gt; (or install your browser of choice) and download and install the latest drivers from the &lt;a href="https://www.wacom.com/en-us/support/product-support/drivers" target="_blank" rel="noopener"&gt;Wacom drivers page&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Wacom Bridge is now generally available on Windows and Mac, and offers new advantages for Wacom users on AWS:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Applications running locally and remotely on AWS transfer their Wacom-specific settings automatically.&lt;/li&gt; 
 &lt;li&gt;Artists can switch from local to remote use of the pen by choosing the necessary application window.&lt;/li&gt; 
 &lt;li&gt;Wacom Inkline draws an instant temporary line on your screen, to bridge any gap between the local pen tip and the remote drawn line.&lt;/li&gt; 
 &lt;li&gt;Amazon DCV provides enhanced security through data transport encrypted through HTTPS/TLS connections.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;You can purchase a Wacom Bridge license (or request a trial) from a &lt;a href="https://www.wacom.com/en-us/enterprise/creative-workflow-solutions/software-solutions#wacom-bridge-contact-form" target="_blank" rel="noopener"&gt;Wacom Sales representative&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="amazon-dcv-setup"&gt;Amazon DCV setup&lt;/h3&gt; 
&lt;p&gt;To use Amazon DCV, you need to download the server application for the Amazon EC2 workstation from &lt;a class="uri" href="https://www.amazondcv.com/" target="_blank" rel="noopener"&gt;https://www.amazondcv.com/&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;On the Amazon EC2 workstation, open the preceding link in your browser of choice, expand the latest &lt;strong&gt;Amazon DCV Server&lt;/strong&gt; entry (2026.0 at the time of this post), choose the &lt;strong&gt;Windows (x86_64)&lt;/strong&gt; link, download the installer, and run it. The default options automatically configure firewall entries for the Amazon DCV server ports, and start the Amazon DCV server.&lt;/p&gt; 
&lt;h3 id="instance-store-setup"&gt;Instance store setup&lt;/h3&gt; 
&lt;p&gt;Finally, consider setting up the instance store on the instance:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;In the search bar at the bottom of the screen, enter &lt;code&gt;Computer Management&lt;/code&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Disk Management&lt;/strong&gt; in the left pane.&lt;/li&gt; 
 &lt;li&gt;If prompted, then choose &lt;strong&gt;OK&lt;/strong&gt; to accept the requested formatting of the instance store. The following figure shows such a prompt.&lt;/li&gt; 
 &lt;li&gt;Open the context menu for the &lt;strong&gt;Unallocated&lt;/strong&gt; drive and choose &lt;strong&gt;New Simple Volume&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Accept the requests, making any wanted changes to the drive name, or assigning to a folder instead.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Finish&lt;/strong&gt; and the new volume is available to use as a temporary drive.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;div style="width: 734px" class="wp-caption aligncenter"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-3.png" target="_blank" rel="noopener"&gt;&lt;img loading="lazy" class="" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-3.png" alt="Disk Management prompt requesting automatic formatting of the newly found instance store" width="724" height="519"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 3: The Disk Management tool prompting the automatic formatting of the instance store&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Proceed to the next section to log in to your workstation to use Amazon DCV.&lt;/p&gt; 
&lt;h2 id="logging-into-your-workstation-through-amazon-dcv"&gt;Logging into your workstation through Amazon DCV&lt;/h2&gt; 
&lt;p&gt;To log in to your machine using Amazon DCV, you must first set up the client software on your local machine:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;On your local machine or laptop, open &lt;a href="https://www.amazondcv.com/" target="_blank" rel="noopener"&gt;Amazon DCV&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;Expand the &lt;strong&gt;Amazon DCV Client&lt;/strong&gt; entry that matches the &lt;strong&gt;Server&lt;/strong&gt; version that you installed on your workstation.&lt;/li&gt; 
 &lt;li&gt;Choose the relevant OS for your machine or laptop, for example &lt;strong&gt;Windows (x86_64)&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Download the installer.&lt;/li&gt; 
 &lt;li&gt;Run the installer.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;When it is installed, you must determine the public IP address of the workstation to connect to:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;In the &lt;strong&gt;Amazon EC2 Console&lt;/strong&gt;, choose &lt;strong&gt;Amazon EC2 Dashboard&lt;/strong&gt; in the top left.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Instances (running)&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose the &lt;code&gt;my_windows_workstation&lt;/code&gt; EC2 instance, in the top pane of the screen.&lt;/li&gt; 
 &lt;li&gt;Choose the copy icon next to the &lt;strong&gt;Public IPv4 address&lt;/strong&gt; in the lower pane to copy the IP address.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;Finally, use the Amazon DCV client to view the workstation:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Open the Amazon DCV client on your local machine.&lt;/li&gt; 
 &lt;li&gt;Paste the previous &lt;strong&gt;IP address&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;, then trust the connection.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;You will see a security warning about an untrusted certificate.&lt;/strong&gt; This is expected behavior because Amazon DCV uses a self-signed certificate by default. For this initial setup, it is safe to accept the certificate and proceed with the connection. For a detailed explanation of why this warning appears and how to implement proper certificate security for production environments, see Amazon DCV Connection Security in &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-5-security/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 5 – Security&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;In the next &lt;strong&gt;Username / Password&lt;/strong&gt; entry field, choose &lt;strong&gt;Administrator&lt;/strong&gt;, and the appropriate password to which you set that user.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;After the connection is established, Amazon DCV opens and displays the remote workstation desktop. The following screen capture shows the running workstation, confirming that your remote session is active and the environment is ready to use. In this example, the Windows Server 2025 desktop is shown with SideFX Houdini open, displaying a rendered scene in the viewport above the Windows taskbar.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-4.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-4.png" alt="Windows Server 2025 workstation running SideFX Houdini, with a rendered scene shown above the Windows taskbar" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 4: A screen capture of a Windows Server 2025 based workstation&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;With Windows, you automatically get brush sensitivity with Wacom and Amazon DCV connectivity. You don’t need to configure additional steps for your brushes to dynamically use the tablet’s controls.&lt;/p&gt; 
&lt;p&gt;Note: If you have need for a managed, non-persistent Windows desktop where several users share one GPU instance, consider &lt;a href="https://docs.aws.amazon.com/appstream2/latest/developerguide/multi-session-recs.html" target="_blank" rel="noopener noreferrer"&gt;Amazon WorkSpaces Applications multi-session fleets&lt;/a&gt;. They’re best for lighter graphics users such as reviewers, CAD viewers and editors, rather than artists working heavily in the viewport.&lt;/p&gt; 
&lt;h2 id="cleaning-up"&gt;Cleaning up&lt;/h2&gt; 
&lt;p&gt;Finally, you must remember to turn off your instances when not in use, either through the &lt;a href="https://aws.amazon.com/console/" target="_blank" rel="noopener"&gt;AWS Management Console&lt;/a&gt;, or through other programmatic methods such as AWS CLI. You incur costs associated with a running machine, and so deactivating machines when not in use reduces your expenditure.&lt;/p&gt; 
&lt;p&gt;This can be done by choosing &lt;strong&gt;Terminate instance&lt;/strong&gt; from the &lt;strong&gt;Instance state&lt;/strong&gt; options of the workstation in the Amazon EC2 console. The instance shuts down and reports a &lt;strong&gt;Terminated&lt;/strong&gt; state on the console, but it automatically disappears after a short time.&lt;/p&gt; 
&lt;p&gt;However, if you want to learn more about the various methods to deactivate an EC2 instance, and create a persistent machine image of your Windows instance, then refer to Part 4 of the series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;This post has shown how Amazon EC2 instances running Windows Server 2025 can create a GPU-backed VFX workstation. Your artists can use the latest technologies to unlock efficiencies, unhampered by the lengthy hardware renewal cycles typically found in on-premises environments.&lt;/p&gt; 
&lt;p&gt;We recommend that you continue to Part 4 of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations&lt;/a&gt;, to learn how to implement GPU optimizations and infrastructure to streamline the provisioning of workstations. Part 4 also covers essential information on security practices for Windows EC2 instances, including build-time hardening and automated patch management to protect your workstation infrastructure from evolving threats.&lt;/p&gt; 
&lt;p&gt;For more information, contact us at &lt;a class="email" href="mailto:aws-visual-compute-interest@amazon.com"&gt;aws-visual-compute-interest@amazon.com&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="further-reading"&gt;Further reading&lt;/h2&gt; 
&lt;p&gt;If you want to augment a VFX workstation environment with a dedicated render farm, then consider the managed service &lt;a href="https://aws.amazon.com/deadline-cloud/" target="_blank" rel="noopener"&gt;AWS Deadline Cloud&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;EC2 instance metrics, such as CPU and memory usage, are sent to &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; logs, so you can access this data through the console and AWS CLI. This information helps you discern whether an EC2 instance is over- or under-provisioned for the work at hand. For example, an instance might have excessive CPU, memory, and networking resources for the current tasks and could be optimized for price. Alternatively, it might not have enough resources to cope. For more information, visit the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring_ec2.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Windows instances can be lengthy to boot. Amazon EC2 Fast Launch for Windows is an AWS feature for &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/win-ami-config-fast-launch.html" target="_blank" rel="noopener"&gt;faster launching of Windows machines&lt;/a&gt; through smart snapshots of the AMI.&lt;/p&gt; 
&lt;p&gt;Another post shows how to &lt;a href="https://aws.amazon.com/blogs/compute/managing-domain-membership-of-dynamic-fleet-of-ec2-instances/" target="_blank" rel="noopener"&gt;programmatically configure a Windows EC2 instance as part of a domain&lt;/a&gt;. This is particularly useful when the instances are used ephemerally, for example as part of a fleet of instances that spool up and down for rendering, and you need methods to bind and remove instances quickly.&lt;/p&gt; 
&lt;p&gt;More advanced examples of using Amazon DCV can be found in the &lt;a href="https://github.com/aws-samples/dcv-samples" target="_blank" rel="noopener"&gt;aws-samples dcv-samples GitHub repo&lt;/a&gt;. This includes methods to broker multiple users and instances. Amazon DCV Connection Gateway provides a single entry point for users to connect to multiple Amazon DCV sessions across different instances, streamlining access management and improving security through centralized authentication.&lt;/p&gt; 
&lt;p&gt;Commercial options also exist to perform artist/instance brokering, using Amazon DCV and Amazon EC2 launch templates. An example of such an offering is &lt;a href="https://leostream.com/" target="_blank" rel="noopener"&gt;Leostream&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For reference, examples of setting up Amazon DCV-capable instances and using &lt;a href="https://aws.amazon.com/cloudformation/" target="_blank" rel="noopener"&gt;AWS CloudFormation&lt;/a&gt; templates as a deployment method can be found in the &lt;a href="https://github.com/aws-samples/amazon-ec2-nice-dcv-samples" target="_blank" rel="noopener"&gt;amazon-ec2-nice-dcv-samples GitHub repo&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;A deeper analysis of bit rates and latency for Amazon DCV connections can be found in &lt;a href="https://aws.amazon.com/blogs/hpc/putting-bitrates-into-perspective/" target="_blank" rel="noopener"&gt;this AWS HPC Blog post&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;More information about Wacom Bridge running on Amazon DCV can be found in this &lt;a href="https://aws.amazon.com/blogs/media/unleash-creative-potential-with-wacom-bridge-powered-by-amazon-dcv/" target="_blank" rel="noopener"&gt;AWS Wacom post&lt;/a&gt; and &lt;a href="https://www.youtube.com/watch?v=T9ztNSBW4xI" target="_blank" rel="noopener"&gt;re:Invent 2024 talk&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-5.jpg" alt="Andy Hayes" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Andy Hayes&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Andy is a Senior Visual Computing Solutions Architect at AWS. With 20 years’ experience in Visual Effects and Animation, Andy has led CG divisions and departments and added supervision to film projects, earning both Annie and Visual Effects Society Awards along the way. At AWS, he partners with studios and creative technology companies across the Media &amp;amp; Entertainment industry, spanning VFX and animation to rendering, virtual production, and games, helping them design and scale the cloud infrastructure and workflows behind their content pipelines. Drawing on his production background, Andy bridges the worlds of artists and engineers, guiding customers as they adopt technologies like high-performance rendering, GPU compute, and increasingly AI and machine learning to solve real creative and technical challenges. He remains passionate about the marriage of art and science that leads to the creation of compelling imagery, and about aligning technology to the evolving needs of the industry.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2761-6.jpg" alt="Mike Owen" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Mike Owen&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Mike is a Principal Visual Computing Solutions Architect at AWS, where he has spent many years helping studios move their creative work to the cloud. He focuses on the architecture behind high-end content creation: cloud workstations, render farm scaling and storage that spans multiple sites. Mike works with studios and creative technology companies across Media &amp;amp; Entertainment, from VFX and animation to finishing and colour. He has pioneered the concept of “Studio in the Cloud” and helped bring industry tools such as Autodesk Flame to AWS, and has contributed to a range of AWS Thinkbox Deadline improvements. Most recently he has led development of KNFSD File Cache, an open-source NFS caching solution from AWS. It lets studios burst large render workloads into the cloud whilst their data stays on existing on-premises storage. He cares about giving artists the same seamless, colour-accurate experience in the cloud that they expect on-premises, and about removing the cost and complexity that usually come with building a global studio.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Building a GPU workstation for visual effects on Amazon EC2: Part 2 – Linux</title>
		<link>https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-2-linux/</link>
		
		<dc:creator><![CDATA[Andy Hayes]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 15:27:12 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">8d6a21f1d9b5c05aa91d42e7c36c4adba8897355</guid>

					<description>The second post in a five-part series on building GPU-backed visual effects (VFX) workstations on Amazon EC2. You deploy and configure a Rocky Linux 9.5 workstation with NVIDIA GPU drivers, Wacom drivers, and Amazon DCV as a high-performance desktop display protocol.</description>
										<content:encoded>&lt;p&gt;For many years Amazon Web Services (AWS) has been guiding customers in the deployment of powerful NVIDIA GPU-backed workstations for graphics-intensive workloads. With the recent expansion of our G-series &lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/a&gt; graphics-based instances, we are excited to introduce new instance families that deliver enhanced performance and capabilities. We are also refreshing our comprehensive guidance on choosing and configuring these powerful virtual workstations.&lt;/p&gt; 
&lt;p&gt;This is the second post in a five-part series, focusing on the deployment of a Rocky Linux 9.5 visual effects (VFX) workstation, using &lt;a href="https://docs.aws.amazon.com/dcv/latest/adminguide/what-is-dcv.html" target="_blank" rel="noopener"&gt;Amazon DCV&lt;/a&gt; as a high-performance desktop display protocol.&lt;/p&gt; 
&lt;blockquote&gt;
 &lt;p&gt;&lt;em&gt;“Amazon DCV gives me the ability to prioritise image quality or smooth performance and playback, depending on the tasks I am performing. It adapts quickly to any monitor used and when in full screen, I forget I am operating a remote workstation.”&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;— Giorgio Pitino, Head of Creative Operations, Outpost VFX&lt;/p&gt; 
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt; 
&lt;p&gt;This post assumes that you have already configured the following:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;An active AWS account with increased GPU Amazon EC2 service quota limits.&lt;/li&gt; 
 &lt;li&gt;A valid Amazon EC2 key pair in your &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/regions_az/" target="_blank" rel="noopener"&gt;AWS Region&lt;/a&gt; of choice.&lt;/li&gt; 
 &lt;li&gt;A configured virtual firewall Security Group, with open TCP/UDP ports 22, 443, 8443, and 3389 limited to only your own IP address.&lt;/li&gt; 
 &lt;li&gt;An &lt;a href="https://aws.amazon.com/iam/" target="_blank" rel="noopener"&gt;AWS Identity and Access Management (IAM)&lt;/a&gt; profile with &lt;a href="https://aws.amazon.com/s3/" target="_blank" rel="noopener"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt; read access, for workstation usage.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;We strongly recommend that you follow Part 1 of the series, &lt;a href="https://aws.amazon.com/blogs/compute/build-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-1-setup/"&gt;Build a GPU workstation for visual effects on Amazon EC2: Part 1 – Setup&lt;/a&gt;, which goes through the preceding steps in detail.&lt;/p&gt; 
&lt;h2 id="launching-the-linux-workstation"&gt;Launching the Linux workstation&lt;/h2&gt; 
&lt;p&gt;The &lt;a href="https://aws.amazon.com/marketplace" target="_blank" rel="noopener"&gt;AWS Marketplace&lt;/a&gt; offers an official Rocky Linux 9 x86-64 &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html" target="_blank" rel="noopener"&gt;Amazon Machine Image (AMI)&lt;/a&gt; that can be used as a base AMI for our GPU workstation.&lt;/p&gt; 
&lt;p&gt;To use this AMI, you need to subscribe to the AMI to use the updates:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Log in to the &lt;strong&gt;AWS Management Console&lt;/strong&gt; and navigate to the &lt;strong&gt;AWS Marketplace&lt;/strong&gt; by searching for its name in the Service search bar, or by navigating:&lt;/li&gt; 
&lt;/ol&gt; 
&lt;blockquote&gt;
 &lt;p&gt;&lt;strong&gt;Services &amp;gt; Cloud Financial Management &amp;gt; AWS Marketplace&lt;/strong&gt;.&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;ol start="2" type="1"&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Discover products&lt;/strong&gt; in the left pane.&lt;/li&gt; 
 &lt;li&gt;Search for “rocky linux 9 official” in the Search field.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Rocky Linux 9 (Official) – x86_64&lt;/strong&gt; to view the marketplace offering.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Continue to Subscribe&lt;/strong&gt; to subscribe to this product.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;This product has no actual fee: other products, such as variations of Rocky Linux with support from third parties, might charge.&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;ol start="6" type="1"&gt; 
 &lt;li&gt;To continue, choose &lt;strong&gt;Accept Terms&lt;/strong&gt; (if you agree).&lt;/li&gt; 
 &lt;li&gt;The subscription process starts, with &lt;strong&gt;Effective date&lt;/strong&gt; showing &lt;strong&gt;pending&lt;/strong&gt;. But when the subscription is complete (which can take a few minutes) this changes to the current date.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;When the subscription process has completed, you can launch an EC2 instance from that AMI:&lt;/p&gt; 
&lt;ol start="8" type="1"&gt; 
 &lt;li&gt;Navigate back to the &lt;strong&gt;AWS Marketplace&lt;/strong&gt; service console page and choose &lt;strong&gt;Manage subscriptions&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Launch new instance&lt;/strong&gt; underneath the entry for &lt;strong&gt;Rocky Linux 9 (Official) – x86_64&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Launch instances&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;When prompted, specify your AWS Region, and choose &lt;strong&gt;Continue to launch through EC2&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;This now opens the Amazon EC2 launch interface.&lt;/p&gt; 
&lt;ol start="12" type="1"&gt; 
 &lt;li&gt;Give the instance a name, for example “my_linux_workstation”.&lt;/li&gt; 
 &lt;li&gt;Note that the AMI has been pre-filled for you.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Instance type,&lt;/strong&gt; choose &lt;strong&gt;g6.4xlarge&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Key pair name&lt;/strong&gt;, open the list and choose your key pair. In the previous post we called it “ec2_test_keypair” to specify the password security credentials.&lt;/li&gt; 
 &lt;li&gt;Edit the &lt;strong&gt;Network settings&lt;/strong&gt; to adjust security and network placement: 
  &lt;ul&gt; 
   &lt;li&gt;Leave the &lt;strong&gt;Subnet&lt;/strong&gt; to &lt;strong&gt;No preference&lt;/strong&gt;.&lt;/li&gt; 
   &lt;li&gt;Make sure that &lt;strong&gt;Auto-assign public IP&lt;/strong&gt; is set to &lt;strong&gt;Enable&lt;/strong&gt;, so that you can access the instance through the internet.&lt;/li&gt; 
   &lt;li&gt;Under the &lt;strong&gt;Firewall (security groups)&lt;/strong&gt; section of the &lt;strong&gt;Network Settings&lt;/strong&gt;, choose &lt;strong&gt;Select existing security group&lt;/strong&gt;, and specify your security group. In the previous post we named it “ec2_test_sg” to set up the firewall for the machine.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;In &lt;strong&gt;Configuration storage&lt;/strong&gt;, expand the default root volume from 10 GiB to 50 GiB of &lt;strong&gt;gp3&lt;/strong&gt; storage.&lt;strong&gt;Important&lt;/strong&gt;: Enable encryption in the &lt;strong&gt;Advanced&lt;/strong&gt; options by checking the &lt;strong&gt;Encrypted&lt;/strong&gt; option and select the default AWS managed key (aws/ebs) or a customer managed AWS KMS key for enhanced control. Amazon Elastic Block Store (Amazon EBS) encryption protects your VFX project files, renders, and application data at rest. Encryption uses industry-standard AES-256 encryption and is transparent to applications with minimal performance impact.&lt;/li&gt; 
 &lt;li&gt;Under &lt;strong&gt;Advanced details&lt;/strong&gt;, specify the role that you created for workstation usage. In the previous post we called it “basic_workstation_role”, through the &lt;strong&gt;IAM instance profile&lt;/strong&gt; list, so your workstation can access additional services.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Launch instance&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;You can now choose the link to the EC2 instance that has been launched or view it through the &lt;strong&gt;Instances&lt;/strong&gt; pane in the &lt;strong&gt;Amazon EC2 Service&lt;/strong&gt; page. The following screen capture shows the newly launched workstation in the EC2 Instances list, where you can confirm it is ready to use. When the “my_linux_workstation” instance is in the &lt;strong&gt;Running&lt;/strong&gt; state, and the &lt;strong&gt;Status check&lt;/strong&gt; is &lt;strong&gt;3/3 checks passed&lt;/strong&gt;, you can continue.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2759-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2759-1.png" alt="EC2 Instances console page showing my_linux_workstation running with 3 of 3 status checks passed" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: A screen capture of the EC2 Instances page, showing my_linux_workstation in a ready state&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="configuring-the-linux-workstation"&gt;Configuring the Linux workstation&lt;/h2&gt; 
&lt;p&gt;Now you proceed to configure the instance with the necessary libraries and software needed to make it a capable workstation for making 2D and 3D content. From a Mac terminal, Linux terminal, or Windows PowerShell, you can now SSH into the &lt;strong&gt;rocky&lt;/strong&gt; user over the public IP address. To find the &lt;strong&gt;Public IPv4 address&lt;/strong&gt;, choose the EC2 instance in the &lt;strong&gt;Instances&lt;/strong&gt; pane (as shown in the preceding figure), and you should find the address located in the top/middle part of the &lt;strong&gt;Details&lt;/strong&gt; section.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;ssh rocky@&amp;lt;&amp;lt;PUBLIC_IP_ADDRESS&amp;gt;&amp;gt; -i &amp;lt;&amp;lt;YOUR_EC2_TEST_KEYPAIR_PEM_FILE&amp;gt;&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;When you are logged in to the machine, you can start with password updates and general necessary packages:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Set a password for your rocky user.
sudo passwd rocky

# Install some useful packages for later use.
sudo yum install wget nano unzip -y

# Install AWS CLI.
# https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
cd ~
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

# Install pip.
curl -O https://bootstrap.pypa.io/get-pip.py
python get-pip.py --user

# Make sure all packages are up-to-date.
sudo yum update -y

# Install GNOME.
sudo yum groupinstall "Server with GUI" -y

# Install kernel-devel and reboot.
sudo yum install kernel-devel -y
sudo reboot&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Reconnect to the instance to disable nouveau drivers, in preparation for installing the GPU drivers:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# We need to disable the nouveau driver which conflicts with NVIDIA graphics cards.
# Make a module configuration to disable it.
sudo nano /etc/modprobe.d/nvidia_nouveau_off.conf

# Add the following lines
blacklist nouveau
options nouveau modeset=0

# CTRL-X and "y" to exit and save changes

# Ensure this file is also in usr/lib.
sudo cp /etc/modprobe.d/nvidia_nouveau_off.conf /usr/lib/modprobe.d/

# Rebuild the initramfs / boot process.
sudo dracut --force

# Set a new boot config based on the running system, and reboot.
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
sudo reboot&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Reconnect to the instance to begin installing the GPU drivers:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Firstly, you can now double check that nouveau is not present on the system.
# You should see no output from the below:
lsmod | grep nouveau&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt; &lt;p&gt;You must use AWS approved NVIDIA GPU drivers, issued through Amazon S3, not only for optimal compatibility and performance, but also to make sure that the necessary professional GRID drivers are automatically provisioned:&lt;/p&gt; &lt;p&gt;&lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-nvidia-driver.html" target="_blank" rel="noopener"&gt;https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-nvidia-driver.html&lt;/a&gt;&lt;/p&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;At the time of writing, these are the current steps to install the correct NVIDIA GPU drivers.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Install supporting libraries for NVIDIA GRID driver.
sudo dnf install -y make gcc elfutils-libelf-devel libglvnd-devel kernel-devel-$(uname -r)

mkdir ~/nvidia
cd ~/nvidia

# Copy the latest GRID driver from the public AWS S3 bucket.
aws s3 cp --recursive s3://ec2-linux-nvidia-drivers/latest/ .
chmod +x NVIDIA-Linux-x86_64*.run
sudo /bin/sh ./NVIDIA-Linux-x86_64*.run

# Follow the prompts to install:
# - you do not need to install 32 bit drivers
# - you should rebuild initramfs if requested.

# Check the driver is installed.
nvidia-smi -q | head&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You should get an output as follows:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-plaintext"&gt;==============NVSMI LOG==============

Timestamp : Wed Jan 8 13:56:10 2025
Driver Version : 550.127.05
CUDA Version : 12.4
Attached GPUs : 1
GPU 00000000:31:00.0
Product Name : NVIDIA L4&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Now set up the Amazon DCV server to stream the desktop to your local machine/client.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Installing Amazon DCV.
# You can follow more detailed / up-to-date instructions at this link:
# https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-installing-linux-server.html

# First, disable the Wayland protocol.
sudo nano /etc/gdm/custom.conf
# Uncomment the "WaylandEnable=false" line.
# CTRL-X and "y" to exit and save changes

# Configure X Server -- check that the system is configured for graphical sessions:
sudo systemctl get-default
# If "multi.target" is returned then perform the following:
sudo systemctl set-default graphical.target

# start the X server
sudo systemctl isolate graphical.target

# Update xorg.conf with multi monitor connectivity.
sudo nvidia-xconfig --preserve-busid --enable-all-gpus --connected-monitor=DFP-0,DFP-1,DFP-2,DFP-3

# Restart X-Server.
sudo systemctl isolate multi-user.target
sudo systemctl isolate graphical.target

# Download and install the Amazon DCV server
mkdir ~/amazondcv
cd ~/amazondcv

# Install the key
sudo rpm --import https://d1uj6qtbmh3dt5.cloudfront.net/NICE-GPG-KEY

# Get the latest Rocky 9 Amazon DCV server.
# Note: The Amazon DCV team provide permanent links to the latest DCV software:
# https://www.amazondcv.com/latest.html
wget https://d1uj6qtbmh3dt5.cloudfront.net/nice-dcv-el9-x86_64.tgz
tar -xvzf ./nice-dcv-el9-x86_64.tgz

# 'cd' into the extracted folder -- note this will be version named, hence the generic line below.
cd $(ls -d */|head -n 1)

# install the server rpm -- note this will be version named, hence the generic line below.
sudo yum install $(ls nice-dcv-server*.rpm|head -n 1)

# Restart the X Server.
sudo systemctl isolate multi-user.target
sudo systemctl isolate graphical.target&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The Amazon DCV server uses parameters to specify configuration options. On Linux this manifests as a file on disk.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Adjust the Amazon DCV config files to enable
# the automatic creation of a session by the "rocky" user...
sudo nano /etc/dcv/dcv.conf

# Under [session-management] add the following line:
create-session = true

# Under [session-management/automatic-console-session] add the following line:
owner = "rocky"

# CTRL-X and "y" to exit and save changes.

# Start DCV and enable it to automatically restart on boot
sudo systemctl restart dcvserver
sudo systemctl enable dcvserver

# Finally, open up the firewall to allow Amazon DCV access.
sudo firewall-cmd --add-port=8443/tcp --permanent
sudo firewall-cmd --add-port=8443/udp --permanent
sudo firewall-cmd --reload&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Note: Looking to the future of Linux based workstations, DCV &lt;span&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-dcv-2026-0/" target="_blank" rel="noopener noreferrer"&gt;now supports Wayland display drivers&lt;/a&gt;&lt;/span&gt; on RHEL 10, Rocky Linux 10, CentOS 10 and Ubuntu 26.04.&lt;/p&gt; 
&lt;p&gt;Now install the Wacom drivers:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;mkdir ~/wacom
cd ~/wacom

# Download the drivers from (again replacing the link below with the latest version):
# https://github.com/linuxwacom/input-wacom/releases
wget https://github.com/linuxwacom/input-wacom/releases/download/v1.3.0/input-wacom-1.3.0.tar.bz2
tar jxf input-wacom-1.3.0.tar.bz2
cd input-wacom-1.3.0
sudo su
./configure
make &amp;amp;&amp;amp; make install
modprobe wacom
dracut --force

# Setup Wacom Pressure Sensitivity
nano /etc/X11/xorg.conf.d/99-wacom-pressure2k.conf

# Add the following lines:
Section "InputClass"
    Identifier "Wacom pressure compatibility"
    MatchDriver "wacom"
    Option "Pressure2K" "true"
EndSection

# CTRL-X and "y" to exit and save changes.

# Setup Wacom with Amazon DCV and Pressure Sensitivity
# Described here: https://docs.aws.amazon.com/dcv/latest/adminguide/enable-stylus.html
sudo nano /etc/X11/xorg.conf

# Add these 2 sections to the end of the file
Section "InputDevice"
    Identifier "DCV Stylus Pen"
    Driver "dcvinput"
    Option "Pressure2K" "true"
EndSection

Section "InputDevice"
    Identifier "DCV Stylus Eraser"
    Driver "dcvinput"
    Option "Pressure2K" "true"
EndSection

# Add the following inside the ServerLayout section
InputDevice "DCV Stylus Pen"
InputDevice "DCV Stylus Eraser"

# CTRL-X and "y" to exit and save changes.

# Restart X display
sudo systemctl isolate multi-user.target
sudo systemctl isolate graphical.target&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The local &lt;strong&gt;instance store&lt;/strong&gt; NVMe devices need mounting. For more information, visit the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/making-instance-stores-available-on-your-instances.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# View the volumes -- note that only our nvme0n1 drive is available.
# Our secondary instance store is not listed.
df -h

Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Size&amp;nbsp; Used Avail Use% Mounted on
devtmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4.0M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 4.0M&amp;nbsp;&amp;nbsp; 0% /dev
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7.4G&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 7.4G&amp;nbsp;&amp;nbsp; 0% /dev/shm
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3.0G&amp;nbsp; 1.3M&amp;nbsp; 3.0G&amp;nbsp;&amp;nbsp; 1% /run
efivarfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128K&amp;nbsp; 3.8K&amp;nbsp; 120K&amp;nbsp;&amp;nbsp; 4% /sys/firmware/efi/efivars
/dev/nvme0n1p4&amp;nbsp;&amp;nbsp; 49G&amp;nbsp;&amp;nbsp; 45G&amp;nbsp; 3.9G&amp;nbsp; 93% /
/dev/nvme0n1p3&amp;nbsp; 936M&amp;nbsp; 716M&amp;nbsp; 221M&amp;nbsp; 77% /boot
/dev/nvme0n1p2&amp;nbsp; 100M&amp;nbsp; 7.0M&amp;nbsp;&amp;nbsp; 93M&amp;nbsp;&amp;nbsp; 8% /boot/efi
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.5G&amp;nbsp;&amp;nbsp; 52K&amp;nbsp; 1.5G&amp;nbsp;&amp;nbsp; 1% /run/user/42
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.5G&amp;nbsp;&amp;nbsp; 36K&amp;nbsp; 1.5G&amp;nbsp;&amp;nbsp; 1% /run/user/1000

# View volumes mapped but not formatted or mounted.
# Note nvme1n1 -- our instance store - is listed but not mounted.
lsblk

NAME&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MAJ:MIN RM&amp;nbsp;&amp;nbsp; SIZE RO TYPE MOUNTPOINTS
nvme0n1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 259:0&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp; 50G&amp;nbsp; 0 disk 
├─nvme0n1p1 259:2&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2M&amp;nbsp; 0 part 
├─nvme0n1p2 259:3&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; 100M&amp;nbsp; 0 part /boot/efi
├─nvme0n1p3 259:4&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 1000M&amp;nbsp; 0 part /boot
└─nvme0n1p4 259:5&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 48.9G&amp;nbsp; 0 part /
nvme1n1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 259:1&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 558.8G&amp;nbsp; 0 disk

# Create a file system on that device
sudo mkfs -t xfs /dev/nvme1n1

# Create a directory to mount the new device.
sudo mkdir /data

# Mount the device to your new directory.
sudo mount /dev/nvme1n1 /data

# Confirm our instance store - nvme1n1 - is now mounted.
df -h

Filesystem&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Size&amp;nbsp; Used Avail Use% Mounted on
devtmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4.0M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; 4.0M&amp;nbsp;&amp;nbsp; 0% /dev
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 31G&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp; 31G&amp;nbsp;&amp;nbsp; 0% /dev/shm
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 13G&amp;nbsp; 1.2M&amp;nbsp;&amp;nbsp; 13G&amp;nbsp;&amp;nbsp; 1% /run
efivarfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 128K&amp;nbsp; 3.8K&amp;nbsp; 120K&amp;nbsp;&amp;nbsp; 4% /sys/firmware/efi/efivars
/dev/nvme0n1p4&amp;nbsp;&amp;nbsp; 49G&amp;nbsp;&amp;nbsp; 44G&amp;nbsp; 5.1G&amp;nbsp; 90% /
/dev/nvme0n1p3&amp;nbsp; 936M&amp;nbsp; 716M&amp;nbsp; 221M&amp;nbsp; 77% /boot
/dev/nvme0n1p2&amp;nbsp; 100M&amp;nbsp; 7.0M&amp;nbsp;&amp;nbsp; 93M&amp;nbsp;&amp;nbsp; 8% /boot/efi
tmpfs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 6.1G&amp;nbsp;&amp;nbsp; 36K&amp;nbsp; 6.1G&amp;nbsp;&amp;nbsp; 1% /run/user/1000
/dev/nvme1n1&amp;nbsp;&amp;nbsp;&amp;nbsp; 559G&amp;nbsp; 4.0G&amp;nbsp; 555G&amp;nbsp;&amp;nbsp; 1% /data
&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Finally, we show some examples of application-specific library setup. Each application potentially has its own list of necessary libraries to install, which can be referenced online. The following are some examples:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# SideFX Houdini :
# https://www.sidefx.com/Support/system-requirements/linux-package-requirements-for-houdini-205/
sudo yum install alsa-lib compat-openssl11 dbus-libs expat fontconfig glibc libatomic libevent libglvnd-glx libglvnd-opengl libICE libSM libX11 libX11-xcb libxcb libXcomposite libXcursor libXdamage libXext libXfixes libXi libxkbcommon libxkbcommon-x11 libXrandr libXrender libXScrnSaver libXt libXtst libzstd nspr nss nss-util openldap pciutils-libs tbb xcb-util xcb-util-image xcb-util-keysyms xcb-util-renderutil xcb-util-wm zlib -y

# Autodesk Maya
# https://help.autodesk.com/view/MAYAUL/2025/ENU/?guid=GUID-D2B5433C-E0D2-421B-9BD8-24FED217FD7F
sudo yum install epel-release -y
sudo yum install libnsl.x86_64 audiofile-dev compat-openssl11 gtk2 libffi libmng libglvnd-opengl libpng15 libpq libXp mesa-libGLU xcb-util-cursor xcb-util-wm xcb-util-image xcb-util-keysyms xcb-util-renderutil xorg-x11-fonts-ISO8859-1-75dpi xorg-x11-fonts-ISO8859-1-100dpi -y&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;And lastly, it is time to clean up.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;cd ~
rm -rf ~/nvidia
rm -rf ~/amazondcv
rm -rf ~/Wacom

# Reboot before logging in
sudo reboot&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="logging-in-to-your-workstation"&gt;Logging in to your workstation&lt;/h2&gt; 
&lt;p&gt;To log in to your machine using Amazon DCV, you must set up the client software on your local machine:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;On your local machine/laptop, open the &lt;a href="https://www.amazondcv.com/latest.html" target="_blank" rel="noopener"&gt;Amazon DCV download&lt;/a&gt; webpage.&lt;/li&gt; 
 &lt;li&gt;Expand the &lt;strong&gt;Amazon DCV Client&lt;/strong&gt; entry that matches the &lt;strong&gt;Server&lt;/strong&gt; version that you installed on your workstation.&lt;/li&gt; 
 &lt;li&gt;Choose the relevant OS for your machine/laptop, for example &lt;strong&gt;Windows (x86_64)&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Download the installer.&lt;/li&gt; 
 &lt;li&gt;Run the installer.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;When it is installed, we need to determine the Public IP address of the workstation to connect to:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;In the &lt;strong&gt;Amazon EC2 Console&lt;/strong&gt;, choose &lt;strong&gt;Amazon EC2 Dashboard&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Instances (running)&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose the “my_linux_workstation” EC2 instance, in the top pane of the screen.&lt;/li&gt; 
 &lt;li&gt;Choose the copy icon next to the &lt;strong&gt;Public IPv4 address&lt;/strong&gt; in the lower pane to copy the IP address.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;Finally, use the &lt;strong&gt;Amazon DCV&lt;/strong&gt; client to view the workstation:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Open the Amazon DCV client on your local machine.&lt;/li&gt; 
 &lt;li&gt;Paste the preceding &lt;strong&gt;IP address&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;, then trust the connection.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;You will see a security warning about an untrusted certificate&lt;/strong&gt;. This is expected behavior because DCV uses a self-signed certificate by default. For this initial setup, it’s safe to accept the certificate and proceed with the connection. For a detailed explanation of why this warning appears and how to implement proper certificate security for production environments, see Amazon DCV Connection Security in &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-5-security/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 5 – Security&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;In the next &lt;strong&gt;Username / Password&lt;/strong&gt; entry field, choose &lt;strong&gt;rocky&lt;/strong&gt;, and the appropriate password to which you set that user.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;After the connection is established, Amazon DCV opens and displays the remote workstation desktop. The following screen capture shows the running workstation, confirming that your remote session is active and the environment is ready to use. In this example, the Rocky Linux desktop is shown with SideFX Houdini open, displaying a rendered scene in the viewport against the Rocky Linux desktop background.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2759-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2759-2.png" alt="Rocky Linux workstation desktop running SideFX Houdini with a rendered scene in the viewport" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: A screen capture of a Rocky Linux-based workstation&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="cleaning-up"&gt;Cleaning up&lt;/h2&gt; 
&lt;p&gt;Finally, you must turn off your instances when not in use, either through the &lt;a href="https://aws.amazon.com/console/" target="_blank" rel="noopener"&gt;AWS Management Console&lt;/a&gt;, or through other programmatic methods such as the &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;. You incur costs associated with a running machine, and so deactivating machines when not in use reduces your expenditure.&lt;/p&gt; 
&lt;p&gt;Deactivating instances can be done by choosing &lt;strong&gt;Terminate instance&lt;/strong&gt; from the &lt;strong&gt;Instance state&lt;/strong&gt; options of the workstation on the Amazon EC2 console. The instance shuts down and reports a “Terminated” state on the console, but it automatically disappears after a short time.&lt;/p&gt; 
&lt;p&gt;However, if you want to learn more about the various methods to deactivate an EC2 instance, and creating a persistent machine image of your Linux instance, then refer to Part 4 of the series: &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations&lt;/a&gt;. Additionally, Part 4 will cover essential information on security practices for Linux EC2 instances, including build-time hardening and automated patch management to protect your workstation infrastructure from evolving threats.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;In this post you have subscribed to and deployed an AWS Marketplace AMI of Rocky Linux to serve as your base image. Then, you modified it with GPU drivers, Wacom drivers, and other modules to make it a capable Linux-backed VFX workstation, using Amazon EC2 GPU accelerated G instance types.&lt;/p&gt; 
&lt;p&gt;You may also be interested in Part 3 of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 3 – Windows&lt;/a&gt;, to learn how to create a Windows-backed VFX workstation.&lt;/p&gt; 
&lt;p&gt;We also recommend that you continue to Part 4 of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 4 – Optimizations&lt;/a&gt;, to learn how to implement GPU optimizations and infrastructure to streamline the provisioning of workstations.&lt;/p&gt; 
&lt;p&gt;For more information contact us at &lt;a class="email" href="mailto:aws-visual-compute-interest@amazon.com"&gt;aws-visual-compute-interest@amazon.com&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="further-reading"&gt;Further reading&lt;/h2&gt; 
&lt;p&gt;If you want to augment a VFX workstation environment with a dedicated render farm, then consider the managed service &lt;a href="https://aws.amazon.com/deadline-cloud/" target="_blank" rel="noopener"&gt;AWS Deadline Cloud&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;EC2 instance metrics, such as CPU and memory usage, are readily sent to &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt; logs, so you can access this data through the console and AWS CLI. This information can be pertinent to discern if an EC2 instance is being over-provisioned or under-provisioned for the work at hand. An over-provisioned instance has excessive CPU, memory, and networking resources for the current tasks and could be optimized for price. Alternatively, an under-provisioned instance does not have enough resources to cope. For more information visit the Amazon EC2 User Guide.&lt;/p&gt; 
&lt;p&gt;More advanced examples of using Amazon DCV can be found in the &lt;a href="https://github.com/aws-samples/dcv-samples" target="_blank" rel="noopener"&gt;aws-samples GitHub repo&lt;/a&gt;. This includes methods to broker multiple users and instances. Furthermore, DCV Connection Gateway provides a single entry point so you can connect to multiple DCV sessions across different instances, streamlining access management and improving security through centralized authentication.&lt;/p&gt; 
&lt;p&gt;Commercial options also exist to perform artist/instance brokering, using Amazon DCV and Amazon EC2 Launch templates. An example of such an offering is &lt;a href="https://leostream.com/" target="_blank" rel="noopener"&gt;Leostream&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For reference, examples of setting up Amazon DCV capable instances, using &lt;a href="https://aws.amazon.com/cloudformation/" target="_blank" rel="noopener"&gt;AWS CloudFormation&lt;/a&gt; templates as a method of deployment, can be found in &lt;a href="https://github.com/aws-samples/amazon-ec2-nice-dcv-samples" target="_blank" rel="noopener"&gt;this GitHub repo&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;A greater depth of analysis of bit rates and latency surrounding Amazon DCV connections can be found in &lt;a href="https://aws.amazon.com/blogs/hpc/putting-bitrates-into-perspective/" target="_blank" rel="noopener"&gt;this AWS HPC post&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2759-3.jpg" alt="Andy Hayes" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Andy Hayes&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Andy is a Senior Visual Computing Solutions Architect at AWS. With 20 years’ experience in Visual Effects and Animation, Andy has led CG divisions and departments and added supervision to film projects, earning both Annie and Visual Effects Society Awards along the way. At AWS, he partners with studios and creative technology companies across the Media &amp;amp; Entertainment industry, spanning VFX and animation to rendering, virtual production, and games, helping them design and scale the cloud infrastructure and workflows behind their content pipelines. Drawing on his production background, Andy bridges the worlds of artists and engineers, guiding customers as they adopt technologies like high-performance rendering, GPU compute, and increasingly AI and machine learning to solve real creative and technical challenges. He remains passionate about the marriage of art and science that leads to the creation of compelling imagery, and about aligning technology to the evolving needs of the industry.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2759-4.jpg" alt="Mike Owen" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Mike Owen&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Mike is a Principal Visual Computing Solutions Architect at AWS, where he has spent many years helping studios move their creative work to the cloud. He focuses on the architecture behind high-end content creation: cloud workstations, render farm scaling and storage that spans multiple sites. Mike works with studios and creative technology companies across Media &amp;amp; Entertainment, from VFX and animation to finishing and colour. He has pioneered the concept of “Studio in the Cloud” and helped bring industry tools such as Autodesk Flame to AWS, and has contributed to a range of AWS Thinkbox Deadline improvements. Most recently he has led development of KNFSD File Cache, an open-source NFS caching solution from AWS. It lets studios burst large render workloads into the cloud whilst their data stays on existing on-premises storage. He cares about giving artists the same seamless, colour-accurate experience in the cloud that they expect on-premises, and about removing the cost and complexity that usually come with building a global studio.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Build a GPU workstation for visual effects on Amazon EC2: Part 1 – Setup</title>
		<link>https://aws.amazon.com/blogs/compute/build-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-1-setup/</link>
		
		<dc:creator><![CDATA[Andy Hayes]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 15:27:06 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">a4ccececc4c11afbe81db3768a05d7da3c90f7e6</guid>

					<description>The first in a five-part series on building NVIDIA GPU-powered virtual workstations on Amazon EC2 G-series instances. Part 1 covers the G instance families, Amazon DCV desktop streaming, connectivity options, and the account, service quota, networking, and IAM prerequisites for deploying GPU-accelerated workstations.</description>
										<content:encoded>&lt;p&gt;For many years Amazon Web Services (AWS) has been guiding users in the deployment of powerful NVIDIA GPU-backed workstations for graphics-intensive workloads. With the recent expansion of our G-series &lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/a&gt; graphics-based instances, we’re excited to introduce new instance families that deliver enhanced performance and capabilities. We’re also refreshing our comprehensive guidance on choosing and configuring these powerful virtual workstations.&lt;/p&gt; 
&lt;p&gt;This is the first in a five-part series providing detailed guidance on instance types, and deployment instructions for building Windows and Linux based NVIDIA GPU powered workstation on GPU accelerated EC2 instances. In this initial post, we explore the instance types, and outline essential AWS configurations for account preparation, security, policies, and other prerequisites. Subsequent posts cover Linux deployment (Part 2), Windows deployment (Part 3), optimizations and infrastructure for standardizing workstations deployment at scale (Part 4), and security considerations (Part 5).&lt;/p&gt; 
&lt;h2 id="g-instance-families"&gt;G instance families&lt;/h2&gt; 
&lt;p&gt;The Amazon EC2 G-series instances come in multiple families, with various types and fractionalization of GPUs, memory-to-CPU ratios, and sizes of vCPU and RAM. The g6 and gr6 instances, equipped with NVIDIA L4 GPUs, deliver up to 200 percent performance improvement in graphics-intensive workloads compared to the widely-adopted g4dn family, while offering enhanced performance and cost efficiency over their g5 predecessors. The g6f and gr6f options introduce more GPU partitioning capabilities with the NVIDIA L4, so you can provision fractional GPU allocations. This supports more cost-effective scaling for workloads that do not need a full GPU, with options for half, quarter, and one-eighth GPU. Fractional instances are ideal for remote workstation applications for staff that need only partial GPU usage, as well as other tasks such as lightweight machine learning (ML) research.&lt;/p&gt; 
&lt;p&gt;The g6e instances, featuring the NVIDIA L40S GPU, go further with double the GPU memory, 2.9x faster GPU memory bandwidth, and up to 2.5 times overall performance improvement compared to g5 instances. All three families offer flexible configurations with 1, 4, or 8 GPUs, providing specialized cores optimized for GPU processing, ray tracing, and machine learning workloads, as shown in the following figure.&lt;/p&gt; 
&lt;p&gt;The latest 7&lt;sup&gt;th&lt;/sup&gt; generation instances, the g7 and g7e offer greater performance in GPU speed and memory with the latest NVIDIA RTX PRO 4500 and 6000 respectively. These instances are well suited for high-end 3D and 2D workloads and artificial intelligence (AI) workloads, delivering 4.6 times the AI inference performance of previous g6 instances. With up to 700 Gbps EFA-enabled network bandwidth, g7 instances help you run graphics and data workloads more efficiently.&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA&lt;br&gt; L4&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA&lt;br&gt; L40S&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA&lt;br&gt; RTX PRO 4500&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA&lt;br&gt; RTX PRO 6000&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7"&gt;Architecture&lt;/td&gt; 
   &lt;td&gt;Ada Lovelace&lt;/td&gt; 
   &lt;td&gt;Ada Lovelace&lt;/td&gt; 
   &lt;td&gt;Blackwell&lt;/td&gt; 
   &lt;td&gt;Blackwell&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7"&gt;Memory&lt;/td&gt; 
   &lt;td&gt;24 GB GDDR6&lt;/td&gt; 
   &lt;td&gt;48 GB GDDR6&lt;/td&gt; 
   &lt;td&gt;32 GB GDDR7&lt;/td&gt; 
   &lt;td&gt;96 GB GDDR7&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7"&gt;Memory Bandwith&lt;/td&gt; 
   &lt;td&gt;300 GB/s&lt;/td&gt; 
   &lt;td&gt;864 GB/s&lt;/td&gt; 
   &lt;td&gt;896 GB/s&lt;/td&gt; 
   &lt;td&gt;1790 GB/s&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7"&gt;Cuda Cores&lt;/td&gt; 
   &lt;td&gt;7680&lt;/td&gt; 
   &lt;td&gt;18176&lt;/td&gt; 
   &lt;td&gt;10496&lt;/td&gt; 
   &lt;td&gt;24064&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7"&gt;Tensor Cores&lt;/td&gt; 
   &lt;td&gt;240&lt;/td&gt; 
   &lt;td&gt;568&lt;/td&gt; 
   &lt;td&gt;328&lt;/td&gt; 
   &lt;td&gt;752&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7"&gt;Ray Tracing Cores&lt;/td&gt; 
   &lt;td&gt;60&lt;/td&gt; 
   &lt;td&gt;140&lt;/td&gt; 
   &lt;td&gt;82&lt;/td&gt; 
   &lt;td&gt;188&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;em&gt;Figure 1: The list of GPU architecture statistics for the L4, L40S, RTX PRO 4500, and RTX PRO 6000 NVIDIA GPUs&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;The 6&lt;sup&gt;th&lt;/sup&gt; and 7&lt;sup&gt;th&lt;/sup&gt; generation of G instances are available in multiple configurations to accommodate diverse GPU, CPU, memory, and networking requirements. The g6, g6f, and g7 instances maintain the traditional 1:4 ratio of vCPUs to memory (GiB) established by previous generations such as g4dn and g5. The gr6 and gr6f families introduce an enhanced 1:8 ratio option, while the g6e and g7e instances natively possess the expanded 1:8 ratio. These higher allocations suit memory-intensive 2D and 3D workloads that frequently encounter memory constraints, providing support for demanding visual computing applications.&lt;/p&gt; 
&lt;p&gt;For the non-fractional g6 and gr6 instances, the configurations of sizes are as follows:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Instance type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA L4 GPU count&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;vCPUs&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Memory (GiB)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;EBS Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Network Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="5"&gt;Single GPU&lt;/td&gt; 
   &lt;td&gt;g6.xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 10&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.2xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 10&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.4xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;Up to 25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.8xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;128&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.16xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;256&lt;/td&gt; 
   &lt;td&gt;20&lt;/td&gt; 
   &lt;td&gt;25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="2"&gt;Single GPU / Memory Biased&lt;/td&gt; 
   &lt;td&gt;gr6.4xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;128&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;Up to 25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;gr6.8xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;256&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="3"&gt;Multi GPU&lt;/td&gt; 
   &lt;td&gt;g6.12xlarge&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;48&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;20&lt;/td&gt; 
   &lt;td&gt;40&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.24xlarge&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;96&lt;/td&gt; 
   &lt;td&gt;384&lt;/td&gt; 
   &lt;td&gt;30&lt;/td&gt; 
   &lt;td&gt;50&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.48xlarge&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;768&lt;/td&gt; 
   &lt;td&gt;60&lt;/td&gt; 
   &lt;td&gt;100&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;em&gt;Figure 2: The list of g6 and gr6 instance types with corresponding GPU amounts, vCPUs, network, and bandwidth data&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;The fractional g6f and gr6f configurations are:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Memory (GiB) to vCPU ratio&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Instance type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA L4 GPU count&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA L4 GPU RAM (GiB)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;vCPUs&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Memory (GiB)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;EBS Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Network Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="4"&gt;4-to-1&lt;/td&gt; 
   &lt;td&gt;g6f.large&lt;/td&gt; 
   &lt;td&gt;1/8&lt;/td&gt; 
   &lt;td&gt;3&lt;/td&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 10&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6f.xlarge&lt;/td&gt; 
   &lt;td&gt;1/8&lt;/td&gt; 
   &lt;td&gt;3&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 10&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6f.2xlarge&lt;/td&gt; 
   &lt;td&gt;1/4&lt;/td&gt; 
   &lt;td&gt;6&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 10&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6f.4xlarge&lt;/td&gt; 
   &lt;td&gt;1/2&lt;/td&gt; 
   &lt;td&gt;12&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;6&lt;/td&gt; 
   &lt;td&gt;Up to 25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td style="background-color: #d6dce7"&gt;8-to-1&lt;/td&gt; 
   &lt;td&gt;gr6f.4xlarge&lt;/td&gt; 
   &lt;td&gt;1/2&lt;/td&gt; 
   &lt;td&gt;12&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;128&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;Up to 25&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;em&gt;Figure 3: The list of g6f and gr6f instance types with corresponding fractional GPU amounts, vCPUs, network, and bandwidth data&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;For the g7 instances, the configurations of sizes are as follows:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Instance type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA RTX PRO 4500 GPU count&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;vCPUs&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Memory (GiB)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;EBS Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Network Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="3"&gt;Single GPU&lt;/td&gt; 
   &lt;td&gt;g7.2xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;Up to 8&lt;/td&gt; 
   &lt;td&gt;Up to 60&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g7.4xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;Up to 100&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7.8xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;128&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;100&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="4"&gt;Multi GPU&lt;/td&gt; 
   &lt;td&gt;g7.12xlarge&lt;/td&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;48&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;20&lt;/td&gt; 
   &lt;td&gt;175&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7.24xlarge&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;96&lt;/td&gt; 
   &lt;td&gt;384&lt;/td&gt; 
   &lt;td&gt;40&lt;/td&gt; 
   &lt;td&gt;350&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g7.48xlarge&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;768&lt;/td&gt; 
   &lt;td&gt;80&lt;/td&gt; 
   &lt;td&gt;700&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7.metal*&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;768&lt;/td&gt; 
   &lt;td&gt;80&lt;/td&gt; 
   &lt;td&gt;700&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;* &lt;a href="https://aws.amazon.com/ec2/instance-types/g7/"&gt;Coming soon&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;Figure 4: The list of g7 instance types with corresponding GPU amounts, vCPUs, network, and bandwidth data&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;For the enhanced g6e the following instance size configurations are:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Instance type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA L40S GPU count&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;vCPUs&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Memory (GiB)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;EBS Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Network Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="5"&gt;Single GPU&lt;/td&gt; 
   &lt;td&gt;g6e.xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 20&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6e.2xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;Up to 20&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6e.4xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;128&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;20&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6e.8xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;256&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;25&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6e.16xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;512&lt;/td&gt; 
   &lt;td&gt;20&lt;/td&gt; 
   &lt;td&gt;35&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="3"&gt;Multi GPU&lt;/td&gt; 
   &lt;td&gt;g6e.12xlarge&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;48&lt;/td&gt; 
   &lt;td&gt;384&lt;/td&gt; 
   &lt;td&gt;20&lt;/td&gt; 
   &lt;td&gt;100&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6e.24xlarge&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;96&lt;/td&gt; 
   &lt;td&gt;768&lt;/td&gt; 
   &lt;td&gt;30&lt;/td&gt; 
   &lt;td&gt;200&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6e.48xlarge&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;1536&lt;/td&gt; 
   &lt;td&gt;60&lt;/td&gt; 
   &lt;td&gt;400&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;em&gt;Figure 5: The list of g6e instance types with corresponding GPU amounts, vCPUs, network, and bandwidth data&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;Moreover, the g7e has the following instance size configurations:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Instance type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;NVIDIA L40S GPU count&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;vCPUs&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Memory (GiB)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;EBS Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Network Bandwidth (Gbps)&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="3"&gt;Single GPU&lt;/td&gt; 
   &lt;td&gt;g7e.2xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;64&lt;/td&gt; 
   &lt;td&gt;Up to 5&lt;/td&gt; 
   &lt;td&gt;50&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g7e.4xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;128&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;50&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7e.8xlarge&lt;/td&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;32&lt;/td&gt; 
   &lt;td&gt;256&lt;/td&gt; 
   &lt;td&gt;16&lt;/td&gt; 
   &lt;td&gt;100&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td style="background-color: #d6dce7" rowspan="3"&gt;Multi GPU&lt;/td&gt; 
   &lt;td&gt;g7e.12xlarge&lt;/td&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;48&lt;/td&gt; 
   &lt;td&gt;512&lt;/td&gt; 
   &lt;td&gt;25&lt;/td&gt; 
   &lt;td&gt;400&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7e.24xlarge&lt;/td&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;96&lt;/td&gt; 
   &lt;td&gt;1024&lt;/td&gt; 
   &lt;td&gt;50&lt;/td&gt; 
   &lt;td&gt;800&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g7e.48xlarge&lt;/td&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;192&lt;/td&gt; 
   &lt;td&gt;2048&lt;/td&gt; 
   &lt;td&gt;100&lt;/td&gt; 
   &lt;td&gt;1600&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;em&gt;Figure 6: The list of g7e instance types with corresponding GPU amounts, vCPUs, network, and bandwidth data&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;EC2 instances mount one (or more) &lt;a href="https://aws.amazon.com/ebs/" target="_blank" rel="noopener"&gt;Amazon Elastic Block Store (Amazon EBS&lt;/a&gt;) volumes for durable, block-level storage. These can be detached from the instance and retained independently from the lifecycle of that instance, allowing modifications of the instance itself (such as changing the size and type) without the loss of storage.&lt;/p&gt; 
&lt;p&gt;Ephemeral NVMe storage on each instance is also provided by Instance Stores, aligned for temporary scratch data that benefits from performant local I/O access, which can be used by 2D/3D applications (for example Foundry Nuke’s cache directory). In the follow-up posts we discuss setting up and configuring these instance stores to maximize efficiency. The 6&lt;sup&gt;th&lt;/sup&gt; and 7&lt;sup&gt;th&lt;/sup&gt; generation EC2 instances automatically have instance stores allocated, dependent on their sizes, as shown in the following figure:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td align="center"&gt;&lt;strong&gt;Instance Type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Instance store volumes&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6f.large, g6f.xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 100GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6f.2xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 200 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.xlarge, g6e.xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 250 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.2xlarge, g6e.2xlarge, g6f.4xlarge, gr6f.4xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 450 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.4xlarge, g6e.4xlarge, gr6.4xlarge, g7.2xlarge, g7.4xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 600 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.8xlarge, g6e.8xlarge, gr6.8xlarge&lt;/td&gt; 
   &lt;td&gt;2 x 450 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.12xlarge, g6e.12xlarge&lt;/td&gt; 
   &lt;td&gt;4 x 940 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.16xlarge, g6e.16xlarge&lt;/td&gt; 
   &lt;td&gt;2 x 940 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g6.24xlarge, g6e.24xlarge&lt;/td&gt; 
   &lt;td&gt;4 x 940 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g6.48xlarge, g6e.48xlarge&lt;/td&gt; 
   &lt;td&gt;8 x 940 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7.8xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 950 GB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g7.12xlarge, g7e.2xlarge, g7e.4xlarge, g7e.8xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 1.9 TB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7.24xlarge, g7e.12xlarge&lt;/td&gt; 
   &lt;td&gt;1 x 3.8 TB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;g7.48xlarge, g7.metal*, g7e.24xlarge&lt;/td&gt; 
   &lt;td&gt;2 x 3.8 TB&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;g7e.48xlarge&lt;/td&gt; 
   &lt;td&gt;4 x 3.8 TB&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;* &lt;a href="https://aws.amazon.com/ec2/instance-types/g7/"&gt;Coming soon&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;Figure 7: The configuration of instance stores on the 6&lt;sup&gt;th&lt;/sup&gt; and 7&lt;sup&gt;th&lt;/sup&gt; generation EC2 instances&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;The 6&lt;sup&gt;th&lt;/sup&gt; and 7&lt;sup&gt;th&lt;/sup&gt; generation G instances represent our latest offering in GPU-powered workstations capable servers, but we still offer previous generations, notably the g5 and g4dn, giving many choices in machine types to match performance and cost needs.&lt;/p&gt; 
&lt;p&gt;You can find specifications of all our instances types, on our &lt;a href="https://aws.amazon.com/ec2/instance-types/" target="_blank" rel="noopener"&gt;Amazon EC2 webpage&lt;/a&gt; (G instances are classed as &lt;em&gt;Accelerated Computing&lt;/em&gt; types).&lt;/p&gt; 
&lt;h2 id="desktop-streaming-with-amazon-dcv"&gt;Desktop streaming with Amazon DCV&lt;/h2&gt; 
&lt;p&gt;Typically, cost-effective Mini PCs or laptops are used to connect to the Amazon EC2 workstation through a desktop streaming protocol. AWS offers a high-end desktop experience through &lt;a href="https://aws.amazon.com/hpc/dcv/" target="_blank" rel="noopener"&gt;Amazon DCV&lt;/a&gt;. This is a performant remote display protocol capable of streaming 4k UHD resolution images over multiple monitors (up to 4), 60 frames per second, QUIC UDP support for high performance image streaming, 4:4:4 8-bit chroma sub-sampling, and stylus/touch device support for M&amp;amp;E workloads. Our posts show how to set up both the server and client for Amazon DCV on Windows and Linux.&lt;/p&gt; 
&lt;p&gt;The recent addition of &lt;a href="https://www.wacom.com/en-us/enterprise/creative-enterprise/wacom-bridge" target="_blank" rel="noopener"&gt;Wacom Bridge&lt;/a&gt; with Amazon DCV has optimized stylus operations further (on Windows at the time of writing, Linux in beta currently). This is both in terms of real-time user feedback on the local device, mitigating the effect of any potential latency delay, but also dedicated channel support for hardware communications to provide even lower latency performance, as well as the synchronization of settings.&lt;/p&gt; 
&lt;h2 id="workstation-connectivity"&gt;Workstation connectivity&lt;/h2&gt; 
&lt;p&gt;When establishing connectivity between your on-premises workstation and your EC2 instance, you have three primary options, each offering different levels of security, performance, and complexity.&lt;/p&gt; 
&lt;h3 id="internet-connectivity-used-in-this-post"&gt;Internet connectivity (used in this post)&lt;/h3&gt; 
&lt;p&gt;For this post, we use the most basic connection method: direct internet connectivity. This approach connects your local workstation to your Amazon EC2 instance over the public internet, with security groups (virtual firewalls) configured to restrict access to your specific IP address and only the necessary ports.&lt;/p&gt; 
&lt;p&gt;This method uses &lt;strong&gt;application-layer security&lt;/strong&gt; to provide built-in encryption for all Amazon DCV streaming sessions, which helps keep your visual data protected during transmission. Security groups operate at the &lt;strong&gt;network&lt;/strong&gt; and &lt;strong&gt;transport&lt;/strong&gt; layers to control which IP addresses and ports can reach your instances. Together, these layers provide complementary security properties:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Confidentiality in transit&lt;/strong&gt;: DCV session traffic is encrypted, which helps prevent an intermediary who intercepts the traffic from reading its contents.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Access control at the instance boundary&lt;/strong&gt;: Security groups accept connections only from IP addresses on your approved list, reducing the instance’s exposure to unsolicited inbound connection attempts.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Reduced attack surface&lt;/strong&gt;: Only the specific ports required for DCV are exposed, which limits how much of the instance is reachable from the network.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;This method provides a straightforward setup suitable for individual users or small teams, combining quick configuration with secure encrypted streaming. We discuss the security group configuration in detail later in this post.&lt;/p&gt; 
&lt;p&gt;The following diagram illustrates this internet-based connectivity architecture. It shows how an artist’s local workstation connects across the public internet to a GPU-backed EC2 instance in AWS, with Amazon DCV carrying the session between them.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-1.png" alt="Architecture diagram of on-premises Windows and Linux workstations connecting over the public internet through Amazon DCV to GPU-backed Amazon EC2 instances in an Amazon VPC" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 8: A streamlined architectural diagram showing on-premises and home workstations integrating with Amazon EC2 instances, using Amazon Machine Images and EBS storage, connecting through the internet&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="vpn-connectivity"&gt;VPN connectivity&lt;/h3&gt; 
&lt;p&gt;For organizations requiring additional security beyond basic internet connectivity, &lt;a href="https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html" target="_blank" rel="noopener"&gt;AWS Site-to-Site VPN&lt;/a&gt; provides encrypted tunnels that use the internet securely. This method creates a secure connection between your on-premises location and your AWS resources, allowing you to access EC2 workstations through encrypted channels while maintaining the high-performance capabilities needed for graphics-intensive work.&lt;/p&gt; 
&lt;p&gt;AWS Site-to-Site VPN adds &lt;strong&gt;network-layer encryption&lt;/strong&gt; on top of the &lt;strong&gt;application-layer&lt;/strong&gt; protection provided by Amazon DCV. The VPN establishes encrypted IPsec tunnels between your on-premises network and AWS, so traffic is protected at the network layer before it reaches the application. In practice this means your DCV session traffic travels inside an additional encrypted tunnel alongside the rest of your network connection.&lt;/p&gt; 
&lt;p&gt;Choosing Site-to-Site VPN over direct internet connectivity comes down to a few practical factors:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Security posture&lt;/strong&gt;: VPN extends your existing corporate network controls and policies into AWS, so the same governance you apply on-premises continues to apply to traffic reaching your instances. This is useful if your organization requires network-layer encryption or treats AWS as an extension of the internal network.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Operational complexity&lt;/strong&gt;: VPN requires configuring and maintaining the tunnel, a customer gateway, and routing on both sides. This is more involved than direct connectivity, which needs only a security group.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Cost&lt;/strong&gt;: Site-to-Site VPN carries &lt;a href="https://aws.amazon.com/vpn/pricing/" target="_blank" rel="noopener"&gt;an hourly connection charge&lt;/a&gt; plus data transfer.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;VPN connectivity is a good fit when you need to extend your corporate network into AWS and maintain consistent security policies across both environments, and when the added setup and cost are justified by that requirement.&lt;/p&gt; 
&lt;p&gt;The following diagram shows the VPN-based connectivity architecture. The key difference from the direct-internet setup is that the EC2 instances now sit in a private subnet with no public internet access. The Site-to-Site VPN carries all traffic between your on-premises network and AWS instead.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-2.png" alt="Architecture diagram of on-premises workstations connecting through an IPsec Site-to-Site VPN to GPU-backed Amazon EC2 instances in a private subnet" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 9: A streamlined architectural diagram showing on-premises and home workstations integrating with Amazon EC2 instances, using Amazon Machine Images and EBS storage, connecting through a Site-to-Site VPN&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="aws-direct-connect"&gt;AWS Direct Connect&lt;/h3&gt; 
&lt;p&gt;For workloads that need consistent network performance and a connection that doesn’t traverse the public internet, &lt;a href="https://aws.amazon.com/directconnect/" target="_blank" rel="noopener"&gt;AWS Direct Connect&lt;/a&gt; establishes a dedicated physical connection between your on-premises location and AWS. Through your chosen network provider, it creates a private link from your premises to the AWS Region containing your Amazon EC2 G instances, which can offer more predictable latency and bandwidth than an internet-based connection.&lt;/p&gt; 
&lt;p&gt;AWS Direct Connect provides additional isolation at the &lt;strong&gt;physical&lt;/strong&gt; and &lt;strong&gt;data link layers&lt;/strong&gt; by using a dedicated connection that doesn’t traverse the public internet. Your traffic travels over private network infrastructure between your location and AWS, which keeps it off shared internet paths and gives you more consistent, predictable network behavior than an internet-based connection. Because the connection is private and dedicated, it isn’t exposed to the general internet in the way a public connection is.&lt;/p&gt; 
&lt;p&gt;AWS Direct Connect is ideal for organizations requiring consistent network performance, enhanced security, and reduced data transfer costs when working with graphics workstations in the cloud. Combined with the &lt;strong&gt;application-layer&lt;/strong&gt; encryption of Amazon DCV, this provides defense-in-depth across the entire network stack, from the physical cables through to the application data itself. This approach provides the most predictable latency and bandwidth for demanding creative workflows.&lt;/p&gt; 
&lt;p&gt;The following diagram depicts the Direct Connect connectivity architecture. As with the VPN option, the EC2 instances sit in private subnets with no need for public internet access, but here the connection runs over a dedicated Direct Connect link between your on-premises location and AWS.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-3.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-3.png" alt="Architecture diagram of on-premises workstations connecting over an AWS Direct Connect link to GPU-backed Amazon EC2 instances in a private subnet" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 10: A streamlined architectural diagram showing on-premises and home workstations integrating with Amazon EC2 instances, using Amazon Machine Images and EBS storage, connecting through a Direct Connect link&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Consult the documentation for further details and options around VPN offerings, as well as Direct Connect, to inform your security decisions. For further information, and additional firewall and protection services that can enhance protection against exploits such as ransomware and DDoS, please see &lt;a href="https://aws.amazon.com/products/security/" target="_blank" rel="noopener"&gt;Security, Identity and Compliance on AWS&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="latency"&gt;Latency&lt;/h2&gt; 
&lt;p&gt;A superior virtual workstation experience relies on low-latency and high-bandwidth connectivity from your local client to your EC2 instance. Bandwidth requirements vary based on several factors such as the number of monitors, screen resolution, frame rate, and visual quality settings. For creative professionals using Wacom tablets or similar input devices, we recommend a latency round trip of 50 ms or less when using Amazon DCV. To evaluate your connection’s suitability, there are a number of third-party websites that you can use to test latency between your location and the nearest Region, such as &lt;a class="uri" href="https://aws-latency-test.com/" target="_blank" rel="noopener"&gt;https://aws-latency-test.com/&lt;/a&gt; or &lt;a class="uri" href="https://www.cloudping.info/" target="_blank" rel="noopener"&gt;https://www.cloudping.info/&lt;/a&gt;.&lt;/p&gt; 
&lt;blockquote&gt;
 &lt;p&gt;&lt;em&gt;“Our collaboration with the AWS Visual Computing team and the use of EC2 instances as virtual workstations, has exceeded our expectations, delivering exceptional result.”&lt;/em&gt;&lt;/p&gt; 
 &lt;p&gt;— John Coyne, Senior Technical Manager, Sky TV&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;h2 id="workstation-build-overview"&gt;Workstation build overview&lt;/h2&gt; 
&lt;p&gt;For the purposes of this post, we focus on deploying a g6 family instance.&lt;/p&gt; 
&lt;p&gt;The following overview outlines the complete build across the whole series. Part 1 covers the prerequisites and base image selection. The remaining phases such as the instance configuration, creating Amazon Machine Images, and setting up launch templates are covered in later parts.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Prerequisites. 
  &lt;ul&gt; 
   &lt;li&gt;Account setup and GPU instance quotas.&lt;/li&gt; 
   &lt;li&gt;Security configurations (access, firewalls, permissions).&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;Base image selection. 
  &lt;ul&gt; 
   &lt;li&gt;Linux and Windows options.&lt;/li&gt; 
   &lt;li&gt;Customization for VFX needs.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;Instance configuration. 
  &lt;ul&gt; 
   &lt;li&gt;Linux and Windows set up.&lt;/li&gt; 
   &lt;li&gt;GPU and system tools installation.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;Creating &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html" target="_blank" rel="noopener"&gt;Amazon Machine Images (AMIs)&lt;/a&gt; to capture the resultant machine image.&lt;/li&gt; 
 &lt;li&gt;Setting up EC2 Launch Templates to encapsulate all boot requirements. 
  &lt;ul&gt; 
   &lt;li&gt;Standardizing deployment parameters.&lt;/li&gt; 
   &lt;li&gt;Streamlining future workstation launches.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;GPU optimization tips and resources.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h2 id="cost-consideration"&gt;Cost consideration&lt;/h2&gt; 
&lt;p&gt;In these posts we use different AWS services, with each service having a cost associated with its usage. EC2 instances are charged by the second, so you must make sure that you shut down or terminate the instances when you are finished to avoid unwanted costs.&lt;/p&gt; 
&lt;h2 id="accessing-aws-services-through-the-aws-command-line-interface"&gt;Accessing AWS services through the AWS Command Line Interface&lt;/h2&gt; 
&lt;p&gt;AWS has many API/SDK entry points for creating and manipulating services. In this post we use the &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;, a convenient utility that you can use to query and set AWS service properties through the command line. In both the Windows and Linux deployment posts we set up the CLI for later convenience.&lt;/p&gt; 
&lt;p&gt;For more information about how to configure the credentials for usage with the CLI, as well as the range of functionality that you can use with it, go to the &lt;a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html" target="_blank" rel="noopener"&gt;AWS CLI User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="workstation-prerequisites-part-1-account-setup-and-service-quotas"&gt;Workstation prerequisites Part 1: account setup and service quotas&lt;/h2&gt; 
&lt;p&gt;The following steps are used to set up a secure Amazon &lt;a href="https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html" target="_blank" rel="noopener"&gt;Virtual Private Cloud&lt;/a&gt; (Amazon VPC) network platform for your instances, providing security and permissions for accessing and configuring your instance:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Create an &lt;a href="https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/" target="_blank" rel="noopener"&gt;AWS account&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;Open and configure the &lt;a href="https://aws.amazon.com/console/" target="_blank" rel="noopener"&gt;AWS Management Console&lt;/a&gt; to gain access to AWS. 
  &lt;ul&gt; 
   &lt;li&gt;Go to the Console.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="setting-the-region"&gt;Setting the AWS Region&lt;/h3&gt; 
&lt;p&gt;At the time of writing, AWS has 39 geographic Regions, each composed of multiple AWS Availability Zones (AZs) to make sure of service availability and durability, and over 35 &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/localzones/" target="_blank" rel="noopener"&gt;AWS Local Zones&lt;/a&gt; (which are infrastructure deployments that place compute, storage, and other select AWS services closer to large population and industry centers). For more information, see the &lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/" target="_blank" rel="noopener"&gt;AWS Documentation on Global Infrastructure&lt;/a&gt;. As we previously mentioned, latency can be critical for optimal virtual workstation experiences. Therefore, we recommend building your workstations in a Region that offers the best latency experience. This is configured on the console itself:&lt;/p&gt; 
&lt;ol start="3" type="1"&gt; 
 &lt;li&gt;Choose your AWS Region that best suits your needs (a drop down of AWS Regions is available at the top right of the Console).&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;AWS services can vary across AWS Regions, so before proceeding you must confirm that g6 instances are available in your AWS Region of choice. This can be done through the Amazon EC2 service page, as shown in the following figure:&lt;/p&gt; 
&lt;ol start="4" type="1"&gt; 
 &lt;li&gt;Open the &lt;strong&gt;Amazon EC2&lt;/strong&gt; service page, the central service page for deploying EC2 instances. 
  &lt;ul&gt; 
   &lt;li&gt;Search for “EC2” in the Service search bar (top left), or choose &lt;strong&gt;Services&lt;/strong&gt; -&amp;gt; &lt;strong&gt;Compute&lt;/strong&gt; -&amp;gt; &lt;strong&gt;EC2&lt;/strong&gt;.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Instance Types&lt;/strong&gt; in the left pane.&lt;/li&gt; 
 &lt;li&gt;Enter “g6” into the &lt;strong&gt;Instance Types&lt;/strong&gt; search bar and confirm that the various g6 instance types are listed as available in that AWS Region. The following image shows a filtered response from the &lt;strong&gt;Instance Types&lt;/strong&gt; pane.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-4.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-4.png" alt="Amazon EC2 Instance Types console page filtered to show the available g6 instance types in a Region" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 11: A screen capture of the Instance Types page, reporting g6 Amazon EC2 availability in a Region&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="service-limits"&gt;Service limits&lt;/h3&gt; 
&lt;p&gt;Limits exist around many AWS services. They act as guard rails for new users and prevent misuse of AWS services. New AWS accounts start with low limits to prevent unintentional spend, so you need to check the account limits to make sure that there is enough GPU vCPU quota to launch your workstation. You can check and request limit changes through the Service Quotas service page:&lt;/p&gt; 
&lt;ol start="7" type="1"&gt; 
 &lt;li&gt;Navigate to the &lt;strong&gt;Service Quotas&lt;/strong&gt; page by searching for its name in the &lt;strong&gt;Services search bar&lt;/strong&gt; (top left of the Console window). Or alternatively choose &lt;strong&gt;Services -&amp;gt; Management and Governance -&amp;gt; Service Quotas&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;You can choose the star icon next to each service to bookmark it for access later at the top of the Console.&lt;/p&gt; 
&lt;ol start="8" type="1"&gt; 
 &lt;li&gt;Under &lt;strong&gt;Manage quotas&lt;/strong&gt; (top right), enter &lt;strong&gt;EC2&lt;/strong&gt; in the search field, choose &lt;strong&gt;Amazon Elastic Compute Cloud (Amazon EC2)&lt;/strong&gt;, and choose &lt;strong&gt;View quotas&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;In the &lt;strong&gt;Service quotas&lt;/strong&gt; search field that appears, enter &lt;strong&gt;On-Demand G&lt;/strong&gt; and the list of quotas should reduce to just &lt;strong&gt;Running On-Demand G and VT instances&lt;/strong&gt;, the quota controlling your access to G instance machines, as shown in the following figure.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-5.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-5.png" alt="Service Quotas console showing the Running On-Demand G and VT instances quota with an applied value of 64" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 12: A screen capture of the Service Quotas page, requesting an increase to the GPU limit&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;You can see the current Applied account-level quota value, which is your limit on how many vCPUs you can use at any given time in this Region. This is not the number of instances (a common misconception)! We recommend making sure that you have at least a quota of 32, because this is enough to run two g6.4xlarge instances, a common size that suits basic 2D and 3D workflows. If the value in the applied account-level quota is below this, then you must submit a request to increase it:&lt;/p&gt; 
&lt;ol start="10" type="1"&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Request Increase at account level&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Enter “32” in the &lt;strong&gt;Increase quota value&lt;/strong&gt; field.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Request&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;When you receive an email confirmation of the increase, check the quota limit again for a value of 32 and you are safe to proceed with the rest of the post.&lt;/p&gt; 
&lt;h2 id="workstation-prerequisites-part-2-networking-and-security"&gt;Workstation prerequisites Part 2: networking and security&lt;/h2&gt; 
&lt;p&gt;When you have received your Service Quota increase, you can continue back in the AWS Management Console to start setting up some auxiliary components needed for workstations, for example security keys, firewall groups, and so on.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Open the &lt;strong&gt;Amazon EC2&lt;/strong&gt; service page, the central service page for deploying EC2 instances. 
  &lt;ul&gt; 
   &lt;li&gt;Search for “EC2” in the Service search bar (top left) or choose &lt;strong&gt;Services&lt;/strong&gt; -&amp;gt; &lt;strong&gt;Compute&lt;/strong&gt; -&amp;gt; &lt;strong&gt;EC2&lt;/strong&gt;.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="amazon-ec2-key-pair-security"&gt;Amazon EC2 key pair security&lt;/h3&gt; 
&lt;p&gt;Amazon EC2 key pairs are security credentials that validate your identity when accessing EC2 instances.&lt;/p&gt; 
&lt;p&gt;To set up an Amazon EC2 key pair:&lt;/p&gt; 
&lt;ol start="2" type="1"&gt; 
 &lt;li&gt;Under &lt;strong&gt;Network and Security&lt;/strong&gt; on the left side of the panel, choose &lt;strong&gt;Key Pairs&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create key pair&lt;/strong&gt; in the top right.&lt;/li&gt; 
 &lt;li&gt;Give your new key pair a name, for example &lt;code&gt;ec2_test_keypair&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Leave the key pair as an &lt;strong&gt;RSA&lt;/strong&gt; type, with a &lt;strong&gt;.pem&lt;/strong&gt; extension, and choose &lt;strong&gt;Create key pair&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Store the automatically downloaded &lt;code&gt;.pem&lt;/code&gt; file in a safe place, because you need it later.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;You should restrict the permissions on the &lt;code&gt;.pem&lt;/code&gt; file so that only you can read it.&lt;/p&gt; 
&lt;p&gt;On a Mac or Linux machine you can change the permission in a terminal:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;chmod 400 &amp;lt;&amp;lt;YOUR_EC2_TEST_KEYPAIR_PEM_FILE&amp;gt;&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;On Windows, open the context menu for the file, choose &lt;strong&gt;Properties&lt;/strong&gt;, then the &lt;strong&gt;Security&lt;/strong&gt; tab, choose &lt;strong&gt;Advanced&lt;/strong&gt;, choose &lt;strong&gt;Disable inheritance&lt;/strong&gt;, and remove access to all users except the current user. For more information surrounding the best use of key pairs, go to the relevant section in the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-key-pairs.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="virtual-firewalls"&gt;Virtual firewalls&lt;/h3&gt; 
&lt;p&gt;Security groups act as virtual firewalls, restricting incoming and outgoing traffic to your G instances. You should set up a security group working on the principle of &lt;em&gt;least privilege&lt;/em&gt;, which means you must be very specific about which ports and which IP addresses can access it:&lt;/p&gt; 
&lt;ol start="7" type="1"&gt; 
 &lt;li&gt;Under &lt;strong&gt;Network and Security&lt;/strong&gt; on the left pane, choose &lt;strong&gt;Security groups&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create Security Group&lt;/strong&gt; in the top left.&lt;/li&gt; 
 &lt;li&gt;Give your security group a name, for example &lt;code&gt;ec2_test_sg&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Give your security group a meaningful description, for example &lt;code&gt;SG for basic EC2 interaction&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Leave the VPC as-is. This automatically presents the ‘default’ VPC in your account and AWS Region.&lt;/li&gt; 
 &lt;li&gt;The following Inbound rules ports must be added to the security group to allow access to that machine from a specific client’s source IP address: in this case your local machine. Under &lt;strong&gt;Inbound rules&lt;/strong&gt;, use the &lt;strong&gt;Add rule&lt;/strong&gt; feature multiple times to add the definitions defined in the following figure, using the &lt;strong&gt;My IP&lt;/strong&gt; drop-down under &lt;strong&gt;Source&lt;/strong&gt; to automatically determine and use your current IP address, appending the /32 CIDR to limit the connectivity to that single address.The following table contains a list of TCP and UDP ports to add to your security group.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;table border="1px" width="120%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Type&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Protocol&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Port Range&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Source&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;SSH&lt;/td&gt; 
   &lt;td&gt;TCP&lt;/td&gt; 
   &lt;td&gt;22&lt;/td&gt; 
   &lt;td&gt;&lt;em&gt;&amp;lt;YOUR “CUSTOM” CLIENT SOURCE IP&amp;gt;&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;SSH for Linux platform.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Custom TCP Rule&lt;/td&gt; 
   &lt;td&gt;TCP&lt;/td&gt; 
   &lt;td&gt;443&lt;/td&gt; 
   &lt;td&gt;&lt;em&gt;&amp;lt;YOUR “CUSTOM” CLIENT SOURCE IP&amp;gt;&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;HTTPS for both platforms.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;Custom TCP Rule&lt;/td&gt; 
   &lt;td&gt;TCP&lt;/td&gt; 
   &lt;td&gt;8443&lt;/td&gt; 
   &lt;td&gt;&lt;em&gt;&amp;lt;YOUR “CUSTOM” CLIENT SOURCE IP&amp;gt;&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;Amazon DCV for both platforms.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Custom UDP Rule&lt;/td&gt; 
   &lt;td&gt;UDP&lt;/td&gt; 
   &lt;td&gt;8443&lt;/td&gt; 
   &lt;td&gt;&lt;em&gt;&amp;lt;YOUR “CUSTOM” CLIENT SOURCE IP&amp;gt;&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;Amazon DCV for both platforms.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr style="background-color: #f1f5fd"&gt; 
   &lt;td&gt;RDP&lt;/td&gt; 
   &lt;td&gt;TCP&lt;/td&gt; 
   &lt;td&gt;3389&lt;/td&gt; 
   &lt;td&gt;&lt;em&gt;&amp;lt;YOUR “CUSTOM” CLIENT SOURCE IP&amp;gt;&lt;/em&gt;&lt;/td&gt; 
   &lt;td&gt;RDP for Windows platform.&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;em&gt;Figure 13: The list of inbound ports that need to be opened to allow user access to the EC2 instance for the purpose of this post&lt;/em&gt;&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;For the purposes of this post, we’re making a single security group that encompasses both Linux and Windows. If you’re only focusing on a specific operating system, then a security consideration would be to remove the unneeded ports.&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;ol start="13" type="1"&gt; 
 &lt;li&gt;For &lt;strong&gt;Outbound rules&lt;/strong&gt;, the default allows all outbound traffic. This is enough for the instance to download packages and reach AWS service endpoints during setup, and because inbound access is already restricted to your IP, it doesn’t open an inbound path. Open outbound traffic is, however, the route that data exfiltration or a compromised host’s callbacks would use. Once your instance is running and you know which destinations it genuinely needs (for example, HTTPS 443 to AWS and your package repositories), restrict outbound rules to those destinations rather than leaving them fully open.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create security group&lt;/strong&gt; to finish making the security group.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="identity-and-access-management"&gt;Identity and Access Management&lt;/h3&gt; 
&lt;p&gt;AWS advocates a policy of least permissions, establishing a strong base security standpoint, which necessitates that you add the permissions needed for access to services. To allow your Amazon EC2 workstation instance to access services such as &lt;a href="https://aws.amazon.com/s3/" target="_blank" rel="noopener"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt; (for graphics drivers), you must create a role to encompass these permissions for your instance. You should set up an &lt;a href="https://aws.amazon.com/iam/" target="_blank" rel="noopener"&gt;AWS Identity and Access Management (IAM)&lt;/a&gt; profile to allow the instance access to the necessary services.&lt;/p&gt; 
&lt;ol start="15" type="1"&gt; 
 &lt;li&gt;Navigate to the &lt;strong&gt;IAM&lt;/strong&gt; service page by entering “IAM” into the Service search field (top left), or choose &lt;strong&gt;Security, Identity &amp;amp; Compliance &amp;gt; IAM&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Roles&lt;/strong&gt; (in the left side pane).&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create role&lt;/strong&gt;, in the top right.&lt;/li&gt; 
 &lt;li&gt;Leave the &lt;strong&gt;Trusted entity type&lt;/strong&gt; as &lt;strong&gt;AWS service&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;You must use AWS approved NVIDIA GPU drivers, issued through Amazon S3, not only for optimal compatibility and performance, but also to make sure that the necessary professional GRID drivers are automatically provisioned. Therefore, you need a role that can read from Amazon S3. You should use a very generic Amazon S3 read-only policy to allow read access to public S3 buckets (such as the bucket on which AWS shares GPU drivers).&lt;/p&gt; 
&lt;ol start="19" type="1"&gt; 
 &lt;li&gt;Under &lt;strong&gt;Use case&lt;/strong&gt;, enter “S3” and then choose &lt;strong&gt;Next&lt;/strong&gt; (bottom right).&lt;/li&gt; 
 &lt;li&gt;Search for &lt;code&gt;AmazonS3ReadOnlyAccess&lt;/code&gt; and choose the box to the left of the policy to add it to the role. Then, choose &lt;strong&gt;Next&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Give your new role a name, for example &lt;code&gt;basic_workstation_role&lt;/code&gt;.&lt;/li&gt; 
 &lt;li&gt;Choose &lt;strong&gt;Create role&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;If later on you want to add more service features to your workstation role (for example to enable write permissions from the workstation to one of your own storage buckets), then you can use the same process to add pre-defined permissions or create your own in JSON.&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;You now have an account, and the resources needed to launch EC2 instances, which are covered in our next posts.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;In this post we have discussed the different generation Amazon EC2 instance families: their memory, network, storage, and GPU options. We have outlined the steps needed not only to prepare an AWS account for running GPU workstations but also to build key infrastructure that is needed to deploy them.&lt;/p&gt; 
&lt;p&gt;We recommend that you continue to Part 2 of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-2-linux/"&gt;Building a GPU workstation for visual effects on Amazon EC2: Part 2 – Linux&lt;/a&gt;, where you can learn how to create a Linux-backed workstation. You can also read Part 3 of our series, &lt;a href="https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows/"&gt;Building a GPU workstation for visual effects with Amazon EC2: Part 3 – Windows&lt;/a&gt;, to learn how to create a Windows-backed workstation.&lt;/p&gt; 
&lt;p&gt;For more information contact us at &lt;a class="email" href="mailto:aws-visual-compute-interest@amazon.com"&gt;aws-visual-compute-interest@amazon.com&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="further-reading"&gt;Further reading&lt;/h2&gt; 
&lt;p&gt;If you want to augment a VFX workstation environment with a dedicated render farm, then consider the managed service &lt;a href="https://aws.amazon.com/deadline-cloud/" target="_blank" rel="noopener"&gt;AWS Deadline Cloud&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;EC2 instance metrics, such as CPU and memory usage, are sent to &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt;, where you can access this data through the AWS Management Console and AWS CLI. This information can be pertinent to discern if an EC2 instance is being over or under provisioned for the work at hand. In other words, it has excessive CPU, memory, and networking resources for the current tasks, and it could be optimized for price, or the alternative where it has not been allocated enough resources to cope. For more information, go to the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring_ec2.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;More advanced examples of using Amazon DCV can be found in this &lt;a href="https://github.com/aws-samples/dcv-samples" target="_blank" rel="noopener"&gt;“aws-samples” GitHub repo&lt;/a&gt;. This includes methods to broker multiple users and instances. Furthermore, DCV Connection Gateway provides a single-entry point for users to connect to multiple DCV sessions across different instances, streamlining access management and improving security through centralized authentication.&lt;/p&gt; 
&lt;p&gt;Commercial options also exist to perform artist/instance brokering, using Amazon DCV and Amazon EC2 Launch templates. An example of such an offering is &lt;a href="https://leostream.com/" target="_blank" rel="noopener"&gt;Leostream&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;For reference, examples of setting up Amazon DCV capable instances, and using &lt;a href="https://aws.amazon.com/cloudformation/" target="_blank" rel="noopener"&gt;AWS CloudFormation&lt;/a&gt; templates as a method of deployment, can be found in this &lt;a href="https://github.com/aws-samples/amazon-ec2-nice-dcv-samples" target="_blank" rel="noopener"&gt;GitHub repo&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;A greater depth of analysis of bit rates, and latency, surrounding Amazon DCV connections can be found in &lt;a href="https://aws.amazon.com/blogs/hpc/putting-bitrates-into-perspective/" target="_blank" rel="noopener"&gt;this AWS HPC post&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-6.jpg" alt="Andy Hayes" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Andy Hayes&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Andy is a Senior Visual Computing Solutions Architect at AWS. With 20 years’ experience in Visual Effects and Animation, Andy has led CG divisions and departments and added supervision to film projects, earning both Annie and Visual Effects Society Awards along the way. At AWS, he partners with studios and creative technology companies across the Media &amp;amp; Entertainment industry, spanning VFX and animation to rendering, virtual production, and games, helping them design and scale the cloud infrastructure and workflows behind their content pipelines. Drawing on his production background, Andy bridges the worlds of artists and engineers, guiding customers as they adopt technologies like high-performance rendering, GPU compute, and increasingly AI and machine learning to solve real creative and technical challenges. He remains passionate about the marriage of art and science that leads to the creation of compelling imagery, and about aligning technology to the evolving needs of the industry.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/23/ComputeBlog-2764-7.jpg" alt="Mike Owen" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Mike Owen&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Mike is a Principal Visual Computing Solutions Architect at AWS, where he has spent many years helping studios move their creative work to the cloud. He focuses on the architecture behind high-end content creation: cloud workstations, render farm scaling and storage that spans multiple sites. Mike works with studios and creative technology companies across Media &amp;amp; Entertainment, from VFX and animation to finishing and colour. He has pioneered the concept of “Studio in the Cloud” and helped bring industry tools such as Autodesk Flame to AWS, and has contributed to a range of AWS Thinkbox Deadline improvements. Most recently he has led development of KNFSD File Cache, an open-source NFS caching solution from AWS. It lets studios burst large render workloads into the cloud whilst their data stays on existing on-premises storage. He cares about giving artists the same seamless, colour-accurate experience in the cloud that they expect on-premises, and about removing the cost and complexity that usually come with building a global studio.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Nitro Sandboxes: Hardware isolation for every EKS pod, ECS task, and EC2 workload</title>
		<link>https://aws.amazon.com/blogs/compute/nitro-sandboxes-hardware-isolation-for-every-eks-pod-ecs-task-and-ec2-workload/</link>
		
		<dc:creator><![CDATA[Alex Graf]]></dc:creator>
		<pubDate>Tue, 10 Nov 2026 20:00:39 +0000</pubDate>
				<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon Elastic Kubernetes Service]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Expert (400)]]></category>
		<guid isPermaLink="false">ed86bd36252822d0e4cb23c658328d7b0bc21e98</guid>

					<description>AWS Nitro Sandboxes is a new Amazon EC2 building block that gives each container, EKS pod, or ECS task the boundary of a hardware-isolated virtual machine, bringing the Nitro System's strong isolation, zero operator access, and cryptographic attestation to container workloads at near-native performance.</description>
										<content:encoded>&lt;p&gt;Security has been the foundation of AWS cloud computing since day one. When we built Amazon Elastic Compute Cloud (Amazon EC2), we designed it with strong isolation that keeps customer workloads and data separated from every other tenant on the same hardware. The AWS Nitro System took that further by moving virtualization, storage, and networking onto dedicated hardware, making zero operator access to customer data the default. Customers then asked us for more. They wanted tightly scoped, attestable environments for their most sensitive processing: the code and data that required protection even from their own administrators. That’s why we built Nitro Enclaves. Today, more of those sensitive workloads run in containers on Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (Amazon ECS), and self-managed Kubernetes and container runtimes on Amazon EC2. Customers are asking for the same level of isolation and confidentiality for container environments.&lt;/p&gt; 
&lt;p&gt;Container environments today host many independent workloads on a single EC2 instance by using Linux container technology. For a lot of customers, Linux containers have become the prevalent workload delivery vehicle because of their ease of deployment and the ability to have them share resources in one host through a shared kernel. This sharing has some downsides. Operators of a shared cluster have access to all the tasks running in it. A weakness in the shared kernel reachable by one container also exposes every other container on the host. With the current rate of Linux Common Vulnerabilities and Exposures (CVEs), containerized workloads need an architecture that isolates each workload from other workloads and from cluster operators.&lt;/p&gt; 
&lt;h2 id="introducing-aws-nitro-sandboxes"&gt;Introducing AWS Nitro Sandboxes&lt;/h2&gt; 
&lt;p&gt;This week we introduced AWS Nitro Sandboxes, a new Amazon EC2 building block that gives each container the boundary of a hardware-isolated virtual machine (VM). Each sandbox gets the security properties of the Nitro System (strong isolation, zero operator access to customer data, and attestation) while keeping the familiar container experience. And isolation is designed so that no one outside the Nitro Sandbox can read its contents: Neither the cluster administrator, the platform team, nor AWS can read EKS pod or ECS task memory.&lt;/p&gt; 
&lt;p&gt;A Nitro Sandbox is a lightweight virtual machine that you launch and control from your EC2 instance. To your instance, it behaves like a child VM. Under the hood, it runs as a separate VM alongside your instance. The Nitro System enforces separation between the sandbox and its parent instance, between sandboxes, and between the sandbox and AWS operators. The parent instance contributes vCPU, memory, and I/O. Nitro keeps the workload isolated and, when you ask, proves what code it is running.&lt;/p&gt; 
&lt;p&gt;Because a Nitro Sandbox is a first-level guest with no nested hypervisor, and the Nitro Hypervisor enforces its CPU and memory boundary in hardware, compute and memory run at near-native EC2 performance. Instead of needing a separate instance for every workload or customer that needs a hard boundary, you can consolidate many isolated workloads onto instances you already run. You can then improve utilization and lower cost without giving up the boundary that made separate instances attractive in the first place.&lt;/p&gt; 
&lt;p&gt;Nitro Sandboxes share the same Nitro System isolation technology that we have operated for years as Nitro Enclaves. With Nitro Enclaves, we designed everything around the smallest possible surface: You dedicate full CPU cores and memory to a separate VM that you can only reach over a vsock channel. With Nitro Sandboxes, we built on the same foundation, but adjusted the experience to the needs of container workloads in three ways. First, a sandbox’s vCPUs can share cores with the parent instance through time slicing. Second, the parent can attach standard virtio network and block devices, not only a vsock channel, so the sandbox gets real networking and storage. Third, you can run the sandbox through a standard virtual machine monitor (VMM) such as Firecracker. The result is a general-purpose, hardware-isolated environment that behaves like a normal VM and runs almost anywhere EC2 runs.&lt;/p&gt; 
&lt;p&gt;We then took Nitro Sandboxes and natively integrated them into Amazon EKS and Amazon ECS, providing a turnkey solution to Nitro-backed, confidential virtual-machine-based container isolation at scale. Nitro Sandboxes are broadly available with the following features:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Instances:&lt;/strong&gt; Every EC2 instance type that supports Nitro Enclaves, across general purpose, compute optimized, memory optimized, storage optimized, and accelerated families, on AWS Graviton, Intel, and AMD processors, in commercial Regions worldwide, at no additional charge.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Storage:&lt;/strong&gt; Sandboxes reach storage the same way an EC2 instance does: local instance store for scratch space, Amazon Elastic Block Store (Amazon EBS) for persistent volumes, and Amazon Simple Storage Service (Amazon S3) or Amazon Elastic File System (Amazon EFS) over the network. To keep data confidential from the parent, you can use attestation-gated AWS Key Management Service (AWS KMS) keys, the same model as Nitro Enclaves, now integrated into Nitro Sandboxes, EKS, and ECS.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Networking:&lt;/strong&gt; Each sandbox runs its own kernel, and therefore its own network stack. The parent connects that stack to your Amazon Virtual Private Cloud (Amazon VPC) the same way it does for containers today. On EKS, pods keep their own VPC IP address through the Amazon VPC CNI. On ECS, each task gets its own elastic network interface in &lt;code&gt;awsvpc&lt;/code&gt; mode. Network policies and security groups are enforced on the parent instance, outside the sandbox, so a compromised workload cannot turn them off.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;With Nitro Sandboxes, you can give every workload that needs a hard boundary its own VM, without giving it its own instance. AI agents that write and run their own code can run each session in a separate sandbox. Code that a prompt injection gets the agent to run stays inside one VM, which is deleted when the session ends. Software as a service (SaaS) providers can run many tenants on shared EKS nodes or ECS Managed Instances, each in its own sandbox, instead of giving each tenant a dedicated instance. Continuous integration and continuous delivery (CI/CD) pipelines can run privileged builds and untrusted pull request code inside a per-job VM rather than on dedicated build machines. And with confidential sandboxes, model providers can deploy closed-weight models in a customer’s account, knowing the weights are decrypted only inside an attested sandbox. Regulated industries can give auditors cryptographic proof of exactly what ran.&lt;/p&gt; 
&lt;h2 id="isolation-by-design"&gt;Isolation by design&lt;/h2&gt; 
&lt;p&gt;Containers on a shared node all trust one Linux kernel. A single kernel issue can lead to data exposure across pods or tasks. With Nitro Sandboxes, each pod, task, or agent runs in its own VM with its own kernel. A kernel issue in one sandbox doesn’t affect its neighbors.&lt;/p&gt; 
&lt;p&gt;The Nitro Hypervisor establishes strong, virtual-machine-based security isolation through its leading &lt;a href="https://aws.amazon.com/blogs/security/ec2-defenses-against-l1tf-reloaded/" target="_blank" rel="noopener"&gt;security posture&lt;/a&gt; and &lt;a href="https://aws.amazon.com/blogs/security/confidential-computing-an-aws-perspective/" target="_blank" rel="noopener"&gt;built-in confidential computing&lt;/a&gt; which we continuously extend. The hypervisor removes the parent’s access to the sandbox’s memory and CPU register state. Only I/O buffers that the sandbox explicitly shares stay visible to the parent.&lt;/p&gt; 
&lt;p&gt;Nitro Sandboxes can therefore treat the parent instance as untrusted and attest to what runs inside. They use the Nitro-based Nitro Secure Module (NSM) to gain an attestation document in the same style as Nitro Enclaves. A workload can be configured to get its secrets only after it proves it is running the code you approved. The system is designed so that no one outside the sandbox can read its contents: Neither the cluster administrator, the platform team, nor AWS can read EKS pod or ECS task memory. You write AWS KMS key policies that require specific attestation measurements before AWS KMS releases a decryption key. This creates a verifiable link between who can decrypt and what code is actually running.&lt;/p&gt; 
&lt;h2 id="isolation-modes-in-eks-and-ecs"&gt;Isolation modes in EKS and ECS&lt;/h2&gt; 
&lt;p&gt;On top of Nitro Sandboxes, EKS and ECS provide two isolation modes. With these modes, you can choose between faster launch times and cryptographic attestation:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Confidential sandbox:&lt;/strong&gt; Sandboxes are fully attestable. Image loading and other runtime operations are gated by a Cedar policy, image contents are verified and extracted inside the sandbox, and the ephemeral layer is encrypted. AWS KMS releases your secrets only to workloads that prove they run the code you approved. Use this mode for anything that handles secrets, including when you want protection from your own operators. SaaS providers can show their customers that tenant data is protected through attestation. Regulated industries can give auditors cryptographic evidence in addition to documentation.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Isolated sandbox:&lt;/strong&gt; Each pod (EKS) or task (ECS) runs in its own hardware-isolated VM with its own kernel, protecting the node and neighboring workloads from anything that happens inside the sandbox. The node and its operators are trusted, just as they are for pods and tasks today, and image validation works the same as it does without sandboxes. For workloads that also need protection from the node operator, use confidential sandbox.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="getting-started-on-amazon-eks"&gt;Getting started on Amazon EKS&lt;/h3&gt; 
&lt;p&gt;To get started on EKS, use EKS Auto Mode. Add &lt;code&gt;runtimeClassName&lt;/code&gt; to your pod spec, and EKS handles instance selection, Nitro component setup, and scheduling. Use &lt;code&gt;confidential-sandbox&lt;/code&gt; for a confidential sandbox or &lt;code&gt;isolated-sandbox&lt;/code&gt; if you do not need protection from node operators. For self-managed EKS, you will need a compatible Amazon Machine Image (AMI) to support Nitro Sandboxes.&lt;/p&gt; 
&lt;p&gt;To learn more about the EKS experience with Nitro Sandboxes, see the &lt;a href="https://aws.amazon.com/blogs/containers/aws-nitro-sandboxes-hardware-enforced-workload-isolation-on-amazon-eks/" target="_blank" rel="noopener"&gt;Amazon EKS blog post&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="getting-started-on-amazon-ecs"&gt;Getting started on Amazon ECS&lt;/h3&gt; 
&lt;p&gt;You can use Nitro Sandboxes on ECS with ECS Managed Instances. ECS launches compatible EC2 instances in your account, sets up a fully configured Bottlerocket image, and runs each task in its own Nitro Sandbox. ECS supports two isolation modes, &lt;code&gt;CONFIDENTIAL_SANDBOX&lt;/code&gt; and &lt;code&gt;ISOLATED_SANDBOX&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;To get started, update the Nitro Sandboxes settings. First, enable &lt;code&gt;nitroEnclavesEnabled&lt;/code&gt; to activate Nitro Sandboxes in your capacity provider. Next, set an isolation mode in your task definition, then add a &lt;code&gt;trustedExecutionConfiguration&lt;/code&gt; block to your task definition and set &lt;code&gt;isolationMode&lt;/code&gt; to &lt;code&gt;ISOLATED_SANDBOX&lt;/code&gt; or &lt;code&gt;CONFIDENTIAL_SANDBOX&lt;/code&gt;. Isolated and confidential tasks use the &lt;code&gt;awsvpc&lt;/code&gt; network mode, so each task gets its own elastic network interface.&lt;/p&gt; 
&lt;p&gt;Each task reports its isolation mode in a read-only &lt;code&gt;trustedExecutionSummary&lt;/code&gt; field when you describe it. Per-task security groups, VPC Flow Logs, Application Load Balancer, Network Load Balancer, and Amazon VPC Lattice work as before. To learn more about the ECS experience with Nitro Sandboxes, see the &lt;a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/isolated-confidential-tasks.html" target="_blank" rel="noopener"&gt;Amazon ECS Developer Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="getting-started-on-amazon-ec2"&gt;Getting started on Amazon EC2&lt;/h3&gt; 
&lt;p&gt;If you manage your own instances, or build your own platform, you can launch Nitro Sandboxes directly on nearly any instance built on the AWS Nitro System. Amazon Linux and Firecracker support Nitro Sandboxes today. We have started to upstream support for Nitro Sandboxes in Linux and other virtual machine monitors. We also worked with operating system vendor partners to add support early, so you can keep the stack your workload already depends on.&lt;/p&gt; 
&lt;p&gt;In addition to containers, Nitro Sandboxes serve as a building block for more in-instance virtualization use cases. Nitro Sandboxes support a special “Direct Mode” switch which disables attestation, but allows the parent to retain access to sandbox memory. We have seen early adopters use this mode to execute non-enlightened operating systems, including Windows or Android, in sandboxes. Other customers have used Nitro Sandboxes to create fully attested package build environments, where each built package receives a tamper-proof signature of its build inputs. See the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-ec2-nitro-sandboxes.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt; for details.&lt;/p&gt; 
&lt;h2 id="pricing-and-availability"&gt;Pricing and availability&lt;/h2&gt; 
&lt;p&gt;Nitro Sandboxes, along with the EKS and ECS integrations, are available at no additional charge. You pay for the EC2 instances, plus the standard EKS Auto Mode or ECS Managed Instances management fee if you use those capabilities. Nitro Sandboxes run on nearly every EC2 instance, EKS cluster, and ECS cluster, so strong per-container, per-task, and in-instance isolation is available to everyone.&lt;/p&gt; 
&lt;p&gt;For more information, see the Nitro Sandboxes documentation in the &lt;a href="https://docs.aws.amazon.com/eks/latest/userguide/sandboxing.html" target="_blank" rel="noopener"&gt;Amazon EKS User Guide&lt;/a&gt;, the &lt;a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/isolated-confidential-tasks.html" target="_blank" rel="noopener"&gt;Amazon ECS Developer Guide&lt;/a&gt;, or the &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-ec2-nitro-sandboxes.html" target="_blank" rel="noopener"&gt;Amazon EC2 User Guide&lt;/a&gt; for direct use on EC2 instances.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/graf-1.jpg"&gt;&lt;img loading="lazy" class="alignnone size-thumbnail wp-image-27494" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/10/graf-1-150x150.jpg" alt="" width="150" height="150"&gt;&lt;/a&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Alex Graf&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Alex is a Principal Engineer on the EC2 team at AWS.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Serverless ICYMI Q3 2026</title>
		<link>https://aws.amazon.com/blogs/compute/serverless-icymi-q3-2026/</link>
		
		<dc:creator><![CDATA[Julian Wood]]></dc:creator>
		<pubDate>Thu, 05 Nov 2026 13:50:18 +0000</pubDate>
				<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">ba34b8bf7745279b918fc9d4a4898f97b8f1385c</guid>

					<description>In this 34th quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q3 2026 that you might have missed.</description>
										<content:encoded>&lt;p&gt;In this 34th quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q3 2026 that you might have missed.&lt;/p&gt; 
&lt;p&gt;In case you missed our last ICYMI, read about what happened in &lt;a href="https://aws.amazon.com/blogs/compute/serverless-icymi-q2-2026/" target="_blank" rel="noopener"&gt;Q2 2026&lt;/a&gt;.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-1.png" alt="Q3 2026 calendar marking the quarter covered by this serverless recap" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: 2026 Q3 calendar&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="amazon-eventbridge"&gt;Amazon EventBridge&lt;/h2&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/eventbridge/" target="_blank" rel="noopener"&gt;Amazon EventBridge&lt;/a&gt; &lt;a href="https://aws.amazon.com/blogs/compute/building-event-driven-applications-at-scale-with-amazon-eventbridge/" target="_blank" rel="noopener"&gt;relaunched the Custom event bus&lt;/a&gt; for organizations where many teams share events. A central team creates one bus, shares it across accounts with &lt;a href="https://aws.amazon.com/ram/" target="_blank" rel="noopener"&gt;AWS Resource Access Manager&lt;/a&gt;, and controls who can publish and subscribe. Application teams create Subscribers in their own accounts instead of chaining forwarding rules between buses. The new bus keeps events for a retention period you choose, preserves order within a key the publisher sets, and accepts Avro, Protocol Buffers, and JSON, including &lt;a href="https://cloudevents.io/" target="_blank" rel="noopener"&gt;CloudEvents&lt;/a&gt;. It runs alongside the classic bus, so adoption is incremental.&lt;/p&gt; 
&lt;div style="width: 560px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-2.png" alt="Shared EventBridge Custom event bus with subscribers in separate team accounts" width="550"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: Shared Custom event bus with subscribers in team accounts&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;More services now publish directly to Amazon EventBridge. &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/secrets-manager-update-notifications" target="_blank" rel="noopener"&gt;AWS Secrets Manager&lt;/a&gt; sends an event when a secret value changes, and &lt;a href="https://aws.amazon.com/s3/" target="_blank" rel="noopener"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt; &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/amazon-s3-event-notifications-system-generated-tags/" target="_blank" rel="noopener"&gt;Event Notifications&lt;/a&gt; now include system-generated tags, so one rule can match events from thousands of buckets. &lt;a href="https://aws.amazon.com/blogs/compute/scheduling-email-campaigns-at-scale-with-amazon-eventbridge-scheduler/" target="_blank" rel="noopener"&gt;Scheduling email campaigns at scale with Amazon EventBridge Scheduler&lt;/a&gt; shows a high-volume scheduling pattern.&lt;/p&gt; 
&lt;h2 id="aws-lambda"&gt;AWS Lambda&lt;/h2&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/lambda/" target="_blank" rel="noopener"&gt;AWS Lambda&lt;/a&gt; functions outside an &lt;a href="https://aws.amazon.com/vpc/" target="_blank" rel="noopener"&gt;Amazon Virtual Private Cloud&lt;/a&gt; (VPC) with 2 GB of memory or more now get &lt;a href="https://aws.amazon.com/blogs/compute/improving-lambda-function-latency-with-scalable-network-bandwidth/" target="_blank" rel="noopener"&gt;scalable network bandwidth&lt;/a&gt;. The bandwidth increases from 625 Mbps at 2 GB up to 3,000 Mbps at 10 GB. Functions that pull large amounts of data from &lt;a href="https://aws.amazon.com/s3" target="_blank" rel="noopener"&gt;Amazon S3&lt;/a&gt; or external sources finish sooner, as the ETL fan-out pattern in the post shows.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/compute/get-started-with-aws-lambda-snapstart-for-container-images/" target="_blank" rel="noopener"&gt;SnapStart now supports container images&lt;/a&gt;, cutting startup for larger images from several seconds to as low as sub-second. Provisioned mode for &lt;a href="https://aws.amazon.com/sqs/" target="_blank" rel="noopener"&gt;Amazon Simple Queue Service&lt;/a&gt; (Amazon SQS) event source mappings now scales to &lt;a href="https://aws.amazon.com/blogs/compute/low-latency-high-throughput-sqs-event-processing-with-aws-lambda-provisioned-mode/" target="_blank" rel="noopener"&gt;10,000 event pollers&lt;/a&gt;, five times the previous limit, for up to 100,000 concurrent invocations. Lambda can also &lt;a href="https://aws.amazon.com/blogs/compute/introducing-self-managed-amazon-s3-buckets-for-aws-lambda-function-code/" target="_blank" rel="noopener"&gt;read function code from your own S3 bucket&lt;/a&gt;. Lambda skips copying the package to its own storage, so code storage quotas stop being a concern and functions activate faster after updates.&lt;/p&gt; 
&lt;h3 id="lambda-managed-instances"&gt;Lambda Managed Instances&lt;/h3&gt; 
&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances.html" target="_blank" rel="noopener"&gt;AWS Lambda Managed Instances&lt;/a&gt;, a capability of AWS Lambda, now supports a &lt;a href="https://aws.amazon.com/blogs/compute/announcing-90-minute-function-timeout-on-aws-lambda-managed-instances/" target="_blank" rel="noopener"&gt;90-minute timeout&lt;/a&gt; for asynchronous and event source mapping invocations, six times the 15-minute limit. This longer timeout can help for jobs such as media transcoding, Monte Carlo simulations, and batch inference. You can run on &lt;a href="https://aws.amazon.com/ec2/graviton/" target="_blank" rel="noopener"&gt;AWS Graviton&lt;/a&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/aws-lambda-graviton5-ec2/" target="_blank" rel="noopener"&gt;-powered C9g, C9gd, M9g, and M9gd instances&lt;/a&gt; with up to 25% better performance than Graviton4. Capacity providers now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/aws-lambda-managed-instances-logs/" target="_blank" rel="noopener"&gt;publish logs&lt;/a&gt; to &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt;, showing scaling activity and instance lifecycle operations. &lt;a href="https://aws.amazon.com/blogs/compute/eliminating-java-cold-starts-with-aws-lambda-managed-instances/" target="_blank" rel="noopener"&gt;Eliminating Java cold starts with AWS Lambda Managed Instances&lt;/a&gt; covers latency-sensitive Java functions.&lt;/p&gt; 
&lt;h3 id="durable-functions"&gt;Durable functions&lt;/h3&gt; 
&lt;p&gt;The &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/lambdadf-dotnet/" target="_blank" rel="noopener"&gt;Durable Execution SDK for .NET&lt;/a&gt; is generally available, joining TypeScript, Python, and Java. You can now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/aws-lambda-durable-custom-sdk/" target="_blank" rel="noopener"&gt;bring your own SDK&lt;/a&gt; for any runtime, checked against an open source conformance test suite. The &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/aws-lambda-durable-pydantic-ai/" target="_blank" rel="noopener"&gt;Pydantic AI integration&lt;/a&gt; makes each model and tool call a durable step, so an interrupted agent resumes where it stopped instead of repeating expensive calls. If your data governance policies require keys you control, you can &lt;a href="https://aws.amazon.com/blogs/compute/implementing-customer-managed-keys-for-aws-lambda-durable-functions-with-terraform/" target="_blank" rel="noopener"&gt;encrypt execution data&lt;/a&gt; with your own &lt;a href="https://aws.amazon.com/kms/" target="_blank" rel="noopener"&gt;AWS Key Management Service&lt;/a&gt; (AWS KMS) key. &lt;a href="https://aws.amazon.com/blogs/compute/observability-best-practices-for-lambda-durable-functions-2/" target="_blank" rel="noopener"&gt;Observability best practices for Lambda durable functions&lt;/a&gt; covers dashboards, alarms, and tracing. Durable functions is also now available in the &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/durablefunctions-european-sovereign-cloud/" target="_blank" rel="noopener"&gt;AWS European Sovereign Cloud&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="lambda-microvms"&gt;Lambda MicroVMs&lt;/h3&gt; 
&lt;p&gt;The following video shows stateful game servers running on Lambda MicroVMs.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=WcAksz0qPcQ" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-3.png" alt="Video thumbnail for building multiplayer game servers on AWS Lambda MicroVMs" width="800"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;Figure 3: Building multiplayer game servers with AWS Lambda MicroVMs&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/compute/secure-code-execution-for-ai-agents-with-aws-lambda-microvms/" target="_blank" rel="noopener"&gt;Secure code execution for AI agents&lt;/a&gt; explains how each &lt;a href="https://aws.amazon.com/blogs/compute/announcing-lambda-microvms-serverless-compute-environments-with-vm-level-isolation-and-near-instant-startup/" target="_blank" rel="noopener"&gt;Lambda MicroVMs&lt;/a&gt; user or job gets its own Firecracker-isolated environment that keeps state for up to 8 hours. MicroVMs is now available in &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/lambda-microvms-5-additional-regions" target="_blank" rel="noopener"&gt;10 Regions&lt;/a&gt; and supports &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/lambda-microvms-supports-privatelink" target="_blank" rel="noopener"&gt;AWS PrivateLink&lt;/a&gt;, without exposing traffic to the public internet. Other posts cover &lt;a href="https://aws.amazon.com/blogs/compute/collecting-cpu-and-memory-metrics-for-aws-lambda-microvms/" target="_blank" rel="noopener"&gt;CPU and memory metrics&lt;/a&gt; and &lt;a href="https://aws.amazon.com/blogs/compute/adding-custom-domains-to-aws-lambda-microvms-with-application-load-balancer/" target="_blank" rel="noopener"&gt;custom domains with an Application Load Balancer&lt;/a&gt;, and the AWS Developers channel shows &lt;a href="https://www.youtube.com/watch?v=WcAksz0qPcQ" target="_blank" rel="noopener"&gt;stateful game servers on MicroVMs&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/compute/running-self-hosted-ai-agent-sandboxes-with-aws-lambda-microvms/" target="_blank" rel="noopener"&gt;Running self-hosted AI agent sandboxes&lt;/a&gt; gives every agent session its own MicroVM in your account, with separate credentials, file system, and network boundary. Each MicroVM launches from a pre-captured snapshot, so new sessions skip application initialization.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-4.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-4.png" alt="Architecture of self-hosted AI agent sandboxes running on AWS Lambda MicroVMs" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 4: Self-hosted agent sandboxes on AWS Lambda MicroVMs architecture&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="other-lambda-updates"&gt;Other Lambda updates&lt;/h3&gt; 
&lt;p&gt;Lambda now offers &lt;a href="https://aws.amazon.com/blogs/compute/introducing-public-preview-runtimes-on-aws-lambda-starting-with-node-js-26-and-python-3-15/" target="_blank" rel="noopener"&gt;public preview runtimes&lt;/a&gt;, starting with Node.js 26 and Python 3.15, so you can test your workloads before general availability. Java 8, 11, and 17 now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/aws-lambda-java-amazon-linux/" target="_blank" rel="noopener"&gt;run on Amazon Linux 2023&lt;/a&gt;, because Amazon Linux 2 reached end of life in June. You can move off Amazon Linux 2 without changing Java version at the same time. Functions support full &lt;a href="https://aws.amazon.com/iam" target="_blank" rel="noopener"&gt;AWS Identity and Access Management&lt;/a&gt; (AWS IAM) &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/aws-lambda-full-iam-resource-based-policies/" target="_blank" rel="noopener"&gt;resource-based policies&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/lambda-recursion-regions" target="_blank" rel="noopener"&gt;recursive loop detection&lt;/a&gt; is in all available commercial Regions. With S3 Files, you can &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/aws-lambda-direct-read-s3files/" target="_blank" rel="noopener"&gt;configure direct reads&lt;/a&gt; from high-performance storage for lower latency or from your bucket for higher throughput. To change function behavior without redeploying, see &lt;a href="https://aws.amazon.com/blogs/compute/implementing-dynamic-feature-flags-with-aws-appconfig-on-aws-lambda/" target="_blank" rel="noopener"&gt;Implementing dynamic feature flags with AWS AppConfig on AWS Lambda&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="aws-step-functions"&gt;AWS Step Functions&lt;/h3&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/step-functions/" target="_blank" rel="noopener"&gt;AWS Step Functions&lt;/a&gt; now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/06/aws-step-functions-integrations/" target="_blank" rel="noopener"&gt;adds SDK integrations for new services automatically&lt;/a&gt; within weeks of release, starting with Lambda MicroVMs. A workflow can launch a MicroVM to run agent-generated code in isolation. &lt;a href="https://aws.amazon.com/blogs/compute/validating-multi-agent-decisions-with-step-functions-and-bedrock-agentcore/" target="_blank" rel="noopener"&gt;Validating multi-agent decisions&lt;/a&gt; with Step Functions and &lt;a href="https://aws.amazon.com/bedrock/agentcore/" target="_blank" rel="noopener"&gt;Amazon Bedrock AgentCore&lt;/a&gt; fans work out to several agents with a Distributed Map and checks their decisions before acting.&lt;/p&gt; 
&lt;h3 id="amazon-sns-and-amazon-api-gateway"&gt;Amazon SNS and Amazon API Gateway&lt;/h3&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/sns/" target="_blank" rel="noopener"&gt;Amazon Simple Notification Service&lt;/a&gt; (Amazon SNS) now supports &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-sns-1mib-support" target="_blank" rel="noopener"&gt;message payloads up to 1 MiB&lt;/a&gt;, four times the previous limit. Set the &lt;code&gt;MaximumMessageSize&lt;/code&gt; topic attribute to publish larger messages without splitting them, following the &lt;a href="https://aws.amazon.com/blogs/compute/more-room-to-build-serverless-services-now-support-payloads-up-to-1-mb/" target="_blank" rel="noopener"&gt;1 MB increase&lt;/a&gt; across other serverless services in January. &lt;a href="https://aws.amazon.com/api-gateway/" target="_blank" rel="noopener"&gt;Amazon API Gateway&lt;/a&gt; now supports &lt;a href="https://aws.amazon.com/blogs/compute/bring-your-own-client-certificate-for-backend-mtls-in-amazon-api-gateway/" target="_blank" rel="noopener"&gt;backend mTLS with your own client certificate&lt;/a&gt; and &lt;a href="https://aws.amazon.com/blogs/compute/customize-amazon-api-gateway-destinations-for-execution-logs/" target="_blank" rel="noopener"&gt;configurable destinations for execution logs&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="amazon-s3"&gt;Amazon S3&lt;/h3&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/ecs/" target="_blank" rel="noopener"&gt;Amazon Elastic Container Service&lt;/a&gt; (Amazon ECS) on &lt;a href="https://aws.amazon.com/ec2/" target="_blank" rel="noopener"&gt;Amazon Elastic Compute Cloud&lt;/a&gt; (Amazon EC2) now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-ecs-s3-files-ec2/" target="_blank" rel="noopener"&gt;supports S3 Files&lt;/a&gt;, and Amazon S3 Vectors, a capability of Amazon S3, adds &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/s3-vectors-introduces-metadata-pre-filtering/" target="_blank" rel="noopener"&gt;metadata pre-filtering&lt;/a&gt;, returning up to 5 times more matches on selective filters. You can &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/s3-removes-30-day-transitions-standard-ia-one-zone-ia" target="_blank" rel="noopener"&gt;move objects to S3 Standard-IA on the day you create them&lt;/a&gt; instead of waiting 30 days. Object Lock adds &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-s3-object-lock-variable-retention/" target="_blank" rel="noopener"&gt;event holds&lt;/a&gt; for retention that starts with a future event, such as a contract closing.&lt;/p&gt; 
&lt;h2 id="building-with-ai"&gt;Building with AI&lt;/h2&gt; 
&lt;p&gt;The Lambda console has a &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/aws-lambda-prompt-coding-agents/" target="_blank" rel="noopener"&gt;one-step setup prompt&lt;/a&gt; that configures your coding agent with AWS Serverless skills and the Serverless MCP server. The &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/aws-lambda-ide-kiro-cursor/" target="_blank" rel="noopener"&gt;console-to-IDE integration now includes Kiro and Cursor&lt;/a&gt; and can convert your function to an &lt;a href="https://aws.amazon.com/serverless/sam/" target="_blank" rel="noopener"&gt;AWS Serverless Application Model&lt;/a&gt; (AWS SAM) template. &lt;a href="https://aws.amazon.com/blogs/compute/set-up-your-ai-coding-agent-to-build-with-aws-step-functions/" target="_blank" rel="noopener"&gt;Set up your AI coding agent to build with AWS Step Functions&lt;/a&gt; does the same for workflows.&lt;/p&gt; 
&lt;h3 id="agent-toolkit-for-aws"&gt;Agent Toolkit for AWS&lt;/h3&gt; 
&lt;p&gt;The AWS MCP Server in the &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/05/agent-toolkit/" target="_blank" rel="noopener"&gt;Agent Toolkit for AWS&lt;/a&gt; added a &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/aws-mcp-server-serverless/" target="_blank" rel="noopener"&gt;serverless capability&lt;/a&gt; that inspects a Lambda function and its connected resources, so your agent can diagnose issues in place. New skills cover &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/aws-auth-agent-skill/" target="_blank" rel="noopener"&gt;Amazon Cognito&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/amazon-documentdb-agent-skill" target="_blank" rel="noopener"&gt;Amazon DocumentDB (with MongoDB compatibility)&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/07/amazon-opensearch-service-agent/" target="_blank" rel="noopener"&gt;Amazon OpenSearch Service&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/redshift-agenttoolkit-for-ai-assisted-datawarehouse-mgmt" target="_blank" rel="noopener"&gt;Amazon Redshift&lt;/a&gt;. The &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noopener"&gt;AWS Command Line Interface&lt;/a&gt; (AWS CLI) can now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/aws-cli-agent-toolkit-update-skill/" target="_blank" rel="noopener"&gt;check for and update all skills&lt;/a&gt; in one command.&lt;/p&gt; 
&lt;h3 id="amazon-bedrock-agentcore"&gt;Amazon Bedrock AgentCore&lt;/h3&gt; 
&lt;p&gt;The &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/new-agentcore-runtime-generally-available" target="_blank" rel="noopener"&gt;new AgentCore runtime&lt;/a&gt;, a capability of Amazon Bedrock AgentCore, reclaims unused memory during a session, so you pay for what you use, and keeps cold starts consistent. &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/aws-bedrock-agentcore-runtime-instances-generally-available/" target="_blank" rel="noopener"&gt;Runtime instances&lt;/a&gt; run agents on Amazon EC2 instance types you choose, much as Lambda Managed Instances does for functions. &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/bedrock-agentcore-payments-ga/" target="_blank" rel="noopener"&gt;AgentCore payments&lt;/a&gt;, a capability of Amazon Bedrock AgentCore, is generally available, and &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/temporal-policies-agentcore/" target="_blank" rel="noopener"&gt;temporal policies&lt;/a&gt; authorize tool calls based on what the agent already did in the session.&lt;/p&gt; 
&lt;p&gt;AgentCore memory, a capability of Amazon Bedrock AgentCore, added &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/agentcore-memory-json-payloads" target="_blank" rel="noopener"&gt;JSON payload extraction&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/agentcorememory-fine-grained-access-control" target="_blank" rel="noopener"&gt;fine-grained access control&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/agentcorememory-flexible-namespaces" target="_blank" rel="noopener"&gt;flexible namespaces&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/agentcore-memory-direct-ingest" target="_blank" rel="noopener"&gt;direct ingestion&lt;/a&gt;. AgentCore Identity, a capability of Amazon Bedrock AgentCore, has a &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-bedrock-agentcore/" target="_blank" rel="noopener"&gt;managed consent portal&lt;/a&gt; for OAuth flows, and &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/08/aws-agent-registry-generally-available" target="_blank" rel="noopener"&gt;AWS Agent Registry&lt;/a&gt; is generally available. Amazon Bedrock &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/bedrock-managed-agents-preview/" target="_blank" rel="noopener"&gt;Managed Agents, powered by OpenAI&lt;/a&gt; is in preview. New models include &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/claude-fable-5-1-aws/" target="_blank" rel="noopener"&gt;Claude Fable 5.1&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/claude-opus-5-5-aws/" target="_blank" rel="noopener"&gt;Claude Opus 5.5&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/claude-sonnet-5-5-aws/" target="_blank" rel="noopener"&gt;Claude Sonnet 5.5&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/openai-gpt-6-astra-on-amazon-bedrock/" target="_blank" rel="noopener"&gt;GPT-6 Astra&lt;/a&gt;, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/openai-gpt-6-sol-luna-on-amazon-bedrock/" target="_blank" rel="noopener"&gt;GPT-6 Sol and Luna&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/moonshot-ai-kimi-k3-on-amazon-bedrock/" target="_blank" rel="noopener"&gt;Kimi K3&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="strands-agents"&gt;Strands Agents&lt;/h3&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-5.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-5.png" alt="Title card introducing the Strands harness open source agent" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 5: Introducing Strands harness&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;a href="https://strandsagents.com/blog/introducing-strands-harness/" target="_blank" rel="noopener"&gt;Strands harness&lt;/a&gt; is an open source, general-purpose agent you start with one line of Python or TypeScript and run locally or deploy anywhere. Across six benchmarks using the same models, it cost 28% less than other popular harnesses with similar accuracy, mostly because of its default context management. &lt;a href="https://strandsagents.com/blog/introducing-harness-optimizer/" target="_blank" rel="noopener"&gt;Harness Optimizer&lt;/a&gt; tunes prompts, tool descriptions, and skills automatically, &lt;a href="https://aws.amazon.com/blogs/database/introducing-strands-dynamodb-storage-durable-agent-storage-for-the-strands-agents-sdk/" target="_blank" rel="noopener"&gt;strands-dynamodb-storage&lt;/a&gt; adds durable agent storage on Amazon DynamoDB, and &lt;a href="https://strandsagents.com/blog/framework-agnostic-evaluation-strands-evals/" target="_blank" rel="noopener"&gt;Strands Evals&lt;/a&gt; now evaluates agents built with other frameworks.&lt;/p&gt; 
&lt;h3 id="kiro"&gt;Kiro&lt;/h3&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-6.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/28/ComputeBlog-2819-6.png" alt="Kiro Crew desktop session view showing agent work across sessions" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 6: Kiro Crew session view&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;a href="https://kiro.dev/blog/introducing-kiro-crew" target="_blank" rel="noopener"&gt;Kiro Crew&lt;/a&gt; is an open source workspace that runs agent work across sessions, schedules, and subagents from a desktop app, web dashboard, or terminal. &lt;a href="https://kiro.dev/changelog/web/kiro-web-is-now-generally-available/" target="_blank" rel="noopener"&gt;Kiro on the web&lt;/a&gt; is generally available, &lt;a href="https://kiro.dev/blog/cloud-sessions" target="_blank" rel="noopener"&gt;cloud sessions&lt;/a&gt; keep CLI and IDE tasks running after you close your laptop, and &lt;a href="https://kiro.dev/blog/introducing-workflows" target="_blank" rel="noopener"&gt;workflows&lt;/a&gt; run multi-step plans across several agents in the background.&lt;/p&gt; 
&lt;h2 id="serverless-blog-posts"&gt;Serverless blog posts&lt;/h2&gt; 
&lt;p&gt;Here are the Q3 2026 serverless blog posts, grouped by the month they published.&lt;/p&gt; 
&lt;h3 id="july"&gt;July&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/announcing-lambda-microvms-serverless-compute-environments-with-vm-level-isolation-and-near-instant-startup/" target="_blank" rel="noopener"&gt;Announcing Lambda MicroVMs: serverless compute environments with VM-level isolation and near-instant startup&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/secure-code-execution-for-ai-agents-with-aws-lambda-microvms/" target="_blank" rel="noopener"&gt;Secure code execution for AI agents with AWS Lambda MicroVMs&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/eliminating-java-cold-starts-with-aws-lambda-managed-instances/" target="_blank" rel="noopener"&gt;Eliminating Java cold starts with AWS Lambda Managed Instances&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/introducing-self-managed-amazon-s3-buckets-for-aws-lambda-function-code/" target="_blank" rel="noopener"&gt;Introducing self-managed Amazon S3 buckets for AWS Lambda function code&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="august"&gt;August&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/low-latency-high-throughput-sqs-event-processing-with-aws-lambda-provisioned-mode/" target="_blank" rel="noopener"&gt;Low-latency, high-throughput SQS event processing with AWS Lambda provisioned mode&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/collecting-cpu-and-memory-metrics-for-aws-lambda-microvms/" target="_blank" rel="noopener"&gt;Collecting CPU and memory metrics for AWS Lambda MicroVMs&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/observability-best-practices-for-lambda-durable-functions-2/" target="_blank" rel="noopener"&gt;Observability best practices for Lambda durable functions&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/implementing-dynamic-feature-flags-with-aws-appconfig-on-aws-lambda/" target="_blank" rel="noopener"&gt;Implementing dynamic feature flags with AWS AppConfig on AWS Lambda&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/introducing-public-preview-runtimes-on-aws-lambda-starting-with-node-js-26-and-python-3-15/" target="_blank" rel="noopener"&gt;Introducing public preview runtimes on AWS Lambda, starting with Node.js 26 and Python 3.15&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/set-up-your-ai-coding-agent-to-build-with-aws-step-functions/" target="_blank" rel="noopener"&gt;Set up your AI coding agent to build with AWS Step Functions&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="september"&gt;September&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/scheduling-email-campaigns-at-scale-with-amazon-eventbridge-scheduler/" target="_blank" rel="noopener"&gt;Scheduling email campaigns at scale with Amazon EventBridge Scheduler&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/bring-your-own-client-certificate-for-backend-mtls-in-amazon-api-gateway/" target="_blank" rel="noopener"&gt;Bring your own client certificate for backend mTLS in Amazon API Gateway&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/announcing-90-minute-function-timeout-on-aws-lambda-managed-instances/" target="_blank" rel="noopener"&gt;Announcing 90-minute function timeout on AWS Lambda Managed Instances&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/customize-amazon-api-gateway-destinations-for-execution-logs/" target="_blank" rel="noopener"&gt;Customize Amazon API Gateway destinations for execution logs&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/validating-multi-agent-decisions-with-step-functions-and-bedrock-agentcore/" target="_blank" rel="noopener"&gt;Validating multi-agent decisions with Step Functions and Bedrock AgentCore&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/running-self-hosted-ai-agent-sandboxes-with-aws-lambda-microvms/" target="_blank" rel="noopener"&gt;Running self-hosted AI agent sandboxes with AWS Lambda MicroVMs&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/adding-custom-domains-to-aws-lambda-microvms-with-application-load-balancer/" target="_blank" rel="noopener"&gt;Adding custom domains to AWS Lambda MicroVMs with Application Load Balancer&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/improving-lambda-function-latency-with-scalable-network-bandwidth/" target="_blank" rel="noopener"&gt;Improving Lambda function latency with scalable network bandwidth&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/building-event-driven-applications-at-scale-with-amazon-eventbridge/" target="_blank" rel="noopener"&gt;Building event-driven applications at scale with Amazon EventBridge&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/implementing-customer-managed-keys-for-aws-lambda-durable-functions-with-terraform/" target="_blank" rel="noopener"&gt;Implementing customer managed keys for AWS Lambda durable functions with Terraform&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="still-looking-for-more"&gt;Still looking for more?&lt;/h2&gt; 
&lt;p&gt;The &lt;a href="http://aws.amazon.com/serverless" target="_blank" rel="noopener"&gt;Serverless landing page&lt;/a&gt; has overall information about building serverless applications. The &lt;a href="https://aws.amazon.com/lambda/resources/?aws-lambda-resources-blog.sort-by=item.additionalFields.createdDate&amp;amp;aws-lambda-resources-blog.sort-order=desc" target="_blank" rel="noopener"&gt;Lambda resources page&lt;/a&gt; contains case studies, webinars, whitepapers, customer stories, reference architectures, and even more Getting Started tutorials.&lt;/p&gt; 
&lt;p&gt;You can also follow the Developer Advocacy team to get the latest news, follow conversations, and interact with the team.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Julian Wood: &lt;a href="https://twitter.com/julian_wood" target="_blank" rel="noopener"&gt;&lt;span class="citation" data-cites="julian_wood"&gt;@julian_wood&lt;/span&gt;&lt;/a&gt;, &lt;a class="uri" href="https://www.linkedin.com/in/julianrwood/" target="_blank" rel="noopener"&gt;https://www.linkedin.com/in/julianrwood/&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;Eric Johnson: &lt;a href="https://twitter.com/edjgeek" target="_blank" rel="noopener"&gt;&lt;span class="citation" data-cites="edjgeek"&gt;@edjgeek&lt;/span&gt;&lt;/a&gt;, &lt;a class="uri" href="https://www.linkedin.com/in/singledigit/" target="_blank" rel="noopener"&gt;https://www.linkedin.com/in/singledigit/&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;Erik Hanchet: &lt;a href="https://x.com/ErikCH" target="_blank" rel="noopener"&gt;&lt;span class="citation" data-cites="ErikCH"&gt;@ErikCH&lt;/span&gt;&lt;/a&gt;, &lt;a class="uri" href="https://www.linkedin.com/in/erikhanchett/" target="_blank" rel="noopener"&gt;https://www.linkedin.com/in/erikhanchett/&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;Salih Gueler: &lt;a href="https://x.com/salihgueler" target="_blank" rel="noopener"&gt;&lt;span class="citation" data-cites="salihgueler"&gt;@salihgueler&lt;/span&gt;&lt;/a&gt;, &lt;a class="uri" href="https://www.linkedin.com/in/salihgueler/" target="_blank" rel="noopener"&gt;https://www.linkedin.com/in/salihgueler/&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;Marcia Villalba: &lt;a href="https://twitter.com/mavi888uy/" target="_blank" rel="noopener"&gt;&lt;span class="citation" data-cites="mavi888uy"&gt;@mavi888uy&lt;/span&gt;&lt;/a&gt;, &lt;a class="uri" href="https://www.linkedin.com/in/marciavillalba" target="_blank" rel="noopener"&gt;https://www.linkedin.com/in/marciavillalba&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;And finally, visit &lt;a href="http://serverlessland.com/" target="_blank" rel="noopener"&gt;Serverless Land&lt;/a&gt; for your serverless needs.&lt;/p&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Implementing PostgreSQL logical replication between Amazon RDS for PostgreSQL instances on separate AWS Outposts</title>
		<link>https://aws.amazon.com/blogs/compute/implementing-postgresql-logical-replication-between-amazon-rds-for-postgresql-instances-on-separate-aws-outposts/</link>
		
		<dc:creator><![CDATA[Belma Canik]]></dc:creator>
		<pubDate>Wed, 04 Nov 2026 22:02:23 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS Outposts]]></category>
		<category><![CDATA[RDS for PostgreSQL]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">61e14fc052910f5f0e991294ed07b18d5bfe4122</guid>

					<description>Learn how to configure PostgreSQL logical replication between two Amazon RDS for PostgreSQL instances on separate AWS Outposts racks, keeping all replication traffic and backups within your on-premises environment by using Customer-owned IP addresses and Local Gateways, without any data traversing the AWS Region.</description>
										<content:encoded>&lt;p&gt;Organizations in regulated industries such as healthcare, financial services, and government often face strict data residency mandates that require all data, including database backups, to remain within their on-premises environment. You can keep backups on-premises with Amazon Relational Database Service (Amazon RDS) local backups on AWS Outposts by setting the backup target to AWS Outposts (&lt;code&gt;--backup-target outposts&lt;/code&gt;). Your AWS Outposts must have Amazon Simple Storage Service (Amazon S3) on Outposts capacity to store those backups locally. While Amazon &lt;a href="https://docs.aws.amazon.com/whitepapers/latest/aws-outposts-high-availability-design/rds-outpost-local-backup.html" target="_blank" rel="noopener"&gt;RDS local backups on Outposts&lt;/a&gt; can keep backup data on-premises, organizations that need high availability across two separate Outposts racks, without any data traversing the AWS Region, lack a built-in, native replication mechanism between Outpost-hosted RDS instances.&lt;/p&gt; 
&lt;p&gt;In this post, we demonstrate how you can configure &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.FeatureSupport.LogicalReplication.html" target="_blank" rel="noopener"&gt;PostgreSQL logical replication&lt;/a&gt; between two Amazon RDS instances running on separate &lt;a href="https://docs.aws.amazon.com/outposts/latest/userguide/what-is-outposts.html" target="_blank" rel="noopener"&gt;AWS Outposts&lt;/a&gt; racks, so that all data remains within your on-premises environment. By using &lt;a href="https://docs.aws.amazon.com/outposts/latest/userguide/routing.html" target="_blank" rel="noopener"&gt;Customer-owned IP addresses (CoIP)&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/outposts/latest/userguide/outposts-local-gateways.html" target="_blank" rel="noopener"&gt;Local Gateways (LGW)&lt;/a&gt;, you can establish secure, low-latency replication between Outposts without exposing any data to the Region.&lt;/p&gt; 
&lt;h2 id="architecture-overview"&gt;Architecture overview&lt;/h2&gt; 
&lt;p&gt;Our solution uses two AWS Outpost racks, each with its own Local Gateway (LGW) configured in Customer-owned IP (CoIP) mode. In this architecture, all database traffic flows through your on-premises network infrastructure:&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/02/ComputeBlog-2830-1.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/02/ComputeBlog-2830-1.png" alt="Two AWS Outposts racks replicating Amazon RDS data through Local Gateways over the on-premises network, bypassing the AWS Region" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Replication architecture across two AWS Outposts racks using Customer-owned IP addresses and Local Gateways&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt; 
&lt;p&gt;Before beginning the configuration, make sure you have:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Two AWS Outpost racks with Local Gateways (LGW) configured in CoIP mode.&lt;/li&gt; 
 &lt;li&gt;CoIP pools configured and shared with your AWS account.&lt;/li&gt; 
 &lt;li&gt;LGW route table associations with your virtual private cloud (VPC) in place.&lt;/li&gt; 
 &lt;li&gt;On-premises network connectivity between the two Outpost Local Gateways.&lt;/li&gt; 
 &lt;li&gt;VPC with subnets spanning both Outposts.&lt;/li&gt; 
 &lt;li&gt;Security groups configured to allow PostgreSQL traffic (port 5432).&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="step-1-create-outpost-subnets-with-coip-configuration"&gt;Step 1: Create Outpost subnets with CoIP configuration&lt;/h2&gt; 
&lt;p&gt;Each Outpost needs a subnet with CoIP auto-assign enabled.&lt;/p&gt; 
&lt;p&gt;While Amazon Elastic Compute Cloud (Amazon EC2) instances can inherit CoIP assignment from subnet settings, RDS instances require explicit CoIP enablement (covered in Step 3).&lt;/p&gt; 
&lt;h3 id="subnet-on-outpost-a"&gt;Subnet on Outpost A&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 create-subnet \
--vpc-id vpc-xxx \
--cidr-block 10.0.1.0/24 \
--availability-zone us-west-2a \
--outpost-arn arn:aws:outposts:us-west-2:OWNER_ACCOUNT:outpost/op-xxx

# Enable CoIP auto-assign (applies to EC2, not RDS)
aws ec2 modify-subnet-attribute \
--subnet-id subnet-xxx \
--map-customer-owned-ip-on-launch \
--customer-owned-ipv4-pool ipv4pool-coip-xxx&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="subnet-on-outpost-b"&gt;Subnet on Outpost B&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 create-subnet \
--vpc-id vpc-xxx \
--cidr-block 10.0.2.0/24 \
--availability-zone us-west-2b \
--outpost-arn arn:aws:outposts:us-west-2:OWNER_ACCOUNT:outpost/op-yyy

aws ec2 modify-subnet-attribute \
--subnet-id subnet-outpost-b \
--map-customer-owned-ip-on-launch \
--customer-owned-ipv4-pool ipv4pool-coip-yyy&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; The &lt;code&gt;MapCustomerOwnedIpOnLaunch&lt;/code&gt; setting works for EC2 instances but doesn’t automatically apply to RDS instances. RDS requires explicit CoIP enablement during instance creation.&lt;/p&gt; 
&lt;h3 id="create-db-subnet-group"&gt;Create DB subnet group&lt;/h3&gt; 
&lt;p&gt;Create a DB subnet group spanning both Outposts:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws rds create-db-subnet-group \
--db-subnet-group-name rds-outposts-subnet-group \
--db-subnet-group-description "Subnet group spanning Outpost A and B" \
--subnet-ids subnet-outpost-a subnet-outpost-b&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="step-2-configure-route-tables-for-cross-outpost-communication"&gt;Step 2: Configure route tables for cross-Outpost communication&lt;/h2&gt; 
&lt;p&gt;This configuration step is often overlooked. Each subnet’s route table requires two Local Gateway routes:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Cross-outpost route: To reach the other Outpost’s CoIP range.&lt;/li&gt; 
 &lt;li&gt;Same-outpost hairpin route: To reach its own CoIP range, which is required because RDS DNS resolves to CoIP. This affects any resource on the subnet that needs to reach the RDS instance by endpoint, including Amazon EC2 application servers on the same Outpost.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="why-the-hairpin-route-is-important"&gt;Why the hairpin route is important&lt;/h3&gt; 
&lt;p&gt;When you enable CoIP on RDS, the DNS endpoint resolves to the CoIP address instead of the private IP. EC2 instances (and other RDS instances) on the same subnet need a route through the LGW to reach CoIP addresses, even for same-Outpost traffic. Without the hairpin route, traffic to the local CoIP range matches the default route (NAT gateway or internet gateway) and is lost.&lt;/p&gt; 
&lt;h3 id="route-configuration-for-outpost-a"&gt;Route configuration for Outpost A&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Cross-outpost: reach Outpost B's CoIP via Outpost A's LGW
aws ec2 create-route \
--route-table-id rtb-outpost-a \
--destination-cidr-block 198.19.5.0/24 \
--local-gateway-id lgw-A

# Same-outpost hairpin: reach Outpost A's own CoIP via its LGW
aws ec2 create-route \
--route-table-id rtb-outpost-a \
--destination-cidr-block 198.19.9.0/24 \
--local-gateway-id lgw-A&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="route-configuration-for-outpost-b"&gt;Route configuration for Outpost B&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Cross-outpost: reach Outpost A's CoIP via Outpost B's LGW
aws ec2 create-route \
--route-table-id rtb-outpost-b \
--destination-cidr-block 198.19.9.0/24 \
--local-gateway-id lgw-B

# Same-outpost hairpin: reach Outpost B's own CoIP via its LGW
aws ec2 create-route \
--route-table-id rtb-outpost-b \
--destination-cidr-block 198.19.5.0/24 \
--local-gateway-id lgw-B&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="final-route-table-summary"&gt;Final route table summary&lt;/h3&gt; 
&lt;p&gt;Outpost A Route Table:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Destination&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Target&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Purpose&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;10.0.0.0/16&lt;/td&gt; 
   &lt;td&gt;local&lt;/td&gt; 
   &lt;td&gt;VPC internal traffic&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;198.19.5.0/24 (Outpost B CoIP)&lt;/td&gt; 
   &lt;td&gt;lgw-A&lt;/td&gt; 
   &lt;td&gt;Cross-outpost&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;198.19.9.0/24 (Outpost A CoIP)&lt;/td&gt; 
   &lt;td&gt;lgw-A&lt;/td&gt; 
   &lt;td&gt;Same-outpost hairpin&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;0.0.0.0/0&lt;/td&gt; 
   &lt;td&gt;NAT GW&lt;/td&gt; 
   &lt;td&gt;Internet access&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;Outpost B Route Table:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Destination&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Target&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Purpose&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;10.0.0.0/16&lt;/td&gt; 
   &lt;td&gt;local&lt;/td&gt; 
   &lt;td&gt;VPC internal traffic&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;198.19.9.0/24 (Outpost A CoIP)&lt;/td&gt; 
   &lt;td&gt;lgw-B&lt;/td&gt; 
   &lt;td&gt;Cross-outpost&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;198.19.5.0/24 (Outpost B CoIP)&lt;/td&gt; 
   &lt;td&gt;lgw-B&lt;/td&gt; 
   &lt;td&gt;Same-outpost hairpin&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;0.0.0.0/0&lt;/td&gt; 
   &lt;td&gt;NAT GW&lt;/td&gt; 
   &lt;td&gt;Internet access&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;h2 id="step-3-create-rds-instances-with-coip-enabled"&gt;Step 3: Create RDS instances with CoIP enabled&lt;/h2&gt; 
&lt;p&gt;In this step, you create the Amazon RDS for PostgreSQL instances on each Outpost using the &lt;code&gt;aws rds create-db-instance&lt;/code&gt; CLI command. CoIP provides local or external connectivity to resources in your Outpost subnets through your on-premises network. It provides lower latency for connections to the DB instance from outside of its VPC on your local network. When you create an Amazon RDS instance on an Outpost, you can enable CoIP to make sure the instance is reachable over your on-premises network through the Local Gateway rather than the Region.&lt;/p&gt; 
&lt;p&gt;The &lt;code&gt;--enable-customer-owned-ip&lt;/code&gt; flag must be explicitly set. RDS doesn’t inherit the subnet’s &lt;code&gt;MapCustomerOwnedIpOnLaunch&lt;/code&gt; setting.&lt;/p&gt; 
&lt;p&gt;Keep in mind that this property isn’t supported in AWS CloudFormation. Use the AWS Command Line Interface (AWS CLI), Terraform (&lt;code&gt;customer_owned_ip_enabled = true&lt;/code&gt;), or the console (select Customer-owned IP address (CoIP) under Access type).&lt;/p&gt; 
&lt;h3 id="create-the-publisher-instance-outpost-a"&gt;Create the publisher instance (Outpost A)&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws rds create-db-instance \
--db-instance-identifier rds-publisher \
--db-instance-class db.r5.xlarge \
--engine postgres \
--engine-version 17.9 \
--master-username postgres \
--master-user-password &amp;lt;SecurePassword&amp;gt; \
--allocated-storage 200 \
--storage-type gp2 \
--storage-encrypted \
--db-subnet-group-name rds-outposts-subnet-group \
--availability-zone us-west-2a \
--no-multi-az \
--no-publicly-accessible \
--enable-customer-owned-ip \
--db-parameter-group-name &amp;lt;parameter-group-with-logical-replication&amp;gt; \
--vpc-security-group-ids sg-xxx \
--region us-west-2&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="create-the-subscriber-instance-outpost-b"&gt;Create the subscriber instance (Outpost B)&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws rds create-db-instance \
--db-instance-identifier rds-subscriber \
--db-instance-class db.r5.xlarge \
--engine postgres \
--engine-version 17.9 \
--master-username postgres \
--master-user-password &amp;lt;SecurePassword&amp;gt; \
--allocated-storage 200 \
--storage-type gp2 \
--storage-encrypted \
--db-subnet-group-name rds-outposts-subnet-group \
--availability-zone us-west-2b \
--no-multi-az \
--no-publicly-accessible \
--enable-customer-owned-ip \
--vpc-security-group-ids sg-xxx \
--region us-west-2&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="verify-coip-assignment"&gt;Verify CoIP assignment&lt;/h3&gt; 
&lt;p&gt;After the instances become available, verify that CoIP addresses have been assigned:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 describe-addresses --region us-west-2 \
--query "Addresses[?CustomerOwnedIp!=null].[CustomerOwnedIp,PrivateIpAddress,NetworkInterfaceId]" \
--output table&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You should see output similar to:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-plaintext"&gt;-------------------------------------------------
|                DescribeAddresses              |
+------------------+-------------+--------------+
| 198.19.9.10      | 10.0.1.15   | eni-xxx      |
| 198.19.5.20      | 10.0.2.25   | eni-yyy      |
+------------------+-------------+--------------+&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="step-4-configure-security-groups"&gt;Step 4: Configure security groups&lt;/h2&gt; 
&lt;p&gt;Security groups must allow PostgreSQL traffic (port 5432) from both CoIP ranges and private subnet ranges:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# Allow traffic from Outpost A CoIP range
aws ec2 authorize-security-group-ingress \
--group-id sg-xxx \
--protocol tcp \
--port 5432 \
--cidr 198.19.9.0/24

# Allow traffic from Outpost B CoIP range
aws ec2 authorize-security-group-ingress \
--group-id sg-xxx \
--protocol tcp \
--port 5432 \
--cidr 198.19.5.0/24

# Allow traffic from Outpost A private subnet
aws ec2 authorize-security-group-ingress \
--group-id sg-xxx \
--protocol tcp \
--port 5432 \
--cidr 10.0.1.0/24

# Allow traffic from Outpost B private subnet
aws ec2 authorize-security-group-ingress \
--group-id sg-xxx \
--protocol tcp \
--port 5432 \
--cidr 10.0.2.0/24&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Make sure egress rules allow all outbound traffic (default) or at minimum port 5432 to the CoIP ranges.&lt;/p&gt; 
&lt;h2 id="step-5-configure-postgresql-logical-replication"&gt;Step 5: Configure PostgreSQL logical replication&lt;/h2&gt; 
&lt;h3 id="enable-logical-replication-on-the-publisher"&gt;Enable logical replication on the publisher&lt;/h3&gt; 
&lt;p&gt;The publisher requires the &lt;code&gt;rds.logical_replication&lt;/code&gt; parameter set to &lt;code&gt;1&lt;/code&gt;, which requires a database reboot:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws rds modify-db-parameter-group \
--db-parameter-group-name publisher-params \
--parameters "ParameterName=rds.logical_replication,ParameterValue=1,ApplyMethod=pending-reboot"

aws rds reboot-db-instance --db-instance-identifier rds-publisher&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;This automatically sets &lt;code&gt;wal_level = logical&lt;/code&gt;, so PostgreSQL can capture the necessary change data for replication.&lt;/p&gt; 
&lt;h3 id="create-replication-user-and-publication-on-the-publisher"&gt;Create replication user and publication on the publisher&lt;/h3&gt; 
&lt;p&gt;Connect to the publisher instance and execute:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;-- Create a replication user
CREATE USER repluser WITH REPLICATION LOGIN PASSWORD 'YourStrongPassword';

-- Grant SELECT on tables to replicate (required for initial COPY)
GRANT SELECT ON ALL TABLES IN SCHEMA public TO repluser;

-- Create table to replicate (example: healthcare appointments)
CREATE TABLE patient_appointments (
    appointment_id SERIAL PRIMARY KEY,
    patient_id INTEGER NOT NULL,
    patient_name VARCHAR(100), -- PHI: can be excluded from replication
    ssn VARCHAR(11), -- PHI: can be excluded from replication
    date_of_birth DATE, -- PHI: can be excluded from replication
    diagnosis_code VARCHAR(10), -- PHI: can be excluded from replication
    appointment_date DATE NOT NULL,
    doctor_id INTEGER NOT NULL,
    department VARCHAR(50),
    billing_amount DECIMAL(10,2),
    procedure_code VARCHAR(10),
    visit_type VARCHAR(20)
);

-- Create a publication for the table
CREATE PUBLICATION my_publication FOR TABLE patient_appointments;

-- Or for all tables in the schema:
-- CREATE PUBLICATION my_publication FOR ALL TABLES;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Keep in mind that the replication user must have &lt;code&gt;SELECT&lt;/code&gt; permission on all published tables. Without it, the initial table synchronization (COPY phase) hangs indefinitely in state ‘d’ (data copy).&lt;/p&gt; 
&lt;h3 id="create-matching-schema-and-subscription-on-the-subscriber"&gt;Create matching schema and subscription on the subscriber&lt;/h3&gt; 
&lt;p&gt;Connect to the subscriber instance and execute:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;-- Create the target table with IDENTICAL schema
-- The table structure must match the publisher exactly
CREATE TABLE patient_appointments (
    appointment_id SERIAL PRIMARY KEY,
    patient_id INTEGER NOT NULL,
    patient_name VARCHAR(100),
    ssn VARCHAR(11),
    date_of_birth DATE,
    diagnosis_code VARCHAR(10),
    appointment_date DATE NOT NULL,
    doctor_id INTEGER NOT NULL,
    department VARCHAR(50),
    billing_amount DECIMAL(10,2),
    procedure_code VARCHAR(10),
    visit_type VARCHAR(20)
);

-- Create the subscription
CREATE SUBSCRIPTION my_subscription
CONNECTION 'host=rds-publisher.xxx.us-west-2.rds.amazonaws.com port=5432 dbname=postgres user=repluser password=YourStrongPassword '
PUBLICATION my_publication;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;PostgreSQL 15+ on RDS defaults to &lt;code&gt;rds.force_ssl = 1&lt;/code&gt;, which means the database rejects any non-SSL connection. When CoIP is enabled, RDS on Outposts automatically uses the CoIP address for all connections from both inside and outside of the VPC. Traffic routes through the Local Gateway even for same-outpost communication. PostgreSQL’s &lt;code&gt;pg_hba.conf&lt;/code&gt; treats these CoIP-routed connections as non-local, and with &lt;code&gt;rds.force_ssl = 1&lt;/code&gt;, the server requires SSL. If the &lt;code&gt;CREATE SUBSCRIPTION&lt;/code&gt; connection string omits &lt;code&gt;sslmode=require&lt;/code&gt;, the subscriber’s connection attempt is rejected with a no &lt;code&gt;pg_hba.conf&lt;/code&gt; entry for host error. To avoid this, always include &lt;code&gt;sslmode=require&lt;/code&gt; in the subscription connection string:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;CREATE SUBSCRIPTION my_subscription CONNECTION 'host=rds-publisher.xxx.us-west-2.rds.amazonaws.com port=5432 dbname=postgres user=repluser password=YourStrongPassword sslmode=require'
PUBLICATION my_publication;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The subscription will automatically:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Create a replication slot on the publisher.&lt;/li&gt; 
 &lt;li&gt;Perform an initial table sync (COPY of existing data).&lt;/li&gt; 
 &lt;li&gt;Begin streaming ongoing changes in real-time.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h2 id="step-6-monitor-and-verify-replication"&gt;Step 6: Monitor and verify replication&lt;/h2&gt; 
&lt;p&gt;To monitor replication and verify that logical replication is functioning correctly between the publisher and subscriber instance, PostgreSQL provides several system catalog views and statistics views to monitor replication health. On the publisher instance, we query &lt;code&gt;pg_stat_replication&lt;/code&gt; to confirm active write-ahead log (WAL) sender connections and track replication progress through sent and written log sequence number (LSN) positions. We also query &lt;code&gt;pg_replication_slots&lt;/code&gt; to verify that the logical replication slot is active and its WAL retention status is healthy. On the subscriber instance, we query &lt;code&gt;pg_subscription&lt;/code&gt; to confirm the subscription is enabled and connected to the correct upstream database. We query &lt;code&gt;pg_subscription_rel&lt;/code&gt; to verify the synchronization state of each replicated table.&lt;/p&gt; 
&lt;h3 id="check-replication-status-on-the-publisher"&gt;Check replication status on the publisher&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;-- View active replication connections
SELECT pid, usename, client_addr, state, sent_lsn, write_lsn
FROM pg_stat_replication;

-- View replication slots
SELECT slot_name, active, restart_lsn, confirmed_flush_lsn, wal_status
FROM pg_replication_slots;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="check-subscription-status-on-the-subscriber"&gt;Check subscription status on the subscriber&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;-- View subscription details
SELECT subname, subenabled, subconninfo FROM pg_subscription;

-- View subscription state
SELECT srsubstate FROM pg_subscription_rel;
-- States: 'i' = init, 'd' = data copy, 'r' = ready, 's' = synced, 'f' = finished table copy&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Expected output after successful initial sync:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-plaintext"&gt;srsubstate
-----------
r&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="test-data-replication"&gt;Test data replication&lt;/h3&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;-- On publisher:
INSERT INTO patient_appointments (patient_id, appointment_date, doctor_id, department, billing_amount, visit_type)
VALUES (1001, '2026-07-15', 42, 'Cardiology', 250.00, 'Follow-up');

-- On subscriber (should appear within seconds):
SELECT count(*) FROM patient_appointments;
SELECT * FROM patient_appointments WHERE patient_id = 1001;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="troubleshooting-common-issues"&gt;Troubleshooting common issues&lt;/h2&gt; 
&lt;h3 id="issue-1-rds-endpoint-not-reachable-through-coip"&gt;Issue 1: RDS endpoint not reachable through CoIP&lt;/h3&gt; 
&lt;p&gt;Symptom: TCP connection to CoIP address times out.&lt;/p&gt; 
&lt;p&gt;Diagnosis:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# From an EC2 instance on the same subnet
telnet rds-publisher.xxx.us-west-2.rds.amazonaws.com 5432&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Check:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Route table has both cross-outpost and same-outpost hairpin routes.&lt;/li&gt; 
 &lt;li&gt;Security groups allow port 5432 from CoIP ranges.&lt;/li&gt; 
 &lt;li&gt;CoIP is enabled on the RDS instance (&lt;code&gt;CustomerOwnedIpEnabled: true&lt;/code&gt;).&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="issue-2-coip-not-assigned-to-rds-instance"&gt;Issue 2: CoIP not assigned to RDS instance&lt;/h3&gt; 
&lt;p&gt;Symptom: &lt;code&gt;CustomerOwnedIpEnabled: false&lt;/code&gt; when describing the RDS instance.&lt;/p&gt; 
&lt;p&gt;Cause: RDS doesn’t inherit the subnet’s &lt;code&gt;MapCustomerOwnedIpOnLaunch&lt;/code&gt; setting. Must be explicitly enabled.&lt;/p&gt; 
&lt;p&gt;Fix:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws rds modify-db-instance \
--db-instance-identifier rds-xxx \
--enable-customer-owned-ip \
--apply-immediately&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="issue-3-initial-sync-stuck-in-state-d"&gt;Issue 3: Initial sync stuck in state ‘d’&lt;/h3&gt; 
&lt;p&gt;Symptom: &lt;code&gt;pg_subscription_rel&lt;/code&gt; shows &lt;code&gt;srsubstate = 'd'&lt;/code&gt; indefinitely.&lt;/p&gt; 
&lt;p&gt;Causes:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Replication user lacks &lt;code&gt;SELECT&lt;/code&gt; permission on published tables.&lt;/li&gt; 
 &lt;li&gt;Table schema mismatch between publisher and subscriber.&lt;/li&gt; 
 &lt;li&gt;Network connectivity issue during COPY phase.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Fix:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;-- On publisher: grant SELECT permission
GRANT SELECT ON ALL TABLES IN SCHEMA public TO repluser;

-- On subscriber: drop and recreate subscription
ALTER SUBSCRIPTION my_subscription DISABLE;
ALTER SUBSCRIPTION my_subscription SET (slot_name = NONE);
DROP SUBSCRIPTION my_subscription;

-- Recreate subscription
CREATE SUBSCRIPTION my_subscription CONNECTION '...' PUBLICATION my_publication;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="issue-4-no-pg_hba.conf-entry-for-host-error"&gt;Issue 4: “no pg_hba.conf entry for host” error&lt;/h3&gt; 
&lt;p&gt;Symptom: Connection refused with pg_hba error when connecting from CoIP address.&lt;/p&gt; 
&lt;p&gt;Cause: &lt;code&gt;rds.force_ssl = 1&lt;/code&gt; (default in PostgreSQL 15+) requires SSL for connections from non-VPC addresses.&lt;/p&gt; 
&lt;p&gt;Fix: Make sure &lt;code&gt;sslmode=require&lt;/code&gt; is included in the connection string:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;CONNECTION 'host=... port=5432 dbname=... user=... password=... sslmode=require'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="issue-5-subscription-pointing-to-wrong-publication"&gt;Issue 5: Subscription pointing to wrong publication&lt;/h3&gt; 
&lt;p&gt;Symptom: Subscription connected but no data replicating.&lt;/p&gt; 
&lt;p&gt;Fix: Drop and recreate subscription with correct publication name:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;ALTER SUBSCRIPTION my_subscription DISABLE;
ALTER SUBSCRIPTION my_subscription SET (slot_name = NONE);
DROP SUBSCRIPTION my_subscription;

-- Clean up orphaned slots on publisher if needed
-- SELECT pg_drop_replication_slot('my_subscription');

CREATE SUBSCRIPTION my_subscription
CONNECTION '...'
PUBLICATION correct_publication_name;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="data-residency-considerations"&gt;Data residency considerations&lt;/h2&gt; 
&lt;p&gt;This architecture provides complete data residency by the following means:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;No regional backups:&lt;/strong&gt; Automated backups to Amazon S3 in the Region are disabled. All data remains on the Outposts.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;On-premises replication:&lt;/strong&gt; All replication traffic flows through Local Gateways and your on-premises network, never traversing the Region backbone.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Local recovery:&lt;/strong&gt; If an Outpost fails, you can promote the subscriber to become the new primary, maintaining business continuity without regional dependencies.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Selective replication:&lt;/strong&gt; With logical replication, you can exclude sensitive columns, such as protected health information (PHI) and personally identifiable information (PII), from replication by creating publications for specific columns or tables.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;For customers who can accept local backups, RDS on Outposts supports local backup to S3 on Outposts for MySQL and PostgreSQL (not supported for Multi-AZ deployments or read replicas). This requires &lt;a href="https://aws.amazon.com/s3/outposts/" target="_blank" rel="noopener"&gt;S3 on Outposts capacity&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="best-practices-and-key-takeaways"&gt;Best practices and key takeaways&lt;/h2&gt; 
&lt;p&gt;Throughout this implementation, we encountered several configuration details that are important for a successful deployment. The following best practices and key takeaways will help you avoid common pitfalls when setting up PostgreSQL logical replication between RDS instances on separate Outposts.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;CoIP must be explicitly enabled on RDS:&lt;/strong&gt; It isn’t inherited from subnet settings. Always include &lt;code&gt;--enable-customer-owned-ip&lt;/code&gt; when creating RDS instances.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Both cross-outpost and hairpin routes are required:&lt;/strong&gt; Without hairpin routes, same-subnet access to CoIP addresses fails because DNS resolves to CoIP instead of the private IP.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Replication user needs &lt;code&gt;SELECT&lt;/code&gt; permission:&lt;/strong&gt; Required for the initial COPY phase. Without it, the subscription hangs in state ‘d’.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Table schemas must be identical:&lt;/strong&gt; The subscriber table must exactly match the publisher table structure, including column names, types, and constraints.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;SSL is enforced by default:&lt;/strong&gt; PostgreSQL 15+ defaults to &lt;code&gt;rds.force_ssl = 1&lt;/code&gt;. Use &lt;code&gt;sslmode=require&lt;/code&gt; for external connections.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Use Terraform or the CLI for deployment:&lt;/strong&gt; AWS CloudFormation doesn’t support the &lt;code&gt;EnableCustomerOwnedIp&lt;/code&gt; property. Use Terraform (&lt;code&gt;customer_owned_ip_enabled = true&lt;/code&gt;) or the AWS CLI.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Monitor replication lag:&lt;/strong&gt; Use the &lt;code&gt;pg_stat_replication&lt;/code&gt; and &lt;code&gt;pg_replication_slots&lt;/code&gt; views to monitor replication health and lag.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Plan for failover:&lt;/strong&gt; Document procedures for promoting the subscriber to primary if Outpost A fails, including application connection string updates.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="comparison-with-multi-az-deployments"&gt;Comparison with Multi-AZ deployments&lt;/h2&gt; 
&lt;p&gt;Multi-AZ deployments remain the recommended approach for high availability on Amazon RDS on AWS Outposts. They provide automatic failover with synchronous replication between a primary DB instance on one Outpost and a standby on a different Outpost. However, Multi-AZ requires two Outposts anchored to different Availability Zones, and local backups aren’t supported for Multi-AZ deployments. As AWS documentation notes, customers whose workloads must abide by data residency regulations should consult with regulators to determine whether Multi-AZ meets their requirements, because only Single-AZ instances support storing all automated backups and logs directly on the Outposts rack. This post presents an alternative approach that uses PostgreSQL logical replication between Outposts for organizations that need an additional layer of data resilience while keeping all data on-premises. It applies specifically where data residency requirements prevent the use of Regional backups and where the Multi-AZ infrastructure prerequisites (two Outposts across two Availability Zones) are not available. The two options have different characteristics:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Feature&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Logical Replication&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Multi-AZ on Outposts&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Data Residency&lt;/td&gt; 
   &lt;td&gt;Complete (no regional backups)&lt;/td&gt; 
   &lt;td&gt;Automated backups to Region S3&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Failover&lt;/td&gt; 
   &lt;td&gt;Manual promotion&lt;/td&gt; 
   &lt;td&gt;Automatic (1-2 minutes)&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Replication Granularity&lt;/td&gt; 
   &lt;td&gt;Table-level or column-level&lt;/td&gt; 
   &lt;td&gt;Entire database instance&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Cross-Region DR&lt;/td&gt; 
   &lt;td&gt;Supported&lt;/td&gt; 
   &lt;td&gt;Requires additional setup&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Network Path&lt;/td&gt; 
   &lt;td&gt;CoIP through Local Gateway&lt;/td&gt; 
   &lt;td&gt;VPC internal (Multi-AZ)&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Use Case&lt;/td&gt; 
   &lt;td&gt;Strict data residency, selective replication&lt;/td&gt; 
   &lt;td&gt;High availability with regional integration&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;For organizations that can accept automated backups to the Region, Multi-AZ deployments offer simpler management and automatic failover. For those with absolute data residency requirements, logical replication with CoIP provides complete control over data locality.&lt;/p&gt; 
&lt;h2 id="clean-up"&gt;Clean up&lt;/h2&gt; 
&lt;p&gt;When you’re done testing, remove the replication resources to avoid unnecessary costs and WAL accumulation.&lt;/p&gt; 
&lt;p&gt;On the target, drop the subscription first:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;DROP SUBSCRIPTION my_subscription;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;On the source, drop the publication:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;DROP PUBLICATION my_publication;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Drop the test tables on both source and target:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;DROP TABLE IF EXISTS patient_appointments;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;If you created dedicated Amazon RDS instances for this walkthrough, delete them through the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DeleteInstance.html" target="_blank" rel="noopener"&gt;AWS Management Console&lt;/a&gt; or &lt;a href="https://docs.aws.amazon.com/cli/latest/reference/rds/delete-db-instance.html" target="_blank" rel="noopener"&gt;CLI&lt;/a&gt; to stop incurring charges. If you modified an existing parameter group, consider reverting &lt;code&gt;rds.logical_replication&lt;/code&gt; to 0 if you no longer need logical replication, and reboot the instance.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;In this post, we showed you how to configure PostgreSQL logical replication between Amazon RDS for PostgreSQL instances on separate AWS Outposts. This approach gives organizations with strict data residency requirements a way to keep all data on-premises. By using Customer-owned IP addresses and Local Gateways, you can establish secure, low-latency replication that keeps all data within your on-premises environment.&lt;/p&gt; 
&lt;p&gt;This architecture is particularly valuable for:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Healthcare providers managing PHI under the Health Insurance Portability and Accountability Act (HIPAA).&lt;/li&gt; 
 &lt;li&gt;Financial institutions with data sovereignty requirements.&lt;/li&gt; 
 &lt;li&gt;Government agencies with classified or sensitive data.&lt;/li&gt; 
 &lt;li&gt;Organizations in regulated industries where data must remain on-premises.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;The configuration requires careful attention to networking details, particularly the hairpin routes and explicit CoIP enablement. After it’s established, it provides a foundation for disaster recovery and high availability without compromising data residency.&lt;/p&gt; 
&lt;p&gt;For more information about &lt;a href="https://aws.amazon.com/rds/outposts/" target="_blank" rel="noopener"&gt;Amazon RDS on AWS Outposts&lt;/a&gt;, visit the RDS on Outposts documentation and &lt;a href="https://docs.aws.amazon.com/outposts/latest/userguide/what-is-outposts.html" target="_blank" rel="noopener"&gt;the AWS Outposts High Availability Design whitepaper&lt;/a&gt;.&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/02/ComputeBlog-2830-2.jpg" alt="Belma Canik" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Belma Canik&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Belma is a Senior Database Specialist Technical Account Manager (STAM) at Amazon Web Services. She helps customers run optimized workloads on AWS and make the best out of their cloud journey. She also helps customers have robust Data Operations that also provide AI-ready data platforms through Data Operations Review at AWS.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Plan and measure EC2 flexibility with Amazon EC2 Capacity Manager</title>
		<link>https://aws.amazon.com/blogs/compute/plan-and-measure-ec2-flexibility-with-amazon-ec2-capacity-manager/</link>
		
		<dc:creator><![CDATA[Yagya Vir Singh]]></dc:creator>
		<pubDate>Wed, 04 Nov 2026 18:11:34 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Announcements]]></category>
		<guid isPermaLink="false">9e7bd47fdd6368dcb0b0efa8dfd09e5abf085b6a</guid>

					<description>Amazon EC2 Capacity Manager offers real-time supportability checks and capacity fulfillment metrics for large EC2 fleets. This post shows how to measure how well your instance type and Availability Zone flexibility performs, find where capacity is strongest before a scale-up, and add it to Auto Scaling groups, Amazon EC2 Fleet, or Karpenter.</description>
										<content:encoded>&lt;p&gt;Global enterprises that run thousands of workloads across hundreds of accounts often configure them to use multiple instance types and Availability Zones. This flexibility gives Amazon Elastic Compute Cloud (Amazon EC2) more options to fulfill each request. At that scale, you need to decide which instance types and Availability Zones to include, and have visibility into how well those choices are working.&lt;/p&gt; 
&lt;p&gt;To gain these insights, Amazon EC2 Capacity Manager offers real-time supportability checks and capacity fulfillment metrics. Supportability checks help you find capacity when you plan a workload by scoring how well each instance type and Availability Zone can support a request. They do this without launching or reserving instances. Capacity fulfillment metrics show whether you configured your launch requests to use multiple instance types and Availability Zones, their fulfillment rate, and where that capacity came from. They measure your actual launches, not the accuracy of a check. Together, they cover both sides of a scale up: deciding where to run, and measuring what was delivered.&lt;/p&gt; 
&lt;p&gt;Both capabilities are included with AWS Unified Operations, the AWS Support plan for global enterprises that run workloads at large scale. You can query data from &lt;a href="https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html#available-regions" target="_blank" rel="noopener"&gt;all commercial AWS Regions&lt;/a&gt; using the Region in which you enabled EC2 Capacity Manager.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-1-1.png" target="_blank" rel="noopener"&gt;&lt;img title="Figure 1: Supportability checks score options before you scale up. Fulfillment metrics measure how your actual launches were fulfilled." src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-1-1.png" alt="Two panels. Plan before you scale up: real-time supportability checks return a High, Medium, or Low score for each option plus an aggregate. Measure what was delivered: capacity fulfillment metrics show a fulfillment rate and a breakdown by instance type and Availability Zone." width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: Supportability checks score options before you scale up. Fulfillment metrics measure how your actual launches were fulfilled.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;This post follows the platform team at AnyCompany, a global enterprise that supports several large scale ups each year. Before each one, the team wants to know which instance types and Availability Zones will best support a workload. In this post, a combination means one instance type in one Availability Zone, such as r5.16xlarge in use1-az5. Capacity Manager measures capacity in vCPUs, and each step shows the AWS Management Console path and the AWS Command Line Interface (AWS CLI) command.&lt;/p&gt; 
&lt;h2 id="before-you-begin"&gt;Before you begin&lt;/h2&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Turn on Capacity Manager&lt;/strong&gt; at the organization level (from the management account or a delegated administrator) or for a single account. Both capabilities work at either level. See &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-manager.html" target="_blank" rel="noopener"&gt;Enabling EC2 Capacity Manager&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Confirm your support plan.&lt;/strong&gt; Your account must be covered by AWS Unified Operations.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;(Optional)&lt;/strong&gt; &lt;strong&gt;To see metrics by workload&lt;/strong&gt;, activate a workload tag as a monitored tag key. Some tags, including aws:eks:cluster-name and aws:autoscaling:groupName, are always available and need no activation. This post uses aws:eks:cluster-name. For more information, see &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-monitored-tag-keys.html" target="_blank" rel="noopener"&gt;Managing monitored tag keys&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="step-1-see-whether-your-workloads-are-getting-the-capacity-they-need"&gt;Step 1: See whether your workloads are getting the capacity they need&lt;/h2&gt; 
&lt;p&gt;Capacity fulfillment metrics start at the request level. A request that can use several combinations is fulfilled if any one of them delivers, so a high request fulfillment rate means flexibility is working. Capacity Manager tracks four request-level metrics.&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Metric&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Console label&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;What it tells you&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;CapacityTotalRequestedVcpu&lt;/td&gt; 
   &lt;td&gt;Requested (vCPUs)&lt;/td&gt; 
   &lt;td&gt;Capacity requested. Retries within five minutes for the same configuration count once.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;CapacityTotalFulfilledVcpu&lt;/td&gt; 
   &lt;td&gt;Fulfilled (vCPUs)&lt;/td&gt; 
   &lt;td&gt;Capacity delivered.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;CapacityRequestFulfillmentRate&lt;/td&gt; 
   &lt;td&gt;Request fulfillment rate&lt;/td&gt; 
   &lt;td&gt;Fulfilled divided by requested, vCPU-weighted.&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;AvgInstAzCountPerRequestedVcpu&lt;/td&gt; 
   &lt;td&gt;Instance Type x AZ count (avg)&lt;/td&gt; 
   &lt;td&gt;Combinations each request is configured to use. A value above 1 means the request is flexible.&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;These metrics break down by account, Region, and tag. To review them on the console, complete the following steps.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Open the &lt;strong&gt;Fulfillment&lt;/strong&gt; tab.&lt;/li&gt; 
 &lt;li&gt;Choose a date range and a metric set (On-Demand or Spot).&lt;/li&gt; 
 &lt;li&gt;Filter by a dimension, such as Region, account, or tag, to see one row for each value.&lt;/li&gt; 
 &lt;li&gt;Sort by Requested (vCPUs) to see your largest workloads first, or by request fulfillment rate to find the ones with the most room to improve.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-2.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-2.png" alt="Capacity Manager Fulfillment tab listing workloads by the aws:eks:cluster-name tag, each row showing its request fulfillment rate and Instance Type x AZ count" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: The Fulfillment tab for an example account, filtered by the aws:eks:cluster-name tag. Each row shows one workload’s request fulfillment rate and Instance Type x AZ count.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;At AnyCompany, the search-index workload requested 51,712 vCPUs and received 45,632, an 88.2 percent request fulfillment rate. Its requests could use an average of 21 combinations. Compare batch-etl, which can use only one combination and fulfills 72.8 percent. Step 2 shows where the search-index capacity came from and where it fell short.&lt;/p&gt; 
&lt;p&gt;To get the same data with the AWS CLI, call get-capacity-manager-metric-data. Spot metrics use a Spot prefix, such as SpotCapacityRequestFulfillmentRate.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 get-capacity-manager-metric-data \
--metric-names capacity-request-fulfillment-rate avg-inst-az-count-per-requested-vcpu \
--start-time 2026-11-02T19:00:00Z --end-time 2026-11-03T19:00:00Z \
--period 86400 \
--filter-by 'DimensionCondition={Dimension=tag:aws:eks:cluster-name,Comparison=equals,Values=[search-index]}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="step-2-see-where-your-flexibility-is-paying-off"&gt;Step 2: See where your flexibility is paying off&lt;/h2&gt; 
&lt;p&gt;The breakdown measures each combination on its own, so per-combination rates are usually lower than the request rate, which includes the benefit of diversification.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-3.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-3.png" alt="Breakdown for the search-index workload showing lower per-combination fulfillment rates against the 88.2 percent request rate" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 3: The search-index request is 88.2 percent fulfilled, while each combination is measured on its own.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;In Figure 3, the three search-index combinations in use1-az5 deliver 68.6–82.8 percent of what is asked. Outside use1-az5, r5.16xlarge delivers 98.5–100 percent in use1-az4 and use1-az6, and r6a.16xlarge delivers 100 percent in use1-az4. Because the request can use any of these combinations, the other zones cover part of what use1-az5 can’t. So those zones are worth keeping, and use1-az5 is where to add options or reserve capacity.&lt;/p&gt; 
&lt;p&gt;On the console, choose &lt;strong&gt;View breakdown&lt;/strong&gt; on any row of the &lt;strong&gt;Fulfillment&lt;/strong&gt; tab. The breakdown lists each combination, and you can sort by fulfillment rate, fulfilled vCPUs, or usage. It adds instance type, instance family, and Availability Zone to the dimensions from Step 1.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-4.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-4.png" alt="Fulfillment breakdown for search-index with per-combination rates and a Check supportability link on each row" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 4: The breakdown for the search-index workload, with a Check supportability link on each row.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;In Figure 4, search-index fulfills 88.2 percent of requested capacity, while its 28 combinations average 46.6 percent on their own. The difference is what flexibility adds: when some combinations come up short, others deliver. The three use1-az5 combinations delivered 26,880 vCPUs, more than half of the 45,632 total, so that zone has the most room to improve. The Check supportability link on each row opens a check for that combination.&lt;/p&gt; 
&lt;p&gt;Through the API, query InstAzFulfillmentRate. The request must include the availability-zone-id dimension and either instance-type or instance-family.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 get-capacity-manager-metric-data \
--metric-names inst-az-fulfillment-rate \
--start-time 2026-11-02T19:00:00Z --end-time 2026-11-03T19:00:00Z \
--period 86400 \
--group-by availability-zone-id instance-type \
--filter-by 'DimensionCondition={Dimension=tag:aws:eks:cluster-name,Comparison=equals,Values=[search-index]}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="step-3-find-where-capacity-is-strongest-before-you-scale-up"&gt;Step 3: Find where capacity is strongest before you scale up&lt;/h2&gt; 
&lt;p&gt;Before a large scale up or migration, the platform team runs a supportability check. They provide the market type (On-Demand or Spot), the capacity amount, the Availability Zones, and the instance types to consider. The check returns a High, Medium, or Low score for each combination, plus an aggregate score for the set. The following example checks a scale up for search-index: 100 instances across its three Availability Zones, with its three current instance types and two candidates, r6i.16xlarge and r7i.16xlarge.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 get-capacity-manager-supportability-scores \
--market-type "on-demand" \
--capacity-amount 100 \
--capacity-unit "instances" \
--capacity-availability-zone-ids '["use1-az4", "use1-az5", "use1-az6"]' \
--instance-types '["r5.16xlarge", "r6a.16xlarge", "r7a.16xlarge", "r6i.16xlarge", "r7i.16xlarge"]'
{
  "AggregateScore": "high",
  "CapacityManagerSupportabilityScores": [
    {"InstanceType": "r5.16xlarge", "AvailabilityZoneId": "use1-az4", "Score": "high"},
    {"InstanceType": "r6a.16xlarge", "AvailabilityZoneId": "use1-az4", "Score": "medium"},
    {"InstanceType": "r7i.16xlarge", "AvailabilityZoneId": "use1-az6", "Score": "medium"},
    {"InstanceType": "r7a.16xlarge", "AvailabilityZoneId": "use1-az4", "Score": "low"},
    ...
  ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Instead of a list, you can also pass &lt;code&gt;--instance-requirements-with-metadata&lt;/code&gt;, with the vCPU and memory ranges inside an &lt;code&gt;InstanceRequirements&lt;/code&gt; object. Capacity Manager scores each matching instance type. For Spot, set the market type to spot.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;--instance-requirements-with-metadata '{
  "InstanceRequirements": {
    "VCpuCount": {"Min": 64, "Max": 64},
    "MemoryMiB": {"Min": 524288}
  }
}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;The Supportability tab on the console runs the same check. Enter the amount, type, Availability Zones, and instance types or attributes, then choose Check supportability. One check can include up to 10 Availability Zones, from more than one Region, and up to 100 combinations. Figure 5 shows the search-index check on the console. The aggregate score is High, so together the set can support 100 instances. r5.16xlarge scores High in all three zones, and r7a.16xlarge scores High in use1-az6. r6a.16xlarge scores Medium in all three zones, and the new candidate r7i.16xlarge scores Medium in use1-az4 and use1-az6. The other six combinations, including every r6i.16xlarge combination, score Low.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-5.png" target="_blank" rel="noopener"&gt;&lt;img title="Figure 5: A check for 100 instances of five instance types across the three search-index Availability Zones, with High aggregate confidence." src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-5.png" alt="Screenshot of the Capacity Manager Supportability tab. The left panel sets 100 On-Demand instances, Availability Zones use1-az4, use1-az5, and use1-az6, and instance types r5.16xlarge, r6a.16xlarge, r7a.16xlarge, r6i.16xlarge, and r7i.16xlarge. The right panel shows High aggregate supportability confidence, 4 of 15 combinations at High, 5 at Medium, and 6 at Low, with a confidence for each combination." width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 5: A check for 100 instances of five instance types across the three search-index Availability Zones, with High aggregate confidence.&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;High means a combination holds more than enough to serve your request. Medium means it can cover the request with little to spare, and Low means it holds less than you asked for. For details, see &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-manager-score-meaning.html" target="_blank" rel="noopener"&gt;What the scores mean&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-manager-score-actions.html" target="_blank" rel="noopener"&gt;What to do based on your score&lt;/a&gt; in the Amazon Elastic Compute Cloud User Guide.&lt;/p&gt; 
&lt;p&gt;Scores are guidance, not commitments. If you need assurance capacity will be there when you launch, use Capacity Reservations or future-dated Capacity Reservations.&lt;/p&gt; 
&lt;p&gt;Run the check when you plan a workload, not on every launch. You call it in the Region where Capacity Manager is turned on, so per-launch calls would add a cross-Region dependency and use up the hourly quota.&lt;/p&gt; 
&lt;h2 id="step-4-add-the-flexibility-to-your-fleet"&gt;Step 4: Add the flexibility to your fleet&lt;/h2&gt; 
&lt;p&gt;After a check shows which combinations can support a workload, add them to your Auto Scaling group, Amazon EC2 Fleet, or Karpenter configuration. You configure flexibility once, and every later launch benefits from it.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-6.png" target="_blank" rel="noopener"&gt;&lt;img title="Figure 6: Use the capabilities to plan flexibility, then configure it in your fleet." src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-6.png" alt="Flow: supportability check and fulfillment metrics, then identify the instance types and zones that support the workload, then add that flexibility to Auto Scaling group, EC2 Fleet, or Karpenter, then launch as usual." width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 6: Use the capabilities to plan flexibility, then configure it in your fleet.&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="add-flexibility"&gt;Add flexibility&lt;/h3&gt; 
&lt;p&gt;For an Auto Scaling group, a mixed instances policy lists instance types in priority order. This example keeps r5.16xlarge, r6a.16xlarge, and r7a.16xlarge, which each delivered 98.5–100 percent outside use1-az5 in Figure 4. It adds r7i.16xlarge, which the check in Figure 5 scored Medium in two zones, and leaves out r6i.16xlarge, which scored Low.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws autoscaling update-auto-scaling-group \
--auto-scaling-group-name search-index-asg \
--mixed-instances-policy file://mixed-instances.json
# mixed-instances.json
{
  "LaunchTemplate": {
    "LaunchTemplateSpecification": {"LaunchTemplateName": "search-index-lt", "Version": "$Latest"},
    "Overrides": [{"InstanceType": "r5.16xlarge"}, {"InstanceType": "r6a.16xlarge"},
      {"InstanceType": "r7a.16xlarge"}, {"InstanceType": "r7i.16xlarge"}]
  },
  "InstancesDistribution": {"OnDemandAllocationStrategy": "prioritized"}
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;For workloads defined by vCPU and memory, attribute-based instance type selection draws on every type that fits. Afterward, watch AvgInstAzCountPerRequestedVcpu (the Instance Type x AZ count (avg) column) to confirm the change.&lt;/p&gt; 
&lt;h3 id="reserve-where-you-need-certainty"&gt;Reserve where you need certainty&lt;/h3&gt; 
&lt;p&gt;In use1-az5, r5.16xlarge delivered 82.8 percent in Figure 4, even though the check in Figure 5 scores it High right now. If the team needs that type in that zone, it can reserve its steady-state baseline with an On-Demand Capacity Reservation and let the rest stay flexible.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 create-capacity-reservation \
--instance-type r5.16xlarge --instance-platform Linux/UNIX \
--availability-zone-id use1-az5 --instance-count 10 \
--instance-match-criteria open --end-date-type unlimited&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;AWS bills you for Capacity Reservations whether or not you use them, so size them to your baseline. If you create one to try this example, cancel it when you no longer need it. Use the reservation ID from the create-capacity-reservation output.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws ec2 cancel-capacity-reservation \
--capacity-reservation-id cr-1234567890abcdef0&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Canceling an active reservation that has no commitment duration, like this one, has no charge. Any instances running in it keep running at On-Demand rates.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;Real-time supportability checks and capacity fulfillment metrics in Amazon EC2 Capacity Manager make flexibility visible. You can find the best instance types and Availability Zones before you scale up, see where flexibility is paying off, and know where to add more.&lt;/p&gt; 
&lt;p&gt;To make this routine, review fulfillment rates each week and open the breakdown for any workload below target. Add a supportability check to change management, so capacity is validated before a change that adds or scales a workload goes live.&lt;/p&gt; 
&lt;p&gt;To get started, open the Fulfillment tab on the AWS console under Capacity Manager. To learn more, go to &lt;a href="https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#CapacityManagerHome" target="_blank" rel="noopener"&gt;EC2 Capacity Manager on AWS Console&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-7.jpg" alt="Yagya Vir Singh" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Yagya Vir Singh&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Yagya is a Senior Technical Account Manager at AWS based in Nashville, Tennessee. He helps enterprise customers plan and operate their workloads on AWS, with a focus on monitoring and observability, cloud governance, cloud financial management, and generative AI.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/11/04/ComputeBlog-2823-8.jpg" alt="Brian Phillippi" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Brian Phillippi&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Brian is a Principal Product Manager – Technical for Amazon EC2, based in Arizona. He works on EC2 capacity products, including EC2 Capacity Manager, and helps large customers plan and secure the capacity they need. Before joining EC2 product management, he spent several years in AWS infrastructure and demand planning, forecasting and planning the capacity behind AWS Regions.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Introducing queue consumption mode for Apache Kafka in AWS Lambda</title>
		<link>https://aws.amazon.com/blogs/compute/introducing-queue-consumption-mode-for-apache-kafka-in-aws-lambda/</link>
		
		<dc:creator><![CDATA[Vaibhav Jain]]></dc:creator>
		<pubDate>Mon, 02 Nov 2026 21:23:46 +0000</pubDate>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<guid isPermaLink="false">62dcccecd9f7ac06b7e30f89cc10bafdbc487c07</guid>

					<description>AWS Lambda event source mappings now support queue consumption mode for Apache Kafka. Using Kafka Share Groups, you can scale consumer parallelism independently of partition count, with per-record acknowledgment, visibility timeouts, and automatic retries on self-managed Kafka 4.2 or later clusters.</description>
										<content:encoded>&lt;p&gt;Queue consumption mode for &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-eventsourcemapping.html" target="_blank" rel="noopener"&gt;AWS Lambda event source mappings (ESMs)&lt;/a&gt; that subscribe to Apache Kafka is now available. Queue consumption mode is available on the self-managed Apache Kafka ESM. It covers both Kafka clusters you operate yourself and managed Kafka offerings such as Confluent Cloud and other providers that offer Kafka 4.2 or later with Kafka Queue support.&lt;/p&gt; 
&lt;p&gt;With this launch, you can build queue-style event-driven workloads on Kafka that process records with high parallelism that scales concurrency to match your backlog instead of your topic layout. Queue mode achieves this using &lt;a href="https://cwiki.apache.org/confluence/spaces/KAFKA/pages/255070434/KIP-932+Queues+for+Kafka#KIP932:QueuesforKafka-Consumerconfiguration" target="_blank" rel="noopener"&gt;Kafka Share Groups (KIP-932)&lt;/a&gt;, introduced in Kafka 4.0. With share groups, multiple consumers read concurrently from the same partitions, so Lambda can process records from a single partition across many parallel invocations. The result is parallelism that is decoupled from partition count, without head-of-line blocking and without introducing a second messaging system into your architecture.&lt;/p&gt; 
&lt;p&gt;Many Kafka workloads treat each event as an independent unit of work rather than a step in an ordered sequence: generating image and video renditions after upload, offloading slow work from a user-facing API, scoring transactions for fraud, delivering notifications, enriching records for inference, processing bulk files, buffering ahead of a rate-limited dependency, and ingesting telemetry. Correctness for these workloads depends on processing records quickly, not in order. The Kafka consumer group protocol, however, assigns each partition to exactly one consumer, so a topic with 10 partitions supports up to 10 concurrent consumers. Over-partitioning raises that ceiling but increases broker resource usage, slows rebalances, and still leaves head-of-line blocking, where one slow record stalls every record behind it. Previously, teams moved this traffic to a separate queuing system, adding a platform to operate and new producer code.&lt;/p&gt; 
&lt;p&gt;In this post, you learn how queue consumption mode works compared to the existing stream mode, what broker and cluster requirements your Kafka 4.2 cluster must meet, and how to scale from on-demand defaults to provisioned mode for high-throughput workloads.&lt;/p&gt; 
&lt;h2 id="whats-new"&gt;What’s new&lt;/h2&gt; 
&lt;p&gt;This launch adds a &lt;code&gt;ConsumptionMode&lt;/code&gt; parameter to the Kafka event source mappings in Lambda. It accepts two values: Stream (the default, matching today’s behavior) and Queue, which uses Kafka Share Groups for parallel consumption. The core primitive in both modes is the &lt;strong&gt;event poller&lt;/strong&gt;, a compute resource that fetches records from Kafka and invokes your Lambda function. Queue mode changes the protocol an event poller uses to obtain those records. Because pollers are no longer bound to individual partitions, queue mode supports higher concurrency. A single poller reaches up to 10 concurrent invocations compared to 5 in stream mode, and queue mode scales independently of partition count. We cover the scaling model in detail later in this post.&lt;/p&gt; 
&lt;h3 id="stream-mode-one-consumer-per-partition-ordered-processing"&gt;Stream mode: One consumer per partition, ordered processing&lt;/h3&gt; 
&lt;p&gt;&lt;code&gt;ConsumptionMode&lt;/code&gt; defaults to &lt;strong&gt;Stream&lt;/strong&gt;, so existing ESMs are unaffected by this launch. In Stream mode, event pollers join a Kafka &lt;strong&gt;consumer group&lt;/strong&gt;, and the broker assigns each partition exclusively to one consumer. This guarantees ordered processing within each partition.&lt;/p&gt; 
&lt;h3 id="queue-mode-multiple-consumers-per-partition-unordered-parallel-processing"&gt;Queue mode: Multiple consumers per partition, unordered parallel processing&lt;/h3&gt; 
&lt;p&gt;Setting &lt;code&gt;ConsumptionMode&lt;/code&gt; to &lt;strong&gt;Queue&lt;/strong&gt; directs Lambda to use the Kafka Share Consumer. Event pollers join a &lt;strong&gt;share group&lt;/strong&gt;, where partitions can be assigned to multiple event pollers for parallel processing without guarantees about order. The broker manages a record lifecycle of Available, Acquired, Acknowledged, and Archived. Fetched records are marked Acquired under a visibility timeout called the record lock duration. A successful invocation acknowledges them. A failed invocation releases them back to Available for any poller to acquire. While an invocation is still running, the poller renews the lock without incrementing the delivery attempt count.&lt;/p&gt; 
&lt;h3 id="choosing-between-the-modes"&gt;Choosing between the modes&lt;/h3&gt; 
&lt;p&gt;Use Stream mode when per-partition ordering matters: change data capture, event sourcing, or per-entity state machines. Use Queue mode when records are independent, and you want parallelism that is not bounded by partition count. You can run a Queue mode ESM and a Stream mode ESM against the same topic. Each operates independently through its own protocol.&lt;/p&gt; 
&lt;h2 id="minimum-requirements"&gt;Minimum requirements&lt;/h2&gt; 
&lt;p&gt;Before you configure an ESM with &lt;code&gt;ConsumptionMode: Queue&lt;/code&gt;, confirm that your Kafka cluster and Lambda function meet the following requirements.&lt;/p&gt; 
&lt;h3 id="cluster-requirements"&gt;Cluster requirements&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;Apache Kafka 4.2 or later, with share groups enabled.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Four broker settings interact with your ESM configuration:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;group.share.partition.max.record.locks&lt;/strong&gt; – The maximum in-flight records per partition. In Queue mode, multiple pollers might acquire records from the same partition concurrently, so the total in-flight count can exceed a single poller’s batch size. Set this value high enough to accommodate your expected concurrency. When the limit is reached, pollers can’t acquire new records from that partition until existing records are acknowledged, or their locks expire.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;group.share.record.lock.duration.ms&lt;/strong&gt; – The visibility timeout for acquired records. In most cases, the default of 30 seconds is sufficient. The poller renews the lock during processing. A long-running function does not typically require a duration longer than 30 seconds.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;group.share.delivery.count.limit&lt;/strong&gt; – The maximum number of times the broker attempts to deliver a record before archiving it. This works alongside &lt;code&gt;MaximumRetryAttempts&lt;/code&gt; to govern retry behavior.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;group.share.max.size&lt;/strong&gt; – The maximum consumers allowed in the share group. When &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/kafka-scaling-modes.html#kafka-provisioned-mode" target="_blank" rel="noopener"&gt;provisioned mode&lt;/a&gt; is active, keep &lt;code&gt;MinimumPollers&lt;/code&gt; ≤ &lt;code&gt;MaximumPollers&lt;/code&gt; ≤ &lt;code&gt;group.share.max.size&lt;/code&gt; so that Lambda scaling isn’t capped by the broker. In on-demand mode, Lambda internally manages poller counts within broker-safe defaults.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="getting-started"&gt;Getting started&lt;/h2&gt; 
&lt;p&gt;In the Lambda console, choose your function, choose &lt;strong&gt;Add trigger&lt;/strong&gt;, and select &lt;strong&gt;Self-managed Apache Kafka&lt;/strong&gt;. Enter your bootstrap servers and topic name, set &lt;strong&gt;Consumption mode&lt;/strong&gt; to &lt;strong&gt;Queue&lt;/strong&gt;, and configure your virtual private cloud (VPC) subnets and security groups. Optionally set &lt;strong&gt;Minimum event pollers&lt;/strong&gt; and &lt;strong&gt;Maximum event pollers&lt;/strong&gt; to use provisioned mode. For on-demand scaling leave those empty.&lt;/p&gt; 
&lt;p&gt;The following AWS CLI command creates the equivalent Queue mode ESM in on-demand mode:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda create-event-source-mapping
--function-name my-function
--self-managed-event-source '{"Endpoints":{"KAFKA_BOOTSTRAP_SERVERS":["broker1.example.com:9092","broker2.example.com:9092"]}}'
--topics my-queue-topic
--batch-size 100
--self-managed-kafka-event-source-config '{"ConsumptionMode": "Queue"}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;code&gt;ConsumptionMode&lt;/code&gt; is the only parameter required to enable Queue mode. &lt;code&gt;BatchSize&lt;/code&gt; sets the maximum records per batch sent to your function, accepts values from 1–10,000, and defaults to 100.&lt;/p&gt; 
&lt;p&gt;With AWS CloudFormation, the equivalent resource looks as follows:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;MyKafkaQueueESM:
  Type: AWS::Lambda::EventSourceMapping
  Properties:
    FunctionName: !Ref MyFunction
    SelfManagedEventSource:
      Endpoints:
        KafkaBootstrapServers:
          - broker1.example.com:9092
          - broker2.example.com:9092
    Topics:
      - my-queue-topic
    BatchSize: 100
    SelfManagedKafkaEventSourceConfig:
      ConsumptionMode: Queue&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Queue mode is also configurable through the AWS SDKs, AWS Serverless Application Model (AWS SAM), and AWS Cloud Development Kit (AWS CDK). For the complete setup walkthrough, see the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-kafka.html" target="_blank" rel="noopener"&gt;AWS Lambda Developer Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;h3 id="scaling-with-on-demand-mode"&gt;Scaling with on-demand mode&lt;/h3&gt; 
&lt;p&gt;Queue mode ESMs use &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/kafka-scaling-modes.html#kafka-default-mode" target="_blank" rel="noopener"&gt;on-demand mode&lt;/a&gt; for scaling by default. Lambda evaluates share group consumer lag at one-minute intervals and adds or removes event pollers as needed, completing scaling actions within three minutes. On-demand mode scales to five event pollers per ESM, each supporting up to 1 MB/s. It reaches its ceiling at either 5 MB/s aggregate throughput or 50 concurrent invocations, whichever comes first. This suits lower-concurrency workloads and development environments.&lt;/p&gt; 
&lt;h3 id="scaling-with-provisioned-mode"&gt;Scaling with provisioned mode&lt;/h3&gt; 
&lt;p&gt;For workloads with strict latency requirements or spiky traffic, &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/kafka-scaling-modes.html" target="_blank" rel="noopener"&gt;provisioned mode&lt;/a&gt; for scaling gives you direct control over the event pollers dedicated to your ESM. Set &lt;code&gt;MinimumPollers&lt;/code&gt; from 1 –200 and &lt;code&gt;MaximumPollers&lt;/code&gt; from 1 to 2,000. However, the broker’s &lt;code&gt;group.share.max.size&lt;/code&gt; setting caps how many members can join a share group, and Kafka 4.2 limits this value to 1,000. Set &lt;code&gt;MaximumPollers&lt;/code&gt; to 1,000 or below unless your broker supports a higher limit. Each provisioned event poller supports up to 5 MB/s.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda create-event-source-mapping
--function-name my-function
--self-managed-event-source '{"Endpoints":{"KAFKA_BOOTSTRAP_SERVERS":["broker1.example.com:9092","broker2.example.com:9092"]}}'
--topics my-queue-topic
--batch-size 100
--self-managed-kafka-event-source-config '{"ConsumptionMode": "Queue"}'
--provisioned-poller-config '{"MinimumPollers": 5, "MaximumPollers": 100}'
--source-access-configurations '[{"Type":"VPC_SUBNET","URI":"subnet-0123456789abcdef0"},{"Type":"VPC_SUBNET","URI":"subnet-0123456789abcdef1"},{"Type":"VPC_SECURITY_GROUP","URI":"sg-0123456789abcdef0"}]'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;To size &lt;code&gt;MinimumPollers&lt;/code&gt;, divide your baseline ingestion rate by 5 MB/s. If your workload is concurrency-bound, divide your target concurrent invocations by 10 instead. A workload needing 300 concurrent invocations requires at least 30 pollers. Setting &lt;code&gt;MinimumPollers&lt;/code&gt; equal to &lt;code&gt;MaximumPollers&lt;/code&gt; pins capacity and disables autoscaling. For detailed sizing guidance, see &lt;a href="https://aws.amazon.com/blogs/compute/introducing-provisioned-mode-for-kafka-event-source-mappings-with-aws-lambda/" target="_blank" rel="noopener"&gt;Introducing provisioned mode for Kafka event source mappings with AWS Lambda&lt;/a&gt; on the AWS Compute Blog.&lt;/p&gt; 
&lt;p&gt;Low-latency processing, schema registry filtering for Avro and Protobuf, and ESM grouping are available only in provisioned mode. Provisioned mode also removes the requirement to configure AWS PrivateLink VPC endpoints, so you are not charged for those endpoints. To switch an ESM to on-demand scaling, pass an empty configuration:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws lambda update-event-source-mapping \
--uuid a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 \
--provisioned-poller-config '{}'&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="cost-optimization-with-provisioned-mode"&gt;Cost optimization with provisioned mode&lt;/h3&gt; 
&lt;p&gt;In provisioned mode, ESMs in the same VPC can share Event Poller Unit (EPU) capacity through a common &lt;code&gt;PollerGroupName&lt;/code&gt;, letting low-throughput ESMs pack onto shared EPUs instead of each holding dedicated capacity. For details, see &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/kafka-scaling-modes.html#kafka-cost-optimization" target="_blank" rel="noopener"&gt;Cost optimization for provisioned mode&lt;/a&gt;. A poller group supports up to 100 ESMs and 2,000 aggregate maximum pollers.&lt;/p&gt; 
&lt;p&gt;Queue mode ESMs share EPUs only with other Queue mode ESMs. The two modes autoscale on different signals, and isolation keeps a new Queue mode ESM from destabilizing existing ordered consumers. Use a unique &lt;code&gt;PollerGroupName&lt;/code&gt; for your Queue mode ESMs. If you reuse a &lt;code&gt;PollerGroupName&lt;/code&gt; across modes, &lt;code&gt;CreateEventSourceMapping&lt;/code&gt; returns a validation error.&lt;/p&gt; 
&lt;h3 id="handling-failures"&gt;Handling failures&lt;/h3&gt; 
&lt;p&gt;&lt;code&gt;MaximumRetryAttempts&lt;/code&gt; accepts values from 0 to 10,000 and defaults to -1, which retries indefinitely. &lt;code&gt;BisectBatchOnFunctionError&lt;/code&gt; splits a batch in half when the function returns an error, isolating a poison-pill record from an otherwise healthy batch. To capture records that exhaust their retries, configure an &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/kafka-on-failure.html" target="_blank" rel="noopener"&gt;on-failure destination&lt;/a&gt;: a Kafka topic, Amazon Simple Queue Service (Amazon SQS), or Amazon Simple Notification Service (Amazon SNS). &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/esm-logging.html" target="_blank" rel="noopener"&gt;ESM logging&lt;/a&gt; to Amazon CloudWatch Logs is available for diagnostics.&lt;/p&gt; 
&lt;h2 id="key-considerations-for-queue-mode"&gt;Key considerations for Queue mode&lt;/h2&gt; 
&lt;p&gt;Keep the following in mind when configuring your event source mapping for Queue mode.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Make your function idempoten –&lt;/strong&gt;&amp;nbsp;Lambda event source mappings process each record at least once, and duplicate processing can occur. See &lt;a href="https://repost.aws/knowledge-center/lambda-function-idempotent" target="_blank" rel="noopener"&gt;How do I make my Lambda function idempotent&lt;/a&gt; in the AWS Knowledge Center.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;No ordering guarantees –&lt;/strong&gt;&amp;nbsp;Records can arrive out of order, including records from the same partition.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Batching window is not supported –&lt;/strong&gt;&amp;nbsp;&lt;code&gt;MaximumBatchingWindowInSeconds&lt;/code&gt; returns a validation error. The Kafka Share Consumer requires every record in a batch to be acknowledged before fetching new records, which is incompatible with a time-based window.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Starting position is not supported –&lt;/strong&gt;&amp;nbsp;&lt;code&gt;StartingPosition&lt;/code&gt; and &lt;code&gt;StartingPositionTimestamp&lt;/code&gt; can’t be used. Queue mode reads from the share group’s committed position. To control where a new share group begins reading, configure &lt;a href="https://kafka.apache.org/42/configuration/group-configs/#groupconfigs_share.auto.offset.reset" target="_blank" rel="noopener"&gt;share.auto.offset.reset&lt;/a&gt; on the broker.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Event filtering supports up to five filter patterns&lt;/strong&gt; per event source mapping.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="pricing-and-availability"&gt;Pricing and availability&lt;/h2&gt; 
&lt;p&gt;Queue consumption mode is available in all AWS Regions where Lambda event source mappings for self-managed Apache Kafka is supported. On-demand mode carries no charge beyond standard Lambda invocation charges. Provisioned mode is billed on EPU usage. For details, see &lt;a href="https://aws.amazon.com/lambda/pricing/" target="_blank" rel="noopener"&gt;AWS Lambda pricing&lt;/a&gt;.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;Queue consumption mode brings queue-style processing to Apache Kafka topics without additional infrastructure and without changes to your producers, topic configuration, or function code. By replacing exclusive partition assignment with share groups, it removes the partition count as a ceiling on parallelism and eliminates head-of-line blocking for workloads built on independent records.&lt;/p&gt; 
&lt;p&gt;To get started, create an event source mapping with &lt;code&gt;ConsumptionMode&lt;/code&gt; set to Queue on a self-managed Apache Kafka 4.2 or later cluster. For configuration details, see &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/with-kafka.html" target="_blank" rel="noopener"&gt;Polling Kafka queue topics&lt;/a&gt; in the AWS Lambda Developer Guide.&lt;/p&gt; 
&lt;p&gt;For more serverless learning resources, visit &lt;a href="https://serverlessland.com/" target="_blank" rel="noopener"&gt;Serverless Land&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;p style="clear: both"&gt; &lt;/p&gt;
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/26/ComputeBlog-2751-1.jpg" alt="Vaibhav Jain" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Vaibhav Jain&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Vaibhav is a Senior Delivery Consultant at Amazon Web Services, where he leads technical delivery for complex data platform and application modernization engagements. He has over 20 years of experience in application development, including 15 years building large-scale distributed systems before joining AWS.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/26/ComputeBlog-2751-2.jpg" alt="Hardith Murari" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Hardith Murari&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Hardith is a Delivery Consultant at Amazon Web Services, focused on application development, modernization, and event-driven architectures. He is driven by a deep interest in cloud infrastructure, distributed systems, and developer tooling, always seeking to improve reliability, scalability, and the overall developer experience on AWS.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/26/ComputeBlog-2751-3.jpg" alt="Nihar Sheth" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Nihar Sheth&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Nihar is a Principal Product Manager for AWS Lambda at Amazon Web Services, where he leads product strategy for serverless compute and event-driven integrations. He is passionate about building capabilities that make it easier to create event-driven, highly scalable applications with a focus on developer experience, performance, and operational simplicity.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Unlocking full-stack observability for AWS Outposts</title>
		<link>https://aws.amazon.com/blogs/compute/unlocking-full-stack-observability-for-aws-outposts/</link>
		
		<dc:creator><![CDATA[Aishwariya Khiani]]></dc:creator>
		<pubDate>Thu, 29 Oct 2026 18:23:18 +0000</pubDate>
				<category><![CDATA[AWS Outposts]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">2255292e50734842343236fd56776a061584b037</guid>

					<description>Learn how to build end-to-end observability for AWS Outposts across four dimensions: network, storage, compute, and containers. This post uses AWS Systems Manager, Amazon CloudWatch, and Amazon EventBridge for unified visibility and automated incident response across hybrid infrastructure spanning your data center and an AWS Region.</description>
										<content:encoded>&lt;p&gt;Your team just deployed &lt;a href="https://aws.amazon.com/outposts/" target="_blank" rel="noopener"&gt;AWS Outposts&lt;/a&gt; to run latency-sensitive workloads on-premises, and now you need to monitor infrastructure that spans both your data center and an AWS Region. Some services run locally on the Outposts, and others depend on Regional endpoints. A network blip between the two can cause silent failures that traditional monitoring tools miss entirely.&lt;/p&gt; 
&lt;p&gt;AWS Outposts extends native AWS services to on-premises environments, but this hybrid topology introduces monitoring challenges that don’t exist in pure-cloud or pure-on-premises setups. Control planes are distributed, critical operations depend on AWS Region connectivity, and fixed, finite capacity requires proactive capacity planning.&lt;/p&gt; 
&lt;p&gt;In this post, you will learn how to build end-to-end observability for Outposts using &lt;a href="https://aws.amazon.com/systems-manager/" target="_blank" rel="noopener"&gt;AWS Systems Manager&lt;/a&gt;, &lt;a href="https://aws.amazon.com/cloudwatch/" target="_blank" rel="noopener"&gt;Amazon CloudWatch&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/eventbridge/" target="_blank" rel="noopener"&gt;Amazon EventBridge&lt;/a&gt;, covering four monitoring dimensions:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Network – Connectivity status, BGP sessions, and Regional service dependency tracking&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;For dependency tracking, watch each Regional service’s own CloudWatch metrics together with the service-link ConnectedStatus: that pairing tells a dependency failure apart from a connectivity drop. For example, AWS Directory Service (DirectoryReachability, AuthenticationFailures), Amazon Relational Database Service (Amazon RDS) (ReplicaLag, DatabaseConnections), and so on.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Storage&lt;/strong&gt; – &lt;a href="https://aws.amazon.com/s3/" target="_blank" rel="noopener"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt; on Outposts capacity, Amazon Elastic Block Store (Amazon EBS) volume utilization, and replication health.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Compute&lt;/strong&gt; – Instance-level metrics, micro-architectural performance, and enhanced networking.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Containers&lt;/strong&gt; – &lt;a href="https://aws.amazon.com/eks/" target="_blank" rel="noopener"&gt;Amazon Elastic Kubernetes Service (Amazon EKS)&lt;/a&gt; on Outposts with Prometheus-based Kubernetes monitoring.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;By the end, you will have a monitoring architecture that gives you unified visibility across your hybrid environment and catches issues before your users do.&lt;/p&gt; 
&lt;h2 id="building-a-monitoring-foundation-with-aws-systems-manager"&gt;Building a monitoring foundation with AWS Systems Manager&lt;/h2&gt; 
&lt;p&gt;The following sections detail how to configure each component of the Systems Manager foundation for your Outposts environment.&lt;/p&gt; 
&lt;h3 id="centralized-management-architecture"&gt;Centralized management architecture&lt;/h3&gt; 
&lt;p&gt;Systems Manager provides the foundation for Outposts monitoring with centralized management across hybrid environments. Configure it to span your cloud and on-premises infrastructure so you get unified visibility, automated operations, and consistent policy enforcement across your distributed AWS resources.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;SSM Agent deployment&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;The Systems Manager agent (SSM Agent) is the basis for monitoring. Use the following commands to install the SSM Agent on your Outpost servers.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;# OS-agnostic SSM Agent installation via user data
# For Amazon Linux/RHEL/CentOS
sudo yum update -y
sudo yum install -y amazon-ssm-agent
sudo systemctl enable amazon-ssm-agent
sudo systemctl start amazon-ssm-agent

# For Ubuntu/Debian
sudo apt-get update -y
sudo apt-get install -y amazon-ssm-agent
sudo systemctl enable amazon-ssm-agent
sudo systemctl start amazon-ssm-agent

# For Windows (PowerShell)
Invoke-WebRequest -Uri "https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/windows_amd64/AmazonSSMAgentSetup.exe" -OutFile "AmazonSSMAgentSetup.exe"
Start-Process -FilePath "AmazonSSMAgentSetup.exe" -ArgumentList "/quiet" -Wait&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;OpsCenter integration&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;Systems Manager OpsCenter provides incident management capabilities that extend beyond basic alerting:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Automated OpsItem creation&lt;/strong&gt;: Configure Amazon EventBridge to automatically create operational work items when specific conditions are met.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Runbook integration&lt;/strong&gt;: Link automated remediation runbooks directly to OpsItems for immediate response.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Cross-service correlation&lt;/strong&gt;: Aggregate related issues across multiple AWS services into single operational views.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Historical analysis&lt;/strong&gt;: Use OpsCenter’s data retention for trend analysis and continuous improvement.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Patch management strategy&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;Implement a patch management approach that addresses the unique requirements of Outposts:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
  "PatchGroups": [
    {
      "Name": "OutpostsCriticalSystems",
      "MaintenanceWindow": "Sunday 02:00-04:00 UTC",
      "PatchBaseline": "Custom-Security-Critical"
    },
    {
      "Name": "OutpostsApplicationServers",
      "MaintenanceWindow": "Sunday 04:00-06:00 UTC",
      "PatchBaseline": "Custom-Application-Stable"
    }
  ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Systems Manager Patch Manager requires the SSM Agent to communicate with Regional endpoints through the service link. If the service link is degraded, patching operations will fail.&lt;/p&gt; 
&lt;h3 id="personal-health-dashboard-integration"&gt;Personal Health Dashboard integration&lt;/h3&gt; 
&lt;p&gt;The integration between AWS Personal Health Dashboard (PHD) and OpsCenter creates a proactive monitoring workflow. When an Outposts health event occurs, this rule automatically creates an OpsItem in Systems Manager, giving your operations team a single view for triage.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Automated event processing&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;Configure Amazon EventBridge rules to automatically process PHD events:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
  "Rules": [
    {
      "Name": "OutpostsPHDIntegration",
      "EventPattern": {
        "source": ["aws.health"],
        "detail-type": ["AWS Health Event"],
        "detail": {
          "service": ["OUTPOSTS"],
          "eventTypeCategory": ["issue", "scheduledChange"]
        }
      },
      "Targets": [
        {
          "Id": "CreateOpsItem",
          "Arn": "arn:aws:ssm:region:account:opsitem",
          "RoleArn": "arn:aws:iam::account:role/EventBridge-OpsCenter-Role"
        }
      ]
    }
  ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="monitoring-dimensions"&gt;Monitoring dimensions&lt;/h2&gt; 
&lt;p&gt;This section covers the four key monitoring dimensions for Outposts, with specific metrics, configurations, and alerting strategies for each.&lt;/p&gt; 
&lt;h3 id="network-monitoring-and-notification"&gt;1. Network monitoring and notification&lt;/h3&gt; 
&lt;p&gt;Network monitoring for Outposts requires approaches that account for the hybrid nature of the deployment:&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Multi-layer connectivity monitoring&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;Implement monitoring across multiple network layers:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Physical layer&lt;/strong&gt;: Monitor fiber-optic connections, network equipment health, and environmental factors. 
  &lt;ul&gt; 
   &lt;li&gt;&lt;strong&gt;ConnectedStatus&lt;/strong&gt;.&lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-1.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-1.jpg" alt="CloudWatch graph of the ConnectedStatus metric for an Outposts service link" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 1: ConnectedStatus metric for the Outposts service link&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Network layer&lt;/strong&gt;: Track routing, Border Gateway Protocol (BGP) sessions, and inter-rack connectivity. 
  &lt;ul&gt; 
   &lt;li&gt;&lt;strong&gt;VIF metrics&lt;/strong&gt;. 
    &lt;ul&gt; 
     &lt;li&gt;VifBgpSessionState.&lt;/li&gt; 
    &lt;/ul&gt; &lt;/li&gt; 
  &lt;/ul&gt; &lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-2.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-2.jpg" alt="CloudWatch graph of the VifBgpSessionState metric for an Outposts virtual interface" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 2: VifBgpSessionState metric for the Outposts virtual interface&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;VifConnectionStatus.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-3.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-3.jpg" alt="CloudWatch graph of the VifConnectionStatus metric for an Outposts virtual interface" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 3: VifConnectionStatus metric for the Outposts virtual interface&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;IfTrafficIn.&lt;/li&gt; 
 &lt;li&gt;IfTrafficOut.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-4.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-4.jpg" alt="CloudWatch graphs of the IfTrafficIn and IfTrafficOut metrics for Outposts network traffic" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 4: IfTrafficIn and IfTrafficOut metrics for Outposts network traffic&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;CapacityExceptions&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-5.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-5.jpg" alt="CloudWatch graph of the CapacityExceptions metric for an Outposts link" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 5: CapacityExceptions metric for the Outposts link&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;LagStatus:&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-6.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-6.png" alt="CloudWatch graph of the LagStatus metric for an Outposts link aggregation group" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 6: LagStatus metric for the Outposts link aggregation group&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Regional service dependency mapping&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;Create detailed dependency maps for critical Regional services:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Amazon Elastic File System (Amazon EFS)&lt;/strong&gt;: Monitor mount target availability and performance across Availability Zones.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;AWS Directory Service&lt;/strong&gt;: Track authentication latency and success rates.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Amazon RDS&lt;/strong&gt;: Monitor cross-Region replication lag and connection pooling.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;AWS Lambda&lt;/strong&gt;: Track cold start times and execution duration for Region-dependent functions.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="storage-monitoring-and-optimization"&gt;2. Storage monitoring and optimization&lt;/h3&gt; 
&lt;p&gt;Outposts provides CloudWatch metrics for both Amazon S3 and Amazon EBS storage resources. Monitor these metrics to track capacity utilization and plan for scaling.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;S3 metrics&lt;/strong&gt;:&lt;/p&gt; 
&lt;p&gt;The &lt;code&gt;S3Outposts&lt;/code&gt; namespace includes the following metrics for Amazon S3 on Outposts buckets. You can monitor the total number of S3 on Outposts bytes provisioned, the total available bytes for objects, and the total size of all objects for a given bucket. Bucket or account-related metrics exist for all direct S3 usage.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;OutpostTotalBytes&lt;/strong&gt;: The total provisioned capacity in bytes for an Outpost.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-7.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-7.png" alt="CloudWatch graph of the OutpostTotalBytes metric for S3 on Outposts provisioned capacity" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 7: OutpostTotalBytes metric for S3 on Outposts provisioned capacity&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;OutpostFreeBytes:&lt;/strong&gt; The count of available bytes on an Outpost to store customer data. &lt;strong&gt;BucketUsedBytes:&lt;/strong&gt; The total size of all objects for the given bucket.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-8.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-8.jpg" alt="CloudWatch graph of the OutpostFreeBytes metric for available S3 on Outposts capacity" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 8: OutpostFreeBytes metric for available S3 on Outposts capacity&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;Other key metrics to monitor include the following:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;AccountUsedBytes:&lt;/strong&gt; The total size of all objects for the specified Outposts account.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;BytesPendingReplication:&lt;/strong&gt; The total number of bytes of objects that are pending replication for a given replication rule. For more information about how to enable replication metrics, see &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/s3-outposts/replication-between-outposts.html" target="_blank" rel="noopener"&gt;Creating replication rules between Outposts&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;OperationsPendingReplication:&lt;/strong&gt; The total number of operations that are pending replication for a given replication rule.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Amazon EBS performance deep dive&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;The following Amazon EBS metrics are available for Outposts volumes:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;EBSVolumeTypeCapacityUtilization:&lt;/strong&gt; The percentage of Amazon EBS volume type capacity in use.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-9.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-9.jpg" alt="CloudWatch graph of the EBSVolumeTypeCapacityUtilization metric for Outposts volumes" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 9: EBSVolumeTypeCapacityUtilization metric for Outposts Amazon EBS volumes&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;EBSVolumeTypeCapacityAvailability:&lt;/strong&gt; The percentage of Amazon EBS volume type capacity available.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-10.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-10.jpg" alt="CloudWatch graph of the EBSVolumeTypeCapacityAvailability metric for Outposts volumes" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 10: EBSVolumeTypeCapacityAvailability metric for Outposts Amazon EBS volumes&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;EBSVolumeTypeCapacityUtilizationGB:&lt;/strong&gt; The number of gigabytes in use for the Amazon EBS volume type.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-11.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-11.png" alt="CloudWatch graph of the EBSVolumeTypeCapacityUtilizationGB metric for Outposts volumes" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 11: EBSVolumeTypeCapacityUtilizationGB metric for Outposts Amazon EBS volumes&lt;/p&gt;
&lt;/div&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;EBSVolumeTypeCapacityAvailabilityGB:&lt;/strong&gt; The number of gigabytes of available capacity for the Amazon EBS volume type.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-12.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-12.png" alt="CloudWatch graph of the EBSVolumeTypeCapacityAvailabilityGB metric for Outposts volumes" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 12: EBSVolumeTypeCapacityAvailabilityGB metric for Outposts Amazon EBS volumes&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Second-generation AWS Outposts racks support both gp2 and gp3 Amazon EBS volume types, whereas first-generation racks support gp2 only.&lt;/p&gt; 
&lt;h3 id="compute-and-capacity-monitoring"&gt;3. Compute and capacity monitoring&lt;/h3&gt; 
&lt;p&gt;Outposts have a fixed capacity that doesn’t auto scale, so compute and capacity metrics are essential for planning. The following instance and capacity metrics are published to the &lt;code&gt;AWS/Outposts&lt;/code&gt; namespace.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Instance metrics&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;UsedInstanceType_Count&lt;/strong&gt;: The number of instance types that are currently in use, including any instance types used by managed services such as &lt;a href="https://aws.amazon.com/rds/" target="_blank" rel="noopener"&gt;Amazon RDS&lt;/a&gt; or &lt;a href="https://aws.amazon.com/elasticloadbalancing/" target="_blank" rel="noopener"&gt;Application Load Balancer&lt;/a&gt;. This metric doesn’t include capacity for any Dedicated Hosts configured on the Outpost.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-13.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-13.jpg" alt="CloudWatch graph of the UsedInstanceType_Count metric for Outposts instance usage" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 13: UsedInstanceType_Count metric for Outposts instance usage&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;InstanceTypeCapacityUtilization:&lt;/strong&gt; The percentage of instance capacity in use. This metric does not include capacity for any Dedicated Hosts configured on the Outpost.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-14.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-14.jpg" alt="CloudWatch graph of the InstanceTypeCapacityUtilization metric for Outposts instances" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 14: InstanceTypeCapacityUtilization metric for Outposts instances&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;InstanceTypeCapacityAvailability:&lt;/strong&gt; The percentage of instance capacity available. This metric doesn’t include capacity for any Dedicated Hosts configured on the Outpost.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-15.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-15.jpg" alt="CloudWatch graph of the InstanceTypeCapacityAvailability metric for Outposts instances" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 15: InstanceTypeCapacityAvailability metric for Outposts instances&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;InstanceFamilyCapacityAvailability:&lt;/strong&gt; The percentage of instance capacity available. This metric does not include capacity for any Dedicated Hosts configured on the Outpost.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-16.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-16.png" alt="CloudWatch graph of the InstanceFamilyCapacityAvailability metric for Outposts instances" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 16: InstanceFamilyCapacityAvailability metric for Outposts instances&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;InstanceFamilyCapacityUtilization:&lt;/strong&gt; The percentage of instance capacity in use. This metric doesn’t include capacity for any Dedicated Hosts configured on the Outpost.&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-17.png" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-17.png" alt="CloudWatch graph of the InstanceFamilyCapacityUtilization metric for Outposts instances" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 17: InstanceFamilyCapacityUtilization metric for Outposts instances&lt;/p&gt;
&lt;/div&gt; 
&lt;h2 id="monitoring-eks-containers-on-aws-outposts-with-amazon-cloudwatch"&gt;Monitoring EKS containers on AWS Outposts with Amazon CloudWatch&lt;/h2&gt; 
&lt;p&gt;AWS Outposts extends AWS infrastructure to your on-premises environment. When running containerized workloads using Amazon EKS (extended clusters) on Outposts, monitoring is critical because unlike the Region, Outposts has fixed capacity that doesn’t auto-scale. Without proper monitoring, pods can fail to schedule, workloads can get OOMKilled, and disk pressure can cause evictions. All of this happens without warning.&lt;/p&gt; 
&lt;p&gt;This section walks through setting up CloudWatch Container Insights for EKS on Outposts, the key metrics to track, and how to build a unified monitoring dashboard.&lt;/p&gt; 
&lt;h3 id="prerequisites"&gt;Prerequisites&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;An AWS Outposts rack deployed and connected to your parent Region.&lt;/li&gt; 
 &lt;li&gt;An EKS cluster with worker nodes running on the Outpost.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;kubectl&lt;/code&gt; configured to access your cluster.&lt;/li&gt; 
 &lt;li&gt;AWS Command Line Interface (AWS CLI) installed and configured.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="step-1-launch-self-managed-worker-nodes-with-amazon-linux-2023-al2023-and-nodeadm"&gt;Step 1: Launch self-managed worker nodes with Amazon Linux 2023 (AL2023) and nodeadm&lt;/h3&gt; 
&lt;p&gt;Outpost subnets don’t support EKS managed node groups, so worker nodes come up as a self-managed node group launched from an EC2 launch template.&lt;/p&gt; 
&lt;p&gt;The AMI must be AL2023. Amazon EKS stopped publishing AL2 AMIs on November 26, 2025, and those images no longer receive security patches or bug fixes, as noted in the &lt;a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-ami-deprecation-faqs.html" target="_blank" rel="noopener"&gt;Amazon EKS AMI deprecation FAQs&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;AL2023 also changes how a node initializes. It uses &lt;code&gt;nodeadm&lt;/code&gt; rather than the AL2 &lt;code&gt;bootstrap.sh&lt;/code&gt; script, so the user data becomes a YAML &lt;code&gt;NodeConfig&lt;/code&gt; document instead of a shell script. AL2023 expects the cluster endpoint, certificate authority, and service CIDR to be passed in explicitly where AL2 discovered them at boot. Missing them is a common reason nodes launch but don’t join the cluster.&lt;/p&gt; 
&lt;p&gt;&lt;code&gt;aws eks describe-cluster&lt;/code&gt; returns all three:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-yaml"&gt;apiVersion: node.eks.aws/v1alpha1
kind: NodeConfig
spec:
  cluster:
    name: &amp;lt;cluster-name&amp;gt;
    apiServerEndpoint: &amp;lt;from: aws eks describe-cluster&amp;gt;
    certificateAuthority: &amp;lt;from: aws eks describe-cluster&amp;gt;
    cidr: &amp;lt;service CIDR from: aws eks describe-cluster&amp;gt;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h3 id="step-2-install-the-cloudwatch-observability-add-on"&gt;Step 2: Install the CloudWatch Observability add-on&lt;/h3&gt; 
&lt;p&gt;On an extended cluster, use the CloudWatch Observability EKS add-on to enable Container Insights. The add-on deploys the CloudWatch agent and Fluent Bit as DaemonSets on your Outpost worker nodes, and it collects container, pod, node, and cluster-level metrics automatically.&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;aws eks create-addon \
  --cluster-name your-cluster-name \
  --addon-name amazon-cloudwatch-observability&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You can also do this from the EKS Console under your cluster’s Add-ons tab.&lt;/p&gt; 
&lt;h3 id="step-3-verify-the-agent-is-running"&gt;Step 3: Verify the agent is running&lt;/h3&gt; 
&lt;p&gt;Confirm that the CloudWatch agent pods are running on each node:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;kubectl get pods -n amazon-cloudwatch&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Expected output:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-text"&gt;NAME                                  READY   STATUS    RESTARTS   AGE
cloudwatch-agent-xxxxx                1/1     Running   0          2m
cloudwatch-agent-yyyyy                1/1     Running   0          2m
fluent-bit-zzzzz                      1/1     Running   0          2m&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;You should see one cloudwatch-agent pod per worker node.&lt;/p&gt; 
&lt;h3 id="step-4-verify-metrics-in-cloudwatch"&gt;Step 4: Verify metrics in CloudWatch&lt;/h3&gt; 
&lt;p&gt;After 5–10 minutes, metrics start flowing into CloudWatch.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Open the CloudWatch Console.&lt;/li&gt; 
 &lt;li&gt;Navigate to &lt;strong&gt;Metrics&lt;/strong&gt; → &lt;strong&gt;All metrics&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Look for the &lt;code&gt;ContainerInsights&lt;/code&gt; namespace.&lt;/li&gt; 
 &lt;li&gt;You will see metrics grouped by &lt;strong&gt;Cluster&lt;/strong&gt;, &lt;strong&gt;Node&lt;/strong&gt;, &lt;strong&gt;Pod&lt;/strong&gt;, &lt;strong&gt;Service&lt;/strong&gt;, and &lt;strong&gt;Namespace&lt;/strong&gt;.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;h3 id="key-metrics-for-eks-containers-on-outposts"&gt;Key metrics for EKS containers on Outposts&lt;/h3&gt; 
&lt;p&gt;Here are the metrics that matter most, organized by level.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Cluster level&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Metric&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Unit&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;cluster_node_count&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Total worker nodes in the cluster&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;cluster_failed_node_count&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Nodes in a failed state&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;strong&gt;Example: cluster_node_count&lt;/strong&gt;&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-18.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-18.jpg" alt="CloudWatch Container Insights graph of the cluster_node_count metric for an EKS cluster" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 18: cluster_node_count metric in CloudWatch Container Insights&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Node level&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Metric&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Unit&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_cpu_utilization&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;% CPU used on each node&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_cpu_reserved_capacity&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;% CPU reserved for system components (kubelet, kube-proxy)&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;3&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_memory_utilization&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;% memory used on each node&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;5&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_filesystem_utilization&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;% disk used on each node&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;6&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_network_total_bytes&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Network throughput (rx + tx)&lt;/td&gt; 
   &lt;td&gt;Bytes/sec&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;7&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_number_of_running_pods&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Pod count per node&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;8&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;node_number_of_running_containers&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Container count per node&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;strong&gt;Example:&lt;/strong&gt;&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-19.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-19.jpg" alt="CloudWatch Container Insights graph of node-level metrics for EKS worker nodes on Outposts" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 19: Node-level Container Insights metrics for EKS worker nodes&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Pod level&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Metric&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Unit&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_cpu_utilization&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;% CPU used by pods&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_cpu_utilization_over_pod_limit&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;CPU usage relative to pod limit&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;3&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_memory_utilization&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;% memory used by pods&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;4&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_memory_utilization_over_pod_limit&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Memory usage relative to pod limit&lt;/td&gt; 
   &lt;td&gt;Percent&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;5&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_network_rx_bytes&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Bytes received per second&lt;/td&gt; 
   &lt;td&gt;Bytes/sec&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;6&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_network_tx_bytes&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Bytes transmitted per second&lt;/td&gt; 
   &lt;td&gt;Bytes/sec&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;7&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;pod_number_of_container_restarts&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Container restart count (stability indicator)&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;&lt;strong&gt;Example:&lt;/strong&gt;&lt;/p&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-20.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-20.jpg" alt="CloudWatch Container Insights graph of pod-level metrics for EKS workloads on Outposts" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 20: Pod-level Container Insights metrics for EKS workloads&lt;/p&gt;
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Service level&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Metric&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Unit&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;1&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;service_number_of_running_pods&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Running pods per service&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;2&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;namespace_number_of_running_pods&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Running pods per namespace&lt;/td&gt; 
   &lt;td&gt;Count&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;div style="width: 810px" class="wp-caption alignnone"&gt;
 &lt;a href="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-21.jpg" target="_blank" rel="noopener"&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-21.jpg" alt="CloudWatch Container Insights graph of service-level running pod counts for EKS on Outposts" width="800"&gt;&lt;/a&gt;
 &lt;p class="wp-caption-text"&gt;Figure 21: Service-level Container Insights metrics for EKS on Outposts&lt;/p&gt;
&lt;/div&gt; 
&lt;h3 id="step-5-build-a-unified-dashboard"&gt;Step 5: Build a unified dashboard&lt;/h3&gt; 
&lt;p&gt;Bring everything together in a single CloudWatch dashboard.&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;Go to CloudWatch Console → &lt;strong&gt;Dashboards&lt;/strong&gt; → &lt;strong&gt;Create dashboard&lt;/strong&gt;.&lt;/li&gt; 
 &lt;li&gt;Name it &lt;code&gt;Outposts-EKS-Monitoring&lt;/code&gt;&lt;/li&gt; 
 &lt;li&gt;Add widgets in this order:&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;&lt;strong&gt;Row 1 — Outposts infrastructure&lt;/strong&gt;&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;code&gt;InstanceFamilyCapacityUtilization&lt;/code&gt; (line chart)&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;EBSVolumeTypeCapacityUtilization&lt;/code&gt; (line chart)&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;UsedInstanceType_Count&lt;/code&gt; (number widget)&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Row 2 — Node health&lt;/strong&gt;&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;code&gt;node_cpu_utilization&lt;/code&gt; (line chart)&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;node_memory_utilization&lt;/code&gt; (line chart)&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;node_filesystem_utilization&lt;/code&gt; (line chart)&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Row 3 — Pod/container workloads&lt;/strong&gt;&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;code&gt;pod_cpu_utilization&lt;/code&gt; (line chart)&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;pod_memory_utilization&lt;/code&gt; (line chart)&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;pod_number_of_container_restarts&lt;/code&gt; (number widget)&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h3 id="why-this-matters-on-outposts"&gt;Why this matters on Outposts&lt;/h3&gt; 
&lt;p&gt;In the Region, if your containers need more resources, the infrastructure scales automatically. On Outposts, you have a fixed pool of compute, memory, and storage.&lt;/p&gt; 
&lt;p&gt;Without monitoring:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Pods fail to schedule when node capacity is exhausted.&lt;/li&gt; 
 &lt;li&gt;Workloads get OOMKilled without warning.&lt;/li&gt; 
 &lt;li&gt;Disk pressure causes pod evictions.&lt;/li&gt; 
 &lt;li&gt;You have no visibility into how close you are to capacity limits.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;By combining Container Insights metrics with Outposts infrastructure metrics in a single dashboard, you get a complete picture, from application-level container health down to physical infrastructure utilization. With it, you can plan capacity proactively before issues affect your workloads.&lt;/p&gt; 
&lt;h3 id="useful-references"&gt;Useful references&lt;/h3&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-on-outposts.html" target="_blank" rel="noopener"&gt;Amazon EKS on AWS Outposts documentation&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-EKS.html" target="_blank" rel="noopener"&gt;CloudWatch Container Insights metrics for EKS&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/mt/monitoring-best-practices-for-aws-outposts/" target="_blank" rel="noopener"&gt;Monitoring best practices for AWS Outposts&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/containers/deploying-containerized-application-on-aws-outposts-with-amazon-eks/" target="_blank" rel="noopener"&gt;Deploying containerized apps on Outposts with EKS&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3OutpostsCapacity.html" target="_blank" rel="noopener"&gt;Managing S3 on Outposts capacity with CloudWatch&lt;/a&gt;&lt;/li&gt; 
&lt;/ul&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;Monitoring AWS Outposts requires visibility across four dimensions that don’t exist in pure-cloud deployments: Region connectivity health, local storage capacity, compute performance on fixed hardware, and container orchestration across hybrid boundaries. The gap between standard cloud monitoring and what Outposts demands is where incidents hide.&lt;/p&gt; 
&lt;p&gt;In this post, we walked through building that visibility layer using Systems Manager as the management foundation, Amazon CloudWatch for metrics and alarms, and Amazon EventBridge for automated incident response through OpsCenter. Together, these services give you a unified monitoring architecture that spans your data center and the parent Region.&lt;/p&gt; 
&lt;h2 id="next-steps"&gt;Next steps&lt;/h2&gt; 
&lt;p&gt;To get started with the monitoring approach described in this post:&lt;/p&gt; 
&lt;ol type="1"&gt; 
 &lt;li&gt;&lt;strong&gt;Deploy the Systems Manager agent&lt;/strong&gt; to all Outpost instances and verify Region connectivity through the Fleet Manager console.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Set up CloudWatch alarms&lt;/strong&gt; for the critical Outpost metrics. Start with ConnectedStatus, OutpostFreeBytes, and CapacityExceptions before expanding to application-level metrics.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Configure the Amazon EventBridge-to-OpsCenter integration&lt;/strong&gt; shown in this post to automate incident creation for Outposts health events.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Build a CloudWatch dashboard&lt;/strong&gt; that combines network, storage, and compute metrics into a single operational view for your Outpost.&lt;/li&gt; 
&lt;/ol&gt; 
&lt;p&gt;For more information, see the following resources:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/outposts/latest/userguide/outposts-monitoring.html" target="_blank" rel="noopener"&gt;AWS Outposts monitoring best practices&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-managedinstances.html" target="_blank" rel="noopener"&gt;AWS Systems Manager hybrid activations&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/outposts/latest/userguide/outposts-cloudwatch-metrics.html" target="_blank" rel="noopener"&gt;Amazon CloudWatch metrics for Outposts&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-EKS-quickstart.html" target="_blank" rel="noopener"&gt;Container Insights for Amazon EKS&lt;/a&gt;&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p style="clear: both"&gt; &lt;/p&gt;
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the authors&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-22.jpg" alt="Aishwariya Khiani" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Aishwariya Khiani&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Aishwariya is a Technical Account Manager at Amazon Web Services with over 9 years of experience across cloud infrastructure, security, and operations. She brings deep expertise in cloud security and Generative AI, working with customers to architect secure, scalable environments and identify meaningful applications of AI that address complex business needs. Aishwariya is committed to helping organizations strengthen their cloud posture, accelerate innovation, and maximize the value of their AWS investments.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-23.jpg" alt="Arun Kumar N C" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Arun Kumar N C&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;As an AWS Technical Account Manager specializing in Cloud networking and Generative AI, Arun excels at building strategic customer relationships and providing expert guidance. He helps customers develop scalable, secure, and cost-effective cloud solutions, offering proactive support and tailored advice to optimize AWS environments and drive successful cloud adoption.&lt;/p&gt; 
 &lt;/div&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2334-24.jpg" alt="Anjali Sharma" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Anjali Sharma&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Anjali is a Senior Technical Account Manager (TAM) at AWS with more than 10 years of IT experience. Her career includes roles as a Cloud Consultant and as an Operations Engineer at AWS Managed Services. In her current role, she partners with global enterprise customers to build secure, resilient, and sustainable solutions on AWS. She is passionate about troubleshooting complex issues and raising operational excellence for her customers, turning findings into prioritized, practical remediation that teams can act on.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Observing AWS Lambda durable functions with the Durable Execution Telemetry Exporter</title>
		<link>https://aws.amazon.com/blogs/compute/observing-aws-lambda-durable-functions-with-the-durable-execution-telemetry-exporter/</link>
		
		<dc:creator><![CDATA[Pooya Paridel]]></dc:creator>
		<pubDate>Wed, 28 Oct 2026 19:36:12 +0000</pubDate>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<guid isPermaLink="false">1eb96e4908aff142fc631c6cce7725f59ea8eb07</guid>

					<description>Durable functions span many Lambda invocations, so per-invocation logs answer the wrong question. The Durable Execution Telemetry Exporter is an SDK plugin that emits one complete record per execution to any of 13 destinations with a one-line change, and a companion MCP server lets an AI agent query that data in plain language.</description>
										<content:encoded>&lt;p&gt;A durable function is an AWS Lambda function that might run for minutes, days, or even up to a year. You build these functions with the &lt;a href="https://docs.aws.amazon.com/durable-execution/" target="_blank" rel="noopener"&gt;Durable Execution SDK&lt;/a&gt;, which provides operations such as steps, waits, and parallel. A single durable execution might be spread across many Lambda invocations, with waits and retries in between. So observing a durable execution, made of many invocations, needs different tools. The question that you want answered is rarely “what did this invocation do?” It’s “how far did my durable execution get, which step failed, how many times did it retry, and how long did the whole thing take?”&lt;/p&gt; 
&lt;p&gt;After you run thousands of executions, the questions widen from one execution to all of them. Some questions are operational. Which step fails most often, and with which error? Which step causes the most retries? Did a step get slower after last week’s deployment? Other questions are about the business the workflow runs. Which customers did last night’s payment failures affect? How long does each manual approval step take? Of the orders that started, how many reached the payment step, and where did the rest stop? Answering these questions needs per execution telemetry data that includes relevant data such as status, timing, steps, and the input and output fields that you choose to emit.&lt;/p&gt; 
&lt;p&gt;Traditional Lambda observability works well for a single invocation. Lambda writes a log stream per invocation, so a durable execution that suspends four times writes to four separate log streams, interleaved with every other concurrent execution. Amazon CloudWatch metrics tell you the function’s error rate, but not which of your workflow’s steps is responsible. Distributed tracing, such as AWS X-Ray or OpenTelemetry, shows the timing of one execution. It isn’t built to answer questions across many executions, such as which step failed most often this week. For that, you need one queryable record per execution.&lt;/p&gt; 
&lt;p&gt;Today we’re introducing the &lt;a href="https://docs.aws.amazon.com/durable-execution/sdk-reference/observability/telemetry/" target="_blank" rel="noopener"&gt;Durable Execution Telemetry Exporter&lt;/a&gt;, an observability plugin for AWS Lambda durable functions. We’re also introducing the Durable Execution Telemetry MCP server, a Model Context Protocol (MCP) server that lets an AI coding agent query the telemetry data. The exporter is open source for TypeScript, Python, Java, and Go, in each language’s Durable Execution SDK repository. AWS provides the MCP server as open source in the &lt;a href="https://github.com/aws/aws-durable-execution-sdk-js/blob/main/packages/aws-durable-execution-sdk-js-telemetry-mcp/README.md" target="_blank" rel="noopener"&gt;aws-durable-execution-sdk-js&lt;/a&gt; repository.&lt;/p&gt; 
&lt;p&gt;With a one-line configuration change, you get a record of each execution, with every step, wait, callback, and invoke, including timing, retry attempts, status, and errors. The exporter delivers it to a destination you choose. There’s no custom instrumentation to write and no separate agent to run.&lt;/p&gt; 
&lt;h2 id="how-the-durable-execution-telemetry-exporter-works"&gt;How the durable execution telemetry exporter works&lt;/h2&gt; 
&lt;p&gt;The Durable Execution Telemetry Exporter is a plugin for the durable execution SDK. It runs inside your Lambda function, in the same process as your handler, and subscribes to the SDK’s instrumentation lifecycle. It doesn’t run in your request path.&lt;/p&gt; 
&lt;p&gt;On every invocation of a durable execution, the plugin builds a cumulative snapshot of that execution, rather than a delta or per-invocation view. Because the durable execution SDK replays your handler from the beginning on each resume and the SDK passes the checkpointed state to the plugin, the plugin can reconstruct the whole execution so far from any invocation. That snapshot is a single JSON document called a &lt;code&gt;DurableExecutionTelemetryRecord&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
  "recordType": "DurableExecutionTelemetry",
  "schemaVersion": "1.0",
  "executionArn": "arn:aws:lambda:us-east-1:111122223333:function:order-processor:$LATEST/durable-execution/abc123/inv456",
  "executionName": "abc123",
  "functionName": "order-processor",
  "status": "SUCCEEDED",
  "startTime": "2026-06-16T17:00:22.100Z",
  "endTime": "2026-06-16T17:00:27.514Z",
  "durationMs": 5414,
  "input": { "orderId": "order-12345", "customerId": "cust-789" },
  "output": { "orderId": "order-12345", "status": "completed", "charged": 99.99 },
  "operations": [
    { "name": "validate-order",  "type": "STEP", "status": "SUCCEEDED", "durationMs": 250 },
    { "name": "check-inventory", "type": "STEP", "status": "SUCCEEDED", "durationMs": 350 },
    { "name": "cool-down",       "type": "WAIT", "status": "SUCCEEDED", "durationMs": 5000 },
    { "name": "charge-payment",  "type": "STEP", "status": "SUCCEEDED", "durationMs": 80 }
  ]
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Each record is complete on its own. One row in a table is one durable execution, which means the questions you ask (slowest step, most-retried step, executions that failed after the payment step) become ordinary queries instead of requiring you to correlate logs across streams.&lt;/p&gt; 
&lt;h2 id="getting-started"&gt;Getting started&lt;/h2&gt; 
&lt;p&gt;Install the plugin alongside the durable execution SDK:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-bash"&gt;npm install @aws/durable-execution-sdk-js-telemetry-exporter&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Then pass it to &lt;code&gt;withDurableExecution&lt;/code&gt;:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-javascript"&gt;import { DurableContext, withDurableExecution } from "@aws/durable-execution-sdk-js";
import { durableExecutionTelemetry } from "@aws/durable-execution-sdk-js-telemetry-exporter";

const handler = async (event: OrderEvent, context: DurableContext) =&amp;gt; {
  const order = await context.step("validate-order", async () =&amp;gt;
    validateOrder(event.orderId),
  );

  const inventory = await context.step("check-inventory", async () =&amp;gt;
    reserveInventory(order),
  );

  await context.wait({ seconds: 30 });

  return await context.step("charge-payment", async () =&amp;gt;
    chargeCustomer(order, inventory),
  );
};

export const lambdaHandler = withDurableExecution(handler, {
  plugins: [durableExecutionTelemetry({})],
});&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;That is the entire integration. With no configuration, the default &lt;code&gt;LambdaLogExporter&lt;/code&gt; writes records as JSON to your function’s own CloudWatch log group. You don’t need to create any infrastructure or grant additional AWS Identity and Access Management (IAM) permissions, because your function already writes its own logs. You can query the result immediately with Amazon CloudWatch Logs Insights:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-plaintext"&gt;fields executionName, status, durationMs
| filter recordType = "DurableExecutionTelemetry" and status = "FAILED"
| sort durationMs desc&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="choosing-where-records-go"&gt;Choosing where records go&lt;/h2&gt; 
&lt;p&gt;The plugin includes 13 destination exporters so you can send records where they are useful:&lt;/p&gt; 
&lt;table border="1px" width="100%" cellpadding="10px"&gt; 
 &lt;tbody&gt; 
  &lt;tr&gt; 
   &lt;td&gt;&lt;strong&gt;Destination&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Exporter&lt;/strong&gt;&lt;/td&gt; 
   &lt;td&gt;&lt;strong&gt;Good for&lt;/strong&gt;&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Function’s own log group&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;LambdaLogExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Getting started, zero setup&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Any CloudWatch log group&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;CloudWatchLogsExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Centralizing records across functions&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon Simple Storage Service (Amazon S3)&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;S3Exporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Amazon Athena SQL, long-term retention&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon DynamoDB&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;DynamoDBExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Fast lookup by execution, live dashboards&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon Aurora&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;AuroraExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Joining workflow data with business data&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon Redshift&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;RedshiftExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Large-scale cross-function analytics&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon OpenSearch Service&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;OpenSearchExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Full-text search, dashboards&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon EventBridge&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;EventBridgeExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Alerting and remediation on failure&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon Data Firehose&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;FirehoseExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Fan-out to S3, Splunk, or third parties&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Amazon Simple Queue Service (Amazon SQS)&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;SQSExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Decoupled downstream processing&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Any OTLP endpoint&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;OTelExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Third-party observability platforms&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Any HTTPS endpoint&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;HttpExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Custom backends and webhooks&lt;/td&gt; 
  &lt;/tr&gt; 
  &lt;tr&gt; 
   &lt;td&gt;Filesystem or Amazon Elastic File System (Amazon EFS)&lt;/td&gt; 
   &lt;td&gt;&lt;code&gt;FileExporter&lt;/code&gt;&lt;/td&gt; 
   &lt;td&gt;Local development, EFS persistence&lt;/td&gt; 
  &lt;/tr&gt; 
 &lt;/tbody&gt; 
&lt;/table&gt; 
&lt;p&gt;The plugin sends records to all configured exporters in parallel. This allows you to route data to different stores based on their characteristics, such as using a fast store for real-time lookups and a less expensive, high-capacity store for long-term storage:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-javascript"&gt;import {
  durableExecutionTelemetry,
  S3Exporter,
  DynamoDBExporter,
  EventBridgeExporter,
} from "@aws/durable-execution-sdk-js-telemetry-exporter";

const telemetry = durableExecutionTelemetry({
  emitMode: "on-complete",
  samplingRate: 1.0,
  exporters: [
    new S3Exporter({ bucket: string }), // Use valid bucket name you own
    new DynamoDBExporter({ tableName: "durable-execution-telemetry-live" }),
    new EventBridgeExporter({}),
  ],
});&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;With the S3 exporter, the plugin writes records under Hive-style partitions (&lt;code&gt;year=YYYY/month=MM/day=DD/&lt;/code&gt;) that an AWS Glue crawler discovers automatically, so Athena queries work without additional modeling:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-sql"&gt;SELECT op.name, COUNT(*) AS failures, AVG(op.durationms) AS avg_ms
FROM durable_execution_telemetry
CROSS JOIN UNNEST(operations) AS t(op)
WHERE status = 'FAILED' AND year = '2026' AND month = '06'
GROUP BY op.name
ORDER BY failures DESC;&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;h2 id="controlling-frequency-and-content"&gt;Controlling frequency and content&lt;/h2&gt; 
&lt;p&gt;Three settings govern what a production deployment costs and exposes.&lt;/p&gt; 
&lt;p&gt;&lt;code&gt;emitMode&lt;/code&gt; determines when the plugin sends a record. The default, &lt;code&gt;on-complete&lt;/code&gt;, emits once when an execution reaches &lt;code&gt;SUCCEEDED&lt;/code&gt; or &lt;code&gt;FAILED&lt;/code&gt;. Use &lt;code&gt;on-failure&lt;/code&gt; for the lowest overhead when you only care about errors, or &lt;code&gt;on-change&lt;/code&gt; when you want to watch executions progress in near real time.&lt;/p&gt; 
&lt;p&gt;&lt;code&gt;samplingRate&lt;/code&gt; reduces frequency. The plugin derives the sampling decision from a hash of the execution ARN. The execution ARN is stable across replays, so the decision is deterministic: a sampled-in execution emits all of its records, and a sampled-out execution emits none. You never receive a half-recorded workflow.&lt;/p&gt; 
&lt;p&gt;&lt;code&gt;content&lt;/code&gt; controls what leaves your function. By default, the plugin includes execution input and output as-is, which is convenient in development and often unacceptable in production. Pass a transform to redact:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-javascript"&gt;const telemetry = durableExecutionTelemetry({
  samplingRate: 0.1,
  content: {
    input: (event) =&amp;gt; ({ orderId: event.orderId }),
    output: (result) =&amp;gt; ({ status: result.status }),
  },
});&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Each destination supports different payload sizes: CloudWatch Logs events at 256 KB, DynamoDB items at 400 KB. Each exporter has a &lt;code&gt;maxRecordSizeBytes&lt;/code&gt;, and when a record exceeds it the plugin truncates for one destination without affecting other destinations: operation results first, then whole operations oldest-first, then execution input and output last. The plugin never drops identity and timeline fields, and it marks a trimmed record &lt;code&gt;truncated: true&lt;/code&gt;, so a truncated record is always distinguishable from a complete one. We recommend using &lt;code&gt;content&lt;/code&gt; transforms to bound payloads deliberately rather than relying on truncation.&lt;/p&gt; 
&lt;h2 id="querying-execution-history-from-an-ai-agent"&gt;Querying execution history from an AI agent&lt;/h2&gt; 
&lt;p&gt;Answering “why did last night’s batch fail” requires knowing which data store you configured, which query dialect it uses, and what the record schema looks like. DynamoDB PartiQL, Athena’s Trino SQL, Aurora PostgreSQL, Amazon Redshift, OpenSearch, and CloudWatch Logs Insights all differ.&lt;/p&gt; 
&lt;p&gt;The Durable Execution Telemetry MCP server removes that requirement. It’s a local stdio server that exposes your configured destination to any MCP-capable agent, including Kiro, Claude Code, and Cursor. Add it with one command:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-plaintext"&gt;kiro-cli mcp add \
  --name durable-telemetry \
  --command npx \
  --args "-y,@aws/durable-execution-sdk-js-telemetry-mcp" \
  --env DURABLE_TELEMETRY_DESTINATION_TYPE=dynamodb \
  --env DURABLE_TELEMETRY_DYNAMODB_TABLE_NAME=durable-execution-telemetry-live \
  --env DURABLE_TELEMETRY_REGION=us-east-1 \
  --scope workspace&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;Configuration is environment-only and credentials come from the standard AWS SDK provider chain, so there’s no state file and no secret. The server exposes five tools:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;code&gt;test_destination&lt;/code&gt; runs read-only connectivity checks. If a required variable is unset, it names the exact variable and returns without making any AWS call.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;describe_schema&lt;/code&gt; returns the record schema, query dialect, and row cap for whichever destination is configured. Agents should call this before writing a query.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;list_executions&lt;/code&gt; filters by status, function name, and time range with no query language involved. This handles most questions.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;get_execution&lt;/code&gt; fetches one record by execution ARN.&lt;/li&gt; 
 &lt;li&gt;&lt;code&gt;query&lt;/code&gt; handles questions the filters cannot express.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;You ask a question and the agent picks the tools:&lt;/p&gt; 
&lt;blockquote&gt;
 &lt;p&gt;&lt;em&gt;Which steps in order-processor failed most often in the last 24 hours, and what was the average retry count?&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;On the SQL destinations, write each query as a &lt;code&gt;SELECT&lt;/code&gt; statement, or as a &lt;code&gt;WITH&lt;/code&gt; statement that ends in a &lt;code&gt;SELECT&lt;/code&gt;. These are the only forms the server runs. It checks a query before it makes any AWS call, so a statement that would change data never reaches your destination. On the CloudWatch Logs destinations, the Logs Insights query language has no statements that write data. So every query through the server is read-only.&lt;/p&gt; 
&lt;h2 id="best-practices-and-considerations"&gt;Best practices and considerations&lt;/h2&gt; 
&lt;p&gt;&lt;strong&gt;Choose &lt;code&gt;operationDetail&lt;/code&gt; deliberately.&lt;/strong&gt; The default, &lt;code&gt;top-level&lt;/code&gt;, records only top-level operations and produces the same set of operations no matter when a record is emitted. &lt;code&gt;full-tree&lt;/code&gt; includes children of contexts such as map items and parallel branches, but by default the durable execution backend prunes finished contexts’ children from the state passed to later invocations. To keep the full tree across a suspend and resume, also set &lt;code&gt;pluginsConfig.childOperationsDepth&lt;/code&gt; on &lt;code&gt;withDurableExecution&lt;/code&gt;. That preservation has a cost: it forces a replay pass over each preserved context on resume, so enable only the depth you need.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Choose operation names that your destination can query.&lt;/strong&gt; The plugin uses names verbatim as keys and identifiers and never sanitizes them. A &lt;code&gt;.&lt;/code&gt; in a name is a field-path separator in CloudWatch Logs Insights and OpenSearch. Letters, digits, &lt;code&gt;-&lt;/code&gt;, and &lt;code&gt;_&lt;/code&gt; are portable everywhere.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Understand what the plugin cannot see.&lt;/strong&gt; The Durable Execution Telemetry Exporter runs inside your function, so it can only emit records when your function is invoked. Terminal states that originate in the Lambda service without an invocation never reach the plugin: &lt;code&gt;STOPPED&lt;/code&gt; from a manual stop, and &lt;code&gt;TIMED_OUT&lt;/code&gt; when the execution timeout is exceeded. For complete lifecycle coverage, subscribe to Lambda durable execution lifecycle events on the default Amazon EventBridge bus and update your destination from a small handler:&lt;/p&gt; 
&lt;div class="hide-language"&gt; 
 &lt;pre&gt;&lt;code class="language-json"&gt;{
  "source": ["aws.lambda"],
  "detail-type": ["Lambda Durable Execution State Change"],
  "detail": { "status": ["STOPPED", "TIMED_OUT"] }
}&lt;/code&gt;&lt;/pre&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;strong&gt;Account for the cost of the destination.&lt;/strong&gt; The plugin adds at most one export each time it emits a record, because it sends only the latest of any updates that pile up. Each record is a complete snapshot, and the latest supersedes all earlier ones. If updates arrive faster than an exporter can handle, the plugin drops the intermediate snapshots. The charges that matter are the ones your destination incurs: CloudWatch Logs ingestion, DynamoDB writes, Aurora capacity, and so on. Combine &lt;code&gt;samplingRate&lt;/code&gt; and &lt;code&gt;emitMode&lt;/code&gt; to control them.&lt;/p&gt; 
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt; 
&lt;p&gt;The Durable Execution Telemetry Exporter gives AWS Lambda durable functions an observability model that matches how they run: one complete record per execution, sent to a destination that fits your team. The Durable Execution Telemetry MCP server lets an AI agent answer questions against that data directly.&lt;/p&gt; 
&lt;p&gt;To get started with durable functions, see the AWS Lambda Developer Guide. For the plugin’s full exporter reference, configuration options, and an AWS Cloud Development Kit (AWS CDK) stack that deploys every destination for testing, see the package &lt;a href="https://github.com/aws/aws-durable-execution-sdk-js/blob/main/packages/aws-durable-execution-sdk-js-telemetry-exporter/README.md" target="_blank" rel="noopener"&gt;README&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;p style="clear: both"&gt; &lt;/p&gt;
&lt;hr style="width: 100%"&gt; 
&lt;h2&gt;About the author&lt;/h2&gt; 
&lt;footer&gt; 
 &lt;div class="blog-author-box" style="padding-top: 2.0em"&gt; 
  &lt;div class="blog-author-image" style="margin-right: 1.0em"&gt;
   &lt;img loading="lazy" class="alignnone size-full" src="https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2026/10/27/ComputeBlog-2775-1.jpg" alt="Pooya Paridel" width="100" height="133"&gt;
  &lt;/div&gt; 
  &lt;h3 class="lb-h4"&gt;Pooya Paridel&lt;/h3&gt; 
  &lt;p style="overflow: hidden"&gt;Pooya, Senior Software Development Engineer at AWS, has over 25 years of software development experience, including more than 7 years at AWS specializing in AWS Step Functions and Lambda Durable Functions. Before shaping the serverless developer experience for Amazon Web Services, he spent years designing high-impact software across entirely different domains, including real-time financial trading engines, stock exchange platforms, Internet of Things (IoT) systems, and CRM applications for real estate.&lt;/p&gt; 
 &lt;/div&gt; 
&lt;/footer&gt;</content:encoded>
					
		
		
			</item>
	</channel>
</rss>