# Amazon EC2

Amazon Elastic Compute Cloud is an AWS cloud computing service that provides resizable, secure compute capacity as virtual servers.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How Bee implemented Zero Operator Access for personal AI on AWS

DevFeed: [How Bee implemented Zero Operator Access for personal AI on AWS](<https://devfeed.tech/articles/how-bee-implemented-zero-operator-access-for-personal-ai-on-aws-146957.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-bee-implemented-zero-operator-access-for-personal-ai-on-aws/>)

Author: Gopinath Jagadesan

Published: 2026-11-20T18:49:05Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [Nitro System](<https://devfeed.tech/topics/nitro-system.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [sensitive data](<https://devfeed.tech/topics/sensitive-data.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bee](<https://devfeed.tech/tags/bee.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [nitro-system](<https://devfeed.tech/tags/nitro-system.md>), [personal-ai](<https://devfeed.tech/tags/personal-ai.md>)

### AI overview

Bee's Zero Operator Access design gates access to customer data on user-held keys and client verification of server software. At boot, EC2 instance attestation measures the operating system and, through PCR14, container images and model artifacts; expected measurements are independently published to Sigstore/Rekor. The Bee app verifies the attestation and transparency proof in the server's certificate before releasing a short-lived key. Data is encrypted within the attested instance before storage, keys remain in memory, and isolated subnets restrict network paths. Read-only images, disabled interactive access, and AWS organizational controls add safeguards, since attestation alone cannot measure network reach or permission changes. Bee says it plans to move inference to Amazon Bedrock Mantle while retaining user-held keys and attested application servers.

### Source excerpt

Bee, an Amazon company, built a personal AI wearable with no mechanism for operators (Bee engineers, other Amazon employees, or AWS infrastructure operators) to access customer data. Learn how Bee uses Amazon EC2 instance attestation and the AWS Nitro System to achieve Zero Operator Access (ZOA).

## Handling large volume of transactions with AWS Lambda Managed Instances

DevFeed: [Handling large volume of transactions with AWS Lambda Managed Instances](<https://devfeed.tech/articles/handling-large-volume-of-transactions-with-aws-lambda-managed-instances-144755.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/handling-large-volume-of-transactions-with-aws-lambda-managed-instances/>)

Author: Mythili Annamalai Sekar

Published: 2026-11-19T21:20:28Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [can](<https://devfeed.tech/tags/can.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [compute](<https://devfeed.tech/tags/compute.md>), [concert](<https://devfeed.tech/tags/concert.md>), [handling](<https://devfeed.tech/tags/handling.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [large](<https://devfeed.tech/tags/large.md>), [managed](<https://devfeed.tech/tags/managed.md>), [post](<https://devfeed.tech/tags/post.md>), [reference](<https://devfeed.tech/tags/reference.md>), [run](<https://devfeed.tech/tags/run.md>), [sample](<https://devfeed.tech/tags/sample.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [test](<https://devfeed.tech/tags/test.md>), [this](<https://devfeed.tech/tags/this.md>), [transactions](<https://devfeed.tech/tags/transactions.md>), [volume](<https://devfeed.tech/tags/volume.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

AWS Lambda Managed Instances runs Lambda functions on EC2 capacity in the customer's account, with AWS managing provisioning, scaling, patching, and routing. Its warm execution environments can be scaled ahead of scheduled bursts and back down afterward; the article's ticketing sample reports 40,000 requests per second for 120 seconds across tests from 5,000 to 40,000 requests per second, with p99 latency within a 3 ms band. The design uses a Valkey atomic queue counter, DynamoDB conditional seat holds with 180-second TTLs, and a transaction that confirms bookings and writes records atomically. Setup requires AWS CLI, SAM, Python 3.13+, a VPC, and network access to DynamoDB and CloudWatch; peak tests also need higher EC2 vCPU and API Gateway throttle quotas. Managed Instances uses EC2 pricing plus a 15% management fee; the article estimates about $37 per simulated burst.

### Source excerpt

AWS Lambda Managed Instances keeps compute capacity warm before a predictable traffic burst and scales it back down afterward. This post walks through a concert-ticketing reference implementation that sustains 40,000 transactions per second for 120 seconds, with a deployable sample you can run, test, and clean up.

## Introducing Amazon EMR Serverless Flex: Run non-urgent Spark jobs at a discount

DevFeed: [Introducing Amazon EMR Serverless Flex: Run non-urgent Spark jobs at a discount](<https://devfeed.tech/articles/introducing-amazon-emr-serverless-flex-run-non-urgent-spark-jobs-at-a-discount-144577.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/introducing-amazon-emr-serverless-flex-run-non-urgent-spark-jobs-at-a-discount/>)

Author: Neil Mukerje

Published: 2026-11-19T20:58:07Z

Content type: release

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [batch](<https://devfeed.tech/tags/batch.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [billing](<https://devfeed.tech/tags/billing.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [discount](<https://devfeed.tech/tags/discount.md>), [driver](<https://devfeed.tech/tags/driver.md>), [flex](<https://devfeed.tech/tags/flex.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [retries](<https://devfeed.tech/tags/retries.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [spark](<https://devfeed.tech/tags/spark.md>), [standard](<https://devfeed.tech/tags/standard.md>)

### AI overview

Amazon EMR Serverless Flex runs non-urgent Spark batch jobs on spare capacity at a fixed 60% discount on worker vCPU and memory charges compared with Standard. It automates Availability Zone and instance selection, protects the driver on a Standard worker, and retries tasks when Flex workers are reclaimed; optional Serverless Storage can reduce recomputation for shuffle-heavy jobs. Flex may start more slowly and run longer than Standard, and a job fails if no executor joins the driver within 20 minutes. In the described 103-query benchmark, all queries completed without resubmission; runtime was 7% longer at 1 TB and 30% longer at 3 TB, while estimated cost fell about 63% at both scales. Results vary with workload and spare capacity. Flex is enabled per job, so teams can compare it with Standard on flexible-deadline workloads.

### Source excerpt

Amazon EMR Serverless Flex is a new execution option that runs non-urgent Spark batch jobs on spare compute capacity at a fixed 60% discount compared to standard pricing. Flex handles Availability Zone selection, instance diversification, driver protection, and automatic retries, so jobs complete even when spare capacity is reclaimed.

## Amazon ElastiCache Serverless turns three

DevFeed: [Amazon ElastiCache Serverless turns three](<https://devfeed.tech/articles/amazon-elasticache-serverless-turns-three-144309.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/amazon-elasticache-serverless-turns-three/>)

Author: Karthik Konaparthi

Published: 2026-11-19T18:35:55Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-coding-assistant](<https://devfeed.tech/tags/ai-coding-assistant.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customers](<https://devfeed.tech/tags/customers.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [patch](<https://devfeed.tech/tags/patch.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Amazon ElastiCache Serverless removes cache capacity planning by scaling with demand; billing is based on stored data (GB-hours) and requests (ECPUs). The article highlights Valkey's faster scaling, lower storage minimum and pricing, plus a 30% Database Savings Plans discount with a one-year commitment. New Valkey 9.0 features include public endpoints (IAM authentication and TLS 1.3 required), online migration from cluster-mode Valkey or Redis OSS with traffic continuing, search, and write-through DynamoDB caching. AWS applies minor and patch updates automatically; major-version upgrades are customer scheduled, and recent patching improvements preserve more connections and in-flight requests. Serverless is presented as a fit for variable traffic and many separate caches; node-based deployments may suit steady workloads, especially with reserved nodes and capacity-tuning staff. The article recommends estimating costs from actual stored data and representative request volume, then checking CloudWatch metrics in a trial workload. Serverless clients must support cluster mode and TLS.

### Source excerpt

In this post, we look back at three years of Amazon ElastiCache Serverless, show how customers use it, cover what we launched this year and how we patch your cache with minimal disruption, show how to estimate what it costs, and help you decide whether it fits your workload.

## Monitor the efficiency and availability of accelerated computing instances with Amazon EC2 Detailed Monitoring and performance status checks

DevFeed: [Monitor the efficiency and availability of accelerated computing instances with Amazon EC2 Detailed Monitoring and performance status checks](<https://devfeed.tech/articles/monitor-the-efficiency-and-availability-of-accelerated-computing-instances-with-amazon-ec2-detailed-monitoring-and-performance-status-checks-144756.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/monitor-the-efficiency-and-availability-of-accelerated-computing-instances-with-amazon-ec2-detailed-monitoring-and-performance-status-checks/>)

Author: Caroline Frost

Published: 2026-11-19T18:34:57Z

Content type: article

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [gpu monitoring](<https://devfeed.tech/topics/gpu-monitoring.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [accelerated](<https://devfeed.tech/tags/accelerated.md>), [accelerated-computing](<https://devfeed.tech/tags/accelerated-computing.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [availability](<https://devfeed.tech/tags/availability.md>), [computing](<https://devfeed.tech/tags/computing.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [one](<https://devfeed.tech/tags/one.md>), [performance](<https://devfeed.tech/tags/performance.md>), [reports](<https://devfeed.tech/tags/reports.md>), [status](<https://devfeed.tech/tags/status.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Amazon EC2 Detailed Monitoring provides one-minute GPU metrics to CloudWatch without an in-guest agent or instance compute, while performance status checks flag recoverable hardware conditions that can impair GPU performance. Metrics include GPU and streaming multiprocessor utilization, memory use, temperature, and interconnect traffic, reported at instance and per-GPU levels; teams can use them to assess capacity and tune workloads. Performance checks appear in the console, `DescribeInstanceStatus`, and CloudWatch, with reboot recommended for a pending GPU memory row remap. Teams can alarm on `StatusCheckFailed_Performance`, then checkpoint work, drain and reboot an affected node, or reset the GPU after stopping its processes. Metrics are limited to supported NVIDIA GPU instance types, carry standard CloudWatch pricing, and complement in-guest tools that provide process, container, pod, and sub-minute detail.

### Source excerpt

Amazon EC2 now reports one-minute per-GPU metrics through Detailed Monitoring and surfaces recoverable hardware conditions with a new performance status check, giving infrastructure teams agentless visibility into accelerated computing efficiency and availability across their fleet.

## Amazon MSK Express brokers available on AWS Graviton4-based M8g instances

DevFeed: [Amazon MSK Express brokers available on AWS Graviton4-based M8g instances](<https://devfeed.tech/articles/amazon-msk-express-brokers-available-on-aws-graviton4-based-m8g-instances-140165.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/amazon-msk-express-brokers-available-on-aws-graviton4-based-m8g-instances/>)

Author: Charishma Makineni

Published: 2026-11-17T22:07:48Z

Content type: release

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-managed-streaming-for-apache-kafka-amazon-msk](<https://devfeed.tech/tags/amazon-managed-streaming-for-apache-kafka-amazon-msk.md>), [amazon-msk](<https://devfeed.tech/tags/amazon-msk.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [based](<https://devfeed.tech/tags/based.md>), [broker](<https://devfeed.tech/tags/broker.md>), [client](<https://devfeed.tech/tags/client.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [cross](<https://devfeed.tech/tags/cross.md>), [express](<https://devfeed.tech/tags/express.md>), [faster](<https://devfeed.tech/tags/faster.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [graviton](<https://devfeed.tech/tags/graviton.md>), [graviton4](<https://devfeed.tech/tags/graviton4.md>), [latency](<https://devfeed.tech/tags/latency.md>), [p99](<https://devfeed.tech/tags/p99.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [size](<https://devfeed.tech/tags/size.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Amazon MSK Express brokers on Graviton4-based M8g instances combine lower costs with better results than M7g in the described tests: broker-hour pricing is 15% lower, broker-side cross-AZ client traffic is uncharged (cutting total cross-AZ transfer cost by 50%), and P99 produce latency was 21-54% lower at the same tested load. Brokers used 9-11 percentage points less CPU, and consumers cleared up to three times more backlog in 30 minutes. Results depend on workload settings; the catch-up test used large brokers only. M8g adds a 24xlarge option, while shared sizes retain the same per-broker storage and network throughput. Teams can create an M8g cluster, update an M7g Express cluster in place one broker at a time, or migrate from Standard or self-managed Kafka using MSK Replicator. Rack-aware consumers can reduce cross-AZ charges further, though reading from follower replicas may add some end-to-end latency.

### Source excerpt

Amazon MSK Express brokers are now available on AWS Graviton4-based M8g instances. Compared with Express on M7g, M8g delivers 15% lower broker-hour pricing, lower P99 produce latency, faster consumer recovery, a new 24xlarge size, and no broker-side charge for cross-AZ client traffic.

## High-quality cost-effective AI image generation on Amazon ECS

DevFeed: [High-quality cost-effective AI image generation on Amazon ECS](<https://devfeed.tech/articles/high-quality-cost-effective-ai-image-generation-on-amazon-ecs-136885.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/high-quality-cost-effective-ai-image-generation-on-amazon-ecs/>)

Author: Nick Biso

Published: 2026-11-17T00:19:06Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [diffusion-transformers](<https://devfeed.tech/topics/diffusion-transformers.md>), [ai-image-generator](<https://devfeed.tech/topics/ai-image-generator.md>), [AWS Inferentia](<https://devfeed.tech/topics/aws-inferentia.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai-image-generation](<https://devfeed.tech/tags/ai-image-generation.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cost](<https://devfeed.tech/tags/cost.md>), [diffusion](<https://devfeed.tech/tags/diffusion.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The described Amazon ECS service runs Z-Image-Turbo on AWS Inferentia2, with one service per image resolution and one request at a time per instance because inference saturates the accelerator. Its key deployment mechanism is compiling model artifacts once in CI/CD, caching them on Amazon EFS, and loading them into containers at startup; the post reports this cuts startup to about two minutes from over 30 minutes and avoids recompilation when changes do not affect the model graph. The excerpt estimates $0.003 per 512px image and $0.011 per 1024px image at $1.97/hour for an inf2.8xlarge in us-east-1, while noting costs vary with utilization and other AWS resources still incur charges. It also describes resolution-based routing and streaming intermediate image frames over WebSockets. Deployment requires AWS quotas for Inf2 instances, CDK bootstrap, and listed local tools; first deployment takes about 45 minutes, including compilation.

### Source excerpt

Learn how to run Z-Image-Turbo, a 6-billion-parameter diffusion transformer, on AWS Inferentia2 and Amazon ECS to generate high-quality images at a fraction of a cent each, with auto-scaling, arbitrary resolution support, and a complete CI/CD pipeline.

## AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field

DevFeed: [AWS Nitro Sandboxes Put Each EKS Pod in Its Own MicroVM with One RuntimeClass Field](<https://devfeed.tech/articles/aws-nitro-sandboxes-put-each-eks-pod-in-its-own-microvm-with-one-runtimeclass-field-134862.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/aws-nitro-sandboxes-eks/>)

Author: Steef-Jan Wiggers

Published: 2026-11-16T09:07:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Nitro System](<https://devfeed.tech/topics/nitro-system.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-nitro-sandboxes-eks](<https://devfeed.tech/tags/aws-nitro-sandboxes-eks.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [containers](<https://devfeed.tech/tags/containers.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [eks](<https://devfeed.tech/tags/eks.md>), [field](<https://devfeed.tech/tags/field.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [half](<https://devfeed.tech/tags/half.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [key](<https://devfeed.tech/tags/key.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [news](<https://devfeed.tech/tags/news.md>), [nitro](<https://devfeed.tech/tags/nitro.md>), [one](<https://devfeed.tech/tags/one.md>), [passthrough](<https://devfeed.tech/tags/passthrough.md>), [pod](<https://devfeed.tech/tags/pod.md>), [release](<https://devfeed.tech/tags/release.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [security](<https://devfeed.tech/tags/security.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Nitro Sandboxes run opted-in EKS pods, ECS tasks, or EC2 workloads in separate Firecracker microVMs with their own guest kernels. On EKS, a RuntimeClass selects isolated or confidential mode; Auto Mode provisions capable nodes, while standard EKS requires a sandbox-enabled AMI. Isolated mode preserves tools such as exec and logs but trusts the parent instance. Confidential mode treats the parent as untrusted and can gate secret release on Nitro attestation measurements; those measurements must be checked by a KMS policy or external verifier for confidentiality guarantees to be complete. Network isolation removes the network device, including DNS, IMDS, and Pod Identity, and breaks HTTP/TCP probes. Constraints include no GPU passthrough, a limit of five sandboxes per node vCPU (halved on SMT instances), and no snapshot, restore, or live migration. The excerpt compares AWS's VM-based overhead, expressed through density and thread limits, with GKE's gVisor user-space kernel and its separate microVM option, which has stated per-pod resource costs and no GPU support.

### Source excerpt

AWS has launched Nitro Sandboxes, running each opted-in EKS pod, ECS task or EC2 workload in its own Firecracker microVM with a separate kernel, enabled by one runtimeClassName field at no extra charge. A confidential mode adds attestation-gated key release. The documentation lists the trade-offs: no GPU passthrough, at most five sandboxes per vCPU, and half the compute on SMT instances. By Steef-Jan Wiggers

## Your EC2 Bill is an Architecture Problem, Not an Accounting One

DevFeed: [Your EC2 Bill is an Architecture Problem, Not an Accounting One](<https://devfeed.tech/articles/your-ec2-bill-is-an-architecture-problem-not-an-accounting-one-134599.md>)

Original publisher: [Read original article](<https://hackernoon.com/your-ec2-bill-is-an-architecture-problem-not-an-accounting-one?source=rss>)

Author: Zayeem Zaki

Published: 2026-11-15T20:00:03Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [accelerated](<https://devfeed.tech/tags/accelerated.md>), [added](<https://devfeed.tech/tags/added.md>), [agent](<https://devfeed.tech/tags/agent.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-billing](<https://devfeed.tech/tags/aws-billing.md>), [aws-cdk](<https://devfeed.tech/tags/aws-cdk.md>), [aws-ec2](<https://devfeed.tech/tags/aws-ec2.md>), [bill](<https://devfeed.tech/tags/bill.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [c](<https://devfeed.tech/tags/c.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cassandra](<https://devfeed.tech/tags/cassandra.md>), [cdk](<https://devfeed.tech/tags/cdk.md>), [charges](<https://devfeed.tech/tags/charges.md>), [compute](<https://devfeed.tech/tags/compute.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>)

### AI overview

The article argues that EC2 cost and resilience are shaped by architecture choices made before billing review. It recommends profiling workloads to choose an instance family, considering Graviton when x86-only dependencies are absent, covering steady demand with a Compute Savings Plan, and using diversified Spot capacity for peaks with On-Demand fallback. For Spot interruptions, it describes capacity pools and allocation strategies, recommends priceCapacityOptimized, and explains that ECS draining and ALB deregistration must finish within the two-minute notice; it suggests a 60-90 second delay and stopTimeout. It advises keeping persistent data off instance disks, using EFS for shared cross-AZ files, and accounting for NAT and cross-AZ traffic costs. The included CDK example combines mixed Graviton instances, an On-Demand base and Spot-heavy capacity, rebalancing, draining, an ALB, and encrypted EFS.

### Source excerpt

Most EC2 bills are high because of early defaults nobody revisits.

## Fix Amazon Aurora MySQL error 63955: Virtual index ID overflow

DevFeed: [Fix Amazon Aurora MySQL error 63955: Virtual index ID overflow](<https://devfeed.tech/articles/fix-amazon-aurora-mysql-error-63955-virtual-index-id-overflow-133436.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/fix-amazon-aurora-mysql-error-63955-virtual-index-id-overflow/>)

Author: Kartik Saini

Published: 2026-11-13T21:10:28Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [TTL in DNS](<https://devfeed.tech/topics/ttl-in-dns.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [backups](<https://devfeed.tech/tags/backups.md>), [dump](<https://devfeed.tech/tags/dump.md>), [error](<https://devfeed.tech/tags/error.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [index](<https://devfeed.tech/tags/index.md>), [limit](<https://devfeed.tech/tags/limit.md>), [logical](<https://devfeed.tech/tags/logical.md>), [migration](<https://devfeed.tech/tags/migration.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [restore](<https://devfeed.tech/tags/restore.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [virtual](<https://devfeed.tech/tags/virtual.md>)

### AI overview

Aurora MySQL error 63955 means the cluster has exhausted virtual index IDs: indexes containing virtual columns--including functional and multi-valued indexes--fail, while existing data and ordinary indexes remain usable. Changing a generated column to STORED can unblock that particular index, but does not reset the IDs. The documented fix is a logical dump and restore; snapshots, clones, point-in-time recovery, and Blue/Green deployments copy physical structures and do not clear the condition. The described migration uses a clone, binary log replication, MyDumper/MyLoader, and a new Aurora MySQL 3.10.0-or-later cluster. It requires planning for a source reboot to enable binary logging, preserving the clone's source log position, migrating users and grants separately, validating the restore, and limiting rollback because schema changes can break reverse replication. On 3.10.0 or later, monitor the error log for VIRTUAL_INDEX_ID_OVERFLOW_WARNING; it is the only stated advance signal.

### Source excerpt

An Amazon Aurora MySQL cluster can exhaust its virtual index ID limit, after which any CREATE INDEX that includes a virtual column fails with error 63955 until you rebuild the databases. This post shows how to recognize the error, why backups cannot clear it, and how to run a logical dump-and-restore migration with monitoring to catch it next time.

## Cost-optimizing AssemblyAI speech-to-text inference on AWS with Amazon EC2 Spot

DevFeed: [Cost-optimizing AssemblyAI speech-to-text inference on AWS with Amazon EC2 Spot](<https://devfeed.tech/articles/cost-optimizing-assemblyai-speech-to-text-inference-on-aws-with-amazon-ec2-spot-132652.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/cost-optimizing-assemblyai-speech-to-text-inference-on-aws-with-amazon-ec2-spot/>)

Author: Belair Albahagwi

Published: 2026-11-13T19:35:35Z

Content type: news

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [asr](<https://devfeed.tech/topics/asr.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Speech Processing](<https://devfeed.tech/topics/speech-processing.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>)

Tags: [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [assemblyai](<https://devfeed.tech/tags/assemblyai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-savings](<https://devfeed.tech/tags/cost-savings.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [regions](<https://devfeed.tech/tags/regions.md>), [retry](<https://devfeed.tech/tags/retry.md>), [scale](<https://devfeed.tech/tags/scale.md>), [speech](<https://devfeed.tech/tags/speech.md>), [speech-to-text](<https://devfeed.tech/tags/speech-to-text.md>), [spot](<https://devfeed.tech/tags/spot.md>), [sqs](<https://devfeed.tech/tags/sqs.md>)

### AI overview

AssemblyAI reports 70% lower inference compute costs than On-Demand pricing using GPU Spot Instances, while maintaining SLA commitments. Its Amazon ECS clusters combine an always-on On-Demand baseline with diversified Spot capacity across g4dn, g5, and g6 GPU families and Availability Zones. Amazon SQS decouples job submission from execution: tasks finish work within Spot's two-minute interruption notice or return unfinished jobs to the queue for another worker to retry. Custom images with model artifacts and containers take about two minutes to create, reducing recovery time. Independent deployments in each AWS Region keep audio within required geographic boundaries. The article says compute demand grew nearly fourfold year over year; interruptions may add processing time, and exhausted retries can be routed to a dead-letter queue for investigation.

### Source excerpt

Learn how AssemblyAI runs cost-optimized speech-to-text inference at scale on AWS, using Amazon ECS, Amazon EC2 Spot GPU instances, and an Amazon SQS-based retry architecture to achieve 70% cost savings while maintaining SLA commitments across European Regions.

## Deploy Amazon S3 Files with Terraform

DevFeed: [Deploy Amazon S3 Files with Terraform](<https://devfeed.tech/articles/deploy-amazon-s3-files-with-terraform-133433.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/deploy-amazon-s3-files-with-terraform/>)

Author: Karthik Akula

Published: 2026-11-13T19:06:41Z

Content type: tutorial

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [mount](<https://devfeed.tech/topics/mount.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [compute](<https://devfeed.tech/tags/compute.md>), [compute-resources](<https://devfeed.tech/tags/compute-resources.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [files](<https://devfeed.tech/tags/files.md>), [groups](<https://devfeed.tech/tags/groups.md>), [iam](<https://devfeed.tech/tags/iam.md>), [module](<https://devfeed.tech/tags/module.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mount](<https://devfeed.tech/tags/mount.md>), [nfs](<https://devfeed.tech/tags/nfs.md>), [s3](<https://devfeed.tech/tags/s3.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The Terraform module deploys Amazon S3 Files as an NFS file system backed by an S3 bucket, with mount targets in private subnets across multiple Availability Zones. It restricts NFS traffic to TCP 2049 between designated security groups, applies resource and identity IAM policies, configures synchronization and optional customer managed KMS encryption, and creates CloudWatch alarms and a per-client dashboard. Examples cover EC2, ECS on Fargate, and Lambda; ECS and Lambda use access points, while EC2 needs ClientRootAccess to write at the file system root. Prerequisites include Terraform 1.5.0 or later, AWS provider 6.53.0 or later, a versioned and encrypted bucket, and a VPC with private subnets in at least two zones. The article notes that alarms have no data when no client is mounted, and the first Lambda invocation may time out shortly after deployment; retry after about a minute.

### Source excerpt

Amazon S3 Files makes Amazon S3 buckets accessible as NFS mounts from AWS compute resources. This post walks through a Terraform module that deploys S3 Files end-to-end: multi-AZ mount targets, security groups, IAM policies, encryption, and Amazon CloudWatch monitoring.

## Bring AWS Security Hub CSPM findings into your Amazon CloudWatch on-call workflow

DevFeed: [Bring AWS Security Hub CSPM findings into your Amazon CloudWatch on-call workflow](<https://devfeed.tech/articles/bring-aws-security-hub-cspm-findings-into-your-amazon-cloudwatch-on-call-workflow-133648.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/bring-aws-security-hub-cspm-findings-into-your-amazon-cloudwatch-on-call-workflow/>)

Author: Samir Behara

Published: 2026-11-13T16:18:57Z

Content type: tutorial

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [AWS Security Hub](<https://devfeed.tech/topics/aws-security-hub.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-guardduty](<https://devfeed.tech/tags/amazon-guardduty.md>), [amazon-inspector](<https://devfeed.tech/tags/amazon-inspector.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-sns](<https://devfeed.tech/tags/amazon-sns.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-cloudwatch](<https://devfeed.tech/tags/aws-cloudwatch.md>), [aws-ec2](<https://devfeed.tech/tags/aws-ec2.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-security-hub](<https://devfeed.tech/tags/aws-security-hub.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cspm](<https://devfeed.tech/tags/cspm.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [production](<https://devfeed.tech/tags/production.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

AWS Security Hub CSPM findings can be ingested into CloudWatch Logs through a telemetry enablement rule, letting operations teams review security signals beside application telemetry. Metric filters can count active, new CRITICAL and HIGH findings for a specific resource; a composite alarm then fires when that finding alarm and the same resource's performance alarm are both active. A 60-minute finding-alarm window helps correlate findings that precede performance symptoms. CloudWatch Logs supports analysis, dashboards, and alarms, while EventBridge remains the path for push-based remediation; the two are complementary. The article recommends starting with a Logs Insights link in alarm descriptions, then adding security checks to triage or correlated escalation. Constraints include Standard log class for metric filters, same account and Region for composite alarms and child alarms, and extra work to run the composite centrally because EC2 vended CPU metrics are not centralized. The opening incident is illustrative, and sample configurations require review before production use.

### Source excerpt

At 2:47 AM, an on-call engineer gets paged: CPU on a production Amazon EC2 instance has been above 95% for five minutes. They open Amazon CloudWatch and run the usual triage, checking recent deployments, traffic spikes, memory, and disk I/O. Nothing lines up. They scale the instance; utilization climbs back within minutes. Thirty-two minutes later, [...]

## 56 AWS API calls in 141 milliseconds: Inside an AI-run intrusion

DevFeed: [56 AWS API calls in 141 milliseconds: Inside an AI-run intrusion](<https://devfeed.tech/articles/56-aws-api-calls-in-141-milliseconds-inside-an-ai-run-intrusion-133228.md>)

Original publisher: [Read original article](<https://www.elastic.co/security-labs/threat-command/cyberstrikeai-aws-cloudtrail-intrusion>)

Author: Samir Bousseaden,Bryan Porras Blanch,Terrance DeJesus

Published: 2026-11-13T15:27:20Z

Content type: news

Language: en

Sources: [Elastic Security Labs](<https://devfeed.tech/sources/elastic-security-labs.md>)

Topics: [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [adversary](<https://devfeed.tech/tags/adversary.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-platform](<https://devfeed.tech/tags/agentic-platform.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-attacks](<https://devfeed.tech/tags/ai-assisted-attacks.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloudtrail](<https://devfeed.tech/tags/cloudtrail.md>), [cyberstrikeai](<https://devfeed.tech/tags/cyberstrikeai.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-engineering](<https://devfeed.tech/tags/detection-engineering.md>), [detection-rules](<https://devfeed.tech/tags/detection-rules.md>), [rules](<https://devfeed.tech/tags/rules.md>), [server](<https://devfeed.tech/tags/server.md>), [threat-intelligence](<https://devfeed.tech/tags/threat-intelligence.md>)

### AI overview

The article documents a 16-day intrusion in which one server attributed to CyberStrikeAI used eight AWS identities across four accounts. Activity included validating credentials, harvesting secrets, reading EC2 user data, decrypting an SSM parameter, and issuing an SSM command; the audit log does not reveal the command or whether it succeeded. The authors characterize the activity as AI-assisted based on attribution and machine-speed behavior, but cannot establish that an LLM agent made decisions or how credentials were obtained. Six Elastic rules produced 78 mostly medium- and low-severity alerts; shared source IP and a 14-day gap made correlation essential. The article proposes two high-severity detections for bulk user-data and account enumeration, behavioral CloudTrail hunts, and an Elastic Workflows proof of concept to deactivate keys and restrict IAM access. Its response steps include rotating credentials and sessions, reviewing SSM history, treating user-data secrets as exposed, and limiting access to userData. IPs are offered for retrospective hunting, while behavioral indicators are described as more durable.

### Source excerpt

A CyberStrikeAI server spent 16 days in four AWS accounts using eight identities, and the CloudTrail record shows why six detection rules each caught only part of it.

## Boosting Amazon RDS for PostgreSQL with AWS Graviton5: Benchmarks

DevFeed: [Boosting Amazon RDS for PostgreSQL with AWS Graviton5: Benchmarks](<https://devfeed.tech/articles/boosting-amazon-rds-for-postgresql-with-aws-graviton5-benchmarks-131172.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/boosting-amazon-rds-with-aws-graviton5-benchmarks/>)

Author: Angel Duenas

Published: 2026-11-12T23:59:59Z

Content type: comparison

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [graviton5](<https://devfeed.tech/tags/graviton5.md>), [m9g](<https://devfeed.tech/tags/m9g.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

In this Sysbench OLTP read/write benchmark, Graviton5-based M9g delivered the highest throughput among Amazon RDS for PostgreSQL instance generations M6g through M9g, with 55% lower p95 latency than M6g, 92% more queries per dollar than M6g, and 20% more than M8g. Tests used PostgreSQL 17.10, default RDS parameters apart from enforced TLS, io2 storage, a 100-thread workload, and five 30-minute runs per class; reported results are medians. The setup aimed to isolate CPU-generation effects, so gains may differ for workloads with another CPU, memory, and I/O balance. The article says Multi-AZ class changes use automatic failover with minimal downtime, while its tested Single-AZ setup needs a brief reboot, and recommends testing production workloads before upgrading.

### Source excerpt

AWS Graviton5 is now available on Amazon RDS through the new M9g instance family. In this post, we benchmark M9g against the M6g, M7g, and M8g generations for Amazon RDS for PostgreSQL, measuring throughput, latency, and price-performance so you can decide whether an upgrade is worth it.

## Scale distributed AI workloads with Ray and Anyscale on Amazon EC2

DevFeed: [Scale distributed AI workloads with Ray and Anyscale on Amazon EC2](<https://devfeed.tech/articles/scale-distributed-ai-workloads-with-ray-and-anyscale-on-amazon-ec2-132423.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/scale-distributed-ai-workloads-with-ray-and-anyscale-on-amazon-ec2/>)

Author: Sindhura Palakodety

Published: 2026-11-12T20:51:20Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [distributed-training](<https://devfeed.tech/topics/distributed-training.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [AWS Trainium](<https://devfeed.tech/topics/aws-trainium.md>), [AWS Inferentia](<https://devfeed.tech/topics/aws-inferentia.md>), [Amazon SageMaker HyperPod](<https://devfeed.tech/topics/amazon-sagemaker-hyperpod.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-chips](<https://devfeed.tech/tags/ai-chips.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [aws](<https://devfeed.tech/tags/aws.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [ml](<https://devfeed.tech/tags/ml.md>), [models](<https://devfeed.tech/tags/models.md>), [multimodal](<https://devfeed.tech/tags/multimodal.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [production](<https://devfeed.tech/tags/production.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [ray](<https://devfeed.tech/tags/ray.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>)

### AI overview

Ray and Anyscale provide a managed way to scale AI/ML pipelines on AWS while keeping Ray workload code consistent from a single instance to distributed clusters. Amazon EC2 offers the most flexibility, Amazon EKS fits organizations already operating Kubernetes but adds orchestration complexity and operator configuration, and SageMaker HyperPod targets resilience-critical large training runs with health monitoring, node replacement, and checkpoint recovery. Anyscale manages cluster lifecycle and autoscaling; compute and data remain in the customer's AWS account. The text describes matching CPU, GPU, Trainium, and Inferentia resources to pipeline stages, using Spot for fault-tolerant batch work, and combining Savings Plans, Capacity Blocks, reservations, and On-Demand capacity. Its suggested progression is to validate locally, scale data processing, expand training on a chosen deployment path, then deploy inference; it says this can be done without workload code changes.

### Source excerpt

Building multimodal AI/ML pipelines on Amazon EC2 means scaling distributed compute, controlling costs across stages, and keeping up with new models and hardware. This post shows how the Ray-powered Anyscale application on AWS helps you deploy Ray across three compute options and scale from prototype to production without code changes.

## Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group

DevFeed: [Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group](<https://devfeed.tech/articles/using-aws-backup-to-resynchronize-a-sql-server-alwayson-availability-group-131175.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/using-aws-backup-to-resynchronize-a-sql-server-alwayson-availability-group/>)

Author: Gabriel Pereira

Published: 2026-11-12T18:37:14Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [sql-server](<https://devfeed.tech/topics/sql-server.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [alwayson](<https://devfeed.tech/tags/alwayson.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-backup](<https://devfeed.tech/tags/aws-backup.md>), [backup](<https://devfeed.tech/tags/backup.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [replica](<https://devfeed.tech/tags/replica.md>), [restore](<https://devfeed.tech/tags/restore.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Backup can rebuild a failed SQL Server AlwaysOn secondary by restoring an application-consistent, VSS-enabled EC2 snapshot, then reconfiguring the node and rejoining it to the Availability Group. This EC2-level restore avoids streaming data from the primary as automatic seeding does and avoids the manual full backup, shipping, and restore cycle. The SQL Server VSS restore runbook cannot restore a secondary; it is limited to standalone databases or AG primaries. After restore, secondary IP addresses must be assigned manually. If VSS prerequisites are missing, resolve any cluster split-brain before rejoining. A broken LSN chain--such as when a primary log backup truncates records while the secondary is offline--requires per-database differential and log backups restored on the secondary with NORECOVERY before rejoining. The text reports about 10 minutes for one 100 GB lab restore and 6m13s to copy backup files in its broken-chain scenario; actual timing depends on volume size, file size, network throughput, and storage performance.

### Source excerpt

Learn how to use AWS Backup to rebuild a failed secondary replica in a SQL Server AlwaysOn Availability Group on Amazon EC2. We walk through capturing an application-consistent snapshot, restoring the EC2 instance, rejoining the Availability Group, and handling a broken LSN chain to reduce recovery time compared to a manual backup and restore.

## NC2 on AWS Adds 6 Intel Xeon 6 Instance Types for Hybrid Cloud

DevFeed: [NC2 on AWS Adds 6 Intel Xeon 6 Instance Types for Hybrid Cloud](<https://devfeed.tech/articles/nc2-on-aws-adds-6-intel-xeon-6-instance-types-for-hybrid-cloud-130123.md>)

Original publisher: [Read original article](<https://www.nutanix.com/blog/nc2-on-aws-intel-xeon-6-instances>)

Author: Dwayne Lessner; Allison Grant

Published: 2026-11-12T01:36:36Z

Content type: release

Language: en

Sources: [Nutanix](<https://devfeed.tech/sources/nutanix.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [intel](<https://devfeed.tech/topics/intel.md>), [nutanix](<https://devfeed.tech/topics/nutanix.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [blog-category](<https://devfeed.tech/tags/blog-category.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [intel](<https://devfeed.tech/tags/intel.md>), [intel-xeon](<https://devfeed.tech/tags/intel-xeon.md>), [intel-xeon-6](<https://devfeed.tech/tags/intel-xeon-6.md>), [nutanix-cloud-clusters-nc2](<https://devfeed.tech/tags/nutanix-cloud-clusters-nc2.md>), [nutanix-cloud-infrastructure-nci](<https://devfeed.tech/tags/nutanix-cloud-infrastructure-nci.md>), [tof-awareness](<https://devfeed.tech/tags/tof-awareness.md>), [vmware-alternative-broadcom-compete](<https://devfeed.tech/tags/vmware-alternative-broadcom-compete.md>)

### AI overview

NC2 on AWS adds six Intel Xeon 6 bare metal options: compute optimized c8id, general purpose m8id, and memory optimized r8id, each in 48xl and 96xl sizes. They run the same AOS and AHV stack as on premises and require AOS 7.5.1.x or later with AHV 11.0.1. These instances use local NVMe for cluster data; capacity grows by adding nodes, and Cloud-SSD EBS capacity is unavailable for them. Clusters may mix Xeon 6 types within the same size group, but cannot mix 48xl and 96xl nodes. Regional availability varies. AHV's default CPU baseline uses the highest generation common to all nodes; Advanced Processor Compatibility lets administrators pin VMs to a supported generation, trading broader live-migration reach on older generations for newer CPU features. That feature requires AOS 6.8+, AHV 20230302.100173+, and Prism Central 2024.1+. The article frames added instance choice as support for workload fit and phased migration while retaining a common operating model.

### Source excerpt

Nutanix Cloud Clusters (NC2) on AWS now supports 6 additional Amazon EC2 bare metal instance types built on Intel Xeon 6 processors.

## Migrate from Amazon EC2 to Amazon ElastiCache Serverless with zero downtime

DevFeed: [Migrate from Amazon EC2 to Amazon ElastiCache Serverless with zero downtime](<https://devfeed.tech/articles/migrate-from-amazon-ec2-to-amazon-elasticache-serverless-with-zero-downtime-129586.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/migrate-from-amazon-ec2-to-amazon-elasticache-serverless-with-zero-downtime/>)

Author: Rong Zhang

Published: 2026-11-11T18:12:18Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [downtime](<https://devfeed.tech/topics/downtime.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>)

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-command-line-interface-aws-cli](<https://devfeed.tech/tags/aws-command-line-interface-aws-cli.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [console](<https://devfeed.tech/tags/console.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [managed](<https://devfeed.tech/tags/managed.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [migration](<https://devfeed.tech/tags/migration.md>), [online](<https://devfeed.tech/tags/online.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache's online migration lets workloads on self-managed Valkey or Redis OSS on EC2 move to ElastiCache Serverless for Valkey while clients keep using one endpoint. ElastiCache validates the source, provisions migration infrastructure, performs a full data sync followed by replication of writes, then routes the endpoint to the serverless cache at a fully synced window. Cutover can be manual, allowing validation first, or automatic; all shards switch together, and traffic continues through the same endpoint. At launch, serverless migrations require cluster-mode sources running Valkey 7.2-8.1 or Redis OSS 4.0-7.2, and target Valkey 7.2, 8.1, or 9.0 at least as new as the source. Prerequisites include an empty reachable target, TLS-capable clients, and source credentials and CA certificates where applicable. The migration is free for 180 days from the account's first preparation; afterward migration nodes are billed per node-hour, while the serverless cache is charged separately. The source should retain headroom and stable network, credentials, certificates, and shard layout until migration completes.

### Source excerpt

On October 20, 2026, Amazon ElastiCache introduced online migration to ElastiCache Serverless for Valkey from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. This post shows what's supported at launch, how online migration works, and how to run a migration in the ElastiCache console.

## Automating Oracle Data Guard switchover and failover on Amazon EC2

DevFeed: [Automating Oracle Data Guard switchover and failover on Amazon EC2](<https://devfeed.tech/articles/automating-oracle-data-guard-switchover-and-failover-on-amazon-ec2-129580.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/automating-oracle-data-guard-switchover-and-failover-on-amazon-ec2/>)

Author: Sai Krishna Namburu

Published: 2026-11-11T17:50:50Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-sns](<https://devfeed.tech/tags/amazon-sns.md>), [automate](<https://devfeed.tech/tags/automate.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [database](<https://devfeed.tech/tags/database.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [failover](<https://devfeed.tech/tags/failover.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [rto](<https://devfeed.tech/tags/rto.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The solution automates Oracle Data Guard role transitions on Amazon EC2 with AWS Step Functions coordinating AWS Lambda tasks. It uses Systems Manager Run Command for database operations, Secrets Manager for SYS credentials, SNS for stage notifications, CloudWatch for execution logs, and DynamoDB for event records. Planned switchovers run 13 pre-checks and eight post-checks; blocking failures halt execution, and the primary workload should be quiesced so redo lag reaches zero. Emergency failovers run 10 standby-focused checks, confirm the primary is unreachable, and capture SCN, timestamps, and log gaps to report potential RPO impact; the former primary may need reinstatement. Prerequisites include configured Data Guard Broker, Flashback, connectivity, SYSDBA access, static listener entries, SSM agents and permissions, a stored SYS password, and an SNS subscription. The described implementation supports one database within the same account and Region, was tested with Oracle Database 19c, and requires Python 3.9+ for Lambda.

### Source excerpt

Oracle Data Guard keeps a standby database in sync for high availability and disaster recovery, but running switchover and failover by hand on Amazon EC2 is slow and error-prone. This post shows how to automate both with AWS Step Functions and AWS Lambda, running validated pre-checks, the role transition, post-checks, and RTO/RPO tracking end to end.

## Building a GPU workstation for visual effects with Amazon EC2: Part 5 - Security

DevFeed: [Building a GPU workstation for visual effects with Amazon EC2: Part 5 - Security](<https://devfeed.tech/articles/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-5-security-129754.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-5-security/>)

Author: Andy Hayes

Published: 2026-11-11T15:27:23Z

Content type: article

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-dcv](<https://devfeed.tech/tags/amazon-dcv.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-guardduty](<https://devfeed.tech/tags/amazon-guardduty.md>), [amazon-inspector](<https://devfeed.tech/tags/amazon-inspector.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [iam](<https://devfeed.tech/tags/iam.md>), [images](<https://devfeed.tech/tags/images.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [patch-management](<https://devfeed.tech/tags/patch-management.md>), [production](<https://devfeed.tech/tags/production.md>), [security](<https://devfeed.tech/tags/security.md>), [storage](<https://devfeed.tech/tags/storage.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [visual-effects](<https://devfeed.tech/tags/visual-effects.md>), [workstation](<https://devfeed.tech/tags/workstation.md>), [workstations](<https://devfeed.tech/tags/workstations.md>)

### AI overview

For production VFX workstations on EC2, security spans desktop access, identity, data protection, and ongoing operations; AWS secures the underlying cloud infrastructure, while customers secure the guest OS and applications. Restrict Amazon DCV access with security groups, subnet ACLs, firewalls, and DCV origin/host filtering; its default self-signed certificate encrypts traffic but triggers browser trust warnings, which a trusted CA certificate can resolve. A DCV Connection Gateway can provide a single entry point and token-based session routing. The post also recommends least-privilege IAM roles instead of static keys, scoped S3 permissions, prompt password changes and SSH key rotation, encrypted EBS volumes and TLS 1.2 or later, and monitoring with CloudTrail, CloudWatch, Access Analyzer, VPC Flow Logs, Inspector, and GuardDuty. Automate image hardening and fleet patching with EC2 Image Builder and Systems Manager Patch Manager. Encrypted EBS snapshots support point-in-time recovery, but recovery procedures should be tested. VPN, Direct Connect, and private-subnet connectivity offer additional network protections according to deployment needs.

### Source excerpt

The final post in our GPU workstation series covers security for visual effects workstations on Amazon EC2: controlling who can reach the desktop, protecting the Amazon DCV session in transit, and safeguarding credentials, images, and storage, plus IAM, encryption, monitoring, and patch management best practices for production VFX environments.

## Building a GPU workstation for visual effects with Amazon EC2: Part 4 - Optimizations

DevFeed: [Building a GPU workstation for visual effects with Amazon EC2: Part 4 - Optimizations](<https://devfeed.tech/articles/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations-129753.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-4-optimizations/>)

Author: Andy Hayes

Published: 2026-11-11T15:27:19Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-dcv](<https://devfeed.tech/tags/amazon-dcv.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [ami](<https://devfeed.tech/tags/ami.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [custom](<https://devfeed.tech/tags/custom.md>), [ecc](<https://devfeed.tech/tags/ecc.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [images](<https://devfeed.tech/tags/images.md>), [launch](<https://devfeed.tech/tags/launch.md>), [optimizations](<https://devfeed.tech/tags/optimizations.md>), [performance](<https://devfeed.tech/tags/performance.md>), [security](<https://devfeed.tech/tags/security.md>), [series](<https://devfeed.tech/tags/series.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [templates](<https://devfeed.tech/tags/templates.md>), [visual-effects](<https://devfeed.tech/tags/visual-effects.md>), [workstation](<https://devfeed.tech/tags/workstation.md>)

### AI overview

Custom AMIs and versioned EC2 launch templates let studios preserve a configured VFX workstation and deploy standardized instances at scale. The article outlines preparing Linux or Windows systems, creating an AMI with appropriately sized storage, and setting launch options such as instance type, security group, key pair, and IAM profile. For Windows, EC2Launch settings control boot behavior; Sysprep removes machine-specific information, while shutting down without it can retain embedded local users. For GPU performance, AWS documents Linux driver initialization and disabling GPU autoboost, which the article says should be evaluated per application. It also suggests disabling NVIDIA ECC to reduce memory-checking overhead for VFX workloads; ECC is enabled again at each fresh start, requires a reboot to disable, and can be automated with startup or user data scripts. User data should not contain hardcoded secrets. The article recommends restricting AMI sharing to named AWS accounts and checking images for embedded credentials. Stopping preserves EBS data but loses RAM and instance-store data; terminating does not retain local information and cannot be reversed by restarting.

### Source excerpt

Part 4 of our series on building GPU workstations for visual effects on Amazon EC2. This post covers standardizing VFX workstation configurations with custom AMIs and launch templates, GPU performance optimizations such as disabling ECC, and security considerations when sharing machine images.

## Building a GPU workstation for visual effects with Amazon EC2: Part 3 - Windows

DevFeed: [Building a GPU workstation for visual effects with Amazon EC2: Part 3 - Windows](<https://devfeed.tech/articles/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows-129752.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-with-amazon-ec2-part-3-windows/>)

Author: Andy Hayes

Published: 2026-11-11T15:27:16Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [3D](<https://devfeed.tech/topics/3d.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aes](<https://devfeed.tech/tags/aes.md>), [amazon-dcv](<https://devfeed.tech/tags/amazon-dcv.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [dcv](<https://devfeed.tech/tags/dcv.md>), [display](<https://devfeed.tech/tags/display.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [has](<https://devfeed.tech/tags/has.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [performance](<https://devfeed.tech/tags/performance.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [remote](<https://devfeed.tech/tags/remote.md>), [series](<https://devfeed.tech/tags/series.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [visual-effects](<https://devfeed.tech/tags/visual-effects.md>), [wacom](<https://devfeed.tech/tags/wacom.md>), [windows](<https://devfeed.tech/tags/windows.md>), [workstation](<https://devfeed.tech/tags/workstation.md>)

### AI overview

The guide walks through setting up a Windows Server 2025 VFX workstation on Amazon EC2, using a g6.4xlarge instance, AWS-approved NVIDIA drivers, Amazon DCV, and Wacom drivers. It requires an AWS account with GPU quota, a key pair, a security group allowing specified ports only from the user's IP, and an IAM profile with S3 read access. The setup expands and encrypts the root volume, connects initially through RDP, then uses DCV for the remote desktop; Windows provides Wacom brush sensitivity without extra configuration. Multi-GPU instance types require all intended GPUs to be present when installing the driver. The document recommends WorkSpaces Applications multi-session fleets for lighter users, not artists doing intensive viewport work. It also covers temporary instance-store setup and advises stopping or terminating instances when idle to reduce costs.

### Source excerpt

The third post in a five-part series on building GPU-backed VFX workstations on Amazon EC2. This post walks through deploying a Windows Server 2025 workstation with NVIDIA GPU drivers, Amazon DCV as the remote display protocol, and Wacom stylus support for a high-performance remote creative environment.

## Building a GPU workstation for visual effects on Amazon EC2: Part 2 - Linux

DevFeed: [Building a GPU workstation for visual effects on Amazon EC2: Part 2 - Linux](<https://devfeed.tech/articles/building-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-2-linux-129751.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/building-a-gpu-workstation-for-visual-effects-on-amazon-ec2-part-2-linux/>)

Author: Andy Hayes

Published: 2026-11-11T15:27:12Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [GPU rendering](<https://devfeed.tech/topics/gpu-rendering.md>), [3D](<https://devfeed.tech/topics/3d.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-dcv](<https://devfeed.tech/tags/amazon-dcv.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [linux](<https://devfeed.tech/tags/linux.md>), [rocky-linux](<https://devfeed.tech/tags/rocky-linux.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [visual-effects](<https://devfeed.tech/tags/visual-effects.md>), [workstation](<https://devfeed.tech/tags/workstation.md>)

### AI overview

The post walks through deploying a Rocky Linux 9.5 VFX workstation on Amazon EC2 and connecting to its desktop with Amazon DCV. It assumes an AWS account with GPU quota, an EC2 key pair, a security group allowing TCP/UDP ports 22, 443, 8443, and 3389 only from the user's IP, and an IAM profile with S3 read access. The launch instructions use the Rocky Linux 9 Marketplace AMI, a g6.4xlarge instance, a 50 GiB gp3 root volume with EBS encryption, and a public IP. After launch, the workflow covers SSH access as rocky, system and NVIDIA GPU setup, DCV server configuration, Wacom drivers, local NVMe mounting, and application libraries. Users install the matching DCV client, connect by public IP, accept the default self-signed certificate for initial setup, and log in with the rocky credentials. The post advises terminating the instance when unused to reduce running costs.

### Source excerpt

The second post in a five-part series on building GPU-backed visual effects (VFX) workstations on Amazon EC2. You deploy and configure a Rocky Linux 9.5 workstation with NVIDIA GPU drivers, Wacom drivers, and Amazon DCV as a high-performance desktop display protocol.

[Next page](<https://devfeed.tech/topics/amazon-ec2.md?cursor=WyIyMDI2LTExLTExVDE1OjI3OjEyKzAwOjAwIiwgIjE5ZTAxZGU3LWMxZjMtNDkzMS04MTEyLTEyOGI5Yzk2OTRkZSJd>)