<?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 News Blog</title>
	<atom:link href="https://aws.amazon.com/blogs/aws/feed/" rel="self" type="application/rss+xml"/>
	<link>https://aws.amazon.com/blogs/aws/</link>
	<description>Announcements, Updates, and Launches</description>
	<lastBuildDate>Wed, 18 Nov 2026 19:39:07 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>AWS Lambda now supports GPU instances for Event Functions on Lambda Managed Instances</title>
		<link>https://aws.amazon.com/blogs/aws/aws-lambda-now-supports-gpu-instances-for-event-functions-on-lambda-managed-instances/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 19:39:07 +0000</pubDate>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Compute]]></category>
		<category><![CDATA[Serverless]]></category>
		<guid isPermaLink="false">30ec3c38ceea489c2a4f7184696062c55b87e28d</guid>

					<description>AWS Lambda now supports GPU instances (G-series) for Event Functions running on Lambda Managed Instances, enabling serverless GPU workloads like machine learning inference, media processing, and rendering. Lambda handles all infrastructure tasks, including instance lifecycle, driver management, and auto scaling, while maximizing GPU utilization across concurrent requests with standard EC2 pricing plus a management fee</description>
										<content:encoded>&lt;p&gt;GPU support is now available for EC2 G-series GPU instances for Event Functions running on &lt;a href="https://aws.amazon.com/lambda/"&gt;AWS Lambda&lt;/a&gt; &lt;a href="https://aws.amazon.com/lambda/lambda-managed-instances/"&gt;Managed Instances&lt;/a&gt; (LMI). You can now run GPU-accelerated workloads, including machine learning inference, media processing, rendering, and scientific computing, on GPU instances with serverless simplicity. GPU-accelerated functions are deployed as container (Open Container Initiative, OCI) images. You build an OCI image, point the function at it, and let Lambda handle provisioning, scaling, and event integration. There are no GPU drivers, CUDA versions, or AMIs to reconcile, and no clusters or device plugins to operate. GPU-accelerated functions run on the same Lambda Managed Instances foundation that already gives you &lt;a href="https://aws.amazon.com/ec2/"&gt;Amazon EC2&lt;/a&gt; pricing and specialized compute without managing servers.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Why customers need this&lt;/strong&gt;&lt;br&gt; Customers keep asking to run GPU workloads with the simplicity of serverless. Building on self-managed GPU infrastructure means selecting instances, installing and reconciling GPU drivers and CUDA libraries, planning capacity, writing scaling logic, and hand-building the event integrations that connect the GPU step to the rest of the application. Serverless GPU services that hide that work often sit outside your AWS environment, with no native event sources, identity, or networking.&lt;/p&gt; 
&lt;p&gt;Cost is the second problem. GPUs are expensive, and utilization is usually low because a single workload rarely saturates a GPU. A small inference task can leave most of a provisioned GPU idle while you pay for the whole thing.&lt;/p&gt; 
&lt;p&gt;This feature closes both gaps. You bring a function, and Lambda runs it on a GPU in minutes, triggered by the same AWS events as any other Lambda Event Function, billed and secured the same way. It also maximizes utilization of every GPU you pay for, by consolidating functions onto instances and keeping GPUs busy across concurrent requests.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;What you can build&lt;/strong&gt;&lt;br&gt; You can run both AI/ML inference and non-ML workloads using GPU-accelerated compute on Lambda Managed Instances. This capability is optimized for inference rather than training, and custom models rather than large foundation models already available on services like &lt;a href="https://aws.amazon.com/bedrock/"&gt;Amazon Bedrock&lt;/a&gt;. Common workloads include:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Custom model inference&lt;/strong&gt;: decision models (such as &lt;a href="https://strandsagents.com/blog/amazon-saves-millions-replacing-sonnet-with-strands-decider/"&gt;Strands Decider&lt;/a&gt;), computer vision, speech-to-text and text-to-speech, recommendation, document analysis, and small-to-mid-size language models deployed as part of an application.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Agentic and event-driven AI&lt;/strong&gt;: custom inference triggered directly by AWS events, composed with the rest of the Lambda programming model.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Media processing and transcoding&lt;/strong&gt;: video and image pipelines triggered on upload.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;3D rendering and generative media&lt;/strong&gt;: frame and asset rendering, diffusion, and text-to-video generation.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Scientific computing and financial modeling&lt;/strong&gt;: simulations, matrix computation, and risk analysis.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Part of the Lambda programming model&lt;/strong&gt;&lt;br&gt; A GPU-accelerated function is one step in a larger application, and it composes with the rest of Lambda. &lt;a href="https://aws.amazon.com/lambda/lambda-durable-functions/"&gt;Lambda durable functions&lt;/a&gt; orchestrate multi-step, long-running workflows around the GPU step, with checkpointing and automatic recovery. &lt;a href="https://aws.amazon.com/lambda/lambda-microvms/"&gt;Lambda MicroVMs&lt;/a&gt; run untrusted or model-generated code in isolated, stateful sandboxes. In an agentic workload, a MicroVM executes the tool-use logic on CPU, then calls a GPU-accelerated function running on Lambda Managed Instances for inference.&lt;/p&gt; 
&lt;p&gt;GPU-accelerated functions also support the extended function timeout on Lambda Managed Instances, up to 90 minutes for asynchronous and &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-services.html"&gt;event source mapping&lt;/a&gt; invocations, so you can run batch and other long-running GPU jobs, such as media transcoding or multi-step inference, without re-architecting. GPU-accelerated functions support container images up to 32 GB (10 GB per file), up to 32 GB of ephemeral storage, 2,048 to 32,768 MB of memory, 3 to 48 GB of accelerator memory, up to 48 concurrent requests per execution environment, and up to 15,000 vCPUs per capacity provider.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Let’s try it out&lt;/strong&gt;&lt;br&gt; To show what this looks like in practice, I deployed an open-source large language model (LLM) from Hugging Face as a Lambda function and sent it a prompt. With the vLLM base image from Lambda, I only set the Hugging Face model ID in the &lt;code&gt;MODEL_ID&lt;/code&gt; environment variable, without writing any inference code. I used Qwen/Qwen2.5-1.5B-Instruct, a small instruction-tuned model that suits in-application tasks such as summarization, classification, and extraction. The flow has four steps: create a capacity provider, build and push the container image, create a function from that image, then publish and invoke. Before you begin, request an increase to your G-series instance quota (listed as &lt;em&gt;Running On-Demand G and VT instances&lt;/em&gt;), because new accounts might start with a quota of 0. For more information, see &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-on-demand-instances.html#ec2-on-demand-instances-limits"&gt;On-Demand Instance quotas&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;First, I created a capacity provider, where I specify the GPU instance types Lambda can use and let it auto-scale. Listing several instance types lets Lambda pick the most cost-effective one that is available and fall back across generations when capacity is tight.&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;{
    "CapacityProviderName": "lmi-gpu-cp",
    "VpcConfig": {
        "SubnetIds": ["subnet-aaaa", "subnet-bbbb", "subnet-cccc"],
        "SecurityGroupIds": ["sg-aaaa"]
    },
    "PermissionsConfig": {
        "CapacityProviderOperatorRoleArn": "arn:aws:iam::111122223333:role/lmi-operator-role"
    },
    "InstanceRequirements": {
        "AllowedInstanceTypes": [
            "g5.2xlarge", "g6.2xlarge", "g6e.2xlarge"
        ]
    },
    "CapacityProviderScalingConfig": {
        "ScalingMode": "Auto",
        "MaxVCpuCount": 96
    }
}
&lt;/code&gt;&lt;/pre&gt; 
&lt;pre&gt;&lt;code&gt;aws --region us-east-2 \
  lambda create-capacity-provider \
  --cli-input-json file://cli-skeletons/create-capacity-provider_gpu.json
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The Lambda console shows the new capacity provider, lmi-gpu-cp, in the Active state. Note the VPC configuration with its subnets and security group.&lt;br&gt; &lt;img class="aligncenter size-full wp-image-106178" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/01-capacity-provider-lmi.png" alt="Lambda console showing the GPU capacity provider lmi-gpu-cp in the Active state with its VPC configuration" width="1800" height="692"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;Figure 1: The capacity provider is Active, with its VPC configuration.&lt;/p&gt; 
&lt;p&gt;Next, I built the container image. Lambda provides a curated &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances-gpu-base-images.html"&gt;vLLM base image&lt;/a&gt; that includes the vLLM inference server, PyTorch, Transformers, and the CUDA toolkit, along with a runtime interface client that supports concurrent invocations. The image serves the model for me, so I don’t write a handler or any inference server code. My entire Dockerfile is one line:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;FROM public.ecr.aws/lambda/deep-learning-containers/vllm:cuda-v1
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;After pushing the image to &lt;a href="https://aws.amazon.com/ecr/"&gt;Amazon ECR&lt;/a&gt;, I created the function. I chose the model with the &lt;code&gt;MODEL_ID&lt;/code&gt; environment variable, which accepts a Hugging Face or ModelScope repository, an &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt; location, or a local path. Lambda downloads the model, manages GPU memory, and serves requests. Qwen2.5-1.5B-Instruct is a public model, so I didn’t need a Hugging Face token. For private or gated models, or to get higher download rate limits, you can also set &lt;code&gt;HF_TOKEN&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;GPU-accelerated functions use &lt;code&gt;AcceleratorConfig&lt;/code&gt; to request accelerator memory. &lt;code&gt;AcceleratorMemorySize&lt;/code&gt; is the minimum GPU memory the function needs, and Lambda places the execution environment on the smallest available GPU that meets it, so the GPU you get can have more memory than you requested. I set &lt;code&gt;PerExecutionEnvironmentMaxConcurrency&lt;/code&gt; to 4, the default. The vLLM server batches concurrent requests on the GPU, so invocations share one copy of the model and the GPU stays busy. I also set &lt;code&gt;ExecutionEnvironmentMemoryGiBPerVCpu&lt;/code&gt; to 4, which gives the function the 16,384 MB of memory and 4 vCPUs it needs while leaving capacity on the 2xlarge instance for Lambda’s management components.&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;{
    "FunctionName": "lmi-gpu-inference",
    "PackageType": "Image",
    "Code": { "ImageUri": "111122223333.dkr.ecr.us-east-2.amazonaws.com/lmi-gpu-inference:latest" },
    "Role": "arn:aws:iam::111122223333:role/lmi-gpu-inference-execution-role",
    "Timeout": 900,
    "MemorySize": 16384,
    "EphemeralStorage": { "Size": 32768 },
    "Environment": { "Variables": { "MODEL_ID": "Qwen/Qwen2.5-1.5B-Instruct" } },
    "CapacityProviderConfig": {
        "LambdaManagedInstancesCapacityProviderConfig": {
            "CapacityProviderArn": "arn:aws:lambda:us-east-2:111122223333:capacity-provider:lmi-gpu-cp",
            "ExecutionEnvironmentMemoryGiBPerVCpu": 4,
            "PerExecutionEnvironmentMaxConcurrency": 4
        }
    },
    "AcceleratorConfig": { "AcceleratorMemorySize": 16 }
}
&lt;/code&gt;&lt;/pre&gt; 
&lt;pre&gt;&lt;code&gt;aws --region us-east-2 \
  lambda create-function \
  --cli-input-json file://cli-skeletons/create-gpu-llm-function.json
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The function overview shows what makes this a GPU-accelerated function: the attached capacity provider that supplies the GPU instances and the vLLM container image deployed from Amazon ECR, all wired into the same function model you already use.&lt;br&gt; &lt;img loading="lazy" class="aligncenter size-full wp-image-106179" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/02-function-overview-lmi.png" alt="Lambda console function overview for lmi-gpu-inference showing the attached capacity provider lmi-gpu-cp, the container image from Amazon ECR, and the x86_64 architecture" width="1800" height="738"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;Figure 2: The lmi-gpu-inference function overview, showing the attached capacity provider and the vLLM container image deployed from Amazon ECR.&lt;/p&gt; 
&lt;p&gt;Functions on Lambda Managed Instances run from a published version, so I published one. Publishing provisions the execution environments, and each one downloads the model weights and warms up the engine before the version becomes active. The cold start happens during the publish step, so the first caller doesn’t wait for it.&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;aws --region us-east-2 \
  lambda publish-version \
  --function-name lmi-gpu-inference \
  --publish-to LATEST_PUBLISHED
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Then I sent the model a prompt. The payload is a standard OpenAI request body: a &lt;code&gt;messages&lt;/code&gt; array routes to chat completions, and a &lt;code&gt;prompt&lt;/code&gt; field routes to text completions.&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;aws --region us-east-2 \
  lambda invoke \
  --function-name 'lmi-gpu-inference:$LATEST.PUBLISHED' \
  --cli-binary-format raw-in-base64-out \
  --payload '{"messages": [{"role": "user", "content": "Explain serverless GPU inference in one sentence."}], "max_tokens": 128}' \
  /dev/stdout
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The model answered from a GPU inside the Lambda execution environment, and the response is a standard OpenAI completion object, so any OpenAI-compatible client works with it.&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;{
  "model": "Qwen/Qwen2.5-1.5B-Instruct",
  "choices": [
    {
      "message": {
        "role": "assistant",
        "content": "Serverless GPU inference is a cloud-based service that allows for efficient execution of machine learning models on NVIDIA GPUs without the need for infrastructure management or maintenance."
      },
      "finish_reason": "stop"
    }
  ],
  "usage": { "prompt_tokens": 39, "completion_tokens": 31, "total_tokens": 70 }
}
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Four concurrent invocations finished in about the same time as a single one, on one execution environment that shares one copy of the model in GPU memory. From a Hugging Face model ID to a live, OpenAI-compatible GPU endpoint took about 10 minutes, most of it unattended while Lambda provisioned capacity and warmed up the model.&lt;/p&gt; 
&lt;p&gt;That’s a working LLM endpoint with no inference server code, no GPU drivers, and no cluster to manage. To try a different model, I update &lt;code&gt;MODEL_ID&lt;/code&gt; and publish a new version, with no image rebuild. Each version is an immutable snapshot, so different models can run side by side as separate versions. It is also a Lambda Event Function, so I can trigger it from an &lt;a href="https://aws.amazon.com/sqs/"&gt;Amazon SQS&lt;/a&gt; queue to process documents in batches, put &lt;a href="https://aws.amazon.com/api-gateway/"&gt;Amazon API Gateway&lt;/a&gt; in front of it, or call it as the inference step in a Lambda durable functions workflow.&lt;/p&gt; 
&lt;p&gt;For production, copy the model weights to an S3 bucket in the same Region, point &lt;code&gt;MODEL_ID&lt;/code&gt; at that bucket, and set &lt;code&gt;VLLM_LOAD_FORMAT=runai_streamer&lt;/code&gt; so the weights stream straight into memory. This gives faster starts and removes the dependency on the Hugging Face Hub. For more guidance, see the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances-gpu-inference.html"&gt;best practices for running inference workloads&lt;/a&gt;. Beyond LLM inference, you can also run custom ML inference, media processing, and other GPU workloads. See the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances-gpu.html"&gt;Lambda documentation&lt;/a&gt; for best practices.&lt;/p&gt; 
&lt;p&gt;The configuration tab shows the settings that matter for a GPU-accelerated function: 16,384 MB of memory, the 15-minute timeout, and 32 GB of ephemeral storage for the downloaded weights, alongside the function-level capacity provider settings: per-environment concurrency of 4, the 4:1 memory-to-vCPU ratio, and 16 GB of accelerator memory.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-106180" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/03-function-configuration-lmi.png" alt="Lambda console configuration tab for lmi-gpu-inference showing 16,384 MB of memory, the 15-minute timeout, 32 GB of ephemeral storage, and the function-level capacity provider settings including per-environment concurrency, the memory-to-vCPU ratio, and accelerator memory" width="1800" height="596"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;Figure 3: The function’s configuration, including memory, timeout, and 32 GB of ephemeral storage, and the function-level capacity provider settings: per-environment concurrency, the memory-to-vCPU ratio, and accelerator memory.&lt;/p&gt; 
&lt;p&gt;When you finish testing, delete the function and then the capacity provider so that Lambda stops the GPU instances and you stop paying for them.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;How it works&lt;/strong&gt;&lt;br&gt; The capabilities below are what you get out of the box, each one removing GPU work you would otherwise own.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Skip the GPU software setup.&lt;/strong&gt; Curated base images ship with the frameworks and tools handled for you, so you do not install or reconcile them: &lt;code&gt;base:cuda&lt;/code&gt; (CUDA toolkit and runtime), &lt;code&gt;cupy:cuda&lt;/code&gt; (CuPy, NumPy, SciPy, Pandas, Numba), &lt;code&gt;pytorch:cuda&lt;/code&gt; (PyTorch, torchvision, torchaudio, transformers, FFmpeg), and serving images &lt;code&gt;vllm:cuda&lt;/code&gt; and &lt;code&gt;sglang:cuda&lt;/code&gt;. Use them directly, extend them, or bring a fully custom image.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;No GPU infrastructure to operate.&lt;/strong&gt; Lambda handles driver compatibility, provisioning, routing, and load balancing, so you ship functions instead of running GPU fleets. Deploy with the same Console, CLI, &lt;a href="https://aws.amazon.com/cloudformation/"&gt;AWS CloudFormation&lt;/a&gt;, &lt;a href="https://aws.amazon.com/cdk/"&gt;AWS CDK&lt;/a&gt;, &lt;a href="https://aws.amazon.com/serverless/sam/"&gt;AWS SAM&lt;/a&gt;, and Terraform workflow as any Lambda Event Function.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Trigger GPU work from any AWS event.&lt;/strong&gt; The same 200+ event sources that trigger Event Functions, including &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt;, &lt;a href="https://aws.amazon.com/sqs/"&gt;Amazon SQS&lt;/a&gt;, &lt;a href="https://aws.amazon.com/api-gateway/"&gt;Amazon API Gateway&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/eventbridge/"&gt;Amazon EventBridge&lt;/a&gt;, trigger GPU-accelerated functions directly, with the same scaling, error handling, and retries. No custom integration code.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Serve concurrent requests on each GPU.&lt;/strong&gt; Each execution environment can process multiple concurrent invocations on the same GPU, which you control with the per-environment concurrency setting. Raising it packs more requests onto each GPU instance to drive utilization up, so you get more throughput from the capacity you already pay for.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Multiple instance types.&lt;/strong&gt; Specify multiple instance types or generations, and Lambda selects the most cost-effective available option and falls back across your list to reduce Insufficient Capacity Errors.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Capacity options.&lt;/strong&gt; GPU instances run as Amazon EC2 On-Demand instances, and your existing Savings Plans and Reserved Instances apply. For predictable GPU availability, create an &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-capacity-reservations.html"&gt;EC2 On-Demand Capacity Reservation (ODCR)&lt;/a&gt; that matches your capacity provider configuration, and Lambda uses that reserved capacity automatically.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Large container images and storage.&lt;/strong&gt; Container images up to 32 GB are supported, along with up to 32 GB of NVMe ephemeral storage in &lt;code&gt;/tmp&lt;/code&gt;. &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances-seekable-oci.html"&gt;Seekable OCI (SOCI) lazy loading&lt;/a&gt; lets your function begin executing before the full image is downloaded, which reduces execution environment startup time by up to 70%.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;See GPU usage without extra setup.&lt;/strong&gt; GPU utilization, GPU memory utilization, GPU memory used, and GPU power utilization appear alongside standard function metrics in &lt;a href="https://aws.amazon.com/cloudwatch/"&gt;Amazon CloudWatch&lt;/a&gt; and in the AWS Lambda console.&lt;/p&gt; 
&lt;p&gt;After invoking the function, the console surfaces the GPU-specific metrics next to the standard ones. Track GPU utilization, GPU memory utilization, GPU memory used, and GPU power utilization to see how much of the accelerator each invocation actually uses, which is the signal that drives both auto-scaling and cost.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-106182" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/04-gpu-metrics-vllm.png" alt="Lambda console Monitor tab showing GPU utilization, GPU memory utilization, GPU memory used, and GPU power utilization charts for a GPU inference function under load" width="1800" height="876"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;Figure 4: GPU utilization, GPU memory utilization, GPU memory used, and GPU power utilization for the vLLM function under concurrent load.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Pricing and availability&lt;/strong&gt;&lt;br&gt; This feature is generally available today, supporting the Amazon EC2 G-series (G4dn, G5, G6, G6f, Gr6, Gr6f, G6e) at launch, with more instance families to come. You pay the underlying EC2 instance fee (eligible for &lt;a href="https://aws.amazon.com/savingsplans/compute-pricing/"&gt;Savings Plans&lt;/a&gt; and Reserved Instances), plus a 9.75 percent management fee for GPU instances, and the standard Lambda request fee of $0.20 per million requests. For pricing and Region availability, see &lt;a href="https://aws.amazon.com/lambda/pricing/"&gt;AWS Lambda pricing&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;You can also build with your AI coding assistants and agents: explore the &lt;a href="https://builder.aws.com/capabilities/?trk=f11c83db-08fa-4852-aa10-20185beeaef6&amp;amp;sc_channel=el"&gt;Builder Center&lt;/a&gt; and connect your tools with the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/quick-start.html"&gt;Agent Toolkit for AWS&lt;/a&gt;, which bundles the AWS MCP Server and curated agent skills.&lt;/p&gt; 
&lt;p&gt;To get started, visit the AWS Lambda console and see the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-managed-instances-gpu.html"&gt;GPU-accelerated functions documentation&lt;/a&gt;.&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Four Continents, Four New AWS Heroes: Closing Out 2026</title>
		<link>https://aws.amazon.com/blogs/aws/four-continents-four-new-aws-heroes-closing-out-2026/</link>
					
		
		<dc:creator><![CDATA[Taylor Jacobsen]]></dc:creator>
		<pubDate>Tue, 17 Nov 2026 17:06:43 +0000</pubDate>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Heroes]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">8792b36d1af1b35d715874ec8395260652442a9e</guid>

					<description>As AWS re:Invent is around the corner, we’re proud to recognize a new group of AWS Heroes. Every Hero finds their own way to give back, whether through sharing what they know, bringing people together, or building tools that help others succeed. What they have in common is a genuine commitment to supporting the builders […]</description>
										<content:encoded>&lt;p&gt;As AWS re:Invent is around the corner, we’re proud to recognize a new group of &lt;a href="https://builder.aws.com/connect/community/heroes" target="_blank" rel="noopener"&gt;AWS Heroes&lt;/a&gt;. Every Hero finds their own way to give back, whether through sharing what they know, bringing people together, or building tools that help others succeed. What they have in common is a genuine commitment to supporting the builders around them learn, grow, and lead.&lt;/p&gt; 
