# AWS Step Functions

AWS Step Functions is a serverless workflow orchestration service for building and coordinating distributed applications through visual workflows, service integration, error handling, and state management.

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

## AWS Weekly Roundup: AWS Nitro Sandboxes, AWS Emulator, and more (November 16, 2026)

DevFeed: [AWS Weekly Roundup: AWS Nitro Sandboxes, AWS Emulator, and more (November 16, 2026)](<https://devfeed.tech/articles/aws-weekly-roundup-aws-nitro-sandboxes-aws-emulator-and-more-november-16-2026-136092.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-weekly-roundup-aws-nitro-sandboxes-aws-emulator-and-more-november-16-2026/>)

Author: Daniel Abib

Published: 2026-11-16T17:55:46Z

Content type: news

Language: en

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

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Nitro System](<https://devfeed.tech/topics/nitro-system.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon OpenSearch Service](<https://devfeed.tech/topics/amazon-opensearch-service.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-opensearch-service](<https://devfeed.tech/tags/amazon-opensearch-service.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [application](<https://devfeed.tech/tags/application.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-emulator](<https://devfeed.tech/tags/aws-emulator.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [demo](<https://devfeed.tech/tags/demo.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [developers](<https://devfeed.tech/tags/developers.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [events](<https://devfeed.tech/tags/events.md>), [news](<https://devfeed.tech/tags/news.md>), [nitro](<https://devfeed.tech/tags/nitro.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [tools](<https://devfeed.tech/tags/tools.md>), [week-in-review](<https://devfeed.tech/tags/week-in-review.md>), [weekly](<https://devfeed.tech/tags/weekly.md>), [weekly-roundup](<https://devfeed.tech/tags/weekly-roundup.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

AWS Emulator lets developers and coding agents test AWS API interactions locally through the AWS CLI or SDKs, without an AWS account or per-attempt cloud provisioning. Its coverage varies: unsupported calls return HTTP 501, and it does not emulate IAM or resource-policy enforcement or cross-account and cross-Region behavior, so production testing on AWS remains necessary. Other launches include Nitro Sandboxes, which isolate pods, tasks, or VMs on shared EC2 instances, with confidential mode adding protection from node operators and attestation; Cognito token exchange for narrower downstream tokens; and Valkey 9 search and aggregations in ElastiCache Serverless. OpenSearch Service cross-Region recovery pairs version 3.7+ domains in one account, with stated recovery objectives under one minute for data loss and under 20 minutes for recovery time, though unplanned failover can lose unreplicated data. The roundup also covers CloudWatch Logs retention policies and the next-generation AgentCore runtime.

### Source excerpt

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 [...]

## How Thermo Fisher Scientific built AI-powered patient matching on AWS

DevFeed: [How Thermo Fisher Scientific built AI-powered patient matching on AWS](<https://devfeed.tech/articles/how-thermo-fisher-scientific-built-ai-powered-patient-matching-on-aws-133534.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-thermo-fisher-scientific-built-ai-powered-patient-matching-on-aws/>)

Author: Kaushal Patel

Published: 2026-11-13T20:26:58Z

Content type: article

Language: en

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

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Entity resolution](<https://devfeed.tech/topics/entity-resolution.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-documentdb](<https://devfeed.tech/tags/amazon-documentdb.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data](<https://devfeed.tech/tags/data.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [launch](<https://devfeed.tech/tags/launch.md>), [matching](<https://devfeed.tech/tags/matching.md>), [modernizing](<https://devfeed.tech/tags/modernizing.md>), [platform](<https://devfeed.tech/tags/platform.md>), [premium](<https://devfeed.tech/tags/premium.md>), [production](<https://devfeed.tech/tags/production.md>), [recruitment](<https://devfeed.tech/tags/recruitment.md>), [risk](<https://devfeed.tech/tags/risk.md>)

### AI overview

Thermo Fisher Scientific built Patient Match AI on a curated AWS patient recruitment data foundation that consolidates more than 20 million profiles (about 1.6 TB) from patient, survey, recruitment, marketing, and consent sources. Users can search in natural language and refine cohorts through a COUNT -> REFINE -> TARGETED LIST -> EXPORT workflow; shared test queries ran in under six seconds, and many common feasibility workflows took minutes rather than days. Aggregate views support exploration, while identity access remains subject to privacy, governance, consent, contactability, and PII controls. Central Insights Hub provides separate dashboards for recruitment progress, site and geographic performance, and other operational measures. AWS services include S3, Glue, Step Functions, Athena, Iceberg, DocumentDB, ECS, and Lambda. AWS Countdown Premium provided architecture and readiness reviews, launch support, and post-launch stabilization; its engineering guidance helped cut estimated processing time by more than threefold. The article reports a Q2 FY26 production launch.

### Source excerpt

Learn how Thermo Fisher Scientific built an AI-powered patient-matching platform on AWS, modernizing its clinical trial recruitment data foundation and using AWS Countdown Premium to de-risk the production launch.

## Modular regression testing framework built on AWS for large-scale systems

DevFeed: [Modular regression testing framework built on AWS for large-scale systems](<https://devfeed.tech/articles/modular-regression-testing-framework-built-on-aws-for-large-scale-systems-132422.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/modular-regression-testing-framework-built-on-aws-for-large-scale-systems/>)

Author: Hannah Zhang

Published: 2026-11-12T21:51:43Z

Content type: tutorial

Language: en

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

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [cases](<https://devfeed.tech/tags/cases.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [framework](<https://devfeed.tech/tags/framework.md>), [large](<https://devfeed.tech/tags/large.md>), [modular](<https://devfeed.tech/tags/modular.md>), [production](<https://devfeed.tech/tags/production.md>), [real-world](<https://devfeed.tech/tags/real-world.md>), [regression](<https://devfeed.tech/tags/regression.md>), [regression-testing](<https://devfeed.tech/tags/regression-testing.md>), [results](<https://devfeed.tech/tags/results.md>), [sample](<https://devfeed.tech/tags/sample.md>), [scale](<https://devfeed.tech/tags/scale.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [systems](<https://devfeed.tech/tags/systems.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

The framework replays sampled production requests against pre-production code and uses a match-fraction CloudWatch alarm as an automated deployment gate. An SNS/SQS event starts a Step Functions workflow; Lambda replays captured traffic, compares normalized business-logic outputs, and logs per-request results. The design can capture at API, service, database, or queue boundaries and is simplest for stateless, deterministic systems. Stateful services need replay IDs and safeguards such as skipping side effects; randomized behavior can use the ID as a seed. Accurate results depend on capturing all relevant request context and choosing domain-specific fields to compare. The framework targets regression detection, not validation of new business logic. The authors report five customer-impacting regressions caught over more than six months, with no false-positive deployment blocks. Replay volume and throttling need controls, and the main cost is processing replayed requests in the tested system.

### Source excerpt

Regression testing must catch behavior changes before they reach production, yet synthetic tests miss real-world edge cases. This post walks through a modular framework, built on AWS, that replays a sample of production traffic against new code and automatically gates deployments on the fraction of results that match production.

## How Hathr.AI delivers multi-tenant agentic RAG for regulated US government workloads with Amazon S3 Vectors

DevFeed: [How Hathr.AI delivers multi-tenant agentic RAG for regulated US government workloads with Amazon S3 Vectors](<https://devfeed.tech/articles/how-hathr-ai-delivers-multi-tenant-agentic-rag-for-regulated-us-government-workloads-with-amazon-s3-vectors-130617.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/how-hathr-ai-delivers-multi-tenant-agentic-rag-for-regulated-us-government-workloads-with-amazon-s3-vectors/>)

Author: Sam Hart

Published: 2026-11-12T15:36:34Z

Content type: article

Language: en

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

Topics: [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [vector embeddings in AI](<https://devfeed.tech/topics/vector-embeddings-in-ai.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-rag](<https://devfeed.tech/tags/agentic-rag.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-documentdb](<https://devfeed.tech/tags/amazon-documentdb.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>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [government](<https://devfeed.tech/tags/government.md>), [hipaa](<https://devfeed.tech/tags/hipaa.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [rag](<https://devfeed.tech/tags/rag.md>), [step-functions](<https://devfeed.tech/tags/step-functions.md>), [strands-agents](<https://devfeed.tech/tags/strands-agents.md>), [tool](<https://devfeed.tech/tags/tool.md>), [us-government](<https://devfeed.tech/tags/us-government.md>), [vector](<https://devfeed.tech/tags/vector.md>), [vector-search](<https://devfeed.tech/tags/vector-search.md>), [vectors](<https://devfeed.tech/tags/vectors.md>)

### AI overview

Hathr.AI moved high-churn vector search from Amazon DocumentDB to Amazon S3 Vectors, using a separate index and ARN for each customer in AWS GovCloud (US). Step Functions and Lambda parse, chunk, and embed uploads; Amazon DocumentDB retains text and metadata, while S3 Vectors stores embeddings. Deletion removes vectors immediately in batches before deleting chunks. IAM scopes ingestion and agent access to customer indexes, and authenticated session context selects the index. Strands Agents on ECS Fargate can search, inspect results, and retry with revised queries; Hathr.AI caps searches per turn. The move addressed shared-cluster resource contention and reduced the DocumentDB cluster to one quarter of peak size. Hathr.AI reports zero failed vector requests, sub-100 ms average query latency, and upload-to-search readiness P99 below one-tenth of its prior time. S3 Vectors has per-index write limits, and index settings such as dimensions, distance metric, and encryption cannot be changed after creation. GovCloud deployments also need partition-specific ARNs and endpoint checks, model availability confirmation, and appropriate data-event logging where audit records are needed.

### Source excerpt

Hathr.AI runs a HIPAA-aligned, multi-tenant agentic RAG tool for regulated industries in AWS GovCloud (US). This post covers its architecture (a Step Functions ingestion pipeline, per-customer Amazon S3 Vectors indexes, and Strands Agents on ECS Fargate) and the results after moving vector search from Amazon DocumentDB to Amazon S3 Vectors.

## How Zillow runs 100 million daily notifications on AWS Step Functions

DevFeed: [How Zillow runs 100 million daily notifications on AWS Step Functions](<https://devfeed.tech/articles/how-zillow-runs-100-million-daily-notifications-on-aws-step-functions-129629.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-zillow-runs-100-million-daily-notifications-on-aws-step-functions/>)

Author: Nishita Kheur

Published: 2026-11-11T23:25:00Z

Content type: article

Language: en

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

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [notifications](<https://devfeed.tech/topics/notifications.md>), [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [a-b-testing](<https://devfeed.tech/tags/a-b-testing.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [batching](<https://devfeed.tech/tags/batching.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [content](<https://devfeed.tech/tags/content.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [express](<https://devfeed.tech/tags/express.md>), [modules](<https://devfeed.tech/tags/modules.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [platform](<https://devfeed.tech/tags/platform.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Zillow replaced more than 10 campaign-specific generators with a configuration-driven Campaign Orchestrator, where each notification runs as a short-lived AWS Step Functions Express workflow and calls reusable, schema-driven Universal Content Generator modules. An in-house router handles queueing, batching, idempotency, replay, pacing, and campaign controls; separate queues and state machines isolate campaign failures. Zillow chose Express for high-volume, seconds-long, idempotent workflows, after evaluating other engines, and reports internal estimates of 9 development weeks versus 32 for a comparable in-house engine, with maintenance falling from about 8 hours weekly to 2. Batching reduces executions and module requests, but requires every step to support bulk inputs and outputs; tracking IDs preserve per-message delivery, retry, or drop decisions. The team also planned quota increases, validated JSONata through Step Functions TestState in CI, and uses schema checks for human and AI-drafted configurations.

### Source excerpt

Zillow sends more than 100 million personalized notifications a day, each as a short-lived AWS Step Functions Express workflow. See how the Comms Experience team replaced more than 10 campaign generators with one configuration-driven orchestration platform and a library of reusable content modules.

## 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.

## Serverless ICYMI Q3 2026

DevFeed: [Serverless ICYMI Q3 2026](<https://devfeed.tech/articles/serverless-icymi-q3-2026-119355.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/serverless-icymi-q3-2026/>)

Author: Julian Wood

Published: 2026-11-05T13:50:18Z

Content type: news

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [icymi](<https://devfeed.tech/tags/icymi.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [q3](<https://devfeed.tech/tags/q3.md>), [recap](<https://devfeed.tech/tags/recap.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The excerpt reports Q3 2026 AWS serverless updates spanning event routing, compute, workflows, storage and AI tooling. EventBridge's relaunched custom bus supports cross-account subscribers, configurable retention, keyed ordering and Avro, Protocol Buffers or JSON; it runs alongside the classic bus. Lambda changes include scalable network bandwidth for larger functions, container-image SnapStart, SQS polling capacity up to 10,000 event pollers, and loading code from customers' S3 buckets. Lambda Managed Instances allow 90-minute invocations and support newer Graviton instances; durable functions add .NET support, bring-your-own SDKs and customer-managed KMS encryption. Lambda MicroVMs provide Firecracker-isolated environments lasting up to eight hours and are available in 10 Regions with PrivateLink. Other reported changes include Step Functions integrations, SNS messages up to 1 MiB, API Gateway backend mTLS, and S3 updates. AI additions include serverless agent-inspection tools, AgentCore features, and Strands harness and evaluation tools. The source is a quarterly recap excerpt with launch claims and links to related resources, not a detailed evaluation of each feature.

### Source excerpt

In this 34th quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q3 2026 that you might have missed.

## Migrate Google BigQuery to an open lakehouse on AWS with Apache Iceberg

DevFeed: [Migrate Google BigQuery to an open lakehouse on AWS with Apache Iceberg](<https://devfeed.tech/articles/migrate-google-bigquery-to-an-open-lakehouse-on-aws-with-apache-iceberg-114202.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/migrate-google-bigquery-to-an-open-lakehouse-on-aws-with-apache-iceberg/>)

Author: Saman Irfan

Published: 2026-11-02T17:21:17Z

Content type: article

Language: en

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

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [BigQuery](<https://devfeed.tech/topics/bigquery.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon S3 Tables](<https://devfeed.tech/topics/amazon-s3-tables.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [AWS Lake Formation](<https://devfeed.tech/topics/aws-lake-formation.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bigquery](<https://devfeed.tech/tags/bigquery.md>), [data](<https://devfeed.tech/tags/data.md>), [design](<https://devfeed.tech/tags/design.md>), [future](<https://devfeed.tech/tags/future.md>), [google](<https://devfeed.tech/tags/google.md>), [google-bigquery](<https://devfeed.tech/tags/google-bigquery.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [migration](<https://devfeed.tech/tags/migration.md>), [open](<https://devfeed.tech/tags/open.md>), [optimize](<https://devfeed.tech/tags/optimize.md>), [over](<https://devfeed.tech/tags/over.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article presents a phased path from BigQuery to an AWS lakehouse using Apache Iceberg tables on Amazon S3, with governance through AWS Glue Data Catalog and Lake Formation and engines selected by workload. It recommends assessing tables, query complexity, consumers, volumes, and access controls; designing storage, partitioning, ingestion, and governance; then converting a representative slice and validating results, performance, and cost. For bulk transfer, export BigQuery tables to Parquet in Google Cloud Storage, move them to S3 with AWS DataSync, create or register Iceberg tables, and synchronize incremental changes during transition. Cutover includes parallel validation and deciding whether each consumer will reconnect, be rebuilt, or relay data. The article distinguishes managed S3 Tables, which handle maintenance automatically, from self-managed Iceberg on general-purpose S3, which requires tuning. It also cautions that BigQuery scan-based and Redshift compute-based pricing are not directly comparable, recommending workload-based benchmarks and monthly TCO estimates. Post-migration steps include query and cost optimization.

### Source excerpt

Learn how to migrate Google BigQuery workloads to an open lakehouse on AWS built on Apache Iceberg and Amazon S3. This post explains why an open lakehouse future-proofs your data, presents the target architecture on AWS, and walks through a step-by-step migration: assess, design, convert, migrate, cut over, and optimize.

## AWS Weekly Roundup: GPT-6.1 Terra on Bedrock, Step Functions as agent tools, and more (November 2, 2026)

DevFeed: [AWS Weekly Roundup: GPT-6.1 Terra on Bedrock, Step Functions as agent tools, and more (November 2, 2026)](<https://devfeed.tech/articles/aws-weekly-roundup-gpt-6-1-terra-on-bedrock-step-functions-as-agent-tools-and-more-november-2-2026-113316.md>)

Original publisher: [Read original article](<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/>)

Author: Daniel Abib

Published: 2026-11-02T16:45:48Z

Content type: news

Language: en

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

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [function calling](<https://devfeed.tech/topics/function-calling.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [agent-tools](<https://devfeed.tech/tags/agent-tools.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-sagemaker-ai](<https://devfeed.tech/tags/amazon-sagemaker-ai.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [aws-fault-injection-service-fis](<https://devfeed.tech/tags/aws-fault-injection-service-fis.md>), [aws-iam-identity-center](<https://devfeed.tech/tags/aws-iam-identity-center.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [gpt](<https://devfeed.tech/tags/gpt.md>), [gpt-6-1](<https://devfeed.tech/tags/gpt-6-1.md>), [gpt-6-1-terra](<https://devfeed.tech/tags/gpt-6-1-terra.md>), [model](<https://devfeed.tech/tags/model.md>), [news](<https://devfeed.tech/tags/news.md>), [step-functions](<https://devfeed.tech/tags/step-functions.md>), [week-in-review](<https://devfeed.tech/tags/week-in-review.md>), [weekly](<https://devfeed.tech/tags/weekly.md>), [weekly-roundup](<https://devfeed.tech/tags/weekly-roundup.md>)

### AI overview

The roundup highlights access and cost across recent AWS launches. GPT-6.1 Terra is generally available on Bedrock; OpenAI reports it scored 15 points above GPT-5.6 Terra on Agents' Last Exam, performed on par with GPT-6 Astra, and completed tasks over three times faster, with input and output token prices at least 50% lower than GPT-6.1 Sol and GPT-5.6 Terra. These are OpenAI figures, not independent results. Bedrock AgentCore Gateway can expose existing Step Functions Standard and Express workflows as MCP tools: agents choose when to run them and supply inputs, while the workflow preserves its defined step order. Other updates include KMS support for NIST ML-KEM, cross-Region identity propagation in IAM Identity Center, ECS GPU sharing with NVIDIA MPS, SOCI lazy loading for Lambda container images, and EKS Auto Mode support for Kubernetes Gateway API. The roundup also reports customer examples, including MoEngage exposing roughly 400 APIs as agent tools and S3 lifecycle changes that reduced costs for one 5.8 PB workload by about 70%.

### Source excerpt

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 [...]

## Aligning AWS security capabilities with standards and security frameworks for the Betting and Gaming industry - Part 2

DevFeed: [Aligning AWS security capabilities with standards and security frameworks for the Betting and Gaming industry - Part 2](<https://devfeed.tech/articles/aligning-aws-security-capabilities-with-standards-and-security-frameworks-for-the-betting-and-gaming-industry-part-2-108414.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/gametech/aligning-aws-security-capabilities-with-standards-and-security-frameworks-for-the-betting-and-gaming-industry-part-2/>)

Author: Sirinda Glasgow

Published: 2026-10-30T14:37:21Z

Content type: article

Language: en

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

Topics: [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [Security](<https://devfeed.tech/topics/security.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [federal information processing standards](<https://devfeed.tech/topics/federal-information-processing-standards.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [network security](<https://devfeed.tech/topics/network-security.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-fraud-detector](<https://devfeed.tech/tags/amazon-fraud-detector.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [audit](<https://devfeed.tech/tags/audit.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-cloudhsm](<https://devfeed.tech/tags/aws-cloudhsm.md>), [aws-codepipeline](<https://devfeed.tech/tags/aws-codepipeline.md>), [aws-control-tower](<https://devfeed.tech/tags/aws-control-tower.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-outposts](<https://devfeed.tech/tags/aws-outposts.md>), [aws-security-hub](<https://devfeed.tech/tags/aws-security-hub.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [aws-well-architected-framework](<https://devfeed.tech/tags/aws-well-architected-framework.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [betting](<https://devfeed.tech/tags/betting.md>), [change-management](<https://devfeed.tech/tags/change-management.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [fraud](<https://devfeed.tech/tags/fraud.md>), [games](<https://devfeed.tech/tags/games.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [gaming-industry](<https://devfeed.tech/tags/gaming-industry.md>), [generation](<https://devfeed.tech/tags/generation.md>), [geolocation](<https://devfeed.tech/tags/geolocation.md>), [industries](<https://devfeed.tech/tags/industries.md>), [information-security](<https://devfeed.tech/tags/information-security.md>), [multi-account](<https://devfeed.tech/tags/multi-account.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [security](<https://devfeed.tech/tags/security.md>), [standards](<https://devfeed.tech/tags/standards.md>)

### AI overview

GLI-19 and GLI-33 set gaming-specific expectations for areas including geolocation, random number generation, responsible gaming, anti-fraud, change management, and disaster recovery. AWS provides general-purpose infrastructure that operators can configure to support these objectives, but it does not design or certify gaming compliance solutions; operators and their licensed suppliers remain responsible for regulatory requirements, implementation, testing, and certification. Examples include Control Tower Region guardrails and API Gateway connections to selected geolocation vendors; KMS GenerateRandom and CloudHSM as general cryptographic capabilities, not gaming RNG products; analytics and machine learning services for operator-designed monitoring; CodePipeline approval gates and Step Functions incident workflows; and multi-AZ databases, cross-Region replication, AWS DRS, and AWS Backup for recovery architectures. The article recommends starting with a SIP assessment and foundational controls, then establishing jurisdiction-specific controls and continuous monitoring and testing. It emphasizes that service use alone does not establish compliance and that legal and regulatory input

### Source excerpt

In Part 1 of this series, we described how AWS security best practices, using the AWS Security Improvement Program (SIP) and the Security pillar of the AWS Well-Architected Framework, can help Betting and Gaming operators strengthen foundational cloud security, covering information security, identity and access management, audit and logging, network security, and multi-account strategy. Part 2 turns to gaming-specific controls and resilience: geolocation, random number generation, responsible gaming and anti-fraud, change management, and disaster recovery.

## Default to serverless for AI agents, then let production data decide what moves

DevFeed: [Default to serverless for AI agents, then let production data decide what moves](<https://devfeed.tech/articles/default-to-serverless-for-ai-agents-then-let-production-data-decide-what-moves-107138.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/serverless-ai-agents/>)

Author: Candace Shamieh; Alex Barksdale; James Eastham; Olivier Nzia

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [serverless monitoring](<https://devfeed.tech/topics/serverless-monitoring.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [long-running](<https://devfeed.tech/topics/long-running.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [azure functions](<https://devfeed.tech/topics/azure-functions.md>), [LangChain](<https://devfeed.tech/topics/langchain.md>), [vercel ai sdk](<https://devfeed.tech/topics/vercel-ai-sdk.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apm](<https://devfeed.tech/tags/apm.md>), [build](<https://devfeed.tech/tags/build.md>), [compare](<https://devfeed.tech/tags/compare.md>), [compute](<https://devfeed.tech/tags/compute.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [execution](<https://devfeed.tech/tags/execution.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [let](<https://devfeed.tech/tags/let.md>), [production](<https://devfeed.tech/tags/production.md>), [profile](<https://devfeed.tech/tags/profile.md>), [run](<https://devfeed.tech/tags/run.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [serverless-monitoring](<https://devfeed.tech/tags/serverless-monitoring.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Start by evaluating serverless for agent workloads, then use production measurements to decide whether particular steps need warm or dedicated capacity. The excerpt reports a study of over 35,000 coding-agent sessions in which the median session spent 20% of its lifetime on LLM or tool calls, with the rest idle between steps. Build an execution profile from arrival patterns, burst and concurrency, response-time goals, active versus elapsed run time, and resource requirements; daily averages can conceal bursts. For multi-step runs that pause, durable workflows can checkpoint progress, release compute, and resume at a timer, event, or callback. Retries should avoid repeating external side effects. Compare placements by cost per successful run, including attempted work, orchestration, storage, network, telemetry, and any added costs from retries; account for minimum warm capacity when required. Production traces can identify whether latency comes from startup or from model, tool, and retrieval activity. Move only steps whose measured latency, utilization, or runtime constraints justify it, and reassess as workload and pricing change.

### Source excerpt

Learn how to run AI agents as serverless workflows, build an execution profile, and compare costs against warm or dedicated compute.

## AI-enriched ingestion pipelines for searchable live and VOD media on AWS

DevFeed: [AI-enriched ingestion pipelines for searchable live and VOD media on AWS](<https://devfeed.tech/articles/ai-enriched-ingestion-pipelines-for-searchable-live-and-vod-media-on-aws-103468.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/media/ai-enriched-ingestion-pipelines-for-searchable-live-and-vod-media-on-aws/>)

Author: Mohan Kumar Guruswamy

Published: 2026-10-27T23:23:57Z

Content type: article

Language: en

Sources: [AWS for M&E Blog](<https://devfeed.tech/sources/aws-for-m-e-blog.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon OpenSearch Service](<https://devfeed.tech/topics/amazon-opensearch-service.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Image](<https://devfeed.tech/topics/image.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-data-automation](<https://devfeed.tech/tags/amazon-bedrock-data-automation.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-opensearch-service](<https://devfeed.tech/tags/amazon-opensearch-service.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-queue-service-sqs](<https://devfeed.tech/tags/amazon-simple-queue-service-sqs.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [amazon-transcribe](<https://devfeed.tech/tags/amazon-transcribe.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-elemental-mediaconvert](<https://devfeed.tech/tags/aws-elemental-mediaconvert.md>), [aws-elemental-medialive](<https://devfeed.tech/tags/aws-elemental-medialive.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [industries](<https://devfeed.tech/tags/industries.md>), [live](<https://devfeed.tech/tags/live.md>), [media](<https://devfeed.tech/tags/media.md>), [media-entertainment](<https://devfeed.tech/tags/media-entertainment.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

The article describes an AWS design that makes live and archived media searchable by its content through parallel AI analysis at ingestion. For live broadcasts, MediaLive writes roughly six-second HLS segments to S3; every 60 seconds, Step Functions processes a batch with Marengo 3.0 embeddings, Bedrock Data Automation scene analysis, and Transcribe, indexing results in OpenSearch within 60-90 seconds. Elemental Inference separately detects live key moments, which can be indexed within 20-30 seconds. The VOD pipeline queues uploads for backpressure, transcodes by media type, then runs similar analysis; dynamic scene segmentation and a 24-hour workflow accommodate longer assets. It uses modality-specific outputs and permits partial indexing if a branch fails. Both pipelines create a shared document structure for unified search. The AI index adds to TAMS while leaving its timeline and existing tools intact. This is Part 1; the unified search architecture is reserved for Part 2.

### Source excerpt

As organizations adopt TAMS and cloud-centered workflows through the Amazon Web Services (AWS) Cloud-Native Agile Production (CNAP) program, the opportunity is clear: Make content discoverable by what it contains rather than how it was tagged. This post, which is Part 1 of a two-part series, describes how AI-powered ingestion pipelines analyze each piece of media at ingest time.

## Fleet-wide computer vision lifecycle at the edge with SageMaker SDK v3

DevFeed: [Fleet-wide computer vision lifecycle at the edge with SageMaker SDK v3](<https://devfeed.tech/articles/fleet-wide-computer-vision-lifecycle-at-the-edge-with-sagemaker-sdk-v3-101018.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/fleet-wide-computer-vision-lifecycle-at-the-edge-with-sagemaker-sdk-v3/>)

Author: Kiowa Jackson

Published: 2026-10-26T17:56:58Z

Content type: article

Language: en

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

Topics: [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [Computer vision](<https://devfeed.tech/topics/computer-vision.md>), [ML model versioning](<https://devfeed.tech/topics/ml-model-versioning.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [image recognition](<https://devfeed.tech/topics/image-recognition.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [camera](<https://devfeed.tech/tags/camera.md>), [computer](<https://devfeed.tech/tags/computer.md>), [computer-vision](<https://devfeed.tech/tags/computer-vision.md>), [edge](<https://devfeed.tech/tags/edge.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [functions](<https://devfeed.tech/tags/functions.md>), [layer](<https://devfeed.tech/tags/layer.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [model](<https://devfeed.tech/tags/model.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [v3](<https://devfeed.tech/tags/v3.md>), [vision](<https://devfeed.tech/tags/vision.md>), [wide](<https://devfeed.tech/tags/wide.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The sample shows how to train and manage separate computer vision models for each camera using SageMaker SDK v3. A dual-branch pipeline trains an anomaly detector and defect classifier, evaluates exported ONNX artifacts, applies independent quality gates, compiles passing models with SageMaker Neo, and registers them with camera metadata for per-camera warm starts. SQS and Step Functions pace retraining through a DynamoDB semaphore, capped at five concurrent executions by default; failures are forwarded to SNS. The article highlights SDK v3 deployment constraints: role validation occurs during synthesis, so the sample uses a two-phase deployment and a concrete role ARN, and its ECR grant is broader to satisfy permission simulation. It reports a roughly 15-minute synthetic-data run costing about $0.07 in compute. The registry artifacts support downstream delivery to devices rather than SageMaker inference endpoints.

### Source excerpt

Fleet-wide computer vision needs a model per camera, not one model for the whole fleet. This post presents a working Amazon SageMaker SDK v3 reference architecture that trains, quality-gates, compiles per-camera models with SageMaker Neo, and versions thousands of them, with an AWS Step Functions layer pacing fleet-scale retraining within account quotas.

## Orchestrating SageMaker AI endpoint auto scaling with AWS CDK

DevFeed: [Orchestrating SageMaker AI endpoint auto scaling with AWS CDK](<https://devfeed.tech/articles/orchestrating-sagemaker-ai-endpoint-auto-scaling-with-aws-cdk-97805.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/orchestrating-sagemaker-ai-endpoint-auto-scaling-with-aws-cdk/>)

Author: Lauren Eterno

Published: 2026-10-23T16:30:10Z

Content type: article

Language: en

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

Topics: [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [Deployment & Scaling](<https://devfeed.tech/topics/deployment-scaling.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-sagemaker-ai](<https://devfeed.tech/tags/amazon-sagemaker-ai.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [aws-cdk](<https://devfeed.tech/tags/aws-cdk.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Updating a SageMaker AI endpoint while Application Auto Scaling is registered can fail because SageMaker requires the scalable target to be deregistered first; manual deregistration can also leave CloudFormation tracking stale or cause a failed rollback. The described reusable AWS CDK construct replaces native scaling resources with three CloudFormation custom resources ordered around the endpoint update: deregister the target, update the endpoint, wait for it to reach InService before registering the target, then wait until the target is queryable before attaching its scaling policy. Asynchronous CDK providers poll readiness with bounded total timeouts. A ConfigHash causes configuration changes to trigger the orchestration, keeping endpoint and scaling updates in one deployment. The text notes the resulting stack also includes provider-generated Lambda functions and Step Functions state machines.

### Source excerpt

Updating a SageMaker AI endpoint that has Application Auto Scaling registered makes AWS CloudFormation and AWS CDK deployments fail. This post shows how to build a reusable AWS CDK construct with CloudFormation custom resources that deregisters and re-registers auto scaling automatically, so you can update the endpoint and its scaling in a single deployment.

## Automate medical coding with Step Functions and Amazon Bedrock AgentCore

DevFeed: [Automate medical coding with Step Functions and Amazon Bedrock AgentCore](<https://devfeed.tech/articles/automate-medical-coding-with-step-functions-and-amazon-bedrock-agentcore-93907.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/automate-medical-coding-with-step-functions-and-amazon-bedrock-agentcore/>)

Author: Sachin Doshi

Published: 2026-10-21T21:26:23Z

Content type: tutorial

Language: en

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

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [function calling](<https://devfeed.tech/topics/function-calling.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [automate](<https://devfeed.tech/tags/automate.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [coding](<https://devfeed.tech/tags/coding.md>), [harness](<https://devfeed.tech/tags/harness.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [medical](<https://devfeed.tech/tags/medical.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [routing](<https://devfeed.tech/tags/routing.md>), [step-functions](<https://devfeed.tech/tags/step-functions.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The workflow uses AWS Step Functions to keep sequencing, routing, and audit history deterministic while limiting an Amazon Bedrock AgentCore agent to ambiguous coding decisions. A Lambda first blocks terms unsafe to autocode, then checks exact dictionary and curated synonym matches; only misses reach the agent, which searches with Titan embeddings and can request study context through a separate tool. The workflow routes on the agent's reported confidence, applies a fixed 0.90 autocode gate, and checks that the selected code exists before writing it back; lower-confidence or invalid cases remain open for human review. The article reports that confidence can vary across identical runs, and vector retrieval can omit the clinically correct candidate, so thresholds need validation against known-correct data and retrieval quality limits results. Its sample is demonstrative, not for clinical use; licensed MedDRA or WHODrug dictionaries require subscriptions.

### Source excerpt

Learn how to combine deterministic orchestration with bounded agentic reasoning using AWS Step Functions and the Amazon Bedrock AgentCore harness. This medical coding workflow escalates cheapest-first: a safety block-list, then exact matching, then an AI agent only for terms that need judgment, keeping every routing decision auditable.

## How to Turn Long-Running Python Simulations Into a Self-Service Platform

DevFeed: [How to Turn Long-Running Python Simulations Into a Self-Service Platform](<https://devfeed.tech/articles/how-to-turn-long-running-python-simulations-into-a-self-service-platform-92867.md>)

Original publisher: [Read original article](<https://towardsdatascience.com/how-to-turn-long-running-python-simulations-into-a-self-service-platform/>)

Author: Anand Rawat

Published: 2026-10-21T14:00:00Z

Content type: article

Language: en

Sources: [Towards Data Science](<https://devfeed.tech/sources/towards-data-science.md>)

Topics: [self-service](<https://devfeed.tech/topics/self-service.md>), [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [editor-s-picks](<https://devfeed.tech/tags/editor-s-picks.md>), [failure](<https://devfeed.tech/tags/failure.md>), [failure-recovery](<https://devfeed.tech/tags/failure-recovery.md>), [first](<https://devfeed.tech/tags/first.md>), [i](<https://devfeed.tech/tags/i.md>), [long-running](<https://devfeed.tech/tags/long-running.md>), [platform](<https://devfeed.tech/tags/platform.md>), [python](<https://devfeed.tech/tags/python.md>), [queues](<https://devfeed.tech/tags/queues.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [running](<https://devfeed.tech/tags/running.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [service](<https://devfeed.tech/tags/service.md>), [simulations](<https://devfeed.tech/tags/simulations.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The platform's main challenge was reliable job control, not raw compute. It separated submission from execution: users stored configurations and received job IDs, SQS buffered work, Lambda orchestrated it, EC2 ran simulations, S3 stored artifacts, and Redshift held structured results. Durable job state, explicit transitions, idempotency, bounded retries and dead-letter handling helped manage duplicate delivery and failures; isolated runs and execution manifests supported traceability and reproducibility. The local SQLite demo illustrates these ideas but lacks worker-loss recovery, visibility timeouts, checkpointing, execution timeouts and dependency-complete manifests, so its results do not establish production behavior. Project records report roughly three times as many experiments per working cycle and near-zero idle EC2 execution cost, while other AWS services still cost money. The author would evaluate AWS Batch or ECS and Step Functions, while cautioning that Kubernetes adds operational costs and that reproducibility needs stronger lineage from the outset.

### Source excerpt

What I learned about queues, failure recovery, and reproducibility while building asynchronous workloads on AWS The post How to Turn Long-Running Python Simulations Into a Self-Service Platform appeared first on Towards Data Science.

## Best Idempotency and Retry Infrastructure for Agents

DevFeed: [Best Idempotency and Retry Infrastructure for Agents](<https://devfeed.tech/articles/best-idempotency-and-retry-infrastructure-for-agents-92491.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-idempotency-retry-infrastructure>)

Author: Swytchcode Team

Published: 2026-10-21T09:53:12.592027Z

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [retry](<https://devfeed.tech/topics/retry.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [inngest](<https://devfeed.tech/tags/inngest.md>), [retry](<https://devfeed.tech/tags/retry.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [trigger](<https://devfeed.tech/tags/trigger.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Agent workflows need both durable orchestration and provider-side idempotency: an engine can resume or replay steps, but cannot tell whether a timed-out write already took effect. The article compares six orchestration tools--Temporal, Inngest, Trigger.dev, AWS Step Functions, Upstash Workflow and Cloudflare Workflows--and says none documents outbound idempotency-key handling as an orchestration feature. Their recovery differs: Temporal replays event history but requires deterministic workflow code; Inngest memoizes completed steps, though that does not protect a write whose response was lost; Trigger.dev supports dashboard bulk replay, which can repeat writes; Step Functions has no step memoization; Upstash can resume from a failed step with completed results preserved; and Cloudflare retries each step five times by default. Swytchcode is presented as a call layer that retries POST/PATCH on rate limits only when a key is set, but it does not provide durable workflow state. The recommended pattern is to generate a deterministic key near each write, avoid automatic retries of unprotected writes, account for provider key-expiry windows, and retain an attempt-level audit trail. To test,

### Source excerpt

Who owns the idempotency key, and does a retry actually reuse it? Temporal, Inngest, Trigger.dev, AWS Step Functions and Cloudflare Workflows compared.

## Migrate MuleSoft APIs to AWS serverless with AWS Transform custom

DevFeed: [Migrate MuleSoft APIs to AWS serverless with AWS Transform custom](<https://devfeed.tech/articles/migrate-mulesoft-apis-to-aws-serverless-with-aws-transform-custom-90832.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/migrate-mulesoft-apis-to-aws-serverless-with-aws-transform-custom/>)

Author: Swapnil Singh

Published: 2026-10-20T15:54:22Z

Content type: article

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [AWS Transform](<https://devfeed.tech/topics/aws-transform.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon API Gateway](<https://devfeed.tech/topics/amazon-api-gateway.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [apis](<https://devfeed.tech/tags/apis.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws](<https://devfeed.tech/tags/aws.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-transform](<https://devfeed.tech/tags/aws-transform.md>), [custom](<https://devfeed.tech/tags/custom.md>), [enterprise-strategy](<https://devfeed.tech/tags/enterprise-strategy.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [migration](<https://devfeed.tech/tags/migration.md>), [mulesoft](<https://devfeed.tech/tags/mulesoft.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Transform custom offers reusable Java or Python definitions to convert MuleSoft applications into serverless AWS artifacts, applying encoded migration rules across a portfolio. The default target uses API Gateway, Lambda, DynamoDB, and Step Functions; simple DataWeave operations map to API Gateway templates, medium complexity to Step Functions intrinsics, and complex parsing or recursive logic to Lambda. Connector mappings vary: some have direct AWS equivalents, while Workday, SAP, and similar systems require custom Lambda integrations, with credentials stored in Secrets Manager and TODOs for endpoint verification. The process analyzes Mule XML, generates infrastructure, code, tests, and deployment documentation, then runs tests and SAM validation/build checks. A pilot and manual review are expected. Deployment, live integration testing, CI/CD, consumer cutover, database migration, and post-deployment performance tuning remain separate work.

### Source excerpt

When you migrate a portfolio of MuleSoft applications to AWS serverless, each application brings its own decisions: how every connector maps to an AWS service, how DataWeave scripts translate to AWS equivalents, and how error-handling strategies carry over. Multiply those decisions across a portfolio, and each migration becomes a one-off exercise. In this post, explore [...]

## dbt State now available free forever

DevFeed: [dbt State now available free forever](<https://devfeed.tech/articles/dbt-state-now-available-free-forever-91154.md>)

Original publisher: [Read original article](<https://www.getdbt.com/blog/dbt-state-now-available-free-forever>)

Author: Reuben McCreanor

Published: 2026-10-20T14:00:00Z

Content type: release

Language: en

Sources: [dbt Labs](<https://devfeed.tech/sources/dbt-labs.md>)

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [2027](<https://devfeed.tech/tags/2027.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [all](<https://devfeed.tech/tags/all.md>), [allows](<https://devfeed.tech/tags/allows.md>), [amazing](<https://devfeed.tech/tags/amazing.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [card](<https://devfeed.tech/tags/card.md>), [dbt](<https://devfeed.tech/tags/dbt.md>), [free](<https://devfeed.tech/tags/free.md>), [models](<https://devfeed.tech/tags/models.md>), [monthly](<https://devfeed.tech/tags/monthly.md>), [product](<https://devfeed.tech/tags/product.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [skip](<https://devfeed.tech/tags/skip.md>), [state](<https://devfeed.tech/tags/state.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

dbt State offers self-hosted dbt users an ongoing free allowance of 1,000 DATT per month after the trial; trial usage does not reduce that month's allowance, which resets on the first. A dbt account is required, but no payment method is needed unless users exceed the allowance, when they can add a card for pay-as-you-go billing or discuss an upfront commit. Most dbt platform users automatically receive 2,000 DATT monthly through March 2027. DATT counts each model or test skipped or cloned once per day, regardless of reuse frequency. dbt State shares state across runs to skip or clone eligible work, and is described as usable in production, staging, or development with self-hosted dbt 1.7+ (v2), dbt platform, Airflow, Dagster, and several listed warehouses.

### Source excerpt

dbt State is now free forever for self-hosted dbt users. Get a monthly allowance, no card needed, and skip unchanged models.

## Your serverless attendee's guide to AWS re:Invent 2026

DevFeed: [Your serverless attendee's guide to AWS re:Invent 2026](<https://devfeed.tech/articles/your-serverless-attendee-s-guide-to-aws-re-invent-2026-87256.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/your-serverless-attendees-guide-to-aws-reinvent-2026/>)

Author: Nicolas Tarzia

Published: 2026-10-14T16:55:24Z

Content type: article

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

A guide to AWS re:Invent 2026 sessions on serverless computing, covering Lambda execution models, event-driven architectures, AI agents, APIs, developer workflows, scaling, and operations. It describes session formats and topics to help attendees choose relevant sessions.

### Source excerpt

AWS re:Invent 2026 offers an extensive selection of serverless and application integration content, including new AWS Lambda execution models, AI agents as a new kind of serverless consumer, and maturing event-driven patterns. This guide helps you navigate the serverless sessions and find the content most relevant to you.

## Running scalable hybrid quantum-classical workflows by integrating Amazon Braket with AWS Batch

DevFeed: [Running scalable hybrid quantum-classical workflows by integrating Amazon Braket with AWS Batch](<https://devfeed.tech/articles/running-scalable-hybrid-quantum-classical-workflows-by-integrating-amazon-braket-with-aws-batch-85259.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/quantum-computing/running-scalable-hybrid-quantum-classical-workflows-by-integrating-amazon-braket-with-aws-batch/>)

Author: Benchen Huang

Published: 2026-10-12T16:37:51Z

Content type: tutorial

Language: en

Sources: [AWS Quantum Technologies Blog](<https://devfeed.tech/sources/aws-quantum-technologies-blog.md>)

Topics: [Quantum Computing](<https://devfeed.tech/topics/quantum-computing.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>)

Tags: [amazon-braket](<https://devfeed.tech/tags/amazon-braket.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-batch](<https://devfeed.tech/tags/aws-batch.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [quantum-computing](<https://devfeed.tech/tags/quantum-computing.md>), [quantum-research](<https://devfeed.tech/tags/quantum-research.md>), [quantum-technologies](<https://devfeed.tech/tags/quantum-technologies.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

This practical example shows how to orchestrate a hybrid quantum-classical QC-AFQMC workflow with Amazon Braket Hybrid Jobs, AWS Batch, AWS Lambda, Amazon S3, and AWS Step Functions. Quantum sampling produces data for parallel classical processing across Monte Carlo walkers, followed by energy averaging. The post describes a sample run on a hydrogen molecule and explains how the state machine coordinates sequencing, monitoring, retries, and data handoffs.

### Source excerpt

Practical quantum computing is hybrid: a quantum processing unit (QPU) executes a classically hard subroutine whose problem structure is amenable to quantum methods, while classical resources handle the surrounding computation. What varies across quantum algorithms is the workflow pattern: how the computation is distributed, what communication is needed, and how the data flows. Variational algorithms [...]

## Building Production-Ready Multi-Agent AI Systems on Amazon EKS: The Complete Step-by-Step Guide

DevFeed: [Building Production-Ready Multi-Agent AI Systems on Amazon EKS: The Complete Step-by-Step Guide](<https://devfeed.tech/articles/building-production-ready-multi-agent-ai-systems-on-amazon-eks-the-complete-step-by-step-guide-77230.md>)

Original publisher: [Read original article](<https://hackernoon.com/building-production-ready-multi-agent-ai-systems-on-amazon-eks-the-complete-step-by-step-guide?source=rss>)

Author: Emmanuela Opurum

Published: 2026-10-08T06:14:06Z

Content type: tutorial

Language: en

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

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [grab agent platform](<https://devfeed.tech/topics/grab-agent-platform.md>), [Amazon SageMaker HyperPod](<https://devfeed.tech/topics/amazon-sagemaker-hyperpod.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [beginners](<https://devfeed.tech/tags/beginners.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [guide](<https://devfeed.tech/tags/guide.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [multi-agent-ai](<https://devfeed.tech/tags/multi-agent-ai.md>), [production](<https://devfeed.tech/tags/production.md>), [solution-architect](<https://devfeed.tech/tags/solution-architect.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

This tutorial walks through building a multi-agent AI application on Amazon EKS, including specialist agents, request routing, retrieval-augmented generation, Bedrock Guardrails, response checks, human approval workflows, and deployment. It provides AWS setup commands, Python code, Kubernetes manifests, and sample requests.

### Source excerpt

This is the complete step-by-step guide to building a production multi-agent AI system on AWS.

## Automate remediation post AWS DevOps Agent investigation

DevFeed: [Automate remediation post AWS DevOps Agent investigation](<https://devfeed.tech/articles/automate-remediation-post-aws-devops-agent-investigation-66985.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/automate-remediation-post-aws-devops-agent-investigation/>)

Author: Michele Scarimbolo

Published: 2026-10-07T15:46:49Z

Content type: tutorial

Language: en

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

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-loop](<https://devfeed.tech/tags/agentic-loop.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [automate](<https://devfeed.tech/tags/automate.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [durable-functions](<https://devfeed.tech/tags/durable-functions.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [eventbridge](<https://devfeed.tech/tags/eventbridge.md>), [functions](<https://devfeed.tech/tags/functions.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article presents an AWS workflow that takes incident investigations from AWS DevOps Agent and prepares remediation actions using Lambda Durable Functions, EventBridge, and Amazon Bedrock. Read-only tools run automatically, while infrastructure changes pause for human approval. The walkthrough describes deployment, validation, and the use of an allowlist and approval gate to control changes.

### Source excerpt

AWS DevOps Agent can diagnose production incidents but is kept in observe-and-report mode so it does not change resources directly. This post shows how to use AWS Lambda Durable Functions, Amazon EventBridge, and Amazon Bedrock to turn its investigation summaries into pre-validated fixes an on-call engineer can approve with a single action.

## Migrate SSIS packages to Aurora PostgreSQL - Part 2

DevFeed: [Migrate SSIS packages to Aurora PostgreSQL - Part 2](<https://devfeed.tech/articles/migrate-ssis-packages-to-aurora-postgresql-part-2-66961.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/migrate-ssis-packages-to-aurora-postgresql-part-2/>)

Author: Suchindranath Hegde

Published: 2026-10-07T15:21:26Z

Content type: tutorial

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>), [DSQL](<https://devfeed.tech/topics/dsql.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-compatible](<https://devfeed.tech/tags/postgresql-compatible.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains how to migrate complex SSIS packages to AWS using Step Functions to coordinate Lambda tasks, Map and Parallel states, and EventBridge scheduling. It also covers error handling, notifications, and operational tradeoffs, with Aurora PostgreSQL as the database target.

### Source excerpt

Part 2 of migrating SSIS packages to Amazon Aurora PostgreSQL tackles the complex packages. Learn how to replace SSIS control flow, Foreach Loop Containers, and Script Tasks with AWS Step Functions state machines, Map and Parallel states, and Lambda, and schedule them with Amazon EventBridge in place of SQL Server Agent.

[Next page](<https://devfeed.tech/topics/aws-step-functions.md?cursor=WyIyMDI2LTEwLTA3VDE1OjIxOjI2KzAwOjAwIiwgIjY3OWE4MWRjLWU3ZGQtNGRhMC1iN2U5LTEzMDhjZGQ0NWFmMCJd>)