&lt;p&gt;Let us take a moment to meet them!&lt;/p&gt; 
&lt;h2 style="clear: both"&gt;Andres Moreno – El Paso, United States&lt;/h2&gt; 
&lt;p&gt;&lt;a href="https://builder.aws.com/community/@andmoredev" target="_blank" rel="noopener noreferrer"&gt;&lt;img loading="lazy" class="alignleft" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/Andres-Moreno_175x263.png" width="175" height="263"&gt;&lt;/a&gt; Serverless Hero &lt;a href="https://builder.aws.com/community/@andmoredev" target="_blank" rel="noopener noreferrer"&gt; Andres Moreno&lt;/a&gt; leads the Cloud del Norte AWS User Group and is a former AWS Community Builder. On his blog, And More Dev, and at conferences and community events, he explains serverless, cloud native architectures, generative AI, and agentic systems in ways that make new technology easier to try. Andres puts special energy into supporting builders across Latin America and helping them explore what’s possible on AWS.&lt;/p&gt; 
&lt;h2 style="clear: both"&gt;Geethika Guruge – Auckland, New Zealand&lt;/h2&gt; 
&lt;p&gt;&lt;a href="https://builder.aws.com/community/@geethika" target="_blank" rel="noopener noreferrer"&gt;&lt;img loading="lazy" class="alignleft" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/Geethika-Guruge_175x263.png" width="175" height="263"&gt;&lt;/a&gt; Community Hero &lt;a href="https://builder.aws.com/community/@geethika" target="_blank" rel="noopener noreferrer"&gt;Geethika Guruge&lt;/a&gt; is a Principal Consultant at Mantel Group whose work spans serverless, DevOps, cloud infrastructure, and agentic AI. Geethika has shared real lessons from building agentic applications and leading large migration and modernization programs at AWS re:Invent, AWS Summits, and AWS Community Days. At home in Auckland, Geethika organizes local AWS meetups that encourage grassroots innovation and mentors the next generation of cloud architects and leaders.&lt;/p&gt; 
&lt;h2 style="clear: both"&gt;Jéssica Cristina Coelho – Belo Horizonte, Brazil&lt;/h2&gt; 
&lt;p&gt;&lt;a href="https://builder.aws.com/community/@jesscoelho" target="_blank" rel="noopener noreferrer"&gt;&lt;img loading="lazy" class="alignleft" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/Je%CC%81ssica-Cristina-Coelho_175x263.png" width="175" height="263"&gt;&lt;/a&gt; Data Hero &lt;a href="https://builder.aws.com/community/@jesscoelho" target="_blank" rel="noopener noreferrer"&gt;Jéssica Cristina Coelho&lt;/a&gt; is a Database Reliability Engineer and a former AWS Community Builder with more than 15 years of experience in databases, cloud, and data engineering. She leads the AWS User Group in Minas Gerais, hosts DataTalks Brasil, teaches MBA courses, and supports Women in Cloud, DevOpsDays, and AWS Community Day events. She speaks at events such as AWS Summit São Paulo and Web Summit Rio on database modernization and generative AI. At AWS re:Invent 2025, she was recognized as a LATAM Diversity &amp;amp; Inclusion Champion.&lt;/p&gt; 
&lt;h2 style="clear: both"&gt;Kazuho Cryer Shinozuka – Tokyo, Japan&lt;/h2&gt; 
&lt;p&gt;&lt;a href="https://builder.aws.com/community/@cryer" target="_blank" rel="noopener noreferrer"&gt;&lt;img loading="lazy" class="alignleft" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/11/Kazuho-Cryer-Shinozuka_175x263.png" width="175" height="263"&gt;&lt;/a&gt; DevTools Hero &lt;a href="https://builder.aws.com/community/@cryer" target="_blank" rel="noopener noreferrer"&gt;Kazuho Cryer Shinozuka&lt;/a&gt; is an AWS CDK Top Contributor and Trusted CDK Community Reviewer. With 200 merged pull requests, he ranks 18th among more than 1,700 contributors. He has reviewed more than 120 pull requests, has been involved in about 2% of all CDK commits, and has published 10 construct libraries, along with tools such as cfn idle cost. Through talks at JAWS DAYS and CDK Conference Japan and through hands on contribution workshops, he helps more developers in Japan start contributing to open source.&lt;/p&gt; 
&lt;h2 style="clear: both"&gt;Learn More&lt;/h2&gt; 
&lt;p&gt;To connect with these Heroes or find one in your region, explore the &lt;a href="https://builder.aws.com/connect/community/heroes" target="_blank" rel="noopener"&gt;AWS Heroes webpage&lt;/a&gt;, and join the conversation on &lt;a href="https://builder.aws.com/community" target="_blank" rel="noopener"&gt;AWS Builder Center&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;— &lt;a href="https://twitter.com/taylorjacobsen" target="_blank" rel="noopener noreferrer"&gt;Taylor&lt;/a&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: AWS Nitro Sandboxes, AWS Emulator, and more (November 16, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-aws-nitro-sandboxes-aws-emulator-and-more-november-16-2026/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Mon, 16 Nov 2026 17:55:46 +0000</pubDate>
				<category><![CDATA[Amazon Bedrock]]></category>
		<category><![CDATA[Amazon CloudWatch]]></category>
		<category><![CDATA[Amazon Cognito]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Amazon Elastic Kubernetes Service]]></category>
		<category><![CDATA[Amazon ElastiCache]]></category>
		<category><![CDATA[Amazon OpenSearch Service]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS re:Invent]]></category>
		<category><![CDATA[AWS Step Functions]]></category>
		<category><![CDATA[Developer Tools]]></category>
		<category><![CDATA[Events]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">c84e831e813aae9c114a1c7179100aac35ea0ad7</guid>

					<description>A second delivery of the same message can reveal more about an application than its happy-path demo. I like tools that make those cases easier to investigate while a change is still small. Last week’s launch of AWS Emulator brings part of that work onto your own machine: developers and coding agents can exercise AWS […]</description>
										<content:encoded>&lt;p&gt;A second delivery of the same message can reveal more about an application than its happy-path demo. I like tools that make those cases easier to investigate while a change is still small. Last week’s launch of &lt;a href="https://aws.amazon.com/products/developer-tools/emulator/"&gt;AWS Emulator&lt;/a&gt; brings part of that work onto your own machine: developers and coding agents can exercise AWS API interactions, inspect results, and try again without provisioning cloud resources for every attempt.&lt;/p&gt; 
&lt;p&gt;I wrote about the Emulator’s launch last week, and it’s my main highlight in this edition. There are also new ways to isolate workloads on shared infrastructure, give an agent narrowly scoped access to a backend, and prepare search applications for a regional disruption. Now, let’s get into this week’s AWS news…&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-106216" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/11/13/aws-emulator-official-diagram_1540.png" alt="Official AWS diagram showing application code, SDKs, CLI, and coding agents calling AWS Emulator on a laptop or CI environment, with a separate path for deployment to AWS." width="1540" height="1155"&gt;&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;AWS Emulator runs locally alongside your code and development tools. Image: &lt;a href="https://aws.amazon.com/products/developer-tools/emulator/"&gt;AWS&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span id="more-106214"&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Headlines&lt;/strong&gt;&lt;br&gt; &lt;a href="https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/"&gt;Test your applications against AWS locally with AWS Emulator&lt;/a&gt; introduces a generally available local environment for AWS API interactions. Point the &lt;a href="https://aws.amazon.com/cli/"&gt;AWS CLI&lt;/a&gt; or &lt;a href="https://aws.amazon.com/developer/tools/"&gt;AWS SDKs&lt;/a&gt; at its HTTPS endpoint, and your application keeps its normal SDK calls. The walkthrough shows a coding agent creating an &lt;a href="https://aws.amazon.com/dynamodb/"&gt;Amazon DynamoDB&lt;/a&gt; table, writing an item, and reading it back. You don’t need an AWS account for emulated operations, and there is no additional service fee. The &lt;a href="https://docs.aws.amazon.com/emulator/latest/userguide/getting-started.html"&gt;getting-started guide&lt;/a&gt; covers Linux packages, Docker for macOS and Windows, and agent-assisted setup; the &lt;a href="https://github.com/aws/aws-emulator"&gt;source is on GitHub&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;What I like is giving an agent concrete feedback while it works: run calls, inspect results, and revise the code. Matt Wood’s &lt;a href="https://aws.amazon.com/blogs/aws-insights/better-feedback-for-building-with-agents/"&gt;perspective on feedback for coding agents&lt;/a&gt; explores why that loop matters. Check the published &lt;a href="https://docs.aws.amazon.com/emulator/latest/userguide/fidelity.html"&gt;fidelity results&lt;/a&gt; for your operations, because coverage varies and unimplemented calls return HTTP 501. The emulator doesn’t reproduce &lt;a href="https://aws.amazon.com/iam/"&gt;IAM&lt;/a&gt; and resource-policy enforcement or cross-account and cross-Region behavior, so test the complete application and its security configuration on AWS before production.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/nitro-sandboxes-eks-ecs-ec2/"&gt;AWS Nitro Sandboxes bring hardware isolation to pods, tasks, and VMs&lt;/a&gt;. You can give an &lt;a href="https://aws.amazon.com/eks/"&gt;Amazon EKS&lt;/a&gt; pod or &lt;a href="https://aws.amazon.com/ecs/"&gt;Amazon ECS&lt;/a&gt; task its own VM boundary while sharing an &lt;a href="https://aws.amazon.com/ec2/"&gt;Amazon EC2&lt;/a&gt; instance. That is useful for tenant workloads, build jobs, and agents executing generated code. Isolated mode separates workloads from their neighbors; confidential mode adds protection from node operators and cryptographic attestation. The &lt;a href="https://aws.amazon.com/blogs/compute/nitro-sandboxes-hardware-isolation-for-every-eks-pod-ecs-task-and-ec2-workload/"&gt;Compute Blog deep dive&lt;/a&gt; explains both modes and their integrations. Nitro Sandboxes have no additional charge on supported instances; EC2 and applicable EKS Auto Mode or ECS Managed Instances fees still apply.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Last week’s launches&lt;/strong&gt;&lt;br&gt; Here are some launches and updates from this past week that caught my attention:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/cognito-token-exchange/"&gt;Amazon Cognito supports OAuth 2.0 token exchange&lt;/a&gt; – You can now exchange a user’s token for one scoped to a downstream service in &lt;a href="https://aws.amazon.com/cognito/"&gt;Amazon Cognito&lt;/a&gt;. The derived token can have narrower permissions and a single audience, with no refresh token; supplying an actor token also identifies the intermediary in an &lt;code&gt;act&lt;/code&gt; claim. For an agent calling a backend on someone’s behalf, that makes delegation more explicit without forwarding the original token. The feature is available on Essentials and Plus plans in all Cognito Regions.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/claude-fable-5-2-aws/"&gt;Claude Fable 5.2 is available on AWS&lt;/a&gt; – You can access the model through &lt;a href="https://aws.amazon.com/bedrock/"&gt;Amazon Bedrock&lt;/a&gt; or Claude Platform on AWS. Anthropic positions it as its most capable generally available model for technical work, including extended engineering tasks, scientific research, and quantitative finance. Bedrock has &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/abuse-detection.html"&gt;model-specific retention requirements&lt;/a&gt;: Fable 5.2 traffic is retained for up to 30 days for abuse detection, with a temporary zero-retention exception for eligible internal use.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-elasticache-serverless-search-aggregations/"&gt;Amazon ElastiCache Serverless adds search and aggregations&lt;/a&gt; – You can now combine vector, full-text, and hybrid search with server-side aggregations in &lt;a href="https://aws.amazon.com/elasticache/"&gt;Amazon ElastiCache&lt;/a&gt; Serverless for Valkey. That gives product discovery, recommendations, and agent-memory retrieval another option for querying frequently changing data. The capability requires Valkey 9, so create a compatible cache or upgrade an existing one. It is available in commercial Regions, AWS GovCloud (US), and the AWS European Sovereign Cloud.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-opensearch-service-managed-cross-region-disaster-recovery/"&gt;Amazon OpenSearch Service adds managed cross-Region disaster recovery&lt;/a&gt; – You can now pair &lt;a href="https://aws.amazon.com/opensearch-service/"&gt;Amazon OpenSearch Service&lt;/a&gt; domains running version 3.7 or later in two Regions within one account. AWS specifies recovery objectives under one minute for data loss and under 20 minutes for recovery time. Planned switchovers preserve all writes; unplanned failovers can lose unreplicated data. The &lt;a href="https://aws.amazon.com/blogs/big-data/managed-cross-region-disaster-recovery-for-amazon-opensearch-service/"&gt;deep dive&lt;/a&gt; covers the remaining work: keeping configuration aligned and redirecting application writes after switching roles, plus secondary-domain and data-transfer charges.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-cloudwatch-log-retention/"&gt;Amazon CloudWatch Logs adds account-level retention policies&lt;/a&gt; – You can now set retention across all log groups or groups matching a name prefix in &lt;a href="https://aws.amazon.com/cloudwatch/"&gt;Amazon CloudWatch&lt;/a&gt;, with policies covering existing groups or only new ones. When policies overlap, the longest retention period applies. A platform team can set a baseline and retain security logs longer without updating every group individually. The feature has no additional charge and is available in commercial Regions except Middle East (Bahrain) and Middle East (UAE).&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/new-agentcore-runtime-default/"&gt;The next generation AgentCore runtime is now the default&lt;/a&gt; – New Amazon Bedrock AgentCore runtimes now use the next-generation runtime by default, so agent sessions start in under 2 seconds, scale up to 8 vCPU and 32 GB, scale to zero when idle, and bill up to 68% less memory, while each session still runs in its own isolated microVM.&lt;/p&gt; 
&lt;p&gt;For a full list of AWS announcements, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/new/"&gt;What’s New with AWS&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Other AWS news&lt;/strong&gt;&lt;br&gt; Here are some additional posts and resources that you might find interesting:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/optimizing-cost-per-task-and-proving-agent-roi-on-amazon-bedrock/"&gt;Optimizing cost per task and proving agent ROI on Amazon Bedrock&lt;/a&gt; – This guide follows an agent’s cost through repeated calls, reasoning, caching, and human review. I like its emphasis on measuring a completed task and comparing outcomes against a documented baseline. Its worked prices are illustrative; use your own workload and reconcile estimated costs with billing data.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/architecture/how-zillow-runs-100-million-daily-notifications-on-aws-step-functions/"&gt;How Zillow runs 100 million daily notifications on AWS Step Functions&lt;/a&gt; – Zillow describes reusable content modules and configuration-driven &lt;a href="https://aws.amazon.com/step-functions/"&gt;AWS Step Functions&lt;/a&gt; Express Workflows for more than 100 million daily notifications. The useful engineering details include idempotent modules, batching, campaign isolation, and testing expressions with the TestState API before deployment. Those patterns apply well beyond notification systems.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Upcoming AWS events&lt;/strong&gt;&lt;br&gt; Check your calendar and sign up for upcoming AWS events:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/reinvent/"&gt;AWS re:Invent&lt;/a&gt; – Join the community in Las Vegas from November 30 to December 4. Browse more than 2,200 sessions, including workshops and deep dives, or register for the free livestream to follow keynotes and selected sessions remotely.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt; – Find community-led technical talks, workshops, and hands-on learning near you. Check each organizer’s page for current dates and registration details.&lt;/p&gt; 
&lt;p&gt;Join the &lt;a href="https://builder.aws.com/"&gt;AWS Builder Center&lt;/a&gt; to connect with builders, share solutions, and access content that supports your development. Browse &lt;a href="https://aws.amazon.com/events/"&gt;here&lt;/a&gt; for upcoming AWS-led in-person and virtual events and developer-focused events.&lt;/p&gt; 
&lt;p&gt;That’s all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;– Daniel Abib&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Test your applications against AWS locally with AWS Emulator</title>
		<link>https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 19:00:44 +0000</pubDate>
				<category><![CDATA[Amazon Bedrock AgentCore]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Developer Tools]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">c0bd049236369d601a6a4b54035a912339948df0</guid>

					<description>AWS Emulator is a free, open-source local emulator in Rust that lets developers test applications against nearly every AWS service on their own machine using the same CLI and SDK commands, with fidelity measured against real AWS behavior.</description>
										<content:encoded>&lt;p&gt;Today we’re announcing AWS Emulator, a local emulator for Amazon Web Services (AWS) that you run on your machine. The &lt;a href="https://aws.amazon.com/cli/"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;, the &lt;a href="https://aws.amazon.com/developer/tools/"&gt;AWS SDKs&lt;/a&gt;, and your coding agents speak to it over a local HTTPS endpoint using the same AWS APIs they would use in the cloud, from your laptop. AWS Emulator has no additional service fee. You pay only for AWS resources when you deploy on AWS. Its source is on &lt;a href="https://github.com/aws/aws-emulator"&gt;GitHub&lt;/a&gt;. You install it from an RPM or Debian package on Linux, and on macOS and Windows you run it in Docker.&lt;/p&gt; 
&lt;p&gt;&lt;span id="more-106044"&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;How it works&lt;/strong&gt;&lt;br&gt; You install the emulator, start it, and point your tools at the local endpoint. When AWS Emulator starts, it generates its own credentials, a config file, and a certificate, and writes them to &lt;code&gt;~/.aws/emulator/9297/&lt;/code&gt;. You set environment variables so the AWS SDK talks to your laptop instead of AWS, and your application code stays unchanged.&lt;/p&gt; 
&lt;p&gt;From there, your existing tests, CLI scripts, and coding agents keep working the way they already do. A unit test that creates an &lt;a href="https://aws.amazon.com/dynamodb/"&gt;Amazon DynamoDB&lt;/a&gt; table, writes an item, and reads it back is the same test, and it runs on your machine without a deployment. A coding agent can create resources, check the result, and iterate again without waiting on a deployment in a Region.&lt;/p&gt; 
&lt;p&gt;The emulator is implemented in Rust so that it stays light on CPU and memory on a laptop. It supports the APIs of AWS services that have an API model in the AWS API models repository on GitHub, and because it’s built from those models, the same ones the AWS SDKs use, your requests and the errors you get back have the same shape as on AWS.&lt;/p&gt; 
&lt;p&gt;If you are a developer, especially one working with coding agents such as Kiro or Claude Code, you can use that loop to test AWS interactions of real complexity locally.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Let’s try it out&lt;/strong&gt;&lt;br&gt; To get started, I installed the package on &lt;a href="https://aws.amazon.com/linux/amazon-linux-2023/"&gt;Amazon Linux 2023&lt;/a&gt;. The package adds the &lt;code&gt;aws-emulator&lt;/code&gt; command to &lt;code&gt;/usr/bin/&lt;/code&gt;, so it’s on the path.&lt;/p&gt; 
&lt;pre class="lang:sh decode:true"&gt;PKG=https://downloads.aws.com/aws-emulator/packages/aws-emulator/LTS/latest
sudo dnf install -y $PKG/aws-emulator-x86_64.rpm

aws-emulator -v&lt;/pre&gt; 
&lt;p&gt;On macOS and Windows, you build a Docker image from the short Dockerfile in the documentation and run the emulator in a container. We don’t publish a ready-made image.&lt;/p&gt; 
&lt;p&gt;I started the emulator with &lt;code&gt;aws-emulator&lt;/code&gt;. It serves HTTPS on &lt;code&gt;127.0.0.1:9297&lt;/code&gt;, so only my own computer can reach it, and it writes its log as JSON lines that show the address, the config file, and the certificate file.&lt;/p&gt; 
&lt;pre class="lang:sh decode:true"&gt;aws-emulator&lt;/pre&gt; 
&lt;p&gt;In another terminal, I set the environment variables that point the AWS CLI at the emulator, and unset any variables that could supply real AWS credentials.&lt;/p&gt; 
&lt;pre class="lang:sh decode:true"&gt;export AWS_ENDPOINT_URL=https://127.0.0.1:9297
export AWS_SHARED_CREDENTIALS_FILE=~/.aws/emulator/9297/emulator_credentials
export AWS_CONFIG_FILE=~/.aws/emulator/9297/config
export AWS_EC2_METADATA_DISABLED=true
export AWS_DISABLE_HOST_PREFIX_INJECTION=true
export AWS_REGION=us-east-1
export AWS_DEFAULT_REGION=us-east-1
unset AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_SESSION_TOKEN AWS_PROFILE&lt;/pre&gt; 
&lt;p&gt;The emulator generates new keys each time it starts. Its access key IDs start with &lt;code&gt;EMULATOR&lt;/code&gt;, so you can’t mistake them for real AWS keys, and it rejects requests signed with any other keys. To confirm that my shell was talking to the emulator, I checked the health endpoint and the caller identity. The emulator uses a single account, &lt;code&gt;000000000000&lt;/code&gt;.&lt;/p&gt; 
&lt;pre class="lang:sh decode:true"&gt;curl --cacert ~/.aws/emulator/9297/ca.pem https://127.0.0.1:9297/__admin/health

aws sts get-caller-identity&lt;/pre&gt; 
&lt;p&gt;Then I created a bucket, copied in a small object, and listed it.&lt;/p&gt; 
&lt;pre class="lang:sh decode:true"&gt;$ aws s3 mb s3://local-getting-started
make_bucket: local-getting-started

$ echo "hello from the emulator" &amp;gt; hello.txt

$ aws s3 cp hello.txt s3://local-getting-started/
upload: ./hello.txt to s3://local-getting-started/hello.txt

$ aws s3 ls s3://local-getting-started/&lt;/pre&gt; 
&lt;p&gt;With the AWS CLI pointed at my laptop, I had the same commands I already use and a local endpoint that answered them.&lt;/p&gt; 
&lt;p&gt;Next I wanted to see it the way I actually work now, so with the emulator still running I opened &lt;a href="https://kiro.dev/"&gt;Kiro&lt;/a&gt; and asked it to create an Amazon DynamoDB table, write an item, and read it back, all against AWS Emulator rather than my AWS account.&lt;/p&gt; 
&lt;pre class="lang:sh decode:true"&gt;kiro&amp;gt; Using the local AWS Emulator (the environment variables
      are already set in this shell), create a DynamoDB table
      "kiro-demo" with a string key "id", put an item
      {id: "item-1", msg: "hello from kiro"}, then read it
      back with get-item.

$ aws dynamodb create-table --table-name kiro-demo \
    --attribute-definitions AttributeName=id,AttributeType=S \
    --key-schema AttributeName=id,KeyType=HASH \
    --billing-mode PAY_PER_REQUEST

$ aws dynamodb put-item --table-name kiro-demo \
    --item '{"id": {"S": "item-1"}, "msg": {"S": "hello from kiro"}}'

$ aws dynamodb get-item --table-name kiro-demo --key '{"id": {"S": "item-1"}}'&lt;/pre&gt; 
&lt;p&gt;To use the same setup with an existing test suite, I would start the emulator, set the same environment variables in the script that runs the tests, and run them as usual.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Using the emulator in process&lt;/strong&gt;&lt;br&gt; Running the emulator as a local process gives you an HTTPS endpoint that works with the AWS CLI and the AWS SDKs through environment variables. Some SDKs need an extra setting to trust the emulator certificate, for example a trust store for the &lt;a href="https://aws.amazon.com/sdk-for-java/"&gt;AWS SDK for Java&lt;/a&gt;. For tests, there is a second option. AWS Emulator ships an embedded mode that you instantiate directly inside your test process and wire into the SDK through its HTTP client, rather than talking to a separate server over the network. Each embedded instance keeps its own state, so tests do not share buckets, tables, or queues, and you can run many of them in parallel. Embedded mode is available for the &lt;a href="https://aws.amazon.com/sdk-for-rust/"&gt;AWS SDK for Rust&lt;/a&gt;. You add the &lt;code&gt;aws-emulator-embedded&lt;/code&gt; crate from GitHub to the &lt;code&gt;[dev-dependencies]&lt;/code&gt; section of your &lt;code&gt;Cargo.toml&lt;/code&gt; file. The following example creates an Amazon DynamoDB table, writes an item, and reads it back, entirely in process.&lt;/p&gt; 
&lt;pre class="lang:rust decode:true"&gt;&lt;code&gt;use aws_emulator_embedded::{AwsEmulatorEmbedded, EmbeddedOptions};
use aws_sdk_dynamodb::types::{
    AttributeDefinition, AttributeValue, BillingMode, KeySchemaElement, KeyType,
    ScalarAttributeType,
};

#[tokio::test]
async fn put_then_get_returns_the_item() {
    let emulator = AwsEmulatorEmbedded::new(EmbeddedOptions::default());
    let config = aws_config::defaults(aws_config::BehaviorVersion::latest())
        .http_client(emulator.http_client())
        .region(aws_config::Region::new("us-east-1"))
        .credentials_provider(emulator.aws_credentials_provider())
        .load()
        .await;
    let ddb = aws_sdk_dynamodb::Client::new(&amp;amp;config);

    ddb.create_table()
        .table_name("emulator-demo-table")
        .attribute_definitions(
            AttributeDefinition::builder()
                .attribute_name("id").attribute_type(ScalarAttributeType::S)
                .build().unwrap())
        .key_schema(
            KeySchemaElement::builder()
                .attribute_name("id").key_type(KeyType::Hash)
                .build().unwrap())
        .billing_mode(BillingMode::PayPerRequest)
        .send().await.unwrap();

    ddb.put_item()
        .table_name("emulator-demo-table")
        .item("id", AttributeValue::S("item-1".into()))
        .item("msg", AttributeValue::S("hi".into()))
        .send().await.unwrap();

    let got = ddb.get_item()
        .table_name("emulator-demo-table")
        .key("id", AttributeValue::S("item-1".into()))
        .send().await.unwrap();
    assert_eq!(got.item().unwrap().get("msg").unwrap().as_s().unwrap(), "hi");
}&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;When it runs as a local process, the emulator requires every request to be signed with Signature Version 4 (SigV4), the same way AWS does, and it exposes a &lt;code&gt;/__admin/health&lt;/code&gt; endpoint on the same port so a script or a container can wait until it is ready before running tests. By default it also sends anonymous usage and error data, and you can turn it off.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;How we measure fidelity&lt;/strong&gt;&lt;br&gt; An emulator is only useful if a test that passes against it would also pass against AWS, so we measure that directly with fidelity tests. A fidelity test is a short program that uses an AWS SDK to run a workflow, such as storing an object and then reading and deleting it, and asserts how AWS behaves. We verify each fidelity test against real AWS. A fidelity test passes only if the emulator matches AWS on the response to every call, including the status code, the body, and the exact error code and message, and on the resources and data that the workflow creates.&lt;/p&gt; 
&lt;p&gt;With each release, we publish how many fidelity tests pass for each service, as k of n. For example, 40 of 50 means that 40 of the service’s 50 fidelity tests pass. The set of fidelity tests is public in the aws-emulator-evaluation-suite repository on GitHub, including the ones that don’t pass yet, so you can see what we verified and run the fidelity tests yourself. Read a score as a snapshot of a product that’s improving. When we add fidelity tests, a score can go down even while the emulator gets better.&lt;/p&gt; 
&lt;p&gt;If the emulator doesn’t implement an operation yet, it returns HTTP 501 (Not Implemented), so your tests fail right away. If the emulator acts differently from AWS, you can tell us by opening an issue in the AWS Emulator repository on GitHub.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;How the emulator is built&lt;/strong&gt;&lt;br&gt; AWS Emulator is built and maintained by agents from the AWS API models using &lt;a href="https://aws.amazon.com/bedrock/agentcore/"&gt;Amazon Bedrock AgentCore&lt;/a&gt; Runtime Instances, &lt;a href="https://aws.amazon.com/codepipeline/"&gt;AWS CodePipeline&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/codecommit/"&gt;AWS CodeCommit&lt;/a&gt;, so it stays current with AWS as those models change.&lt;/p&gt; 
&lt;p&gt;One group of agents looks for gaps, both by comparing emulator responses against real AWS and by statically comparing the emulator’s code against the published Smithy models, and files an issue for each gap it finds. Another group picks up an issue, writes tests, implements the behavior, and reviews the change for correctness, performance, and security. When the change is ready, it is pushed to a source repository, and that push triggers an AWS CodePipeline run that runs the fidelity tests before the change is published to the public GitHub repository.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;How we keep it secure&lt;/strong&gt;&lt;br&gt; Because the code is written by agents, an independent security agent reviews changes adversarially, both while the fix is being made and again in the release pipeline as a final check before anything ships.&lt;/p&gt; 
&lt;p&gt;Security of your own use remains a shared responsibility. We build the emulator to run safely on your machine: it listens only on your own computer by default and rejects requests that aren’t signed with its own keys. You decide where it runs, what data you put in it, and how you test before production. Don’t use the emulator to test whether your application is secure. It doesn’t evaluate &lt;a href="https://aws.amazon.com/iam/"&gt;AWS Identity and Access Management (IAM)&lt;/a&gt; policies and resource-based policies the way AWS does, so a request that AWS denies might succeed in the emulator. Keep real credentials out of the environment of your test jobs, and test your security settings and your whole application on AWS before you go to production.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Now available&lt;/strong&gt;&lt;br&gt; AWS Emulator is generally available today. It has no additional service fee. You pay only for AWS resources when you deploy on AWS. You can install it from RPM or Debian packages on Linux, run it in Docker on macOS and Windows, or build from source, and it works with the AWS SDKs and the AWS CLI once you set environment variables. At launch, it has some limits. It doesn’t evaluate IAM policies the way AWS does, and each emulator acts as a single account, with no cross-account or cross-Region behavior. How closely it matches AWS varies by service and feature. To see how well the emulator covers the services that you use, check the fidelity scores in the AWS Emulator documentation.&lt;/p&gt; 
&lt;p&gt;If you want to check regional availability, visit the &lt;a href="https://builder.aws.com/capabilities/?trk=f11c83db-08fa-4852-aa10-20185beeaef6&amp;amp;sc_channel=el"&gt;AWS Capabilities by Region&lt;/a&gt; page in AWS Builder Center. If you want to call APIs, search documentation, find regional availability, and check troubleshooting about this new feature, try using the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/getting-started-aws-mcp-server.html"&gt;AWS MCP Server&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/plugins.html"&gt;plugins&lt;/a&gt; with your preferred AI tool.&lt;/p&gt; 
&lt;p&gt;To get started, visit the &lt;a href="https://github.com/aws/aws-emulator"&gt;AWS Emulator repository on GitHub&lt;/a&gt; and see the AWS Emulator documentation.&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;Updated on November 12, 2026: Added links to the AWS Emulator repository on GitHub.&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: AgentCore Runtime V2, Amazon DynamoDB bulk put items, and more (November 9, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-agentcore-runtime-v2-amazon-dynamodb-bulk-put-items-and-more-november-9-2026/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Mon, 09 Nov 2026 17:55:26 +0000</pubDate>
				<category><![CDATA[Amazon Athena]]></category>
		<category><![CDATA[Amazon Aurora]]></category>
		<category><![CDATA[Amazon Bedrock]]></category>
		<category><![CDATA[Amazon Bedrock AgentCore]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon Elastic Container Registry]]></category>
		<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Amazon Inspector]]></category>
		<category><![CDATA[Amazon S3 Tables]]></category>
		<category><![CDATA[Amazon SageMaker Unified Studio]]></category>
		<category><![CDATA[Amazon Simple Notification Service (SNS)]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Direct Connect]]></category>
		<category><![CDATA[AWS Fargate]]></category>
		<category><![CDATA[AWS Glue]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[AWS Security Hub]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">92fb165d30993e71e0cdd70801398f45f9518c7d</guid>

					<description>Most of the cost of adopting something new isn’t the new thing, it’s the move. Moving a Hive table to Apache Iceberg has typically meant weeks of engineering work. Last week, Amazon S3 Tables turned that into three steps: start, sync as often as you need, complete. The source stays writable except for a few […]</description>
										<content:encoded>&lt;p&gt;Most of the cost of adopting something new isn’t the new thing, it’s the move. Moving a Hive table to Apache Iceberg has typically meant weeks of engineering work. Last week, &lt;a href="https://aws.amazon.com/s3/features/tables/"&gt;Amazon S3 Tables&lt;/a&gt; turned that into three steps: start, sync as often as you need, complete. The source stays writable except for a few minutes at cutover. The same week, &lt;a href="https://aws.amazon.com/dynamodb/"&gt;Amazon DynamoDB&lt;/a&gt; started loading data from S3 into tables that already exist.&lt;/p&gt; 
&lt;p&gt;The pattern I like is that neither one asks you to stop what’s running. That’s also the way to read the agent news this week. The new &lt;a href="https://aws.amazon.com/bedrock/agentcore/"&gt;Amazon Bedrock AgentCore&lt;/a&gt; Runtime is a single field on the runtime you already have, and Web Answer is a tool you attach to a gateway you already run. Now, let’s get into this week’s AWS news…&lt;/p&gt; 
&lt;p&gt;&lt;span id="more-106158"&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Headlines&lt;/strong&gt;&lt;br&gt; &lt;a href="https://aws.amazon.com/blogs/machine-learning/the-new-agentcore-runtime-elastic-optimized-and-consistently-fast-starts/"&gt;The new AgentCore Runtime: elastic, optimized, and consistently fast starts&lt;/a&gt; – If you run agents on AgentCore and haven’t tried the &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/new-agentcore-runtime-generally-available/"&gt;new runtime&lt;/a&gt; since it became generally available, it’s worth a look. It changes two things. First, memory: sessions start small, page in more on demand, and give memory back when it goes cold instead of holding the peak, so you pay for what your agent uses. Second, cold starts: AgentCore prepares your environment once, snapshots it, and restores the snapshot for every new instance. In the team’s tests, that kept P75 cold starts at about 2 seconds for images from 200 MB up to 2 GB, while the original runtime rose from roughly 5.4 seconds to nearly 30 seconds as images grew. The per-unit rate is higher, but you use far fewer GB-hours, so the team expects most agents to see a lower bill, though that isn’t guaranteed.&lt;/p&gt; 
&lt;p&gt;To opt in, you set &lt;code&gt;platformVersion&lt;/code&gt; to &lt;code&gt;V2&lt;/code&gt; when you create or update a runtime. Create and update take several minutes while the snapshot is prepared, and your container must report healthy on &lt;code&gt;/ping&lt;/code&gt; within 120 seconds, so report health only after initialization finishes. The docs cover &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-v2-optimize.html"&gt;how to optimize your agent for V2&lt;/a&gt;. V2 is available in &lt;a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-how-it-works.html#runtime-platform-versions"&gt;10 Regions&lt;/a&gt;, and committed baseline pricing is coming soon.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/aws/amazon-s3-tables-now-offer-managed-migration-of-apache-hive-tables-to-apache-iceberg/"&gt;Amazon S3 Tables now offer managed migration of Apache Hive tables to Apache Iceberg&lt;/a&gt; – You can now migrate Parquet tables registered in the &lt;a href="https://aws.amazon.com/glue/"&gt;AWS Glue&lt;/a&gt; Data Catalog into S3 Tables without building a pipeline or provisioning compute. S3 Tables validates the source and produces a compatibility report covering every object in scope. Each sync copies only what changed, so production keeps writing until cutover. Afterward you can query the table with &lt;a href="https://aws.amazon.com/athena/"&gt;Amazon Athena&lt;/a&gt;, &lt;a href="https://aws.amazon.com/sagemaker/unified-studio/"&gt;Amazon SageMaker Unified Studio&lt;/a&gt;, or any engine that speaks the Iceberg REST API. You pay only for the data copied, with no charge for the conversion, and objects in &lt;a href="https://aws.amazon.com/s3/storage-classes/intelligent-tiering/"&gt;S3 Intelligent-Tiering&lt;/a&gt; keep their tier. At launch it works within the same account and Region, in 10 Regions.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Last week’s launches&lt;/strong&gt;&lt;br&gt; Here are some launches and updates from this past week that caught my attention:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-dynamodb-now-supports-bulk-put-items/"&gt;Amazon DynamoDB now supports bulk put items&lt;/a&gt; – You can now load line-delimited DynamoDB JSON or Amazon Ion files from &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt; into existing tables as a managed, asynchronous job. Each record can carry its own condition expression, so one file can mix plain, insert-only, and version-guarded writes. Writes use dedicated system capacity and cost less than the equivalent per-request writes. An Accelerated tier handles deadline-bound jobs. The &lt;a href="https://aws.amazon.com/blogs/database/introducing-bulk-put-items-for-amazon-dynamodb-load-data-from-amazon-s3-into-existing-tables-at-scale/"&gt;Database blog post&lt;/a&gt; gives illustrative Accelerated times of less than 1 hour for 100 million 1 KB items. One thing to know before you start: canceling doesn’t roll back items already written.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/web-answer-amazon-bedrock/"&gt;Announcing Web Answer on Amazon Bedrock AgentCore&lt;/a&gt; – You can now give an agent a single tool call that returns a synthesized, cited answer to a natural-language question, instead of building your own search, retrieval, and citation pipeline. Web Answer plans its own searches, runs several in parallel, and decides when it has enough evidence. You attach it as a target on AgentCore Gateway and call it over MCP, and you can limit it with domain include and deny lists and publish-date filters. It’s available in US East (N. Virginia). The &lt;a href="https://aws.amazon.com/blogs/machine-learning/getting-started-with-web-answer-on-amazon-bedrock-agentcore/"&gt;getting started post&lt;/a&gt; explains when to use it instead of Web Search, which returns ranked results for your own model to synthesize.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-lambda-queue-kafka-esm/"&gt;AWS Lambda now supports queues for Apache Kafka in self-managed Kafka event sources&lt;/a&gt; – You can now process records from a single Kafka partition across many parallel &lt;a href="https://aws.amazon.com/lambda/"&gt;AWS Lambda&lt;/a&gt; invocations. Classic consumer groups cap parallelism at the partition count. Queue mode uses Kafka share groups and needs Kafka 4.2 or later with share groups enabled. It works with self-managed clusters and managed offerings such as Confluent Cloud. You give up ordering and get at-least-once delivery, so your functions need to be idempotent. The &lt;a href="https://aws.amazon.com/blogs/compute/introducing-queue-consumption-mode-for-apache-kafka-in-aws-lambda/"&gt;Compute blog walkthrough&lt;/a&gt; covers poller scaling and when to keep stream mode.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/interconnect-last-mile-preview-equinix/"&gt;AWS announces AWS Interconnect – last mile preview with Equinix&lt;/a&gt; – You can now set up a private, managed connection from Equinix’s network of 282 data centers to AWS without ordering cross-connects or configuring routers. Capacity is quad-redundant across two locations and four links, with BGP and VLANs configured for you, a 99.99% availability SLA, and MACsec by default. You pick a Region, bandwidth, and &lt;a href="https://aws.amazon.com/directconnect/"&gt;AWS Direct Connect&lt;/a&gt; gateway, then paste the activation key into Equinix Fabric. The preview covers the San Jose metro and, as of &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/interconnect-last-mile-northern-virginia/"&gt;last Thursday&lt;/a&gt;, Northern Virginia, with 1 Gbps connections at no charge.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/security-hub-sbom-inventory/"&gt;AWS Security Hub now provides an SBOM inventory for your compute resources&lt;/a&gt; – You can now see every software package installed across your organization’s &lt;a href="https://aws.amazon.com/ec2/"&gt;Amazon EC2&lt;/a&gt; instances, &lt;a href="https://aws.amazon.com/ecr/"&gt;Amazon ECR&lt;/a&gt; images, and Lambda functions in &lt;a href="https://aws.amazon.com/security-hub/"&gt;AWS Security Hub&lt;/a&gt;, with each package’s version and how many resources run it. That’s the list you want the next time a widely used library has a vulnerability. The inventory builds on the SBOMs that &lt;a href="https://aws.amazon.com/inspector/"&gt;Amazon Inspector&lt;/a&gt; already generates, so it fills in automatically wherever Inspector is enabled. It’s included in Security Hub Essentials at no additional cost.&lt;/p&gt; 
&lt;p&gt;For a full list of AWS announcements, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/new/"&gt;What’s New with AWS&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Other AWS news&lt;/strong&gt;&lt;br&gt; Here are some additional posts and resources that you might find interesting:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/compute/serverless-icymi-q3-2026/"&gt;Serverless ICYMI Q3 2026&lt;/a&gt; – Julian Wood’s quarterly recap is a quick serverless catch-up before re:Invent: Lambda SnapStart for container images, a 90-minute timeout on Lambda Managed Instances, Lambda MicroVMs in 10 Regions, 1 MiB payloads in &lt;a href="https://aws.amazon.com/sns/"&gt;Amazon SNS&lt;/a&gt;, and the new AgentCore Runtime.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/database/aws-contributes-a-large-transaction-binary-log-optimization-to-mysql/"&gt;AWS contributes a large-transaction binary log optimization to MySQL&lt;/a&gt; – With binlog on, a huge transaction holds a global commit lock while its events are copied, blocking every other commit. The optimization, which &lt;a href="https://aws.amazon.com/rds/aurora/"&gt;Amazon Aurora&lt;/a&gt; MySQL has run in production since 2019, promotes the spill file into the binlog instead of copying it. In AWS’s tests, commit latency for a 50 GiB transaction dropped from about 7 minutes to about 2 to 2.5 seconds. It has now shipped to community MySQL.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/architecture/how-orderserv-achieved-up-to-64-cost-savings-with-multi-tenant-ecs/"&gt;How OrderServ achieved up to 64% cost savings with multi-tenant ECS&lt;/a&gt; – Cognizant’s food-ordering platform went from one &lt;a href="https://aws.amazon.com/ecs/"&gt;Amazon ECS&lt;/a&gt; cluster per brand on &lt;a href="https://aws.amazon.com/fargate/"&gt;AWS Fargate&lt;/a&gt; to a shared cluster on EC2 Auto Scaling groups with warm pools. The 64% applies to a 3-year Compute Savings Plan (47% with a 1-year plan). Scaling time also fell from 5–7 minutes to 30–60 seconds.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Upcoming AWS events&lt;/strong&gt;&lt;br&gt; Check your calendar and sign up for upcoming AWS events:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/reinvent/"&gt;AWS re:Invent&lt;/a&gt; – re:Invent returns to Las Vegas from November 30 to December 4. The &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/eventcatalog/page/eventcatalog"&gt;event catalog&lt;/a&gt; is live and reserved seating is open, so &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/reg"&gt;register&lt;/a&gt; and claim your spots before they fill up.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt; – Community-led conferences planned and delivered by community leaders, with a few more before the year ends: &lt;a href="https://awscommunityday.com.br/#norte"&gt;Belém, Brazil&lt;/a&gt; (November 14), &lt;a href="https://jawsfesta2026.jaws-ug.jp/"&gt;JAWS FESTA 2026 in Akita, Japan&lt;/a&gt; (November 17), and &lt;a href="https://www.meetup.com/aws-womens-user-group-port-harcourt/events/316776385/"&gt;Port Harcourt, Nigeria&lt;/a&gt; (December 12).&lt;/p&gt; 
&lt;p&gt;Join the &lt;a href="https://builder.aws.com/build/capabilities?trk=f11c83db-08fa-4852-aa10-20185beeaef6&amp;amp;sc_channel=el"&gt;AWS Builder Center&lt;/a&gt; to connect with builders, share solutions, and access content that supports your development. Browse &lt;a href="https://aws.amazon.com/events/"&gt;here&lt;/a&gt; for upcoming AWS-led in-person and virtual events and developer-focused events.&lt;/p&gt; 
&lt;p&gt;That’s all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;– Daniel Abib&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Amazon S3 Tables now offer managed migration of Apache Hive tables to Apache Iceberg</title>
		<link>https://aws.amazon.com/blogs/aws/amazon-s3-tables-now-offer-managed-migration-of-apache-hive-tables-to-apache-iceberg/</link>
					
		
		<dc:creator><![CDATA[Channy Yun (윤석찬)]]></dc:creator>
		<pubDate>Wed, 04 Nov 2026 23:34:52 +0000</pubDate>
				<category><![CDATA[Amazon S3 Tables]]></category>
		<category><![CDATA[Analytics]]></category>
		<category><![CDATA[AWS Glue]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Storage]]></category>
		<guid isPermaLink="false">7d30dbf9b73fcfe8e471c3e83d1f2ee69b4b3343</guid>

					<description>You can now migrate existing Apache Hive datasets in Amazon S3 to fully managed Apache Iceberg tables in Amazon S3 Tables, with no pipelines to build or compute to provision, while production workloads keep running.</description>
										<content:encoded>&lt;p&gt;Today, we’re announcing a simple, cost-effective path for data lake modernization. &lt;a href="https://aws.amazon.com/s3/features/tables/"&gt;Amazon S3 Tables&lt;/a&gt; now support managed migration of your &lt;a href="https://hive.apache.org"&gt;Apache Hive&lt;/a&gt; tables to &lt;a href="https://iceberg.apache.org"&gt;Apache Iceberg&lt;/a&gt;. Migration works with Parquet tables in Amazon S3 that are registered in the &lt;a href="https://aws.amazon.com/glue"&gt;AWS Glue&lt;/a&gt; Data Catalog and allows you to upgrade your data lake with no pipelines to build or compute to provision, while production workloads keep running.&lt;/p&gt; 
&lt;p&gt;Apache Iceberg has become the open standard for large analytics datasets. It lets you manage petabyte-scale tables with features like schema evolution, hidden partitioning, and time travel queries, while keeping your data open and queryable with any Iceberg-compatible engine. Amazon S3 Tables offer fully managed storage purpose-built to keep Iceberg tables performant and cost-effective as they grow, with features like automatic maintenance, optimization, replication, and &lt;a href="https://aws.amazon.com/s3/storage-classes/intelligent-tiering/"&gt;S3 Intelligent-Tiering&lt;/a&gt; built-in.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;What is new&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Previously, migrating Apache Hive tables to Apache Iceberg could take weeks of engineering work to build and manage the required infrastructure. Converting data types and building rollback capabilities added operational complexity. Now, this is available as a managed, API-driven operation.&lt;/p&gt; 
&lt;p&gt;S3 Tables handle the entire migration workflow, including data validation, compatibility checks, type conversions, file recompression, and compaction. Before copying any data, S3 Tables identify every source object in scope and generate a compatibility report. You can sync as many times as you need without stopping writes to your source table, except for a few minutes during cutover. Once you are ready, you can complete the migration, minimizing time that tables are offline.&lt;/p&gt; 
&lt;p&gt;Compared to self-managed approaches, S3 Tables managed migrations are cost-effective because you pay only for the data copied, with no charge for the Hive-to-Iceberg conversion, and source objects in S3 Intelligent-Tiering stay in their current access tier.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;A first look at the migration&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; To migrate an AWS Glue Hive table, choose your destination table bucket in the &lt;a href="https://console.aws.amazon.com/s3"&gt;S3 console&lt;/a&gt;, then choose &lt;strong&gt;Create table from migration&lt;/strong&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105694" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/20/2026-s3-tables-hive-to-iceberg-1.jpg" alt="" width="1800" height="972"&gt;&lt;/p&gt; 
&lt;p&gt;Create a namespace and table name for your destination Iceberg table. The destination table is created using recommended default settings tuned for query performance and storage efficiency.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-106134 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/30/2026-s3-tables-hive-to-iceberg-2.jpg" alt="" width="1749" height="2560"&gt;&lt;/p&gt; 
&lt;p&gt;When you start the migration, S3 Tables validate the source table, generate a compatibility report, and begin copying data. The destination table is read-only during the migration. Once you complete migration, the destination table is promoted to read-write.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-105984 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/12/2026-s3-tables-hive-to-iceberg-3.jpg" alt="" width="1800" height="1003"&gt;&lt;/p&gt; 
&lt;p&gt;You can begin working with your data right away using a direct integration with &lt;a href="https://aws.amazon.com/athena"&gt;Amazon Athena&lt;/a&gt; and &lt;a href="https://aws.amazon.com/sagemaker/unified-studio/"&gt;Amazon SageMaker Unified Studio&lt;/a&gt; in the AWS console, or use any tool compatible with the Apache Iceberg REST API to directly query the tables. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-migrate.html"&gt;S3 Tables migration documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;You can also use &lt;a href="https://aws.amazon.com/cli"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/sdkref/latest/guide/version-support-matrix.html"&gt;AWS SDKs&lt;/a&gt;, or the &lt;a href="https://aws.amazon.com/products/developer-tools/agent-toolkit-for-aws/"&gt;Agent Toolkit for AWS&lt;/a&gt;. For example, set up migration jobs and call the &lt;code class="lang-bash"&gt;start-table-migration&lt;/code&gt; command.&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;cat &amp;gt; /tmp/start-migration.json &amp;lt;&amp;lt;'EOF'
{
  "roleARN": "arn:aws:iam::123456789012:role/S3TablesMigrationRole",
  "destinationTable": {
    "tableBucketARN": "arn:aws:s3tables:us-east-1:123456789012:bucket/my-destination-bucket",
    "namespace": "mynamespace",
    "name": "my_destination_table",
    "encryptionConfiguration": {
      "sseAlgorithm": "aws:kms",
      "kmsKeyArn": "arn:aws:kms:us-east-1:123456789012:key/1234abcd-12ab-34cd-56ef-1234567890ab"
    },
    "storageClassConfiguration": { "storageClass": "INTELLIGENT_TIERING" },
    "tags": { "team": "s3tables", "purpose": "migration" },
    "properties": {
      "writeFormat": "parquet",
      "icebergFormatVersion": 2,
      "compressionCodec": "zstd",
      "dictionaryEncoding": true
    },
    "schema": {
      "type": "struct",
      "schemaId": 0,
      "identifierFieldIds": [1],
      "fields": [
        { "id": 1, "name": "id",      "type": "long",   "required": true, "doc": "primary key" },
        { "id": 2, "name": "payload", "type": "string", "required": false }
      ]
    },
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"icebergSortOrder": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"orderId": 1,
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"fields": [ { "sourceId": 1, "transform": "identity", "direction": "asc", "nullOrder": "nulls-first" } ]
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}
&amp;nbsp;&amp;nbsp;},
&amp;nbsp;&amp;nbsp;"sourceType": "glueTable",
  "source": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"glueTable": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"catalogId": "123456789012",
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"databaseName": "my_glue_database",
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"tableName": "my_source_table"
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}
&amp;nbsp;&amp;nbsp;},
&amp;nbsp;&amp;nbsp;"dataMigration": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"maintenanceSettings": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"icebergCompaction": { "targetFileSizeMB": 512, "strategy": "binpack" },
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"icebergSnapshotManagement": { "minSnapshotsToKeep": 3, "maxSnapshotAgeHours": 168 }
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;},
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"migrationPolicies": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"unmatchedSourceFieldsPolicy": "fail",
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"incompatibleValuesPolicy": "fail"
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}
&amp;nbsp;&amp;nbsp;},
&amp;nbsp;&amp;nbsp;"reviewMigrationPlan": false,
&amp;nbsp;&amp;nbsp;"migrationOutput": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"bucket": "arn:aws:s3:::my-report-bucket",
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"prefixes": {
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"tableCompatibilityReport": "reports/table-compatibility/",
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"objectCompatibilityReport": "reports/object-compatibility/",
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;"objectMigrationReport": "reports/object-migration/"
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;}
&amp;nbsp;&amp;nbsp;}
}
EOF

aws s3tables start-table-migration \
&amp;nbsp;&amp;nbsp;--cli-input-json file:///tmp/start-migration.json&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;To catch up the destination table with changes in the source, call &lt;code&gt;sync-table-migration&lt;/code&gt; as many times as you need before you complete the migration. Each sync copies only what changed.&lt;/p&gt; 
&lt;p&gt;If you’re using coding agents like &lt;a href="https://kiro.dev"&gt;Kiro&lt;/a&gt;, the &lt;code&gt;migrating-hive-tables-to-s3-tables&lt;/code&gt; skill in the Agent Toolkit for AWS provides step-by-step migration guidance with safety guardrails for agents. The skill can:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Analyze existing IAM policies and recommend equivalent destination policies&lt;/li&gt; 
 &lt;li&gt;Validate the migration plan before getting started&lt;/li&gt; 
 &lt;li&gt;Execute the Start → Sync → Complete API calls&lt;/li&gt; 
 &lt;li&gt;Monitor job progress and guide validation and cutover&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;To learn more, visit the &lt;a href="https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/analytics-skills/migrating-hive-tables-to-s3-tables"&gt;GitHub README page for the skill&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Now available&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Amazon S3 Tables managed migration is available today in US East (N. Virginia, Ohio), US West (Oregon), Asia Pacific (Mumbai, Singapore, Sydney, Tokyo), and Europe (Frankfurt, Ireland, Stockholm) Regions. At launch, the capability supports AWS Glue-registered Hive tables stored in Parquet format within the same AWS account and AWS Region. If you want to call APIs, search documentation, find regional availability, or troubleshoot about this new feature, try using the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/getting-started-aws-mcp-server.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el" target="_blank" rel="noopener noreferrer"&gt;AWS MCP Server&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/plugins.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el" target="_blank" rel="noopener noreferrer"&gt;plugins&lt;/a&gt; with your preferred AI tool.&lt;/p&gt; 
&lt;p&gt;Try it in the &lt;a href="https://console.aws.amazon.com/s3?trk=769a1a2b-8c19-4976-9c45-b6b1226c7d20&amp;amp;sc_channel=el"&gt;Amazon S3 console&lt;/a&gt; today and send feedback to &lt;a href="https://repost.aws/tags/TADSTjraA0Q4-a1dxk6eUYaw/amazon-simple-storage-service"&gt;AWS re:Post for Amazon S3&lt;/a&gt; or through your usual AWS Support contacts.&lt;/p&gt; 
&lt;p&gt;— &lt;a href="https://linkedin.com/in/channy/"&gt;Channy&lt;/a&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: GPT-6.1 Terra on Bedrock, Step Functions as agent tools, and more (November 2, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-gpt-6-1-terra-on-bedrock-step-functions-as-agent-tools-and-more-november-2-2026/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Mon, 02 Nov 2026 16:45:48 +0000</pubDate>
				<category><![CDATA[Amazon Aurora]]></category>
		<category><![CDATA[Amazon Bedrock]]></category>
		<category><![CDATA[Amazon Bedrock AgentCore]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon Elastic Container Registry]]></category>
		<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Amazon Elastic Kubernetes Service]]></category>
		<category><![CDATA[Amazon SageMaker AI]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Certificate Manager]]></category>
		<category><![CDATA[AWS Fault Injection Service (FIS)]]></category>
		<category><![CDATA[AWS IAM Identity Center]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[AWS Key Management Service]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[AWS re:Invent]]></category>
		<category><![CDATA[AWS Step Functions]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">a75ee10f33f51c28e1b3189dc509cb78f1c8eaa7</guid>

					<description>The agentic launches that stayed with me last week had nothing to do with how capable a model is. They were about reach. AWS Step Functions, which already orchestrates over 220 AWS services, can now be handed to an agent as a tool, so workflows teams already trust became callable without a rewrite. In the […]</description>
										<content:encoded>&lt;p&gt;The agentic launches that stayed with me last week had nothing to do with how capable a model is. They were about reach. &lt;a href="https://aws.amazon.com/step-functions/"&gt;AWS Step Functions&lt;/a&gt;, which already orchestrates over 220 AWS services, can now be handed to an agent as a tool, so workflows teams already trust became callable without a rewrite. In the same week, the AI blog published how one engagement platform exposed roughly 400 internal API operations the same way. Neither story involves rebuilding anything, only describing what exists and letting the agent find it.&lt;/p&gt; 
&lt;p&gt;The other thread was cost. OpenAI’s newest Terra model reached &lt;a href="https://aws.amazon.com/bedrock/"&gt;Amazon Bedrock&lt;/a&gt; priced well below the model beside it, and two post-quantum launches landed for a deadline nobody can put on a calendar yet. Now, let’s get into this week’s AWS news…&lt;/p&gt; 
&lt;p&gt;&lt;span id="more-106136"&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Headlines&lt;/strong&gt;&lt;br&gt; &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/openai-gpt-6-1-terra-on-amazon-bedrock/"&gt;OpenAI GPT-6.1 Terra is now generally available on Amazon Bedrock&lt;/a&gt;, and what interests me is where it sits rather than what it tops. Terra is the everyday-workload line of the GPT-6 family. In OpenAI’s Agents’ Last Exam evaluation it scored 15 percentage points higher than GPT-5.6 Terra, performed on par with GPT-6 Astra, and completed tasks more than three times faster than both. Those are OpenAI’s figures, not an independent test. The price is what I would check first: input and output tokens are at least 50% lower than GPT-6.1 Sol and GPT-5.6 Terra. It takes up to 1 million input tokens with text and image input, and you can reach it from the Bedrock APIs or ChatGPT Work and Codex.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/step-functions-workflows-ai-agent-tools/"&gt;AWS Step Functions workflows are now available as AI agent tools&lt;/a&gt; through &lt;a href="https://aws.amazon.com/bedrock/agentcore/"&gt;Amazon Bedrock AgentCore&lt;/a&gt; Gateway, which connects agents to tools over the Model Context Protocol (MCP). The division of labor is the idea: the agent decides when to run a workflow and what input to pass; Step Functions runs each step exactly as you defined it. A support agent can trigger a refund, and the eligibility check, the manager approval, and the credit still happen in that order every time, because the ordering was never the model’s to improvise. Your existing Standard and Express workflows qualify as connector targets, and agents can also look up runs. It’s available in all Regions where AgentCore Gateway is, at standard rates.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Last week’s launches&lt;/strong&gt;&lt;br&gt; Here are some launches and updates from this past week that caught my attention:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/kms-ml-kem-post-quantum/"&gt;AWS Key Management Service now supports ML-KEM for post-quantum key encapsulation&lt;/a&gt; – You can now establish a shared secret with a post-quantum algorithm using &lt;a href="https://aws.amazon.com/kms/"&gt;AWS KMS&lt;/a&gt; keys, with private keys in FIPS 140-3 Level 3 validated HSMs. All three NIST FIPS 203 parameter sets are supported through &lt;code&gt;Encapsulate&lt;/code&gt;, which produces a random 32-byte shared secret and its ciphertext, and &lt;code&gt;Decapsulate&lt;/code&gt;, which recovers it. The threat is harvest now, decrypt later: an adversary records today’s key exchange and recovers the secret once quantum computers are powerful enough. It’s available everywhere KMS runs except the Middle East (UAE and Bahrain) and China Regions. &lt;a href="https://aws.amazon.com/rds/aurora/"&gt;Amazon Aurora&lt;/a&gt; PostgreSQL added &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aurora-postgresql-post-quantum-tls-key-exchange/"&gt;post-quantum TLS key exchange&lt;/a&gt; the same week, on versions 18 and higher.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-iam-identity-center-cross-region-tip/"&gt;AWS IAM Identity Center now supports cross-Region trusted identity propagation&lt;/a&gt; – You can now carry a user’s identity with their request to AWS services in another Region. This removes a genuine architectural constraint: trusted identity propagation used to require every service accessing that identity to sit in the same Region, which left two unappealing options, broad &lt;a href="https://aws.amazon.com/iam/"&gt;IAM&lt;/a&gt; roles that cannot distinguish individual users, or consolidating all your services into a single Region. Now the identity travels with the request automatically, so you grant access by user and group membership and audit who accessed what. It’s available at no additional cost everywhere &lt;a href="https://aws.amazon.com/iam/identity-center/"&gt;IAM Identity Center&lt;/a&gt; runs.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-ecs-gpu-sharing-nvidia-mps/"&gt;Amazon ECS now supports GPU sharing with NVIDIA Multi-Process Service (MPS)&lt;/a&gt; – You can now run multiple &lt;a href="https://aws.amazon.com/ecs/"&gt;Amazon ECS&lt;/a&gt; tasks concurrently on a single NVIDIA GPU, the practical answer to work that only ever uses a fraction of one, like small-model inference and multi-model serving. You declare the GPU memory each container needs and can optionally cap its share of GPU compute, and ECS places tasks on GPUs with available capacity as your services scale, with no code changes. It works on ECS Managed Instances and ECS on &lt;a href="https://aws.amazon.com/ec2/"&gt;Amazon EC2&lt;/a&gt;, and on Managed Instances it watches the MPS control daemon and replaces the instance if it turns unhealthy. It’s available in all commercial and AWS GovCloud (US) Regions.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-lambda-seekable-oci-soci/"&gt;AWS Lambda supports Seekable OCI (SOCI) lazy loading for Lambda Managed Instances&lt;/a&gt; – You can now have &lt;a href="https://aws.amazon.com/lambda/"&gt;AWS Lambda&lt;/a&gt; fetch only the files needed at each stage of startup instead of pulling a whole container image first, which AWS puts at up to 70% off container startup time. You create a SOCI index, push it to &lt;a href="https://aws.amazon.com/ecr/"&gt;Amazon ECR&lt;/a&gt;, point the image URI at the indexed tag, and Lambda detects it automatically. The technique also &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/sagemaker-ai-soci-images-training/"&gt;reached&lt;/a&gt; &lt;a href="https://aws.amazon.com/sagemaker-ai/"&gt;Amazon SageMaker AI&lt;/a&gt; training and processing jobs, with &lt;a href="https://aws.amazon.com/blogs/machine-learning/announcing-soci-indexed-images-for-faster-sagemaker-ai-jobs/"&gt;benchmarks&lt;/a&gt;: lazy loading held at 3 to 11 seconds regardless of image size, against a median 3 minutes 42 seconds for a 13.2 GB image, a range they report as 8x to 46x.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-eks-auto-mode-kubernetes-gateway-api/"&gt;Amazon EKS Auto Mode now supports Kubernetes Gateway API&lt;/a&gt; – You can now declare how traffic reaches your applications with Gateway and HTTPRoute resources on &lt;a href="https://aws.amazon.com/eks/"&gt;Amazon EKS&lt;/a&gt; without installing a separate controller, and EKS Auto Mode provisions and manages the underlying AWS load balancing infrastructure. You get HTTP and gRPC routing, cross-namespace routing, weighted traffic splitting, header-based routing, and automatic TLS certificate discovery through &lt;a href="https://aws.amazon.com/certificate-manager/"&gt;AWS Certificate Manager&lt;/a&gt;. Existing Ingress workloads keep working alongside them, so this is additive rather than a migration. Gateway API support is included with EKS Auto Mode; standard load balancing charges apply.&lt;/p&gt; 
&lt;p&gt;For a full list of AWS announcements, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/new/"&gt;What’s New with AWS&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Other AWS news&lt;/strong&gt;&lt;br&gt; Here are some additional posts and resources that you might find interesting:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/mt/how-nubank-automated-disaster-recovery-with-the-aws-devops-agent/"&gt;How Nubank automated disaster recovery with the AWS DevOps Agent&lt;/a&gt; – Nubank serves more than 140 million customers across Brazil, Mexico, and Colombia, and classifies over 300 business flows as critical, each tested on a regulator’s schedule. Nubank reports that handing evidence collection and report writing to the &lt;a href="https://aws.amazon.com/devops-agent/"&gt;AWS DevOps Agent&lt;/a&gt; cut a test cycle from about 4.3 hours to roughly 40 minutes, and quadrupled flow coverage in 2026 to more than 160. One execution terminated more than 900 EKS instances under synthetic traffic with &lt;a href="https://aws.amazon.com/fis/"&gt;AWS Fault Injection Service&lt;/a&gt;, producing the evidence its regulator needed.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/how-moengage-turned-over-400-apis-into-agent-tools-with-agentcore-gateway/"&gt;How MoEngage turned over 400 APIs into agent tools with AgentCore Gateway&lt;/a&gt; – Roughly 400 internal REST API operations, built by 25 teams, sitting in private VPCs across seven Regions, with tenant identity that could never become a parameter the model gets to set. MoEngage estimates the managed path saved about six months of platform engineering. The detail worth stealing: a full tool listing would have crossed 20,000 tokens per connection, so agents search for tools by describing a task instead of receiving the catalog.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/storage/reducing-petabyte-scale-s3-storage-costs-with-evidence-based-lifecycle-rules/"&gt;Reducing petabyte-scale S3 storage costs with evidence-based lifecycle rules&lt;/a&gt; – The hard part isn’t deciding to act, it’s knowing which data has gone cold and where it can safely live. This uses S3 Storage Lens groups and Storage Class Analysis to prove access patterns before moving anything. In the engagement described, 5.8 PB of logs in &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt; Standard at approximately $241,000 per month showed an access ratio below 0.1% past 90 days, and a 90-day transition to Glacier Instant Retrieval cut the bill by roughly 70%, a figure the author ties to that workload.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Upcoming AWS events&lt;/strong&gt;&lt;br&gt; Check your calendar and sign up for upcoming AWS events:&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/reinvent/"&gt;AWS re:Invent&lt;/a&gt; – re:Invent returns to Las Vegas from November 30 to December 4, with more than 2,200 sessions. The &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/eventcatalog/page/eventcatalog"&gt;event catalog&lt;/a&gt; is live and reserved seating is open, so &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/reg"&gt;register&lt;/a&gt; and claim your spots before they fill up.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt; – Community-led conferences planned and delivered by community leaders. The 2026 season is winding down as re:Invent approaches, so check the hub for what’s still on.&lt;/p&gt; 
&lt;p&gt;Join the &lt;a href="https://builder.aws.com/build/capabilities?trk=f11c83db-08fa-4852-aa10-20185beeaef6&amp;amp;sc_channel=el"&gt;AWS Builder Center&lt;/a&gt; to connect with builders, share solutions, and access content that supports your development. Browse &lt;a href="https://aws.amazon.com/events/"&gt;here&lt;/a&gt; for upcoming AWS-led in-person and virtual events and developer-focused events.&lt;/p&gt; 
&lt;p&gt;That’s all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;– Daniel Abib&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: Amazon Polly Generative engine, TorchNeuron for Trainium, and more (October 26, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-amazon-polly-generative-engine-torchneuron-for-trainium-and-more-october-26-2026/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Mon, 26 Oct 2026 15:02:24 +0000</pubDate>
				<category><![CDATA[Amazon Bedrock]]></category>
		<category><![CDATA[Amazon Bedrock AgentCore]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Amazon Elastic File System (EFS)]]></category>
		<category><![CDATA[Amazon ElastiCache]]></category>
		<category><![CDATA[Amazon Polly]]></category>
		<category><![CDATA[Amazon SageMaker AI]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Cloud Financial Management]]></category>
		<category><![CDATA[AWS DataSync]]></category>
		<category><![CDATA[AWS Neuron]]></category>
		<category><![CDATA[AWS Trainium]]></category>
		<category><![CDATA[AWS WAF]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[RDS for Oracle]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">da6ca251ec6556de7daf75747bcf2af4e10a86a5</guid>

					<description>A few weeks ago I presented to a small group of commercial and technology leaders from Brazilian agribusiness at the AWS office in São Paulo. My talk ran through where generative AI fits across the different stages of an agribusiness operation, and the point I kept returning to is that the markets we call traditional […]</description>
										<content:encoded>&lt;p&gt;A few weeks ago I presented to a small group of commercial and technology leaders from Brazilian agribusiness at the AWS office in São Paulo. My talk ran through where generative AI fits across the different stages of an agribusiness operation, and the point I kept returning to is that the markets we call traditional are exactly the ones where keeping up with this technology decides who ends up ahead of the curve. Nobody there was arguing about whether AI belongs in agriculture. The questions were about delivery: who receives the output, in which language, on which device, often while driving between farms. That is why a launch I might otherwise have filed under routine leads my list this week. The &lt;a href="https://aws.amazon.com/polly/"&gt;Amazon Polly&lt;/a&gt; Generative engine upgrade added 14 new voices, two of them in Brazilian Portuguese. When your user has both hands on a steering wheel, the interface is a voice.&lt;/p&gt; 
&lt;p&gt;&lt;img style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/23/genai-agronegocio-speaker-crop-1280.jpg" alt="Presenting a session titled GenAI no Agronegocio Brasileiro to a group of agribusiness leaders seated around a boardroom table at the AWS office in Sao Paulo"&gt;&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;Presenting “GenAI no Agronegócio Brasileiro” at the AWS office in São Paulo.&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;The rest of the week had a sharper edge. The biggest launch is a security service built on the premise that the gap between a vulnerability being disclosed and a vulnerability being exploited has effectively closed, and AWS published the honeypot evidence for exactly that in the same week. Now, let’s get into this week’s AWS news…&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;AWS Continuum for code vulnerabilities is now generally available&lt;/strong&gt;&lt;br&gt; AWS Continuum reframes vulnerability management as an end-to-end job rather than a scanner that hands you a list. It builds a context graph from your repositories and your AWS environment, assigns each finding an evidence level, and reproduces exploitable findings in an isolated sandbox with proof-of-concept code so you see the issue rather than a severity label. It ranks issues by how close the attack path runs to business-critical systems, then opens the fix as a pull request. The control boundary matters: every remediation currently requires human approval, so you review and merge the pull request, with autonomous classes of fix gated behind confidence thresholds for the future.&lt;/p&gt; 
&lt;p&gt;The “why now” came from AWS’s own honeypots in the same week. Amazon Threat Intelligence found a &lt;a href="https://aws.amazon.com/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/"&gt;PHP2Shell exploitation attempt in MadPot telemetry&lt;/a&gt; dated October 17, four days before CVE-2026-109618 and CVE-2026-109619 were publicly disclosed, and on disclosure day proof-of-concept exploits were circulating around 02:00 UTC, roughly twelve hours before the embargo was due to lift at 14:00 UTC. The practical reading is direct: a patch window measured in days assumes a delay that no longer exists, and an investigation should start from the earliest known exploitation rather than from the disclosure date. AWS also published the &lt;a href="https://aws.amazon.com/blogs/security/using-aws-waf-to-apply-mitigations-for-php2shell-rce-vulnerabilities-cve-2026-109618-and-cve-2026-109619/"&gt;AWS WAF mitigations&lt;/a&gt; for the same CVEs. Continuum is available in US East (N. Virginia) and US West (Oregon).&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Introducing Amazon ECS Gateway&lt;/strong&gt;&lt;br&gt; Amazon ECS Gateway splits the work of exposing a service between the people who own the network and the people who own the application. Platform teams define one gateway with the organization’s subnets, security groups, TLS certificates, listener settings, and AWS WAF web ACLs. Application teams opt in by adding a gateway connector to the service definition, and ECS gives them an ACM certificate, a unique DNS hostname, listener rules, a target group, and a security group that admits traffic only from the Application Load Balancer.&lt;/p&gt; 
&lt;p&gt;The numbers make the economics clear: up to 25 services share a single ALB, ECS provisions the first ALB on first connect and removes ALBs when they are no longer needed, and a gateway can associate with up to 10,000 clusters, with five gateways per cluster. You can adopt it incrementally with UpdateService while your existing load balancer stays in place. Amazon ECS Gateway is available in all commercial Regions where Amazon ECS is available, at no additional charge.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Last week’s launches&lt;/strong&gt;&lt;br&gt; Here are some launches that caught my attention this week.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/amazon-polly-delivers-a-major-upgrade-to-its-generative-engine/"&gt;Amazon Polly delivers a major upgrade to its Generative engine&lt;/a&gt; – The Generative engine now runs a larger, more expressive catalog: 57 generative voices across 11 languages and 25 locales, with 14 new voices across 9 locales and Hindi and Finnish generally available for the first time. Two of the new voices are Brazilian Portuguese, Leo and Carolina. It is a drop-in upgrade, so the voice names, the same SynthesizeSpeech call, and the price all stay the same while the output gets more natural.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-announce-native-pytorch-support-trainium"&gt;AWS announces TorchNeuron: native PyTorch support for AWS Trainium (public beta)&lt;/a&gt; – TorchNeuron is an open source PyTorch backend that lets you run your model on Trainium by switching to .to(‘neuron’), a configuration change instead of a rewrite, with eager execution and torch.compile intact. It integrates with the Neuron Kernel Interface for custom operators, and it works on Trainium2 and Trainium3 instances. If you want the bigger picture on why hardware choice should not lock in your software, the &lt;a href="https://aws.amazon.com/blogs/aws-insights/your-last-hardware-decision-shouldnt-decide-what-you-build-next/"&gt;AWS Insights piece on that theme&lt;/a&gt; is a good companion read, and the release lands alongside &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-announce-neuron-2-33-0"&gt;AWS Neuron 2.33&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/announcing-new-ways-to-customize-models-with-sagemaker-ai-without-managing-gpus/"&gt;New ways to customize models with Amazon SageMaker AI, without managing GPUs&lt;/a&gt; – Training sessions are now generally available, giving you control of the post-training loop, including custom loss functions and reward signals, while SageMaker AI handles GPU allocation, distributed execution, fault recovery, and checkpoint storage. You pay for the tokens SageMaker AI processes, and the meter stops while your reward function scores a batch. There is a &lt;a href="https://aws.amazon.com/blogs/machine-learning/write-your-own-training-loop-without-managing-gpus-with-amazon-sagemaker-training-sessions/"&gt;full technical walkthrough&lt;/a&gt;, the &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/training-session-apis-on-sagemaker-ai"&gt;training session APIs&lt;/a&gt;, and new support for &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-sagemaker-muse-qwen-ministral/"&gt;Muse Glimmer, Qwen 3.8, and Ministral 3&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/claude-structured-outputs-bedrock/"&gt;Structured outputs for Claude models available on Amazon Bedrock&lt;/a&gt; – You can now get schema-compliant JSON back from any Anthropic Claude model on Amazon Bedrock, across both the bedrock-runtime and bedrock-mantle endpoints, without custom parsing, retry logic, or post-processing. That makes jobs like pulling every required field from a financial report, parsing clinical notes, or routing support tickets by intent far more reliable to automate.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-elasticache-serverless-valkey-online-migration/"&gt;Amazon ElastiCache Serverless for Valkey now supports online migration with zero downtime&lt;/a&gt; – You can migrate self-managed Valkey or Redis OSS on Amazon EC2 into ElastiCache Serverless with zero downtime, meaning zero errors returned to the client during the move, measured the way the ElastiCache SLA measures availability. You prepare the migration, start the data sync, then choose a manual or automatic cutover, with no third-party replication tools. It is available in all commercial Regions, the China Regions, and the AWS GovCloud (US) Regions.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Other AWS news&lt;/strong&gt;&lt;br&gt; Here are some additional projects and posts that you might find interesting.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/discover-tools-at-runtime-with-aws-agent-registry/"&gt;Discover tools at runtime with AWS Agent Registry&lt;/a&gt; – AWS Agent Registry is a managed catalog for MCP servers, agents, and agent skills, so an orchestrator can search approved capabilities at runtime instead of compiling every tool in at build time. This walkthrough shows the discover, instantiate, and execute loop in a working sample, with search results that return connection metadata but never invocation credentials.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/aws-cloud-financial-management/tokenomics-for-coding-agents-benchmark-cost-and-quality-on-your-own-code/"&gt;Tokenomics for coding agents: benchmark cost and quality on your own code&lt;/a&gt; – Coding assistants replay a growing transcript on every turn, so their cost math is nothing like ordinary inference. This post gives you open source tooling to measure model, harness, and hosting choices on your own repositories and build a cost-and-quality frontier you own, with sample results where routing came out 44.7 percent cheaper for 4.8 percent lower mean quality.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/blogs/database/how-u-s-bank-migrated-119-tb-from-oracle-exadata-to-amazon-rds-for-oracle/"&gt;How U.S. Bank migrated 119 TB from Oracle Exadata to Amazon RDS for Oracle&lt;/a&gt; – U.S. Bank moved four Oracle Exadata databases totaling about 119 TB to Amazon RDS for Oracle using a config-driven pipeline built on Oracle XTTS, AWS DataSync, and Amazon EFS. The initial baseline copy finished in about 7 days with zero data loss and cutovers averaging roughly four hours per database, over a bandwidth-capped Direct Connect link.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Upcoming AWS events&lt;/strong&gt;&lt;br&gt; Mark your calendars for these upcoming events.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://reinvent.awsevents.com/"&gt;AWS re:Invent&lt;/a&gt; – AWS re:Invent runs November 30 to December 4 in Las Vegas, with more than 2,200 sessions. The session catalog is live and reserved seating is open, so now is the time to build your schedule.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt; – AWS Community Day Brasil Norte takes place in Belém on October 31, closing out the 2026 Brazilian community season. Check the hub for events near you.&lt;/p&gt; 
&lt;p&gt;That’s all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;– Daniel&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Continuum for code vulnerabilities is now generally available</title>
		<link>https://aws.amazon.com/blogs/aws/aws-continuum-for-code-vulnerabilities-is-now-generally-available/</link>
					
		
		<dc:creator><![CDATA[Esra Kayabali]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 20:33:10 +0000</pubDate>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Security, Identity, & Compliance]]></category>
		<guid isPermaLink="false">7ce6bf5eb7b5d26b8ad5cb6ced771ac43468759d</guid>

					<description>AWS Continuum for code vulnerabilities is a new security service that uses AI to automatically find, validate, and prioritize code vulnerabilities in your environment, then delivers ready-to-review fixes as pull requests replacing what previously took hours of manual investigation and days of cross-team coordination.</description>
										<content:encoded>&lt;p&gt;Today, we’re announcing the general availability of &lt;a href="https://aws.amazon.com/continuum/"&gt;AWS Continuum for code vulnerabilities&lt;/a&gt;. AWS Continuum is a security service that finds and validates code vulnerabilities, then delivers fixes as patches you can automate or as pull requests in your repositories. AWS Continuum for code vulnerabilities confirms which findings are exploitable in your environment, ranks the resulting issues by business impact, and proposes a fix for each one. Every remediation starts in a mode where Continuum proposes the fix and a person approves it before it ships. In the future, you will be able to decide which actions Continuum can take on its own, within the guardrails you define.&lt;/p&gt; 
&lt;p&gt;Using frontier artificial intelligence (AI) models, threat actors can turn a vulnerability disclosure into working exploit code in minutes, and the same tools that speed up development also increase the volume of findings your teams must process. If your organization runs a large application estate, your scanners likely produce thousands of findings a day, and many of them need no action. A finding can be unreachable, unexploitable, or already mitigated by a runtime control. Generic severity scores don’t tell you which resources a threat actor can actually reach, so a critical score on a dev-only utility looks the same as a medium score on a service one step away from a payments database. Previously, confirming whether a finding was exploitable took hours of manual investigation, and shipping a fix with confidence took days of coordination across security, infrastructure, and application teams, because the blast radius of a change is hard to assess without business context. To close that gap, Continuum proves which findings are exploitable and bounds the risk of each fix it proposes.&lt;/p&gt; 
&lt;p&gt;Continuum builds a context graph from two primary sources: your code repositories and your AWS environment. For AWS, you set up a collector in the account and Region where your code runs. The collector gathers resource details such as AWS Config resources and network configuration so Continuum can judge whether a vulnerability is reachable over the network and what a threat actor could reach from it. From this graph, Continuum learns which systems are business-critical, who owns them, how services depend on one another, and which data each one touches. It uses that picture to identify your highest-value systems, such as customer data stores, payment pipelines, and authentication services, and then ranks each resulting issue by how close its attack path runs to those systems.&lt;/p&gt; 
&lt;p&gt;Continuum analyzes each finding against your code and its environment context and assigns an evidence level, such as a verdict proven by static analysis of the vulnerable code path. For findings it can reproduce, Continuum runs the exploit in an isolated sandbox and attaches proof-of-concept code with the reproduction steps. It produces the attack path, the supporting source analysis, and a blast radius assessment instead of a risk score alone. It also evaluates whether your existing defenses would detect and stop the validated path.&lt;/p&gt; 
&lt;p&gt;For each confirmed issue, Continuum generates a fix (a code patch, a dependency upgrade, or a configuration change) and opens it as a pull request in your connected repository, ready to review. Every fix requires human approval: you review and merge the pull request, so the final decision stays with your team. In the future, you will be able to build confidence in specific remediation classes and let Continuum apply those fixes automatically once its confidence gates pass, such as test coverage, scope bounds, and historical success rate.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;AWS Continuum for code vulnerabilities in action&lt;br&gt; &lt;/strong&gt;&lt;/span&gt;To show how this works, I open &lt;a href="https://console.aws.amazon.com/continuum/home"&gt;AWS Continuum&lt;/a&gt; in the console and go to &lt;strong&gt;Code vulnerabilities&lt;/strong&gt;. Before I can review issues, I set up an environment. I connect a code source, either a GitHub integration or an Amazon S3 bucket, and then create an environment that scans it on a schedule I choose. An Amazon S3 source has a couple of prerequisites: the bucket sits in the same account and AWS Region where I turn on AWS Continuum, and I grant access through an AWS Identity and Access Management (IAM) role that AWS Continuum assumes. I can optionally add AWS infrastructure context by setting up an AWS Continuum collector in the account and Region where my code runs and authorizing my environment to use it. For the full requirements and steps, see the AWS Continuum &lt;a href="http://docs.aws.amazon.com/continuum/latest/userguide/what-is-continuum.html"&gt;User Guide&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;The &lt;strong&gt;Overview&lt;/strong&gt; page brings these pieces together in one place, showing my &lt;strong&gt;Code integrations&lt;/strong&gt;, the &lt;strong&gt;Environments&lt;/strong&gt; built on them, and the status of any &lt;strong&gt;AWS collector&lt;/strong&gt; that supplies AWS resource context.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="alignnone wp-image-106064 size-full" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/19/1218373720644947-1.png" alt="" width="3032" height="1416"&gt;&lt;/p&gt; 
&lt;p&gt;I open one of my environments. The &lt;strong&gt;Issues&lt;/strong&gt; tab lists validated, prioritized issues rather than raw scanner output, each with a severity, a status, and the time it was created. I choose one of the issues.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-2c.png"&gt;&lt;img loading="lazy" class="alignnone size-full wp-image-106112" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-2c.png" alt="" width="2462" height="2580"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;The &lt;strong&gt;Overview&lt;/strong&gt; rates it High severity, with the status &lt;strong&gt;Completed&lt;/strong&gt; and the remediation already &lt;strong&gt;Delivered&lt;/strong&gt; to GitHub. The &lt;strong&gt;Risk assessment&lt;/strong&gt; explains why. Continuum rates its &lt;strong&gt;Exploitability&lt;/strong&gt; as &lt;strong&gt;Exploitable&lt;/strong&gt;, with an evidence level of &lt;strong&gt;Static proven&lt;/strong&gt; and a validation run status of &lt;strong&gt;Completed&lt;/strong&gt;. &lt;strong&gt;Likelihood&lt;/strong&gt; is &lt;strong&gt;High&lt;/strong&gt;, since the service is reachable from an attacker, requires no authentication, and needs no user interaction. &lt;strong&gt;Impact&lt;/strong&gt; is &lt;strong&gt;Moderate&lt;/strong&gt;, which means an attacker gains the ability to modify business data, with a blast radius reaching other users in the same tenant. A &lt;strong&gt;Proof&lt;/strong&gt; section includes the source analysis behind the verdict.&lt;/p&gt; 
&lt;p&gt;The &lt;strong&gt;Remediation&lt;/strong&gt; section shows a fix already delivered as a pull request in GitHub, changing four files, with 50 lines added and 24 removed across the cart service. Continuum opens the fix as a pull request titled &lt;strong&gt;Continuum fix&lt;/strong&gt;, and I choose &lt;strong&gt;View pull request&lt;/strong&gt; to open it in GitHub. The console is explicit that a generated patch does not mean the issue is fixed. I still review and merge it, which keeps the final decision with my team. A &lt;strong&gt;Contributing&lt;/strong&gt; findings section lists the specific scanner finding this issue was built from.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-3c.png"&gt;&lt;img loading="lazy" class="alignnone size-full wp-image-106106" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-3c.png" alt="" width="2462" height="3812"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;The pull request description carries the same risk assessment, remediation summary, and proof from the console, so whoever reviews it in GitHub sees the evidence without leaving their workflow.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-4c.png"&gt;&lt;img loading="lazy" class="alignnone size-full wp-image-106108" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-4c.png" alt="" width="3032" height="3394"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;The &lt;strong&gt;Findings&lt;/strong&gt; tab lists the raw scanner findings across the environment, the evidence that issues are built from.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-5c.png"&gt;&lt;img loading="lazy" class="alignnone size-full wp-image-106114" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/22/1218373720644947-5c.png" alt="" width="3032" height="2620"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;The &lt;strong&gt;Scans&lt;/strong&gt; tab shows the history of each scan with its status, origin, and request and completion times, and I use &lt;strong&gt;Configure scan frequency&lt;/strong&gt; to change the cadence or &lt;strong&gt;Queue scan&lt;/strong&gt; to run one on demand. The &lt;strong&gt;Configuration&lt;/strong&gt; tab is where I manage the environment: the code and context sources it reads from, its code integrations, environment settings such as whether Continuum creates remediation patches, and the AWS collectors it uses for AWS context.&lt;/p&gt; 
&lt;p&gt;In a single workflow, I work through the validated issues in priority order with each scan, reviewing the evidence and scope behind each one before I approve and merge the fixes I trust. Every fix waits for my approval, so the backlog keeps shrinking while my team keeps control of what ships.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;Now available&lt;/strong&gt;&lt;/span&gt;&lt;br&gt; AWS Continuum for code vulnerabilities is available today in US East (N. Virginia) and US West (Oregon)&amp;nbsp;Regions. For pricing, visit the &lt;a href="https://aws.amazon.com/continuum/pricing"&gt;pricing page&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To learn more, visit the &lt;a href="https://aws.amazon.com/continuum/"&gt;AWS Continuum for code vulnerabilities product page&lt;/a&gt; and the &lt;a href="http://docs.aws.amazon.com/continuum/latest/userguide/what-is-continuum.html"&gt;User Guide&lt;/a&gt;. Give it a try in the AWS Continuum console today, and send us feedback through your usual AWS Support contacts.&lt;/p&gt; 
&lt;a href="https://www.linkedin.com/in/esrakayabali/"&gt;— Esra&lt;/a&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Introducing Amazon ECS Gateway: A fully-managed ingress solution for ECS services</title>
		<link>https://aws.amazon.com/blogs/aws/introducing-amazon-ecs-gateway-a-fully-managed-ingress-solution-for-ecs-services/</link>
					
		
		<dc:creator><![CDATA[Channy Yun (윤석찬)]]></dc:creator>
		<pubDate>Tue, 20 Oct 2026 17:03:38 +0000</pubDate>
				<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Compute]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">b26c8ec6bfaf7141b02ddd51b0832cb797e2fa86</guid>

					<description>Try Amazon ECS Gateway, a new account-level resource that simplifies ingress networking for containerized workloads by dynamically provisioning and managing the necessary infrastructure on your behalf, with all resources created directly in your account.</description>
										<content:encoded>&lt;p&gt;When platform teams manage containerized applications at scale on &lt;a href="https://aws.amazon.com/ecs/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon Elastic Container Service (Amazon ECS)&lt;/a&gt;, configuring ingress networking for each service often becomes a bottleneck. For every new service, teams must provision and connect &lt;a href="https://aws.amazon.com/elasticloadbalancing/application-load-balancer/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Application Load Balancers (ALBs)&lt;/a&gt;, &lt;a href="https://aws.amazon.com/certificate-manager/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Certificate Manager (ACM)&lt;/a&gt; certificates, &lt;a href="https://aws.amazon.com/waf/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS WAF&lt;/a&gt; web ACLs, and security groups, then keep those resources in sync as services scale, update, or operate. This per-service overhead slows down deployment velocity and increases the risk of configuration drift across an organization.&lt;/p&gt; 
&lt;p&gt;Today, we’re announcing &lt;a href="https://aws.amazon.com/ecs/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon ECS Gateway&lt;/a&gt;, a new account-level resource that simplifies ingress networking for containerized workloads by dynamically provisioning and managing the necessary infrastructure on your behalf, with all resources created directly in your account.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-106076" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/20/2026-ECS-Gateway-architecture.png" alt="" width="1675" height="977"&gt;&lt;/p&gt; 
&lt;p&gt;ECS Gateway introduces a clear separation of responsibilities between platform teams and application teams.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Platform teams&lt;/strong&gt; create and configure a gateway, defining organizational networking standards including subnets, security groups, TLS certificates, listener settings, and WAF web ACLs, in a single place. They then associate the gateway with one or more ECS clusters, making it available to services running on those clusters.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Application teams&lt;/strong&gt; opt their services in by adding a gateway connector parameter when creating or updating a service. ECS provisions the required per-service resources automatically: an ACM certificate, a unique DNS hostname, listener rules, target groups, and a service security group that permits inbound traffic only from the ALB. No networking expertise required.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;ECS Gateway offers host-based routing using ALBs and enables up to 25 services to share a single ALB, optimizing infrastructure costs. ECS manages the full lifecycle of the underlying infrastructure, provisioning the first ALB when your first service connects, adding more ALBs as capacity is reached, and removing them when no longer needed. Each service receives a unique DNS hostname, giving your teams a ready-to-use endpoint the moment provisioning completes.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;A first look at ECS Gateway&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; In the &lt;a href="https://console.aws.amazon.com/ecs/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;ECS console&lt;/a&gt;, platform team can create a gateway and sets its configuration. The infrastructure role is an IAM role that ECS assumes to provision and manage networking resources such as ALBs, security groups, and certificates in your account. To create a gateway, provide a gateway name and select an infrastructure role. You can optionally associate the gateway with ECS clusters during creation or later.&lt;/p&gt; 
&lt;p&gt;Choose a load balancing scheme, either public or VPC-internal traffic routing. Under &lt;strong&gt;Additional Settings&lt;/strong&gt;, you can also set up a listener, port, maximum count of load balancers the gateway can scale to, and a web ACL lets you protect your web applications. Some settings, including the name, scheme, VPC, subnets, IP address type, listener protocol and port cannot be changed after gateway creation.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105491" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/02/2026-ecs-gateway-1-create.jpg" alt="" width="1719" height="2560"&gt;&lt;/p&gt; 
&lt;p&gt;Using &lt;a href="https://aws.amazon.com/cli/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;, call &lt;code&gt;CreateGateway&lt;/code&gt; with a name (unique per account), an infrastructure role, and a configuration object. No infrastructure is provisioned until a service connects with a gateway connector.&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws ecs create-gateway \
  --name my-team-gateway \
  --infrastructure-role-arn arn:aws:iam::123456789012:role/ECSGatewayRole \
  --configuration '{
    "HostSharedAlb": {
      "networkConfiguration": {
        "subnets": [
          "subnet-080779f9bd887757a",
          "subnet-03d5b2fead6bc6258",
          "subnet-0861210a397d31252",
          "subnet-06539e194023cb77a"
        ],
        "ipAddressType": "ipv4"
      },
      "scheme": "internet-facing"
    }
  }'
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Once the gateway is created, you can take a look at the detailed configuration, gateway routes, load balancers, and associated clusters.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105492" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/02/2026-ecs-gateway-1-create-2.jpg" alt="" width="1800" height="978"&gt;&lt;/p&gt; 
&lt;p&gt;Now associate the gateway with one or more clusters (many-to-many), to make it available to ECS services on those clusters.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105493" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/02/2026-ecs-gateway-2-connect.jpg" alt="" width="1800" height="1148"&gt;&lt;/p&gt; 
&lt;p&gt;Use &lt;code&gt;AssociateGatewayWithCluster&lt;/code&gt; to make the gateway available to services on a cluster:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws ecs associate-gateway-with-cluster \ 
--gateway my-team-gateway \ 
--cluster arn:aws:ecs:us-east-1:123456789012:cluster/my-cluster&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;To create and manage the ECS Gateway programmatically, including calling APIs and searching documentation, try the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/getting-started-aws-mcp-server.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS MCP Server&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/plugins.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;plugins&lt;/a&gt; with your preferred AI coding tool. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/gateway-overview.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon ECS Gateway documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;ECS Gateway:Behind the scenes&lt;br&gt; &lt;/strong&gt;A gateway can be associated with up to 10,000 clusters, and a single cluster supports up to five gateway associations. This many-to-many relationship gives platform teams the flexibility to share a gateway across environments or assign multiple gateways (for example, public and private) to a single cluster.&lt;/p&gt; 
&lt;p&gt;Platform teams can control access by choosing which gateways to associate with which clusters. For additional control, use IAM policies to restrict who can deploy services to specific clusters.&lt;/p&gt; 
&lt;p&gt;Application teams add the gateway connector to each service definition in &lt;code&gt;CreateService&lt;/code&gt; or &lt;code&gt;UpdateService&lt;/code&gt;. If you have an existing ECS service with its own load balancer, you can adopt ECS Gateway incrementally by calling &lt;code&gt;UpdateService&lt;/code&gt; to add a gateway connector. Both ingress paths remain available, allowing you to validate the gateway connection before removing the existing load balancer configuration.&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws ecs create-service \ 
  --cluster my-cluster \ 
  --service my-api-service \ 
  --task-definition my-api-service:1 \ 
  --gateway-connectors '[{ "portName": "api", "filters": {"accessTypes": ["PUBLIC"]}, "healthCheck": {...} }]'&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;At deployment time, Amazon ECS evaluates the gateways associated with the cluster and connects the service to every compatible gateway. A gateway is compatible when its access type matches the service’s connector filter, it is in the same VPC as the service, and it covers all Availability Zones used by the service’s configured subnets.&lt;/p&gt; 
&lt;p&gt;For each connection, Amazon ECS assigns the service to an ALB with available capacity and provisions the per-service resources: an ACM certificate, a unique DNS hostname, a listener rule routing traffic for that hostname to the service target group, and a service security group allowing inbound traffic only from the ALB security group. If no existing ALB has capacity, ECS creates a new one (up to &lt;code&gt;maxAlbCount&lt;/code&gt; referring to quota limit). Once provisioning completes, the gateway route becomes &lt;code&gt;ACTIVE&lt;/code&gt;, and the service URL is ready to receive traffic.&lt;/p&gt; 
&lt;p&gt;ECS Gateway handles common operational scenarios automatically:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Redeployments&lt;/strong&gt;: On each deployment, ECS re-evaluates gateway associations. If new compatible gateways have been associated since the last deployment, your service connects to them. If a gateway has been disassociated, your service disconnects and the route is removed. Your service always reflects the current state of the cluster gateways at deployment time.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Service deletion&lt;/strong&gt;: ECS automatically disconnects the service from every gateway, removes all gateway routes, and cleans up all per-service resources. If the service held the last route on an ALB, that ALB is deprovisioned.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Things to Know&lt;/strong&gt;&lt;br&gt; Here are a few important details to keep in mind:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Networking&lt;/strong&gt;: ECS Gateway is available for ECS services using the &lt;code&gt;awsvpc&lt;/code&gt; network mode across all launch types (Amazon ECS EC2, AWS Fargate, and ECS Managed Instances). Your service Availability Zones (AZs) must be a subset of each gateway’s AZs on the cluster. A gateway ALB only routes traffic to tasks in AZs where it has subnets. We recommend creating gateways and services for a given cluster with the same set of AZs.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Capacity&lt;/strong&gt;: If &lt;code&gt;maxAlbCount&lt;/code&gt; is reached and no ALB has available capacity, the deployment fails. Default quota limit of &lt;code&gt;maxAlbCount&lt;/code&gt; is 10. Plan your &lt;code&gt;maxAlbCount&lt;/code&gt; setting according to the number of services you expect to connect.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Observability&lt;/strong&gt;: Use ALB metrics in CloudWatch with the &lt;code&gt;TargetGroup&lt;/code&gt; dimension to monitor per-service traffic, and &lt;code&gt;LoadBalancer&lt;/code&gt; dimension to monitor traffic across the shared ALB. Use &lt;code&gt;describe-target-health&lt;/code&gt; to check real-time target status. Configure CloudWatch alarms for metrics such as &lt;code&gt;HealthyHostCount&lt;/code&gt;, &lt;code&gt;TargetResponseTime&lt;/code&gt;, and &lt;code&gt;HTTPCode_Target_5XX_Count&lt;/code&gt;, using gateway ARN-based tagging so monitoring scales automatically with your &lt;code&gt;maxAlbCount&lt;/code&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Now available&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Amazon ECS Gateway is available now in all commercial AWS Regions where ECS is available at no additional charge. You pay only for the underlying infrastructure provisioned in your account when services connect to a gateway, including applicable ALB charges, CloudWatch logs and metrics, ACM certificates, and data transfer charges. To learn more, visit the &lt;a href="https://aws.amazon.com/ecs/pricing/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon ECS Pricing page&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;To get started,&amp;nbsp;create your first gateway today in the &lt;a href="https://console.aws.amazon.com/ecs/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;ECS console&lt;/a&gt;, and&amp;nbsp;send feedback to &lt;a href="https://repost.aws/tags/TAefn4YSprR-uCBYmbofOpHw/amazon-elastic-container-service?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS re:Post for ECS&lt;/a&gt; or through your usual AWS Support contacts.&lt;/p&gt; 
&lt;p&gt;— &lt;a href="https://linkedin.com/in/channy"&gt;Channy&lt;/a&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: AWS Lambda Web Functions, Amazon S3 on the Vercel Marketplace, and more (October 19, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-aws-lambda-web-functions-amazon-s3-on-the-vercel-marketplace-and-more-october-19-2026/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Mon, 19 Oct 2026 15:34:59 +0000</pubDate>
				<category><![CDATA[Amazon Aurora]]></category>
		<category><![CDATA[Amazon Bedrock AgentCore]]></category>
		<category><![CDATA[Amazon CloudFront]]></category>
		<category><![CDATA[Amazon CloudWatch]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon OpenSearch Service]]></category>
		<category><![CDATA[Amazon S3 Tables]]></category>
		<category><![CDATA[Amazon SageMaker AI]]></category>
		<category><![CDATA[Amazon SageMaker HyperPod]]></category>
		<category><![CDATA[Amazon SageMaker JumpStart]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[AWS Trainium]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">cd5eb4df7600955259cf3d08d3dc859f994f08c5</guid>

					<description>Nothing last week added a new kind of compute. What it did instead was shorten the distance between the code you already have and that code being live. AWS Lambda learned to run a plain HTTP server with no adapter in front of it, and Amazon S3 became something you can provision from inside the […]</description>
										<content:encoded>&lt;p&gt;Nothing last week added a new kind of compute. What it did instead was shorten the distance between the code you already have and that code being live. &lt;a href="https://aws.amazon.com/lambda/"&gt;AWS Lambda&lt;/a&gt; learned to run a plain HTTP server with no adapter in front of it, and &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt; became something you can provision from inside the tool you were already using, without opening the AWS Management Console. Different services, same direction.&lt;/p&gt; 
&lt;p&gt;The counterweight arrived on Thursday. As it gets easier to put things into production, it matters more that you can say what those things are allowed to do, and this week’s most interesting read is about exactly that. Now, let’s get into this week’s AWS news…&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Headlines&lt;/strong&gt;&lt;br&gt; &lt;a href="https://aws.amazon.com/blogs/aws/announcing-aws-lambda-web-functions-for-fast-consistent-web-app-performance-anywhere/"&gt;AWS Lambda Web Functions&lt;/a&gt; is a new form factor that runs a standard HTTP web application on Lambda without rewriting it into an event handler. You take a port-listening server built with Express, Hono, Fastify, or Next.js, run &lt;code&gt;aws lambda-web deploy&lt;/code&gt;, and get back a live HTTPS URL in under a minute. No adapters, no infrastructure to set up first, no framework lock-in. Lambda now has three form factors on the same Firecracker isolation, which compose inside one application: Event Functions (the model you already know) for async work, Web Functions for the user-facing layer, and MicroVMs for stateful sandboxes running untrusted code.&lt;/p&gt; 
&lt;p&gt;Two details make this more than repackaging. Each execution environment handles up to 128 concurrent requests, so a burst of traffic shares warm environments instead of mapping one request to one environment, and billing meters the CPU time your code actually uses rather than wall-clock time. For server-side rendering, API backends, and inference endpoints streaming tokens, where most of the elapsed time is spent waiting, that changes the arithmetic. Adding &lt;code&gt;--regions&lt;/code&gt; to the same deploy command replicates your code and configures latency-based routing behind a single global URL, and you can split traffic across revisions by weight for a canary rollout. It’s available in five Regions, running Node.js 24 on Arm64 with VPC connectivity. The &lt;a href="https://aws.amazon.com/blogs/compute/exploring-aws-lambda-web-functions-for-building-web-applications/"&gt;AWS Compute Blog&lt;/a&gt; has a longer walkthrough, and &lt;a href="https://aws.amazon.com/cloudfront/"&gt;Amazon CloudFront&lt;/a&gt; can now &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/cloudfront-lambda-web-functions-origin/"&gt;use a Web Function endpoint as an origin&lt;/a&gt; with origin access control.&lt;/p&gt; 
&lt;p&gt;The week’s other headline isn’t a launch. &lt;a href="https://aws.amazon.com/blogs/machine-learning/trust-in-depth-giving-agents-more-autonomy-without-losing-control/"&gt;Trust in Depth: giving agents more autonomy without losing control&lt;/a&gt; makes an argument I keep running into in practice: putting a person in the loop for every agent action works at small scale and then quietly stops working, because people asked to check everything stop catching what matters. The alternative is four questions answered at four moments, which AWS calls scope, know, bound, and observe. The part worth sitting with is that an agent’s limits belong outside its own reasoning, in &lt;a href="https://aws.amazon.com/bedrock/agentcore/"&gt;Amazon Bedrock AgentCore&lt;/a&gt; policies enforced at the gateway, because an agent cannot turn off a control it does not run. AWS has run automated reasoning in production for more than a decade, including AWS Identity and Access Management at more than 2.1 billion requests per second, and the case here is for pointing it at the rules you write for agents.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Last week’s launches&lt;/strong&gt;&lt;br&gt; Here are some launches and updates from this past week that caught my attention:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/aws/amazon-s3-vercel-marketplace-v0/"&gt;Amazon S3 is now available on the Vercel Marketplace and v0 by Vercel&lt;/a&gt; – You can now provision S3 general purpose buckets, &lt;a href="https://aws.amazon.com/s3/features/tables/"&gt;S3 Tables&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/s3/features/vectors/"&gt;S3 Vectors&lt;/a&gt; from the Vercel dashboard, or by describing what you want to build in v0. It joins existing integrations for &lt;a href="https://aws.amazon.com/rds/aurora/"&gt;Amazon Aurora&lt;/a&gt;, &lt;a href="https://aws.amazon.com/dynamodb/"&gt;Amazon DynamoDB&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/opensearch-service/features/serverless/"&gt;Amazon OpenSearch Serverless&lt;/a&gt;, so the whole stack sits in one AWS account with one bill. The authentication detail is the good part: a short-lived OIDC token is exchanged at runtime with AWS Security Token Service for credentials scoped to that resource, so no static keys are stored anywhere.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/ec2-t8i-instances-south-america/"&gt;Amazon EC2 T8i instances are now available in South America (São Paulo)&lt;/a&gt; – The newest burstable generation reached the São Paulo Region, which matters for the unglamorous half of a workload: login gateways, small databases, CI/CD runners, low-traffic sites. &lt;a href="https://aws.amazon.com/ec2/"&gt;Amazon EC2&lt;/a&gt; T8i delivers up to 30 percent better price performance than T3, with up to 70 percent higher compute performance and 2.4 times the Amazon EBS bandwidth. It keeps the same CPU credit system as T3, so moving over is a size change rather than a redesign, and &lt;code&gt;t8i.micro&lt;/code&gt; and &lt;code&gt;t8i.small&lt;/code&gt; are available under the AWS Free Tier.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/introducing-reflection-beam-an-open-weight-model-for-agentic-coding-on-aws/"&gt;Reflection Beam, an open-weight model for agentic coding, is now on AWS&lt;/a&gt; – You can now deploy Beam, Reflection AI’s open-weight model for agentic coding and long-horizon tasks, from &lt;a href="https://aws.amazon.com/sagemaker-ai/jumpstart/"&gt;Amazon SageMaker JumpStart&lt;/a&gt;. It’s a sparse mixture-of-experts model with 501 billion total and 23 billion active parameters, released on Hugging Face under Apache 2.0, and Reflection reports an effective context length of 1 million tokens. Start with a JumpStart real-time endpoint, or use &lt;a href="https://aws.amazon.com/sagemaker-ai/hyperpod/"&gt;SageMaker HyperPod&lt;/a&gt; Inference with SGLang or vLLM when you need Kubernetes-native control. It was also &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/01/reflection-beam-on-sagemaker-jumpstart-and-aws-trainium/"&gt;ported and optimized for AWS Trainium3&lt;/a&gt;, and launches in N. Virginia and Ohio.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-lambda-durable-go-sdk-support/"&gt;AWS Lambda Durable Execution SDK for Go is now generally available&lt;/a&gt; – You can now write multi-step Go workflows that checkpoint their own progress and pause for up to a year while waiting on an external event, without building progress tracking yourself. That covers deployment rollouts with approval gates and pipelines that call a model and then stop for human review. It behaves like ordinary Go tooling: &lt;code&gt;go get&lt;/code&gt; to add it, deploy a single static binary on the &lt;code&gt;provided.al2023&lt;/code&gt; runtime, and test a full workflow locally with the &lt;code&gt;durabletest&lt;/code&gt; package, no network access or credentials required.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/cloudwatch-pipelines-log-routing/"&gt;Amazon CloudWatch announces log routing and chained log parsers&lt;/a&gt; – You can now define routes in an &lt;a href="https://aws.amazon.com/cloudwatch/"&gt;Amazon CloudWatch&lt;/a&gt; pipeline that send each event to a different log group based on conditions evaluated against processed fields, so severity, source, or event type can each land somewhere with its own retention and access controls. Chained parsers handle the other half: parsers run in sequence, with later ones consuming fields that earlier ones produced, so you can parse a JSON envelope first and then run a Grok parser over a field it extracted.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;For a full list of AWS announcements, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/new/"&gt;What’s New with AWS&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Other AWS news&lt;/strong&gt;&lt;br&gt; Here are some additional posts and resources that you might find interesting:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/security/aws-security-agent-now-part-of-aws-continuum-exploited-33-of-37-new-real-world-cves/"&gt;AWS Security Agent exploited 33 of 37 new real-world CVEs&lt;/a&gt; – The team pointed their autonomous penetration-testing agent, now part of &lt;a href="https://aws.amazon.com/continuum/"&gt;AWS Continuum&lt;/a&gt;, at 37 recently disclosed CVEs packaged as live containerized targets, starting from nothing but an endpoint URL and a one-line hint. It captured 35 flags, and after auditing every win against the challenge’s canonical proof of concept, 33 of 37 (89.2 percent) held up as genuine end-to-end exploitation. The two misses are what make the post worth your time: in both, the agent found and exploited the bug, then took the target down before it could read the flag. A capable autonomous attacker is also a destructive one.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/compute/your-serverless-attendees-guide-to-aws-reinvent-2026/"&gt;Your serverless attendee’s guide to AWS re:Invent 2026&lt;/a&gt; – A curated path through a very large catalog, worth having before the good sessions fill up.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/architecture/how-dynata-scaled-ai-across-the-development-lifecycle-with-ai-dlc-and-kiro-ide/"&gt;How Dynata scaled AI across the development lifecycle with AI-DLC and Kiro IDE&lt;/a&gt; – What changes when agentic coding stops being an individual habit and becomes how a team works.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Upcoming AWS events&lt;/strong&gt;&lt;br&gt; Check your calendar and sign up for upcoming AWS events:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/events/reinvent/"&gt;AWS re:Invent&lt;/a&gt; – re:Invent returns to Las Vegas from November 30 to December 4, with more than 2,200 sessions. The &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/eventcatalog/page/eventcatalog"&gt;event catalog&lt;/a&gt; is live and reserved seating is open, so &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/reg"&gt;register&lt;/a&gt; and claim your spots before they fill up.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt; – Community-led conferences planned and delivered by community leaders. Here in Brazil, the 2026 season closes with &lt;a href="https://awscommunityday.com.br/norte/"&gt;AWS Community Day Brasil Norte&lt;/a&gt; in Belém on October 31, the final stop in a year that covered every region of the country for the first time.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Join the &lt;a href="https://builder.aws.com/build/capabilities?trk=f11c83db-08fa-4852-aa10-20185beeaef6&amp;amp;sc_channel=el"&gt;AWS Builder Center&lt;/a&gt; to connect with builders, share solutions, and access content that supports your development. Browse &lt;a href="https://aws.amazon.com/events/"&gt;here&lt;/a&gt; for upcoming AWS-led in-person and virtual events and developer-focused events.&lt;/p&gt; 
&lt;p&gt;That’s all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;— Daniel Abib&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Amazon S3 is now available on the Vercel Marketplace and v0 by Vercel</title>
		<link>https://aws.amazon.com/blogs/aws/amazon-s3-vercel-marketplace-v0/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Wed, 14 Oct 2026 19:30:48 +0000</pubDate>
				<category><![CDATA[Amazon S3 Tables]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<guid isPermaLink="false">dde1e88f3c93eabd2dbb3913d365d085496d24b2</guid>

					<description>Amazon Simple Storage Service (Amazon S3), including Amazon S3 Tables and Amazon S3 Vectors, is natively available on the Vercel Marketplace and v0 by Vercel.</description>
										<content:encoded>&lt;p&gt;Developers building web and AI applications on Vercel can now add Amazon S3 storage resources directly from the Vercel Marketplace and v0, combining the durability, scalability, and performance of S3 with the convenience of Vercel’s provisioning workflow. Starting today, &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt;, including &lt;a href="https://aws.amazon.com/s3/features/tables/"&gt;Amazon S3 Tables&lt;/a&gt; and &lt;a href="https://aws.amazon.com/s3/features/vectors/"&gt;Amazon S3 Vectors&lt;/a&gt;, is natively available on the &lt;a href="https://vercel.com/marketplace/aws"&gt;Vercel Marketplace&lt;/a&gt; and &lt;a href="https://v0.app/"&gt;v0 by Vercel&lt;/a&gt;, covering three distinct workloads: everyday storage, analytics, and AI.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Why this matters&lt;/strong&gt;&lt;br&gt; Millions of developers build, deploy, and scale web and AI applications on Vercel. Storage is essential to performant applications, but provisioning it previously required navigating to the AWS Management Console to configure policies and credentials. Now, S3 storage integrates directly into the Vercel developer experience, with resource provisioning and connection configuration handled automatically. Together with existing integrations for &lt;a href="https://aws.amazon.com/rds/aurora/"&gt;Amazon Aurora&lt;/a&gt;, &lt;a href="https://aws.amazon.com/dynamodb/"&gt;Amazon DynamoDB&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/opensearch-service/features/serverless/"&gt;Amazon OpenSearch Serverless&lt;/a&gt;, you get a complete application stack inside Vercel (from your database layer through to object, vector, and open table storage), all on one AWS account with one bill.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Storage for every application&lt;/strong&gt;&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;S3 general purpose buckets&lt;/strong&gt;: Store virtually unlimited objects, including files, images, videos, and documents, for data lakes, cloud-native applications, and mobile apps. S3 delivers the most durable storage in the cloud, designed to provide 99.999999999% (11 nines) data durability and 99.99% availability by default.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;S3 Tables&lt;/strong&gt;: Fully managed Apache Iceberg storage optimized for analytics with automated table maintenance and compaction. S3 Tables are directly queryable from any Iceberg REST catalog API-compatible engine, including DuckDB.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;S3 Vectors&lt;/strong&gt;: Purpose-built vector storage and query for AI applications such as retrieval-augmented generation (RAG) and semantic search, reducing the cost of uploading, storing, and querying vectors by up to 90%.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105952" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/06/screenshot-1-vercel-marketplace-aws.jpg" alt="AWS page on the Vercel Marketplace with $100 in free AWS credits, serverless scale, and an Install button" width="1537" height="1026"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;&lt;em&gt;Figure 1 – The AWS page on the Vercel Marketplace.&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Getting started&lt;/strong&gt;&lt;br&gt; From the Vercel dashboard, go to the Storage tab and choose Create. Select AWS, pick your S3 bucket type, choose a Region, and create the bucket. Provisioning takes a few seconds.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-106033" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/13/screenshot-2-create-resource-1.png" alt="" width="1306" height="1614"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;&lt;em&gt;Figure 2 – Creating an Amazon S3 general purpose bucket in Vercel by choosing a Region and a name.&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;Connect the bucket to a project, then pull the environment variables with the Vercel CLI:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;vercel link 
vercel env pull .env.local&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The integration injects &lt;code&gt;AWS_REGION&lt;/code&gt;, &lt;code&gt;AWS_ROLE_ARN&lt;/code&gt;, &lt;code&gt;AWS_RESOURCE_ARN&lt;/code&gt;, and a bucket name such as &lt;code&gt;S3_BUCKET_NAME&lt;/code&gt;, &lt;code&gt;S3_TABLE_BUCKET_NAME&lt;/code&gt;, or &lt;code&gt;S3_VECTOR_BUCKET_NAME&lt;/code&gt;. At runtime, the &lt;code&gt;awsCredentialsProvider&lt;/code&gt; from &lt;code&gt;@vercel/functions/oidc&lt;/code&gt; exchanges a short-lived OIDC token with AWS Security Token Service (AWS STS) for temporary credentials scoped to your resource. No static keys are stored anywhere.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Object storage with S3&lt;/strong&gt;&lt;br&gt; This Next.js route uploads a file to a general purpose bucket:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-javascript"&gt;import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";
import { awsCredentialsProvider } from "@vercel/functions/oidc";

const s3 = new S3Client({
  region: process.env.AWS_REGION,
  credentials: awsCredentialsProvider({
    roleArn: process.env.AWS_ROLE_ARN,
  }),
});

export async function POST(request) {
  const formData = await request.formData();
  const file = formData.get("file");

  await s3.send(new PutObjectCommand({
    Bucket: process.env.S3_BUCKET_NAME,
    Key: file.name,
    Body: Buffer.from(await file.arrayBuffer()),
    ContentType: file.type,
  }));

  return Response.json({ success: true });
}&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Use &lt;code&gt;ListObjectsV2Command&lt;/code&gt; and &lt;code&gt;GetObjectCommand&lt;/code&gt; with the same client to list and read objects.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Analytics with S3 Tables&lt;/strong&gt;&lt;br&gt; S3 Tables offer S3 storage purpose-built for analytics and are designed to automatically optimize query performance as data volumes grow. They provide fully managed Apache Iceberg tables with automated table maintenance and compaction, and they work with any Apache Iceberg REST Catalog-compliant engine. You can use DuckDB inside a Vercel Function for lightweight queries. This example attaches the table bucket by its ARN and runs an aggregate query:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-javascript"&gt;import { DuckDBInstance } from "@duckdb/node-api";
import { awsCredentialsProvider } from "@vercel/functions/oidc";

const creds = await awsCredentialsProvider({
  roleArn: process.env.AWS_ROLE_ARN,
})();

const db = await DuckDBInstance.create();
const conn = await db.connect();

await conn.run("INSTALL aws; LOAD aws; INSTALL httpfs; LOAD httpfs; INSTALL iceberg; LOAD iceberg;");

await conn.run(`
  CREATE SECRET s3cred (
    TYPE s3,
    KEY_ID '${creds.accessKeyId}',
    SECRET '${creds.secretAccessKey}',
    SESSION_TOKEN '${creds.sessionToken}',
    REGION '${process.env.AWS_REGION}'
  );
`);

await conn.run(`
  ATTACH '${process.env.AWS_RESOURCE_ARN}' AS s3tables (
    TYPE iceberg,
    ENDPOINT_TYPE s3_tables
  );
`);

const rows = await (await conn.run(`
  SELECT town_city, AVG(median_price) AS avg_price
  FROM s3tables."${process.env.S3_TABLES_NAMESPACE}".town_monthly
  GROUP BY town_city
  ORDER BY avg_price DESC
  LIMIT 10
`)).getRowObjects();&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;If you run DuckDB inside a Next.js route, add &lt;code&gt;@duckdb/node-api&lt;/code&gt; to &lt;code&gt;serverExternalPackages&lt;/code&gt; in &lt;code&gt;next.config.mjs&lt;/code&gt; so the native bindings are not bundled.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Vector search with S3 Vectors&lt;/strong&gt;&lt;br&gt; S3 Vectors deliver purpose-built, cost-optimized vector storage for AI agents, AI inference, and semantic search of your content stored in Amazon S3. S3 Vectors provides native support for storing and querying vectors without a separate vector database, but it does not generate them. Create the embeddings with your model of choice, then query the index for the closest matches:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-javascript"&gt;import { S3VectorsClient, QueryVectorsCommand } from "@aws-sdk/client-s3vectors";
import { awsCredentialsProvider } from "@vercel/functions/oidc";

const vectors = new S3VectorsClient({
  region: process.env.AWS_REGION,
  credentials: awsCredentialsProvider({
    roleArn: process.env.AWS_ROLE_ARN,
  }),
});

export async function POST(request) {
  const { embedding } = await request.json();

  const result = await vectors.send(new QueryVectorsCommand({
    vectorBucketName: process.env.S3_VECTOR_BUCKET_NAME,
    indexName: "documents",
    queryVector: { float32: embedding },
    topK: 5,
    returnMetadata: true,
  }));

  return Response.json({ matches: result.vectors });
}&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;&lt;strong&gt;Building with v0 by Vercel&lt;/strong&gt;&lt;br&gt; From v0, describe what you want to build and it provisions the right resource. Ask for “a photo gallery where users upload images using AWS” to get a general purpose bucket, “a support bot that answers questions from my PDFs” to get S3 Vectors, or “an analytics dashboard for my clickstream data” to get S3 Tables. v0 then configures the connection and generates working code.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105950" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/06/screenshot-4-v0-app.jpg" alt="v0 chat with the Amazon S3 Vectors integration connected and the generated PDF support bot application in the Preview panel" width="1646" height="959"&gt;&lt;/p&gt; 
&lt;p style="text-align: center"&gt;&lt;em&gt;Figure 3 – v0 generating a PDF support bot from a natural language prompt, with Amazon S3 Vectors connected and the application in the Preview panel.&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Combining S3 with AWS databases&lt;/strong&gt;&lt;br&gt; Every AWS service on Vercel shares the same account and authentication model, so you can combine them with no extra setup. For example, store file metadata in Aurora with the files in S3, or store document text in DynamoDB with embeddings in S3 Vectors for RAG retrieval.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Using Vercel with your AWS account&lt;/strong&gt;&lt;br&gt; You can create a new AWS account through the integration, which supports S3 features for building and testing. You can also link an existing AWS account to use your full set of S3 and AWS capabilities and keep your current billing. If you link an existing AWS account, Vercel works only with new buckets that you create through the platform. Because every S3 resource lives in your own AWS account, you keep AWS-native tooling and a single place to manage storage.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Pricing and availability&lt;/strong&gt;&lt;br&gt; There is no charge for the integration, and you pay standard Amazon S3 pricing for the resources you use. New AWS accounts created through Vercel receive $100 in credits valid for six months. Amazon S3, including S3 Tables and S3 Vectors, is available from v0 and the Vercel Marketplace in all commercial AWS Regions supported by Vercel. To get started, visit &lt;a href="https://v0.app/"&gt;v0&lt;/a&gt; or the AWS page on the &lt;a href="https://vercel.com/marketplace/aws"&gt;Vercel Marketplace&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Join the conversation&lt;/strong&gt;&lt;br&gt; If you want to call APIs, search documentation, find regional availability, and check troubleshooting about this new feature, try using the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/getting-started-aws-mcp-server.html"&gt;AWS MCP Server&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/plugins.html"&gt;plugins&lt;/a&gt; with your preferred AI tool. Share your feedback on &lt;a href="https://repost.aws/tags/TADSTjraA0Q4-a1dxk6eUYaw/amazon-simple-storage-service"&gt;AWS re:Post for Amazon S3&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;— Daniel&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: Prime Day 2026 by the numbers, Claude Haiku 5.5, Amazon Nova 2.5 Sonic, and more (October 13, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-prime-day-2026-by-the-numbers-claude-haiku-5-5-amazon-nova-2-5-sonic-and-more-october-13-2026/</link>
					
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Tue, 13 Oct 2026 15:59:06 +0000</pubDate>
				<category><![CDATA[Amazon Athena]]></category>
		<category><![CDATA[Amazon Aurora]]></category>
		<category><![CDATA[Amazon Bedrock]]></category>
		<category><![CDATA[Amazon GuardDuty]]></category>
		<category><![CDATA[Amazon Nova]]></category>
		<category><![CDATA[Amazon RDS]]></category>
		<category><![CDATA[Amazon Redshift]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[AWS Fault Injection Service (FIS)]]></category>
		<category><![CDATA[AWS Glue]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[AWS re:Invent]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Strands Agents]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">7d8a98739984e60ca9480501cf2c370433bebfb8</guid>

					<description>Some numbers are hard to picture until you sit with them for a moment. Last week we published the Prime Day 2026 metrics, and the one that stuck with me is 2.3 quadrillion: the daily requests Amazon ElastiCache peaked at during the event. Prime Day ran back in June, so this post always lands as […]</description>
										<content:encoded>&lt;p&gt;Some numbers are hard to picture until you sit with them for a moment. Last week we published the Prime Day 2026 metrics, and the one that stuck with me is 2.3 quadrillion: the daily requests &lt;a href="https://aws.amazon.com/elasticache/"&gt;Amazon ElastiCache&lt;/a&gt; peaked at during the event. Prime Day ran back in June, so this post always lands as a retrospective, and that gap is part of what makes it worth reading. By the time the numbers reach you, the only evidence that any of it happened is that nothing went wrong.&lt;/p&gt; 
&lt;p&gt;The rest of the week pulled in a different direction: smaller, cheaper, and more constrained. Claude Haiku 5.5 arrived on &lt;a href="https://aws.amazon.com/bedrock/"&gt;Amazon Bedrock&lt;/a&gt; at roughly 75 percent less than Haiku 4.5, Amazon Nova 2.5 Sonic made voice agents quicker on their feet, and Strands Box showed up to put real boundaries around what an agent is allowed to do. Now, let’s get into this week’s AWS news…&lt;/p&gt; 
&lt;p&gt;&lt;span id="more-105986"&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Headlines&lt;/strong&gt;&lt;br&gt; &lt;a href="https://aws.amazon.com/blogs/aws/all-the-numbers-amazon-prime-day-2026-powered-by-aws/"&gt;All the numbers: Amazon Prime Day 2026 powered by AWS&lt;/a&gt; is the latest entry in a tradition that goes back to 2016, and the scale is still difficult to hold in your head. Over the four days of Prime Day, &lt;a href="https://aws.amazon.com/dynamodb/"&gt;Amazon DynamoDB&lt;/a&gt; processed more than 59 trillion requests while peaking at 192 million requests per second, and kept single-digit millisecond responses throughout. &lt;a href="https://aws.amazon.com/lambda/"&gt;AWS Lambda&lt;/a&gt; handled over 2.3 trillion invocations per day. &lt;a href="https://aws.amazon.com/ebs/"&gt;Amazon EBS&lt;/a&gt; peaked above 24.8 trillion I/O operations, moving more than an exabyte of data daily. &lt;a href="https://aws.amazon.com/ecs/"&gt;Amazon ECS&lt;/a&gt; launched an average of 158.3 million tasks per day on &lt;a href="https://aws.amazon.com/fargate/"&gt;AWS Fargate&lt;/a&gt;, a 47.7 percent jump over last year, and &lt;a href="https://aws.amazon.com/ec2/graviton/"&gt;AWS Graviton&lt;/a&gt; powered up to 49 percent of the &lt;a href="https://aws.amazon.com/ec2/"&gt;Amazon EC2&lt;/a&gt; compute that Amazon.com used.&lt;/p&gt; 
&lt;p&gt;The number I keep coming back to, though, isn’t a throughput record. The team ran more than 44,000 &lt;a href="https://aws.amazon.com/fis/"&gt;AWS Fault Injection Service&lt;/a&gt; experiments ahead of the event, more than six times what they ran in 2025. Those are deliberate failures injected on purpose, months in advance, so that the trillions of requests above turn into an ordinary shopping afternoon. If you’re preparing for your own peak moment, &lt;a href="https://aws.amazon.com/premiumsupport/aws-countdown/"&gt;AWS Countdown Premium&lt;/a&gt; is built for exactly that kind of planning.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Last week’s launches&lt;/strong&gt;&lt;br&gt; Here are some launches and updates from this past week that caught my attention:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/introducing-claude-haiku-5-5-on-aws/"&gt;Claude Haiku 5.5 is now available on AWS&lt;/a&gt; – You can now use the fastest model in the Claude 5.5 family on Amazon Bedrock and Claude Platform on AWS, at around 75 percent less than Claude Haiku 4.5 for most tasks. It’s the first Haiku with effort controls, so you can tune cost against intelligence per task instead of fixing one setting for a whole workload. It pairs naturally with Claude Opus 5.5: Opus plans and makes the judgment calls, and because Haiku is fast and cheap, you can run many Haiku subagents in parallel for routing, classification, and small code changes across many files.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-nova-2.5-sonic/"&gt;Amazon Nova 2.5 Sonic for voice agents&lt;/a&gt; – You can now build real-time voice agents on a speech-to-speech &lt;a href="https://aws.amazon.com/nova/"&gt;Amazon Nova&lt;/a&gt; model with better reasoning, instruction following, and tool-calling accuracy, plus lower latency. That combination matters for multi-step work: a support agent can look up an order, check return eligibility, and start the return inside one conversation. It keeps expressive voices in seven languages, controllable turn-taking, and a 256K context window, and pairs with Strands Bidi Agents, &lt;a href="https://strandsagents.com/blog/bidi-agents-now-ga/"&gt;now generally available&lt;/a&gt;, to get a production voice agent going in a few lines of code.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/guardduty-rds-data-exfiltration/"&gt;Amazon GuardDuty RDS Protection now detects data exfiltration and destruction&lt;/a&gt; – &lt;a href="https://aws.amazon.com/guardduty/"&gt;Amazon GuardDuty&lt;/a&gt; now looks past login anomalies to the queries themselves on &lt;a href="https://aws.amazon.com/rds/aurora/"&gt;Amazon Aurora&lt;/a&gt; PostgreSQL and &lt;a href="https://aws.amazon.com/rds/"&gt;Amazon RDS&lt;/a&gt; for PostgreSQL. RDS Protection for data activity builds behavioral baselines and uses ML-based anomaly detection plus threat intelligence to flag unusual data access, with no agents, extra infrastructure, or database configuration changes. This closes a real gap: once an attacker has valid credentials from phishing or a misconfiguration, their queries can look indistinguishable from your application’s.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-Lambda-supports-oauth-kafka-esm/"&gt;AWS Lambda supports OAuth for self-managed Apache Kafka event sources&lt;/a&gt; – You can now authenticate Lambda Kafka consumers through your enterprise identity provider, such as Amazon Cognito or Okta. Event source mappings previously supported only SASL/PLAIN, SASL/SCRAM, and mTLS, which left teams in regulated industries unable to use Kafka ESM at all. Now you get the automatic scaling, batching, error handling, and event filtering of Kafka ESM with the same identity governance you apply everywhere else. It works with self-hosted clusters and managed offerings including Confluent Cloud, Aiven, and Redpanda.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/redshift-iceberg-materialized-views"&gt;Amazon Redshift adds Apache Iceberg materialized views&lt;/a&gt; – You can now pre-compute expensive joins and aggregations once in &lt;a href="https://aws.amazon.com/redshift/"&gt;Amazon Redshift&lt;/a&gt; and store the result as an Iceberg table in &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt;, registered in the &lt;a href="https://aws.amazon.com/glue/"&gt;AWS Glue&lt;/a&gt; Data Catalog. You create them with familiar SQL, and the results are immediately queryable by any Iceberg-compatible engine, including &lt;a href="https://aws.amazon.com/athena/"&gt;Amazon Athena&lt;/a&gt;, Apache Spark, Trino, and Snowflake. Redshift keeps them current by recomputing only what changed. There’s a &lt;a href="https://aws.amazon.com/blogs/big-data/materialize-once-query-anywhere-introducing-iceberg-materialized-views-in-amazon-redshift/"&gt;good deep dive on the AWS Big Data blog&lt;/a&gt; if you want the details.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;For a full list of AWS announcements, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/new/"&gt;What’s New with AWS&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Other AWS news&lt;/strong&gt;&lt;br&gt; Here are some additional posts and resources that you might find interesting:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/opensource/introducing-strands-box-ai-agent-sandboxes-powered-by-dogwood/"&gt;Introducing Strands Box: AI agent sandboxes powered by Dogwood&lt;/a&gt; – As more of us let agents run shell commands and call APIs without approving every step, isolation alone stops being enough. &lt;a href="https://github.com/strands-agents/box"&gt;Strands Box&lt;/a&gt; is an open source sandbox (Apache 2.0, developer preview) that combines OS-level containment with fine-grained policies written in Dogwood, so permissions can depend on what the agent has already done. You can say “let the agent post to the incident channel, but no more than three times every 10 minutes” and have that enforced from outside the agent’s process. It also keeps real credentials out of the agent’s environment by attaching them at an egress gateway.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/security/aws-continuum-sets-a-new-standard-in-autonomous-code-security/"&gt;AWS Continuum sets a new standard in autonomous code security&lt;/a&gt; – Related to that theme, AWS Continuum for Penetration Testing &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/10/aws-continuum-penetration-testing/"&gt;now integrates into your CI/CD pipeline&lt;/a&gt; in public preview, turning penetration testing into a deploy-time event instead of something that happens off to the side. Developers get findings with severity, affected endpoints, and remediation guidance right in the pipeline output, and the pipeline re-tests to verify fixes.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/how-postman-runs-agent-mode-for-40-million-developers-on-amazon-bedrock/"&gt;How Postman runs Agent Mode for 40 million developers on Amazon Bedrock&lt;/a&gt; – A look at the architecture behind a feature serving a very large developer audience. Worth reading if you’re moving an agentic feature from a demo to something that has to hold up under real traffic.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/icymi-what-landed-for-ai-builders-in-september-2026/"&gt;ICYMI: What landed for AI builders in September 2026&lt;/a&gt; – If you lost track of a month that included a lot of model launches, this is a tidy catch-up in one place.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Upcoming AWS events&lt;/strong&gt;&lt;br&gt; Check your calendar and sign up for upcoming AWS events:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/events/reinvent/" data-agent-id="141"&gt;AWS re:Invent&lt;/a&gt; – re:Invent returns to Las Vegas from November 30 to December 4, and reserved seating is now open. The session catalog is live, so &lt;a href="https://registration.awsevents.com/flow/awsevents/reinvent2026/reg" data-agent-id="142"&gt;register&lt;/a&gt; and claim your spots in chalk talks, workshops, and builders’ sessions before they fill up.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt; – Community-led conferences planned and delivered by community leaders, and this is a busy stretch. Upcoming stops include &lt;a href="https://www.aws-aicd.com/"&gt;San Francisco&lt;/a&gt; (October 13), &lt;a href="https://awscommunitydaysoflo.com/"&gt;Miami&lt;/a&gt; (October 14), &lt;a href="https://awscommunitydayaus.com/"&gt;Brisbane&lt;/a&gt; (October 16), &lt;a href="https://www.awscommunityday.co.za/"&gt;Cape Town&lt;/a&gt; (October 16), &lt;a href="https://www.awscommunityday.mt/"&gt;Malta&lt;/a&gt; (October 16), and &lt;a href="https://acd.awsugmum.in/"&gt;Mumbai&lt;/a&gt; (October 17). Here in Brazil, the &lt;a href="https://awscommunityday.com.br/"&gt;community calendar&lt;/a&gt; has more editions coming before the end of the year.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Join the &lt;a href="https://builder.aws.com/build/capabilities?trk=f11c83db-08fa-4852-aa10-20185beeaef6&amp;amp;sc_channel=el"&gt;AWS Builder Center&lt;/a&gt; to connect with builders, share solutions, and access content that supports your development. Browse &lt;a href="https://aws.amazon.com/events/"&gt;here&lt;/a&gt; for upcoming AWS-led in-person and virtual events and developer-focused events.&lt;/p&gt; 
&lt;p&gt;That’s all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;– Daniel Abib&lt;/p&gt; 
&lt;p&gt;&lt;em&gt;This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!&lt;/em&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Announcing AWS Lambda Web Functions</title>
		<link>https://aws.amazon.com/blogs/aws/announcing-aws-lambda-web-functions-for-fast-consistent-web-app-performance-anywhere/</link>
					
		
		<dc:creator><![CDATA[Micah Walter]]></dc:creator>
		<pubDate>Mon, 12 Oct 2026 22:34:47 +0000</pubDate>
				<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">4158873d220345e053e781fb51ca252fff001d13</guid>

					<description>AWS Lambda Web Functions is a serverless compute primitive that runs your HTTP framework natively, delivering fast, consistent responses through multi-concurrent execution and automated global distribution.</description>
										<content:encoded>&lt;p&gt;Today, we’re announcing &lt;a href="https://aws.amazon.com/lambda/lambda-web-functions/"&gt;AWS Lambda Web Functions&lt;/a&gt;, a new form factor that lets you run standard HTTP web applications on Lambda without rewriting your code into an event handler. You can take a standard port-listening server built with Express, Hono, Fastify, Next.js, or any Node.js framework, deploy it with a single command, and Lambda automatically handles scaling, multi-region distribution, and active CPU billing. No adapters, no infrastructure to manage, and no framework lock-in.&lt;/p&gt; 
&lt;p&gt;With this launch, AWS Lambda now offers three distinct form factors, each built on the same Firecracker isolation technology and designed for a different programming model.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Lambda Event Functions&lt;/strong&gt; are what you already know as Lambda functions. They use the event-driven, single-concurrent handler model with wall-clock billing. We’re introducing the “Event Functions” name to highlight that programming model: your function receives an event, processes it, and returns a response. The event-driven programming model is ideal for event processing, queue consumers, and invocations triggered by other AWS services.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Lambda Web Functions&lt;/strong&gt; use an HTTP-native programming model with multi-concurrent execution and active CPU billing. Your code listens on a port and handles standard HTTP requests. That programming model is ideal for web applications, API backends, and interactive HTTP workloads where multiple concurrent requests and I/O-heavy processing are the norm.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Lambda MicroVMs&lt;/strong&gt; provide isolated, stateful sandbox environments with customer-managed lifecycles for running untrusted or user-generated code.&lt;/p&gt; 
&lt;p&gt;The three complement each other. An application might use Event Functions for asynchronous backend processing, Web Functions for the user-facing API and server-side rendering layer, and MicroVMs for interactive code execution features, all within the same AWS account and sharing the same operational model.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;Why Web Functions&lt;br&gt; &lt;/strong&gt;&lt;/span&gt;Modern web applications need to serve global audiences with fast, consistent response times while giving developers the freedom to use standard frameworks and iterate quickly. Building this today typically requires assembling multiple infrastructure components, configuring multi-region deployments, setting up latency-based routing, and tuning billing models to avoid paying for I/O wait. Developers often find themselves adapting their application code to fit a specific compute model rather than deploying the HTTP server they already have.&lt;/p&gt; 
&lt;p&gt;Lambda Web Functions removes this complexity. Each execution environment handles multiple requests simultaneously (up to 128 concurrent requests per environment), which means a burst of incoming traffic can share warm environments instead of mapping each request to a new one. Web Functions meter the CPU time your code uses, so time spent waiting on a database query or an API call consumes little CPU. Memory is metered for as long as the execution environment exists. For I/O-heavy web workloads like server-side rendering, API backends, and AI inference endpoints streaming token responses, this can reduce compute costs.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;Let’s try it out&lt;br&gt; &lt;/strong&gt;&lt;/span&gt;To get started, I wrote a simple Express.js server. This is the same code I run locally with &lt;code&gt;node index.js&lt;/code&gt;, no Lambda-specific adapters or wrappers required.&lt;/p&gt; 
&lt;pre&gt;&lt;code class="language-javascript"&gt;import express from 'express';

const app = express();
const [host, port] = process.env.AWS_LAMBDA_HTTP_ENDPOINT.split(':');

app.get('/', (req, res) =&amp;gt; {
  res.json({ message: 'Hello from Lambda Web Functions!' });
});

app.listen(port, host, () =&amp;gt; {
  console.log(`Server running on port ${port}`);
});
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The only difference from running locally is the &lt;code&gt;AWS_LAMBDA_HTTP_ENDPOINT&lt;/code&gt; environment variable, which Lambda sets to the host and port your server must listen on. To run locally, set it yourself, for example &lt;code&gt;AWS_LAMBDA_HTTP_ENDPOINT=127.0.0.1:3000 node index.js&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;With my code ready, I deployed using the &lt;a href="https://aws.amazon.com/cli/"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt;:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;aws lambda-web deploy --name my-web-app --code ./my-app
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;One command. No prior resource setup. The CLI bundled my source, created the Web Function, published its first revision, attached a Web Function endpoint, and returned a live HTTPS URL in under a minute.&lt;/p&gt; 
&lt;p&gt;A revision is an immutable snapshot of the code I deployed. The endpoint is the HTTPS URL that routes traffic to a revision, or splits traffic across revisions. Those are the resources I use to iterate and to control how traffic moves to new code.&lt;/p&gt; 
&lt;p&gt;I tested it immediately:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;$ curl https://&amp;lt;domain-id&amp;gt;.&amp;lt;shard-id&amp;gt;.lambda-web.us-east-1.on.aws/
{"message":"Hello from Lambda Web Functions!"}
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Next, I wanted my application to serve users in Europe and Asia with lower latency. I redeployed with multiple regions:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;aws lambda-web deploy --name my-web-app --code ./my-app \
    --regions us-east-1,eu-west-1,ap-northeast-1
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Lambda Web Functions replicated my code to all three regions and configured latency-based routing automatically. Each request now routes to the Region with the lowest latency for the caller, on a best-effort basis, through one global URL (&lt;code&gt;&amp;lt;domain-id&amp;gt;.lambda-web.global.on.aws&lt;/code&gt;).&lt;/p&gt; 
&lt;p&gt;When I updated my code and ran the same deploy command again, the CLI detected the existing function, uploaded the new revision, and pointed the endpoint at it. Total turnaround from code change to live: seconds.&lt;/p&gt; 
&lt;p&gt;For production workflows that require a more gradual rollout, I can shift traffic between revisions with a single API call:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;aws lambda-web update-web-function-endpoint \
    --function-name my-web-app \
    --endpoint-name dev \
    --auto-deployment-mode Disabled \
    --revision-weights '[{"revisionId": "&amp;lt;current-revision-id&amp;gt;", "weight": 90}, {"revisionId": "&amp;lt;new-revision-id&amp;gt;", "weight": 10}]'
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;This sends 90% of endpoint traffic to the current revision and 10% to the new one, giving me a canary deployment without additional tooling.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;Better together with Amazon CloudFront&lt;br&gt; &lt;/strong&gt;&lt;/span&gt;For applications that combine static and dynamic content, Web Functions works well alongside &lt;a href="https://aws.amazon.com/cloudfront/"&gt;Amazon CloudFront&lt;/a&gt;. You can select a Web Function endpoint as the origin for your CloudFront distribution. Static assets are served from the cache while dynamic requests route to your Web Function, giving you CDN performance for static content with serverless compute for the dynamic parts.&lt;/p&gt; 
&lt;p&gt;Web Functions improves the private-origin experience with CloudFront.&amp;nbsp;With this launch, you attach CloudFront &lt;a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-origin.html"&gt;origin access control (OAC)&lt;/a&gt; to a Web Function endpoint instead. CloudFront signs requests to the origin, and the endpoint allows only your distribution to invoke it. You get the same private-origin pattern CloudFront already provides for &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon Simple Storage Service (Amazon S3)&lt;/a&gt;, without exposing the endpoint or adding custom authorization to your app.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;Now available&lt;br&gt; &lt;/strong&gt;&lt;/span&gt;AWS Lambda Web Functions is available today in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Tokyo), and Europe (Ireland). Web Functions run Node.js 24 (nodejs24.x) on Arm64 at launch and support Amazon Virtual Private Cloud (VPC) connectivity, allowing your function to access resources that exist within a VPC.&lt;/p&gt; 
&lt;p&gt;To get started, deploy your first Web Function in under a minute:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;aws lambda-web deploy --name hello-world --hello-world
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;For pricing details, visit the &lt;a href="https://aws.amazon.com/lambda/pricing/"&gt;AWS Lambda pricing page&lt;/a&gt;. To learn more, see the &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/web-functions.html"&gt;Lambda Web Functions documentation&lt;/a&gt;.&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>All the numbers: Amazon Prime Day 2026 powered by AWS</title>
		<link>https://aws.amazon.com/blogs/aws/all-the-numbers-amazon-prime-day-2026-powered-by-aws/</link>
					
		
		<dc:creator><![CDATA[Channy Yun (윤석찬)]]></dc:creator>
		<pubDate>Tue, 06 Oct 2026 16:09:36 +0000</pubDate>
				<category><![CDATA[Amazon Aurora]]></category>
		<category><![CDATA[Amazon CloudFront]]></category>
		<category><![CDATA[Amazon CloudWatch]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon Elastic Block Store (Amazon EBS)]]></category>
		<category><![CDATA[Amazon Elastic Container Service]]></category>
		<category><![CDATA[Amazon ElastiCache]]></category>
		<category><![CDATA[Amazon GuardDuty]]></category>
		<category><![CDATA[Amazon Simple Email Service (SES)]]></category>
		<category><![CDATA[Amazon Simple Queue Service (SQS)]]></category>
		<category><![CDATA[AWS CloudTrail]]></category>
		<category><![CDATA[AWS Fargate]]></category>
		<category><![CDATA[AWS Fault Injection Service (FIS)]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[AWS Support]]></category>
		<category><![CDATA[Graviton]]></category>
		<category><![CDATA[Kinesis Data Streams]]></category>
		<category><![CDATA[Case Studies]]></category>
		<guid isPermaLink="false">26926696f501ea30f54a1a0580ce8eb01bf59235</guid>

					<description>Amazon Prime Day 2026 was exclusively for Prime members and ran June 23–26, 2026 with millions of deals across more than 35 categories. As part of our annual tradition of sharing how AWS powered Prime Day (2016, 2017, 2019, 2020, 2021, 2022, 2023, 2024, and 2025), I want to share the services and chart-topping metrics […]</description>
										<content:encoded>&lt;p&gt;&lt;a class="link" href="https://www.aboutamazon.com/news/tag/prime-day" target="_self" rel="noopener"&gt;&lt;span class="text v2"&gt;Amazon Prime Day 2026&lt;/span&gt;&lt;/a&gt;&lt;span class="text v2"&gt; was exclusively for Prime members and ran June 23–26, 2026 with millions of deals across more than 35 categories.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;As part of our annual tradition of sharing how AWS powered Prime Day (&lt;a href="https://aws.amazon.com/blogs/aws/how-aws-powered-amazons-biggest-day-ever/"&gt;2016&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/prime-day-2017-powered-by-aws/"&gt;2017&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/amazon-prime-day-2019-powered-by-aws/"&gt;2019&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/amazon-prime-day-2020-powered-by-aws/"&gt;2020&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/prime-day-2021-two-chart-topping-days/"&gt;2021&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/amazon-prime-day-2022-aws-for-the-win/"&gt;2022&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/prime-day-2023-powered-by-aws-all-the-numbers/"&gt;2023&lt;/a&gt;, &lt;a href="https://aws.amazon.com/blogs/aws/how-aws-powered-prime-day-2024-for-record-breaking-sales/"&gt;2024&lt;/a&gt;, and &lt;a href="https://aws.amazon.com/blogs/aws/aws-services-scale-to-new-heights-for-prime-day-2025-key-metrics-and-milestones/"&gt;2025&lt;/a&gt;), I want to share the services and chart-topping metrics from AWS that made your amazing shopping experience possible.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105273" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/08/10/about-amazon-hero-pd-2026-tabletop-blue.jpg" alt="" width="2000" height="1125"&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Prime Day 2026 – all the numbers&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; As always, Prime Day was powered by AWS. Here are some of the most interesting and/or mind-blowing metrics:&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Elastic Compute Cloud (Amazon EC2) and AWS Graviton&lt;/strong&gt; – During Amazon Prime Day 2026, AWS Graviton powered up to 49% of the Amazon EC2 compute used by Amazon.com.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Elastic Block Store (Amazon EBS)&lt;/strong&gt; –&amp;nbsp;During Prime Day 2026, Amazon EBS, our high-performance block storage service, peaked at over 24.8 trillion I/O operations, moving over an exabyte of data daily.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;AWS Lambda&lt;/strong&gt; – AWS Lambda handled over 2.3 trillion invocations per day during Prime Day 2026.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Elastic Container Service (ECS) and Fargate&lt;/strong&gt; – During Prime Day 2026, Amazon ECS launched an average of 158.3 million tasks per day on AWS Fargate, representing a 47.7 percent increase from the previous year’s Prime Day average.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon CloudFront &lt;/strong&gt;– Amazon CloudFront delivered over 2.1 trillion HTTP requests during the global week of Prime Day 2026, a 5 percent increase in total requests compared to Prime Day 2025.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon DynamoDB&lt;/strong&gt; –&amp;nbsp;Amazon DynamoDB, a serverless, fully managed, distributed NoSQL database, powers multiple high-traffic Amazon properties and systems including Alexa, the Amazon.com sites, and all Amazon fulfillment centers. Over the course of Prime Day 2026, between June 23 and June 26, 2026, DynamoDB processed over 59 trillion requests. DynamoDB maintained high availability while delivering single-digit millisecond responses and peaking at 192 million requests per second.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Aurora&lt;/strong&gt; – On Prime Day, Amazon Aurora, a relational database management system (RDBMS) built for high performance and availability at global scale for PostgreSQL, MySQL, and DSQL, processed hundreds of billions of transactions, stored 5,491 terabytes of data, and transferred 1,194 terabytes of data.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon ElastiCache&lt;/strong&gt; – During Prime Day, Amazon ElastiCache peaked at serving over 2.3 quadrillion daily requests and 2.1 trillion requests in a minute.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Kinesis Data Streams&lt;/strong&gt; – Amazon Kinesis Data Streams, a fully managed serverless data streaming service, processed a peak of 988 million records per second during Prime Day 2026.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Simple Notification Service (SNS)&lt;/strong&gt; – Amazon SNS, a fully managed pub/sub messaging service for application-to-application and application-to-person communication, delivered 5 trillion messages in a single day during Prime Day 2026.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon Simple Queue Service (SQS)&lt;/strong&gt; – Amazon SQS, a fully managed message queuing service for microservices, distributed systems, and serverless applications, received a peak of 213 million messages per second during Prime Day 2026&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;AWS CloudTrail&lt;/strong&gt; – AWS CloudTrail processes billions of API activity events per day for governance, compliance, and operational auditing. During Prime Day 2026, that volume surged to 3.6 trillion events in just four days, a 44% increase over Prime Day 2025.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon CloudWatch&lt;/strong&gt; – Amazon CloudWatch processed over 2.15 quadrillion metric observations per day during Prime Day 2026.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Amazon GuardDuty&lt;/strong&gt; – During Prime Day 2026, Amazon GuardDuty monitored an average of 14.08 trillion log events per hour, a 59% increase from last year’s Prime Day.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;AWS Fault Injection Service (FIS)&lt;/strong&gt; – We ran over 44,000 AWS FIS experiments – more than six times what we conducted in 2025 – to help ensure Amazon.com remains highly available on Prime Day.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Prepare to scale&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; If you’re preparing for similar business-critical events, product launches, and migrations, I recommend that you take advantage of &lt;a href="https://aws.amazon.com/premiumsupport/aws-countdown/"&gt;AWS Countdown Premium&lt;/a&gt;. From retail peak seasons to major sporting events, elections, and healthcare enrollment periods, we help you deliver flawless experiences when it matters most. Our experts help you manage your infrastructure to handle massive traffic spikes while maintaining security and performance. We work alongside your team to scale infrastructure, optimize costs during demand surges, strengthen security measures, and monitor real-time demands. To learn more, visit &lt;a href="https://aws.amazon.com/premiumsupport/aws-countdown-critical-events/"&gt;AWS Countdown Premium for business critical events&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;I look forward to seeing what other records will be broken next year!&lt;/p&gt; 
&lt;p&gt;— &lt;a href="https://linkedin.com/in/channy/"&gt;Channy&lt;/a&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>AWS Weekly Roundup: Amazon Bedrock Managed Agents powered by OpenAI, Q3 service availability updates, Kiro workflows, and more (October 5, 2026)</title>
		<link>https://aws.amazon.com/blogs/aws/aws-weekly-roundup-amazon-bedrock-managed-agents-powered-by-openai-q3-service-availability-updates-kiro-workflows-and-more-october-5-2026/</link>
					
		
		<dc:creator><![CDATA[Channy Yun (윤석찬)]]></dc:creator>
		<pubDate>Mon, 05 Oct 2026 15:41:19 +0000</pubDate>
				<category><![CDATA[Amazon Bedrock]]></category>
		<category><![CDATA[Amazon S3 Tables]]></category>
		<category><![CDATA[AWS Partner Network]]></category>
		<category><![CDATA[AWS Well-Architected Tool]]></category>
		<category><![CDATA[Kiro]]></category>
		<category><![CDATA[Strands Agents]]></category>
		<category><![CDATA[Week in Review]]></category>
		<guid isPermaLink="false">b763b52a942275354399615fd56b8f7232f71f2c</guid>

					<description>Last week, we announced a public preview of Amazon Bedrock Managed Agents powered by OpenAI, built on a customized version of OpenAI’s Agents API engineered to be AWS-native and integrated with AWS resources. You can now build agents optimized for OpenAI models that run entirely inside AWS with the identities, permissions, and governance controls you […]</description>
										<content:encoded>&lt;p&gt;Last week, we announced a &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/bedrock-managed-agents-preview/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;public preview of Amazon Bedrock Managed Agents powered by OpenAI&lt;/a&gt;, built on a customized version of OpenAI’s Agents API engineered to be AWS-native and integrated with AWS resources. You can now build agents optimized for OpenAI models that run entirely inside AWS with the identities, permissions, and governance controls you already use.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-103824" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/04/28/2026-bedrock-managed-agents-openai.png" alt="" width="1400" height="890"&gt;You can choose an execution environment: self-hosted compute to use an existing development machine, container, or compute environment or Amazon Bedrock AgentCore Runtime, for managed runtime sessions and configurable storage in your AWS account. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/bedrock-managed-agents-openai.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon Bedrock documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105933" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/10/04/bma-architecture.png" alt="" width="1600" height="440"&gt;&lt;/p&gt; 
&lt;p&gt;In addition, we are adding new frontier models on Amazon Bedrock to expand your model choices:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/openai-gpt-6-1-sol-on-amazon-bedrock/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;OpenAI GPT-6.1 Sol&lt;/a&gt;: An upgrade to GPT-6 Sol, GPT-6.1 Sol delivers exceptionally strong performance on agentic coding, computer use, and professional work. According to OpenAI, it approaches GPT-6 Astra across demanding evaluations at roughly one-fifth of the cost, giving developers more room to build and run capable agents at scale. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-openai-gpt-6-1-sol.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;GPT-6.1 Sol model card&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/openai-gpt-6-astra-ultrafast-on-amazon-bedrock/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;OpenAI GPT-6 Astra UltraFast mode&lt;/a&gt;: Ultrafast is a premium speed tier for GPT-6 Astra, built for workloads where speed matters most. According to OpenAI, Ultrafast delivers up to 6x faster inference in the API, with up to 300 tokens per second. The Amazon Bedrock inference engine delivers the performance, security, and reliability required for production workloads. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-openai-gpt-6-astra.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;GPT-6 Astra model card&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/claude-sonnet-5-5-aws/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Anthropic Claude Sonnet 5.5&lt;/a&gt;: Claude Sonnet 5.5 is a smarter, more efficient Sonnet and a step up from Sonnet 5, making it a natural upgrade for teams already building on Sonnet. It’s stronger for coding, completing well-scoped tasks as part of a larger coding strategy such as building and fixing features with Claude in the same session or verifying output against requirements. To learn more, visit the&amp;nbsp;&lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-sonnet-5-5.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Claude Sonnet 5.5 model card&lt;/a&gt;.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-bedrock-grok-4-7/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;SpaceXAI Grok 4.7&lt;/a&gt;: Grok 4.7 builds on Grok 4.6 with better mixed-document handling, more dependable repo-scale coding with planning and error recovery, and enhanced browser-use agents for form fills and portal navigation. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-xai-grok-4-7.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Grok 4.7 model card&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Last week’s launches&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Here are some launches that got my attention:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/aws/announcing-aws-well-architected-agent-an-ai-powered-intelligence-to-optimize-your-cloud-environment-preview/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Well-Architected Agent (preview)&lt;/a&gt;: You can use an AI-powered agent service that analyzes your AWS environment to deliver targeted, contextual recommendations for improving your applications’ cost, security, performance, and resilience. The agent analyzes your infrastructure, understands your unique business goals, and delivers contextual recommendations.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/aws/amazon-aurora-postgresql-now-supports-direct-querying-of-apache-iceberg-and-parquet-data-in-your-data-lake/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon Aurora PostgreSQL supports direct querying of Apache Iceberg and Parquet data&lt;/a&gt;: You can directly query operational data together with data stored in data lakes in Apache Iceberg and Parquet formats using your existing PostgreSQL applications and tools, without extract, transform, and load (ETL) pipelines or data duplication.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/aws/amazon-s3-tables-now-support-all-apache-iceberg-v3-data-types/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon S3 Tables support all Apache Iceberg V3 data types&lt;/a&gt;: Amazon S3 Tables add support for geometry, geography, unknown, and nanosecond timestamp data types, along with column default values, as defined in the Iceberg V3 specification. You can now store geospatial coordinates and nanosecond-precision event times natively instead of encoding them in strings or integers.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;For a full list of AWS announcements, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/new/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;What’s New with AWS&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;AWS service availability updates&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; When the availability of an AWS service or feature changes, we provide customers guidance in &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/09/aws-service-availability/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Product Lifecycle Changes&lt;/a&gt; on available alternatives and support for migration so that disruptions to your operations are minimized. The following lifecycle changes were updated on September 29, 2026.&lt;/p&gt; 
&lt;p&gt;Services moving to Maintenance (no longer accessible to new customers starting October 29, 2026):&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/chime-sdk/latest/ag/sip-applications-service-change.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon Chime SDK SIP Media Application&lt;/a&gt;&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/workspaces-web/latest/adminguide/workspaces-secure-browser-maintenance-mode.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon WorkSpaces Secure Browser&lt;/a&gt;&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Services entering Sunset:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/managed-blockchain/latest/hyperledger-fabric-dev/managed-blockchain-end-of-support.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon Managed Blockchain&lt;/a&gt; (end of support September 29, 2027)&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/devops-guru/latest/userguide/devops-guru-end-of-support.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Amazon DevOps Guru&lt;/a&gt; (end of support September 30, 2027)&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/sap/latest/sap-AnyDB/ase-backint-end-of-support.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Backint Agent for SAP ASE&lt;/a&gt; (end of support September 29, 2027)&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://docs.aws.amazon.com/infrastructure-composer/latest/dg/composer-availability-change.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Infrastructure Composer&lt;/a&gt; (standalone console end of support December 7, 2026)&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Services reaching End of Support (as of September 29, 2026):&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Amazon Mechanical Turk&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;We understand that changes in availability can impact your operations. For specific guidance, consult the relevant service documentation or contact AWS Support.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Other AWS news&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Here are some additional projects and news items you may find interesting:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;a href="https://kiro.dev/blog/introducing-workflows/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Introducing Kiro workflows&lt;/a&gt;: Kiro workflows enable you to carry out complex tasks from start to finish with multiple agents and less supervision. We’ve been building Kiro itself with workflows, including the new cloud configuration, cloud sessions, and most of the workflow experience.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://strandsagents.com/blog/introducing-strands-decider/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;Introducing Strands Decider&lt;/a&gt;: Strands Decider is one of a new class of decision models or system one models, a type of model that has been gaining significant attention since TypeSafe AI’s launch of Jev earlier this month. Strands Decider 2B is a small, open source, decision model optimized for fast experimentation, local development, and innovation.&lt;/li&gt; 
 &lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/apn/new-fde-pathways-for-aws-partners-get-ready-for-production-agentic-ai-delivery/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;New FDE pathways for AWS Partners&lt;/a&gt;: On June 30, AWS announced the Forward Deployed Engineering (FDE) organization, backed by a $1 billion investment, and extended this hands-on delivery approach to AWS Partners through the Partner-Led FDE motion. Now, AWS Partners have a structured way to build and validate that depth with three new Partner FDE pathways and credentials that recognize the applied proficiency required to deliver production agentic AI.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;For a full list of AWS blog posts, be sure to keep an eye on the &lt;a href="https://aws.amazon.com/blogs/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Blogs&lt;/a&gt; page.&lt;/p&gt; 
&lt;p&gt;Learn more about AWS, browse and join upcoming &lt;a href="https://aws.amazon.com/events/explore-aws-events/?refid=e61dee65-4ce8-4738-84db-75305c9cd4fe"&gt;AWS-led in-person and virtual events&lt;/a&gt;, &lt;a href="https://aws.amazon.com/startups/events?tab=upcoming?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;startup events&lt;/a&gt;, and &lt;a href="https://builder.aws.com/connect/events?trk=e61dee65-4ce8-4738-84db-75305c9cd4fe&amp;amp;sc_channel=el"&gt;developer-focused events&lt;/a&gt;, including upcoming &lt;a href="https://aws.amazon.com/events/reinvent/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS&amp;nbsp;re:Invent&lt;/a&gt; and &lt;a href="https://aws.amazon.com/events/community-day/"&gt;AWS Community Days&lt;/a&gt;. Join the &lt;a href="https://builder.aws.com/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Builder Center&lt;/a&gt; to connect with builders, share solutions, and access content that supports your development.&lt;/p&gt; 
&lt;p&gt;That is all for this week. Check back next Monday for another Weekly Roundup!&lt;/p&gt; 
&lt;p&gt;— &lt;a href="https://www.linkedin.com/in/channy"&gt;Channy&lt;/a&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Announcing AWS Well-Architected Agent, an AI-powered intelligence to optimize your cloud environment (preview)</title>
		<link>https://aws.amazon.com/blogs/aws/announcing-aws-well-architected-agent-an-ai-powered-intelligence-to-optimize-your-cloud-environment-preview/</link>
					
		
		<dc:creator><![CDATA[Channy Yun (윤석찬)]]></dc:creator>
		<pubDate>Thu, 01 Oct 2026 20:04:04 +0000</pubDate>
				<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[AWS Support]]></category>
		<category><![CDATA[AWS Well-Architected]]></category>
		<category><![CDATA[Customer Enablement]]></category>
		<category><![CDATA[Generative AI]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">6936a126ff37e6868dadff2a0b59022a185e8d3c</guid>

					<description>Introducing the public preview of AWS Well-Architected Agent, an AI-powered service that analyzes your AWS environment to deliver targeted, contextual recommendations for improving your applications' cost, security, performance, and resilience—with ready-to-implement fixes aligned to your business goals.</description>
										<content:encoded>&lt;p&gt;Today, we’re announcing the public preview of &lt;strong&gt;AWS Well-Architected Agent&lt;/strong&gt;, an AI-powered service that analyzes your AWS environment to deliver targeted, contextual recommendations for improving your applications’ cost, security, performance, and resilience. The AWS Well-Architected Agent analyzes your infrastructure, understands unique business goals, and delivers contextual recommendations with ready-to-implement fixes. It delivers context-aware optimization without relying on manual audits or generic checklists.&lt;/p&gt; 
&lt;p&gt;The agent evaluates your environment as an experienced cloud architect would. It automatically correlates utilization metrics, resource configurations, and application topology, and analyzes against Well-Architected best practices across 65+ AWS services. It generates recommendations aligned to your declared business goals, delivers implementation packages with every finding, and surfaces cross-pillar trade-offs making it simpler to remediate the findings.&lt;/p&gt; 
&lt;p&gt;Here are the three main features of this service:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Goal-aligned intelligence&lt;/strong&gt;: AWS Well-Architected Agent replaces flat, undifferentiated findings with context-aware, prioritized recommendations. You declare your business objectives and share your application context. The agent automatically generates and prioritizes recommendations by impact and effort against those goals.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Three-level recommendations&lt;/strong&gt;: AWS Well-Architected Agent provides individual resource findings with specific dollar impact (where applicable) and step-by-step remediation, consolidated findings across multiple resources scoped to your application, and broad architectural patterns and designs with Infrastructure as Code (IaC) code changes needed to align with Well-Architected best practices.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Optionality in remediation&lt;/strong&gt;: You can choose your path on how you want to remediate with a complete implementation steps tailored to your environment: the console walk-throughs, updated IaC changes for architecture-level recommendations, and &lt;a href="https://aws.amazon.com/cli?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Command Line Interface (AWS CLI)&lt;/a&gt; commands.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;AWS Well-Architected Agent in action&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; To get started, create an agent profile to define the scope of what Well-Architected Agent can access and provide recommendations on, complete the IAM role setup to access resources, conduct architecture review, and remediate recommendations.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Create an agent profile&lt;/strong&gt;&lt;br&gt; In the &lt;a href="https://console.aws.amazon.com/wellarchitected/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Well-Architected console&lt;/a&gt;, choose &lt;strong&gt;Get started with Well-Architected Agent&lt;/strong&gt;. You can define an agent profile that specifies which AWS accounts and applications to monitor, which optimization pillars to focus on, and the permissions required.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-105820 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/27/2026-well-architect-agent-1.jpg" alt="" width="1142" height="2560"&gt;&lt;/p&gt; 
&lt;p&gt;You can choose AWS accounts or AWS Regions to monitor and optimization pillars that matter most to your business. You can also set goals for each pillar: cost optimization, performance, resilience, and security.&lt;/p&gt; 
&lt;p&gt;To give access to the agent for your AWS environment, provision customer-managed IAM roles the agent uses to read resource configurations, utilization metrics, and application topology. To learn more, visit the &lt;a href="https://docs.aws.amazon.com/wellarchitected/latest/userguide/security-iam-agent.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;IAM prerequisite for AWS Well-Architected Agent&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;When you choose &lt;strong&gt;Get Started&lt;/strong&gt;, the agent creates your agent profile. Resource and application recommendations will be generated within 24 hours after profile creation.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-105821 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/27/2026-well-architect-agent-7.jpg" alt="" width="1800" height="1101"&gt;&lt;/p&gt; 
&lt;p&gt;You can conduct an architecture review on pre-deployment workloads by uploading an IaC project in &lt;a href="https://github.com/hashicorp/terraform"&gt;Terraform&lt;/a&gt;, &lt;a href="https://aws.amazon.com/cloudformation/"&gt;AWS CloudFormation&lt;/a&gt;, or &lt;a href="https://aws.amazon.com/cdk/"&gt;AWS Cloud Development Kit (CDK)&lt;/a&gt; to be analyzed. Choose &lt;strong&gt;Conduct architecture review&lt;/strong&gt; in the dashboard, upload a.zip file containing IaC project or repository file, and select which Well-Architected lens to use for reviewing your infrastructure.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105164" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/07/29/2026-well-architect-agent-6.jpg" alt="" width="1800" height="1221"&gt;&lt;/p&gt; 
&lt;p&gt;You can define your applications to add context which will enhance the relevancy and further contextualize recommendations. Choose &lt;strong&gt;Add application context&lt;/strong&gt; in the dashboard, add your applications with AWS accounts, AWS Regions, AWS services, tags if you want to narrow the scope to specific resources, and the details of applications.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter size-full wp-image-105166" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/07/29/2026-well-architect-agent-8.jpg" alt="" width="1800" height="1430"&gt;&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Review prioritized recommendations and start remediating&lt;/strong&gt;&lt;br&gt; Now you can see generated prioritized recommendations generated by the agent across your resources and applications, selected pillars, ranked against your declared goals, with automation-ready remediation included.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-105822 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/27/2026-well-architect-agent-2.jpg" alt="" width="1800" height="2094"&gt;&lt;/p&gt; 
&lt;p&gt;When you choose the specific recommendation, you can see the details, insights into why the agent are suggesting the recommendation, impacts and trade-off, and recommended fixes across affected AWS resources.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-105823 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/27/2026-well-architect-agent-3.jpg" alt="" width="1800" height="2531"&gt;&lt;/p&gt; 
&lt;p&gt;Choose &lt;strong&gt;Start remediation&lt;/strong&gt; to address recommended fixes. You can choose the console, updated IaC template, CLI commands to remediate by the resolution type. It provides detailed step-by-step instructions and you can roll out this instruction and verify the result.&lt;/p&gt; 
&lt;p&gt;&lt;img loading="lazy" class="aligncenter wp-image-105824 size-full" style="border: solid 1px #ccc" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/27/2026-well-architect-agent-4.jpg" alt="" width="1800" height="1459"&gt;&lt;/p&gt; 
&lt;p&gt;When you choose &lt;strong&gt;Using updated IaC template&lt;/strong&gt;, the agent provides the code changes needed to update your existing IaC templates such as the CDK function shown above which you can copy directly into your codebase.&lt;/p&gt; 
&lt;p&gt;You can also configure API access to integrate recommendations directly into your existing development and operations workflows. To interact with the agent programmatically, including calling APIs and searching documentation, try the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/getting-started-aws-mcp-server.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS MCP Server&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/plugins.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;plugins&lt;/a&gt; with your preferred AI coding tool.&amp;nbsp;To learn more, visit the &lt;a href="https://docs.aws.amazon.com/wellarchitected/latest/userguide/agent.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Well-Architected Agent documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Things to know&lt;/strong&gt;&lt;br&gt; Here are some things that you should know about the Well-Architected Agent.&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Automation&lt;/strong&gt;: You can receive recommendations with the exact IaC code changes needed to remediate, with risks identified by pillar, catching issues before they reach production. Recommendations are delivered through the console and API so you can act without context-switching. Recommendations are also updated periodically, so new recommendations are available for your team to track regularly.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Evaluation&lt;/strong&gt;: Generative AI capabilities produce this recommendation, which may contain errors or incomplete information. You are responsible for evaluating the recommendation in your specific context and implementing appropriate oversight and safeguards. Learn more about &lt;a href="https://aws.amazon.com/ai/responsible-ai/policy/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Responsible AI practices&lt;/a&gt;.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;You can still use existing &lt;a href="https://aws.amazon.com/well-architected-tool/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Well-Architected Tool&lt;/a&gt; to manually evaluate your cloud architecture with &lt;a href="https://docs.aws.amazon.com/wellarchitected/latest/userguide/lenses-custom.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;user-defined lenses&lt;/a&gt; that measure your workload using your own best practices.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Join the preview&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Access to the AWS Well-Architected Agent and its recommendations is available in US East (N. Virginia), US East (Ohio), and US West (Oregon). You can onboard workloads from any AWS commercial Region. AWS Well-Architected Agent is delivered by AWS Support and available to AWS customers with an &lt;a href="https://aws.amazon.com/premiumsupport/plans/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Support plan&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Give it a try today in the &lt;a href="https://console.aws.amazon.com/wellarchitected/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&amp;amp;sc_channel=el"&gt;AWS Well-Architected console&lt;/a&gt; and send feedback&amp;nbsp;through your usual AWS Support contacts.&lt;/p&gt; 
&lt;p&gt;— &lt;a href="https://linkedin.com/in/channy"&gt;Channy&lt;/a&gt;&lt;/p&gt;</content:encoded>
					
					
			
		
		
			</item>
		<item>
		<title>Amazon S3 Tables now support all Apache Iceberg V3 data types</title>
		<link>https://aws.amazon.com/blogs/aws/amazon-s3-tables-now-support-all-apache-iceberg-v3-data-types/</link>
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Wed, 30 Sep 2026 22:10:00 +0000</pubDate>
				<category><![CDATA[Amazon S3 Tables]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Storage]]></category>
		<guid isPermaLink="false">817caa03e06c6ac753e2104bcdd58418a88fea6e</guid>

					<description>Amazon S3 Tables now support all data types in the Apache Iceberg V3 spec, along with column default values, deletion vectors, and row lineage. Upgrade existing V2 tables or create new V3 tables with built-in compaction, maintenance, and engine compatibility.</description>
										<content:encoded>&lt;p&gt;&lt;a href="https://aws.amazon.com/s3/features/tables/"&gt;Amazon S3 Tables&lt;/a&gt; now support all data types in the Apache Iceberg V3 specification. You can create V3 tables or upgrade existing V2 tables to take advantage of &lt;a href="https://iceberg.apache.org/spec/#version-3-extended-types-and-capabilities"&gt;V3 features&lt;/a&gt; like deletion vectors, row lineage, and new data types such as variant, nanosecond timestamps, unknown, geometry, and geography.&lt;/p&gt; 
&lt;p&gt;Apache Iceberg has become the open standard for managing large analytics datasets. It lets you manage petabyte-scale tables with features like schema evolution, hidden partitioning, and time travel queries, while keeping your data in open Parquet files in data lakes on object storage like &lt;a href="https://aws.amazon.com/s3/"&gt;Amazon S3&lt;/a&gt;. Amazon S3 Tables offer storage purpose-built to keep Iceberg tables performant and cost-effective as they grow, with fully managed features like automatic compaction, maintenance, replication, and Intelligent-Tiering.&lt;/p&gt; 
&lt;p&gt;Teams running analytics on Apache Iceberg V2 tables often hit the same limits as their data grows. A compliance request to delete 50,000 user records from a 2-billion-row table leaves behind positional delete files that slow queries until compaction runs. Semi-structured events land as JSON strings that every query has to parse. Geospatial coordinates and nanosecond-precision timestamps get encoded as strings or integers. Each workaround adds storage cost, query latency, and pipeline code. With V3, Iceberg solves these challenges by offering native support for semi-structured and geospatial data, faster row-level operations, and built-in row lineage for data governance.&lt;/p&gt; 
&lt;p&gt;Starting today, Amazon S3 Tables support all V3 data types, including variant, nanosecond timestamps, geometry, geography, and unknown, along with deletion vectors and row lineage. You can create new V3 tables or upgrade existing V2 tables in place, and S3 Tables continue to run compaction and maintenance for you.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Apache Iceberg V3&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; V3 is the latest version of the &lt;a href="https://iceberg.apache.org/spec/#version-3-extended-types-and-capabilities"&gt;Iceberg specification&lt;/a&gt;. Among its many improvements, V3 introduces capabilities that address the most common pain points in V2. This includes:&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Deletion vectors&lt;/strong&gt; replace V2’s positional delete files with a compact binary format. That 50,000-row compliance delete now writes a single deletion vector file instead of thousands of small deletes, significantly reducing compaction time and delete file overhead.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Row lineage&lt;/strong&gt; adds &lt;code&gt;_row_id&lt;/code&gt; and &lt;code&gt;_last_updated_sequence_number&lt;/code&gt; to each record automatically. Your downstream pipelines can query these fields to find changed rows without scanning the full table.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;New data types&lt;/strong&gt; let you store semi-structured, geospatial, and nanosecond-precision data natively instead of encoding it as strings or integers:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Nanosecond timestamp(tz)&lt;/strong&gt; for nanosecond-precision timestamps&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Geometry&lt;/strong&gt; and &lt;strong&gt;geography&lt;/strong&gt; for geospatial data&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Unknown&lt;/strong&gt; for columns with no known type&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;Variant data type&lt;/strong&gt; stores semi-structured data in columnar format. During writes, the engine shreds variant data into hidden columns and collects statistics. At query time, those statistics enable file pruning that significantly reduces I/O compared to parsing JSON strings.&lt;/p&gt; 
&lt;p&gt;The following sections walk through how to use these V3 capabilities in practice, with examples that show how to create tables, work with the new data types, and manage data at scale.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Getting started&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; A retail analytics team tracks user behavior across web and mobile apps. Each event has a different structure: page views include URLs and duration, purchases include items and amounts, and searches include query terms and result counts. With V3’s variant type, you store all event shapes in one table without predefined schemas:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;CREATE TABLE my_catalog.namespace.clickstream (
  event_id bigint,
  event_time timestamp,
  user_id string,
  payload variant
)
USING iceberg
TBLPROPERTIES ('format-version' = '3')
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Insert events with different payload shapes without worrying about schema evolution:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;INSERT INTO my_catalog.namespace.clickstream VALUES
  (1, current_timestamp(), 'user-42',
   PARSE_JSON('{"action": "purchase", "amount": 99.99, "items": ["laptop_stand"]}')),
  (2, current_timestamp(), 'user-17',
   PARSE_JSON('{"action": "page_view", "url": "/products/webcam", "duration_ms": 4200}'));
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Now query the variant column directly, without &lt;code&gt;PARSE_JSON&lt;/code&gt; at read time. With Amazon EMR Spark, use &lt;code&gt;variant_get&lt;/code&gt;:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;SELECT
  event_id,
  user_id,
  variant_get(payload, '$.action', 'string') AS action,
  variant_get(payload, '$.amount', 'double') AS amount
FROM my_catalog.namespace.clickstream
WHERE variant_get(payload, '$.action', 'string') = 'purchase'
  AND variant_get(payload, '$.amount', 'double') &amp;gt; 50.00
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;To enable deletion vectors for write operations, configure merge-on-read mode:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;ALTER TABLE my_catalog.namespace.clickstream
SET TBLPROPERTIES (
  'write.delete.mode' = 'merge-on-read',
  'write.update.mode' = 'merge-on-read',
  'write.merge.mode' = 'merge-on-read'
)
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Now when you run a compliance delete, V3 writes a small deletion vector instead of rewriting data files:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;DELETE FROM my_catalog.namespace.clickstream
WHERE user_id = 'user-42'
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;S3 Tables compaction handles these deletion vector files automatically on the next maintenance cycle.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Upgrading from V2&lt;/strong&gt;&lt;br&gt; AWS provides backwards compatibility for both versions to minimize disruption during migration to V3. Existing V2 readers continue to work on upgraded tables until you’re ready to fully adopt V3 features. For more details, see the &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/working-with-apache-iceberg-v3.html"&gt;S3 Tables Iceberg V3 documentation&lt;/a&gt;.&lt;br&gt; Upgrade an existing table atomically without rewriting data:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;ALTER TABLE my_catalog.namespace.existing_table
SET TBLPROPERTIES ('format-version' = '3')
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;On the next compaction cycle, S3 Tables remove old V2 delete files. New modifications use deletion vectors automatically. Row lineage fields initialize on the first data modification after the upgrade.&lt;/p&gt; 
&lt;p&gt;This is a one-way operation. The Apache Iceberg specification does not support downgrading from V3 to V2. Verify that all engines accessing the table support V3 before upgrading.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Using row lineage for incremental pipelines&lt;/strong&gt;&lt;br&gt; After your table has V3 data, use row lineage to build efficient incremental pipelines:&lt;/p&gt; 
&lt;pre class="lang-sql"&gt;&lt;code&gt;SELECT *, _row_id, _last_updated_sequence_number
FROM my_catalog.namespace.clickstream
WHERE _last_updated_sequence_number &amp;gt; 42
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;This returns only rows modified after sequence number 42. Your downstream jobs can checkpoint this value and process only new changes on each run, instead of scanning the full table.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Compatibility across AWS analytics services&lt;/strong&gt;&lt;br&gt; AWS offers the broadest native Apache Iceberg support of any major cloud provider, with Iceberg-compatible services at every layer of the data stack: ingestion, storage, catalog, and analytics. You can store and automatically optimize V3 tables in Amazon S3 Tables, write data with &lt;a href="https://aws.amazon.com/emr/"&gt;Amazon EMR&lt;/a&gt; Spark, integrate and manage data with &lt;a href="https://aws.amazon.com/blogs/aws/aws-glue-6-0-now-available-with-30-lower-price-and-full-apache-iceberg-v3-support/"&gt;AWS Glue&lt;/a&gt;, and run analytics with &lt;a href="https://aws.amazon.com/redshift/"&gt;Amazon Redshift&lt;/a&gt;. To learn more about AWS analytics support for V3, see the &lt;a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/apache-iceberg-on-aws/table-spec-v3.html"&gt;Apache Iceberg on AWS prescriptive guidance&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Both S3 Tables and &lt;a href="https://aws.amazon.com/glue/"&gt;AWS Glue&lt;/a&gt; Data Catalog support the Iceberg REST Catalog (IRC) API, enabling interoperability across engines regardless of the catalog endpoint.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Things to know&lt;/strong&gt;&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;S3 Tables compaction fully supports V3 deletion vector files and preserves row lineage metadata.&lt;/li&gt; 
 &lt;li&gt;The new V3 data types (variant, nanosecond timestamps, geometry, geography, and unknown) require an engine built on Apache Spark 4.0 or later, such as AWS Glue 6.0 or later, or Amazon EMR release 8.1 or later.&lt;/li&gt; 
 &lt;li&gt;You can create V3 tables from the &lt;a href="https://console.aws.amazon.com/s3/"&gt;Amazon S3 console&lt;/a&gt;, &lt;a href="https://docs.aws.amazon.com/cli/latest/reference/s3tables/"&gt;AWS CLI&lt;/a&gt;, or any engine that supports the Iceberg REST Catalog API.&lt;/li&gt; 
 &lt;li&gt;The new V3 data types are supported only for tables that use the Parquet file format (not ORC or Avro).&lt;/li&gt; 
 &lt;li&gt;Columns of type variant, geometry, geography, or nanosecond timestamp can’t be included in a table’s sort order for compaction. Tables containing these columns still compact under the sort and Z-order strategies when the sort order uses columns of other types.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Now available&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Amazon S3 Tables support for all Apache Iceberg V3 data types is now available in all AWS Regions where S3 Tables are supported. Apache Iceberg V3 support is available at no additional charge; standard S3 Tables pricing applies.&lt;/p&gt; 
&lt;p&gt;To get started, visit the &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables.html"&gt;Amazon S3 Tables documentation&lt;/a&gt; or create a table bucket from the &lt;a href="https://console.aws.amazon.com/s3/"&gt;Amazon S3 console&lt;/a&gt;. If you want to call APIs, search documentation, find regional availability, and check troubleshooting about this feature, try using the &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/getting-started-aws-mcp-server.html"&gt;AWS MCP Server&lt;/a&gt; and &lt;a href="https://docs.aws.amazon.com/agent-toolkit/latest/userguide/plugins.html"&gt;plugins&lt;/a&gt; with your preferred AI tool. Send feedback to &lt;a href="https://repost.aws/tags/TADSTjraA0Q4-a1dxk6eUYaw/amazon-simple-storage-service"&gt;AWS re:Post&lt;/a&gt; or through your usual &lt;a href="https://aws.amazon.com/support/"&gt;AWS Support&lt;/a&gt; contacts.&lt;/p&gt; 
&lt;p&gt;– Daniel Abib&lt;/p&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Amazon S3 Vectors now supports metadata pre-filtering for higher recall on filtered searches</title>
		<link>https://aws.amazon.com/blogs/aws/amazon-s3-vectors-now-supports-metadata-pre-filtering-for-higher-recall-on-filtered-searches/</link>
		
		<dc:creator><![CDATA[Daniel Abib]]></dc:creator>
		<pubDate>Wed, 30 Sep 2026 20:03:34 +0000</pubDate>
				<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Storage]]></category>
		<guid isPermaLink="false">e76e8a63de9311bd1dde4b12497cc264c4918389</guid>

					<description>Amazon S3 Vectors now supports metadata pre filtering, delivering up to 5x higher recall on filtered searches. Filters evaluate before similarity search so scoped queries return more relevant results. Ideal for RAG, agentic apps, and document search.</description>
										<content:encoded>&lt;p&gt;Today, we’re announcing metadata pre-filtering for &lt;a href="https://aws.amazon.com/s3/features/vectors/"&gt;Amazon S3 Vectors&lt;/a&gt;, which delivers higher recall on filtered queries by evaluating your metadata filter before the similarity search. You can filter on attributes such as tenant, category, status, or time, and pre-filtering adds prefix matching with &lt;code&gt;$startsWith&lt;/code&gt; for paths, URLs, and hierarchical keys. Each vector carries up to 2 KB of filterable metadata, and a single query supports up to 100 filter constraints. There is no additional cost, no re-ingestion, and no change to your queries.&lt;/p&gt; 
&lt;p&gt;Most applications never search a whole index. They search the part of it that belongs to a particular user, account, or category, and they express that scope as a metadata filter. Semantic search, retrieval-augmented generation (RAG), and agentic applications all need the same thing from a filtered query: a similarity search that covers the vectors matching the filter, and returns the closest of them. With pre-filtering, a filtered query returns more of the relevant matches your index contains, giving you higher recall on filtered searches.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Common use cases&lt;/strong&gt;&lt;br&gt; Pre-filtering applies wherever results have to be both relevant and correctly scoped:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;&lt;strong&gt;Legal and professional services&lt;/strong&gt;: A law firm or e-discovery platform searches documents scoped to a single client, and with &lt;code&gt;$startsWith&lt;/code&gt; narrows further by matter number, folder path, or document ID prefix. A single client is a small share of a firm-wide archive, and filters this narrow are where pre-filtering improves recall most.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Financial services&lt;/strong&gt;: An investment research platform searches analyst notes, filings, and call transcripts scoped by issuer, document type, and publication date.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Media and entertainment&lt;/strong&gt;: A streaming service filters by content rating and regional licensing before the semantic search, finding similar titles restricted to G and PG content licensed in one territory.&lt;/li&gt; 
 &lt;li&gt;&lt;strong&gt;Agentic applications&lt;/strong&gt;: An agent working within a user’s session filters on fields such as owner, document set, and timestamp so its searches cover the material relevant to the task at hand. Higher recall means more of that material reaches the agent, which improves task reliability&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;How pre-filtering works&lt;/strong&gt;&lt;br&gt; Each vector in an S3 Vectors index can carry application-defined metadata, and a query can filter on those fields.&lt;/p&gt; 
&lt;p&gt;Every vector index has an index mode. On an index whose index mode is &lt;code&gt;ENHANCED&lt;/code&gt;, S3 Vectors resolves your filter first, then searches only the vectors that match. On an index whose index mode is &lt;code&gt;CLASSIC&lt;/code&gt;, S3 Vectors performs the vector search and filter evaluation in tandem, validating each candidate vector against your filter as it searches. Existing indexes use &lt;code&gt;CLASSIC&lt;/code&gt; until you update them.&lt;/p&gt; 
&lt;p&gt;Consider a support knowledge base of 8 million tickets, where an agent searches one customer’s history for a recurring error. If that customer accounts for 400 of those tickets, resolving &lt;code&gt;customer_id&lt;/code&gt; first means the similarity search runs across all 400 of them, so the agent sees that customer’s prior occurrences. Before the index was updated, the same query drew its candidates from the full 8 million, and the result set contained fewer of that customer’s matching tickets.&lt;/p&gt; 
&lt;p&gt;On highly selective filters, pre-filtering returns up to 5x more of the matching vectors than the same query returned before on &lt;code&gt;CLASSIC&lt;/code&gt; indexes.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Getting started&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Before you start, make sure your IAM policy grants permissions for the new actions.&lt;/p&gt; 
&lt;p&gt;You can get started in three steps. The walkthrough below builds a small product-catalog index and runs a selective filter against it, the same pattern you would use for a multi-tenant RAG store or a document search scoped to one client.&lt;/p&gt; 
&lt;p&gt;First, create a vector index:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors create-index \ 
  --index-name product-catalog \ 
  --vector-bucket-name my-vector-bucket \ 
  --dimension 1536 \ 
  --distance-metric cosine&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The &lt;code&gt;dimension&lt;/code&gt; must match the output size of your embedding model, and &lt;code&gt;distance-metric&lt;/code&gt; should match how that model was trained (cosine is common for text embeddings). Second, write vectors with the PutVectors API, attaching up to 2 KB of filterable metadata to each vector:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors put-vectors \
  --index-name product-catalog \
  --vector-bucket-name my-vector-bucket \
  --vectors '[{
    "key": "doc-001",
    "data": {"float32": [0.1, 0.2, 0.3, ...]},
    "metadata": {
      "tenant_id": "t-10428",
      "category": "legal",
      "created_date": "2026-03-15",
      "active": true
    }
  }]'
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Each vector carries the attributes your application filters on. In this example, &lt;code&gt;tenant_id&lt;/code&gt; scopes results to a single customer, &lt;code&gt;category&lt;/code&gt; narrows by document type, &lt;code&gt;created_date&lt;/code&gt; records when the document was created, and &lt;code&gt;active&lt;/code&gt; is a boolean flag. By default every metadata field is filterable, so you can query on any of them without declaring a schema up front.&lt;/p&gt; 
&lt;p&gt;Third, run a filtered similarity query with the QueryVectors API. The filter uses a compact JSON syntax where a bare key-value pair is an equality match, and operators such as &lt;code&gt;$and&lt;/code&gt;, &lt;code&gt;$or&lt;/code&gt;, and &lt;code&gt;$gt&lt;/code&gt; combine or refine conditions. Pass &lt;code&gt;--return-metadata&lt;/code&gt; so the query returns each vector’s metadata:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors query-vectors \
  --index-name product-catalog \
  --vector-bucket-name my-vector-bucket \
  --query-vector '{"float32": [0.1, 0.2, 0.3, ...]}' \
  --top-k 50 \
  --return-metadata \
  --filter '{"$and": [
    {"tenant_id": "t-10428"},
    {"category": "legal"},
    {"active": true}
  ]}'
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;The expected result is a single vector, &lt;code&gt;doc-001&lt;/code&gt;, the only one matching all three filter conditions (tenant_id, category, and active):&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-json"&gt;{
  "vectors": [
    {
      "distance": 0.9717477560043335,
      "key": "doc-001",
      "metadata": {
        "tenant_id": "t-10428",
        "category": "legal",
        "created_date": "2026-03-15",
        "active": true
      }
    }
  ],
  "distanceMetric": "cosine"
}
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;S3 Vectors first narrows the search space to vectors matching all three filter conditions, then returns the 50 most similar vectors from that subset. Because the filter is applied before the search, those results are drawn from across all the vectors that match it.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Prefix matching with $startsWith&lt;/strong&gt;&lt;br&gt; Pre-filtering adds a prefix match operator for filtering on paths, URLs, and hierarchical keys. A document store that encodes case and folder structure into a document ID can scope a search to a subtree in one condition:&lt;/p&gt; 
&lt;pre&gt;&lt;code&gt;--filter '{"$startsWith": {"document_id": "matter-4417/exhibits/"}}'
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;&lt;code&gt;$startsWith&lt;/code&gt; joins the existing operators: equality, numeric range, set membership, existence checks, and boolean logic with &lt;code&gt;$and&lt;/code&gt; and &lt;code&gt;$or&lt;/code&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;strong&gt;Turning on pre-filtering for existing indexes&lt;/strong&gt;&lt;br&gt; Call UpdateIndexMode on an existing index to turn on pre-filtering:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors update-index-mode \
  --vector-bucket-name my-vector-bucket \
  --index-name product-catalog \
  --index-mode ENHANCED
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Pre-filtering takes effect in place. Your existing vectors are not re-ingested, your queries do not change, and the new filter operators are available immediately.&lt;/p&gt; 
&lt;p&gt;Here is the difference on the same index and the same query. Before the update, a query scoped to one tenant returns two of the ten results requested:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors query-vectors \
  --vector-bucket-name my-vector-bucket \
  --index-name product-catalog \
  --query-vector '{"float32": [0.1, 0.2, 0.3, ...]}' \
  --top-k 10 \
  --return-metadata \
  --filter '{"tenant_id": "t-10428"}'
&lt;/code&gt;&lt;/pre&gt; 
&lt;pre&gt;&lt;code class="lang-json"&gt;{
  "vectors": [
    { "key": "doc-114", "distance": 0.41 },
    { "key": "doc-322", "distance": 0.55 }
  ],
  "distanceMetric": "cosine"
}
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;After the update, the same query returns a full result set drawn from across that tenant’s documents:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-json"&gt;{
  "vectors": [
    { "key": "doc-018", "distance": 0.09 },
    { "key": "doc-207", "distance": 0.13 },
    { "key": "doc-114", "distance": 0.41 },
    ... 7 more
  ],
  "distanceMetric": "cosine"
}
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;&lt;strong&gt;Rolling out across your indexes&lt;/strong&gt;&lt;br&gt; Once you have validated pre-filtering on an index, set the default index mode on the vector bucket so that new indexes use &lt;code&gt;ENHANCED&lt;/code&gt; without a follow-up call:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors put-vector-bucket-default-index-mode \
  --vector-bucket-name my-vector-bucket \
  --default-index-mode ENHANCED
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;To bring the rest of your existing indexes across, list them and check the index mode on each one, then call UpdateIndexMode on the ones still using &lt;code&gt;CLASSIC&lt;/code&gt;:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-bash"&gt;aws s3vectors list-indexes \
  --vector-bucket-name my-vector-bucket

aws s3vectors get-index \
  --vector-bucket-name my-vector-bucket \
  --index-name product-catalog
&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;&lt;strong&gt;Things to know&amp;nbsp;&lt;/strong&gt;&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt;Indexes created in vector buckets created on or after September 30, 2026 use index mode &lt;strong&gt;ENHANCED&lt;/strong&gt;. Indexes in buckets that existed before that date use &lt;strong&gt;CLASSIC&lt;/strong&gt; until you set the bucket default, including indexes created in those buckets afterward.&lt;/li&gt; 
 &lt;li&gt;A single query supports up to 100 filter constraints, counted per value the filter evaluates. If a query exceeds that, you can usually consolidate the filter, replacing a 300-value &lt;strong&gt;$in&lt;/strong&gt; over legal cases with a single &lt;strong&gt;caseId&lt;/strong&gt; field, for example, or split it into smaller queries, run them in parallel, and merge the results by distance.&lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Now available&lt;/u&gt;&lt;/strong&gt;&lt;br&gt; Metadata pre-filtering is available at no additional cost in all commercial AWS Regions where &lt;a href="https://aws.amazon.com/s3/features/vectors/"&gt;Amazon S3 Vectors&lt;/a&gt; is available, and in the AWS China Regions. You pay standard S3 Vectors pricing for storage, PUT requests, and queries. For full pricing details, visit the &lt;a href="https://aws.amazon.com/s3/pricing/"&gt;Amazon S3 pricing page&lt;/a&gt;. For regional availability, visit &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors-regions-quotas.html"&gt;Amazon S3 Vectors Regions and quotas&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;Whether you’re scoping a RAG application to one tenant, scoping an agent’s searches to one user’s documents, or narrowing a catalog search to a licensing window, pre-filtering lets you apply those filters without trading away recall. To learn more and get started, visit the &lt;a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors.html"&gt;Amazon S3 Vectors documentation&lt;/a&gt;. Send feedback to &lt;a href="https://repost.aws/tags/TADSTjraA0Q4-a1dxk6eUYaw/amazon-simple-storage-service"&gt;AWS re:Post for S3&lt;/a&gt; or through your usual AWS Support contacts.&lt;/p&gt; 
&lt;p&gt;— Daniel Abib&lt;/p&gt;</content:encoded>
					
		
		
			</item>
		<item>
		<title>Amazon Aurora PostgreSQL now supports direct querying of Apache Iceberg and Parquet data in your data lake</title>
		<link>https://aws.amazon.com/blogs/aws/amazon-aurora-postgresql-now-supports-direct-querying-of-apache-iceberg-and-parquet-data-in-your-data-lake/</link>
					
		
		<dc:creator><![CDATA[Esra Kayabali]]></dc:creator>
		<pubDate>Wed, 30 Sep 2026 17:22:31 +0000</pubDate>
				<category><![CDATA[Amazon Aurora]]></category>
		<category><![CDATA[Amazon Simple Storage Service (S3)]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Launch]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">ea1cc456e7a2e65a27ab5c8db65b3016bf527355</guid>

					<description>Amazon Aurora PostgreSQL now lets you directly query Apache Iceberg and Parquet data stored in your data lake alongside live operational data—no ETL pipelines required. Powered by DuckDB embedded within Aurora, this capability enables single queries that join transactional and historical data using familiar PostgreSQL syntax. It supports AWS Glue Data Catalog, S3, and S3 Tables, with optimizations like predicate pushdown and caching for efficient performance.</description>
										<content:encoded>&lt;p&gt;Today, we’re announcing a new capability for &lt;a href="https://aws.amazon.com/rds/aurora/"&gt;Amazon Aurora PostgreSQL&lt;/a&gt; that you can use to directly query operational data together with data stored in your data lake in Apache Iceberg and Apache Parquet formats, using your existing PostgreSQL applications and tools. By eliminating the need to extract, transform, and load (ETL) structured data from data lakes into your operational database, you can reduce operational complexity and simplify application development. You can also use Aurora PostgreSQL to query data from data lakes managed in Iceberg REST Catalog (IRC)-compatible catalogs, giving you access to data across a breadth of analytics systems without moving or duplicating it. Whether you’re powering real-time dashboards, enriching transactions with historical context, or building AI agents that reason over both live and archived data, you can now do it all through a single, familiar interface.&lt;/p&gt; 
&lt;p&gt;Previously, if your application needed to combine recent transactional data in Aurora with historical records stored in Amazon S3, a common approach was to build reverse ETL pipelines that duplicated data, increased infrastructure costs, and required ongoing engineering effort to keep everything synchronized. This challenge only grows as you increasingly embed AI agents into your applications, where it is impractical to predict and pre-replicate every dataset an agent might need.&lt;/p&gt; 
&lt;p&gt;DuckLabs, the team that maintains the DuckDB project, recently joined Amazon, and this capability is an example of how the efficiency of DuckDB is being integrated into our services. DuckDB is now embedded directly within Aurora PostgreSQL, so you can query live operational data (including uncommitted writes) alongside your data lake in a single query. Query processing stays within Aurora, with no additional network hops and no ETL pipelines that duplicate data. You can query Apache Iceberg tables managed through the AWS Glue Data Catalog, as well as Parquet and Iceberg data stored in Amazon S3 and S3 Tables. You do all of this using familiar PostgreSQL syntax and your existing applications and tools.&lt;/p&gt; 
&lt;p&gt;We’re excited to bring the speed and simplicity of DuckDB directly into Aurora PostgreSQL, so you and your agents can query and combine operational and Iceberg data using the familiar PostgreSQL applications, tools, and endpoints already in use. By building this capability around DuckDB, future improvements to the open source engine can continue to bring performance and functionality gains to Aurora and other AWS services.&lt;/p&gt; 
&lt;p&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;What is new&lt;br&gt; &lt;/strong&gt;&lt;/span&gt;This capability is supported on two Aurora PostgreSQL major versions: 17 (starting with 17.11) and 18 (starting with 18.6). To use it, you create an Aurora PostgreSQL cluster, attach an IAM role with the &lt;code&gt;AuroraAnalytics&lt;/code&gt; feature, and enable the &lt;code&gt;aurora_analytics&lt;/code&gt; extension. The IAM role is what gives Aurora access to your data in Amazon S3 and the AWS Glue Data Catalog. You then create foreign tables that point to your Iceberg or Parquet data in the data lake, and query them using familiar PostgreSQL syntax. You can complete this setup through the &lt;a href="https://console.aws.amazon.com/rds/home"&gt;Amazon RDS console&lt;/a&gt;, or with any PostgreSQL client such as psql. The process is well documented in the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/" target="_blank" rel="noopener noreferrer"&gt;Aurora PostgreSQL documentation&lt;/a&gt;.&lt;/p&gt; 
&lt;p&gt;&lt;a href="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/24/1218110723436617-0c.png"&gt;&lt;img loading="lazy" class="alignnone size-full wp-image-105780" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/24/1218110723436617-0c.png" alt="" width="842" height="787"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;You can query data across external IRC-compatible catalogs through AWS Glue Data Catalog federation. You register the external catalog once with Glue, and then create foreign tables for the tables you want to query, the same way you would for any Glue-native table. A single query can then join data stored in Aurora with Iceberg tables registered across multiple catalogs, so applications get a unified view without moving data or replacing your existing catalog investments.&lt;/p&gt; 
&lt;p&gt;Aurora also applies optimizations such as predicate pushdown and column pruning so that only the relevant data is read. This keeps queries efficient even as the underlying data grows. Frequently accessed data is also cached in your Aurora instance, so subsequent queries against the same data return faster. You can inspect this behavior per query using &lt;code&gt;aurora_analytics_stat_statements()&lt;/code&gt;, which reports metrics such as rows scanned, bytes read from Amazon S3, and cache hits.&lt;/p&gt; 
&lt;p&gt;To see how direct querying works, I connected to my Aurora PostgreSQL database using psql and created the extension:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-sql"&gt;CREATE EXTENSION aurora_analytics;&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;For my walkthrough, I set up a simple financial scenario. I have a &lt;code class="inline-code"&gt;recent_transactions&lt;/code&gt; table in Aurora with the last 7 days of customer transactions, and a Parquet file in Amazon S3 containing 5 years of historical transaction data. To make Aurora aware of the historical data, I created a foreign table pointing at the Parquet file in S3:&lt;/p&gt; 
&lt;pre&gt;&lt;code class="lang-sql"&gt;CREATE FOREIGN TABLE transaction_history ()
SERVER aurora_analytics_server
OPTIONS (
    location 's3://&amp;lt;my-bucket&amp;gt;/finance/transaction_history.parquet',
    format 'parquet'
);&lt;/code&gt;&lt;/pre&gt; 
&lt;p&gt;Notice the empty parentheses in the &lt;code class="inline-code"&gt;CREATE FOREIGN TABLE&lt;/code&gt; statement. Aurora automatically reads the schema from the Parquet file metadata, so you do not need to define columns manually. For workloads with many tables, you can skip creating them one at a time: a single &lt;code&gt;IMPORT FOREIGN SCHEMA&lt;/code&gt; statement bulk-creates foreign tables for every Iceberg or Parquet table in an AWS Glue Data Catalog database, inferring schemas automatically.&lt;/p&gt; 
&lt;p&gt;With both tables in place, I ran a single query that combines the recent operational data in Aurora with the historical data in S3:&lt;/p&gt; 
&lt;div class="code-block-wrapper"&gt; 
 &lt;div class="token-line"&gt; 
  &lt;pre&gt;&lt;code class="lang-sql"&gt;SELECT merchant, category, amount, transaction_date, 'recent' AS source
FROM recent_transactions
WHERE customer_id = 'C-1001'
UNION ALL
SELECT merchant, category, amount, transaction_date, 'historical' AS source
FROM transaction_history
WHERE customer_id = 'C-1001'
  AND transaction_date &amp;gt;= CURRENT_DATE - INTERVAL '5 years'
ORDER BY transaction_date DESC
LIMIT 15;&lt;/code&gt;&lt;/pre&gt; 
 &lt;/div&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;a href="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/24/1218110723436617-1a.png"&gt;&lt;img loading="lazy" class="alignnone size-full wp-image-105781" src="https://d2908q01vomqb2.cloudfront.net/da4b9237bacccdf19c0760cab7aec4a8359010b0/2026/09/24/1218110723436617-1a.png" alt="" width="811" height="731"&gt;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;The result shows both recent and historical transactions in a single result set. The 7 most recent rows come from Aurora, and the rest come directly from the Parquet file in S3. DuckDB handles the analytical scan of the Parquet data under the hood, while Aurora handles the operational data. That single query would have previously required a pipeline to move the historical data into the database first.&lt;/p&gt; 
&lt;p&gt;If a query pattern needs single-digit-millisecond latency, you can materialize data from the data lake into a native Aurora PostgreSQL table using familiar commands such as &lt;code&gt;CREATE TABLE AS SELECT&lt;/code&gt;, &lt;code&gt;INSERT INTO ... SELECT&lt;/code&gt;, or &lt;code&gt;MERGE INTO&lt;/code&gt;. The materialized table lives in Aurora and is queried like any other PostgreSQL table, giving you a low-latency path for hot data without operating a separate ingestion pipeline. The read queries can run on any Aurora PostgreSQL instance in your cluster, whether the writer or a read replica, so you can offload analytical scans from your operational workload. The materialization commands write data into Aurora, so they run on the writer instance.&lt;/p&gt; 
&lt;p id="get-started-today"&gt;&lt;span style="text-decoration: underline"&gt;&lt;strong&gt;Get started today&lt;/strong&gt;&lt;/span&gt;&lt;br&gt; Direct querying of Apache Iceberg and Parquet data from Amazon Aurora PostgreSQL is available today in all commercial AWS Regions and AWS GovCloud (US) Regions, at no additional charge. You pay only for the incremental Aurora compute the queries consume and &lt;a href="https://aws.amazon.com/s3/pricing/"&gt;Amazon S3 request costs&lt;/a&gt; for reading data lake files.&lt;/p&gt; 
&lt;p&gt;To learn more, visit the &lt;a href="https://aws.amazon.com/rds/aurora/features" target="_blank" rel="noopener noreferrer nofollow"&gt;Amazon Aurora features page&lt;/a&gt;, read the &lt;a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/" target="_blank" rel="noopener noreferrer nofollow"&gt;Aurora PostgreSQL documentation&lt;/a&gt;, or try it in the &lt;a href="https://console.aws.amazon.com/rds/" target="_blank" rel="noopener noreferrer nofollow"&gt;Amazon RDS console&lt;/a&gt;. We welcome your feedback through &lt;a href="https://repost.aws/" target="_blank" rel="noopener noreferrer nofollow"&gt;AWS re:Post&lt;/a&gt; or through your usual AWS Support contacts.&lt;/p&gt; 
&lt;a href="https://www.linkedin.com/in/esrakayabali/"&gt;— Esra&lt;/a&gt;</content:encoded>
					
					
			
		
		
			</item>
	</channel>
</rss>