# Amazon CloudWatch

Amazon CloudWatch is an observability service for monitoring and optimizing applications, infrastructure, metrics, logs, and traces.

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

## Introducing mTLS for Network Load Balancer

DevFeed: [Introducing mTLS for Network Load Balancer](<https://devfeed.tech/articles/introducing-mtls-for-network-load-balancer-144602.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-mtls-for-network-load-balancer/>)

Author: Rizwan Mushtaq

Published: 2026-11-19T22:45:08Z

Content type: release

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [mtls](<https://devfeed.tech/tags/mtls.md>), [mutual-tls](<https://devfeed.tech/tags/mutual-tls.md>), [network](<https://devfeed.tech/tags/network.md>), [spiffe](<https://devfeed.tech/tags/spiffe.md>), [store](<https://devfeed.tech/tags/store.md>), [tls](<https://devfeed.tech/tags/tls.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Network Load Balancer (NLB) can verify client certificates at a TLS listener, so only clients that pass trust, optional identity filters, and revocation checks reach backend targets; targets receive no client certificate data. Configure verify mode with a trust store built from a CA bundle in Amazon S3, optionally add a CRL, and optionally filter on certificate CN, OU, DNS SAN, or URI SAN (including SPIFFE IDs). Filters use exact or prefix matching, are OR-combined, and apply per listener. NLB checks trust chains, certificate expiry and purpose, then filters and revocation; expired certificates can be allowed through an advanced setting. CRLs are imported when added and must be added again when updated. Access logs record authentication failures, while CloudWatch metrics cover handshakes, errors, latency, and certificate expiration. The article also describes setup prerequisites, testing, trust store sharing, limits, and configuration through console, CLI, SDKs, or CloudFormation.

### Source excerpt

Network Load Balancer now offloads mutual TLS for you. Learn how to attach a trust store, validate client certificates against your revocation lists, restrict access by CN, OU, or SPIFFE ID with client certificate filtering, and monitor connections with access logs and Amazon CloudWatch metrics.

## Performance impact of excessive logging in Amazon Aurora PostgreSQL

DevFeed: [Performance impact of excessive logging in Amazon Aurora PostgreSQL](<https://devfeed.tech/articles/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql-144312.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql/>)

Author: Baji Shaik

Published: 2026-11-19T19:10:08Z

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>), [Logging](<https://devfeed.tech/topics/logging.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [logging](<https://devfeed.tech/tags/logging.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [throughput](<https://devfeed.tech/tags/throughput.md>)

### AI overview

In a pgbench test on Aurora PostgreSQL 17, verbose logging had little effect at 8 clients, but at 800 clients, logging every statement reduced throughput by about 10%; adding `pgaudit.log = ALL` cut whole-run throughput from 16,202 to 5,039 TPS. Sampling showed sessions mostly active on CPU rather than waiting on instrumented resources, and a 537 MB log file written in under a minute supported a bottleneck in log generation and writing. The article recommends checking `pg_settings`, correlating slow periods with `pg_stat_activity` wait events and RDS log-file sizes, and testing at production-like concurrency. For audit needs, it suggests narrowing logged statement classes or using `pgaudit.log_statement = off` to retain structured audit details while dropping embedded SQL text; it advises confirming the reduction on the workload.

### Source excerpt

Excessive database and audit logging can quietly become a performance bottleneck in Amazon Aurora and Amazon RDS for PostgreSQL. Using a reproducible pgbench example, this post shows when logging overhead is negligible and when it cuts throughput by about three times, how to spot it with wait events and log file evidence, and how to reduce it.

## AWS Lambda Durable Functions observability with OpenTelemetry

DevFeed: [AWS Lambda Durable Functions observability with OpenTelemetry](<https://devfeed.tech/articles/aws-lambda-durable-functions-observability-with-opentelemetry-144754.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/aws-lambda-durable-functions-observability-with-opentelemetry/>)

Author: Ricardo Marques

Published: 2026-11-19T19:09:43Z

Content type: tutorial

Language: en

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

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [observability](<https://devfeed.tech/topics/observability.md>), [serverless monitoring](<https://devfeed.tech/topics/serverless-monitoring.md>), [function as a service](<https://devfeed.tech/topics/function-as-a-service.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.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>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [durable-execution](<https://devfeed.tech/tags/durable-execution.md>), [durable-functions](<https://devfeed.tech/tags/durable-functions.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [span](<https://devfeed.tech/tags/span.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

The `aws-durable-execution-sdk-python-otel` plugin assigns deterministic trace IDs so invocations of one AWS Lambda Durable Functions execution can appear as a unified trace, with spans reflecting operation wall-clock time and avoiding duplicate spans during replay. Setup requires Python 3.11+, the ADOT Lambda layer, X-Ray active tracing and write permissions, and passing `InvocationOtelPlugin` to the durable execution handler. The post distinguishes execution view, which groups work under the workflow span but depends on the vendor's span-ingestion window, from invocation view, which can export shorter invocation spans sooner; the final workflow span still covers the full execution and may be rejected if too old. Logger enrichment adds trace and span IDs to logs by default. The ADOT layer adds cold-start and memory overhead (about 40-60 MB); the post recommends measuring impact, naming durable operations, and using sampling to manage trace costs. The excerpt's walkthrough covers a sequential workflow with a human approval callback, not every SDK primitive or failure path.

### Source excerpt

A single AWS Lambda Durable Functions workflow can span many invocations, fragmenting its traces. This post shows how the OpenTelemetry plugin for the AWS Durable Execution SDK generates deterministic trace IDs that unify every invocation into one distributed trace, and how to set it up, read the traces, and apply best practices.

## Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache

DevFeed: [Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache](<https://devfeed.tech/articles/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache-144311.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache/>)

Author: Paul Ross

Published: 2026-11-19T18:39:15Z

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>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-managed-grafana](<https://devfeed.tech/tags/amazon-managed-grafana.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [insights](<https://devfeed.tech/tags/insights.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [latency](<https://devfeed.tech/tags/latency.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [node](<https://devfeed.tech/tags/node.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [query](<https://devfeed.tech/tags/query.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache for Valkey sends engine and host metrics to CloudWatch in OpenTelemetry format without an exporter or collector. The article demonstrates using ElastiCache Insights to locate a hot shard or node, then PromQL to rank nodes, inspect command latency, and alarm across all nodes as cluster membership changes. Standard monitoring publishes core metrics every 60 seconds; selected detailed metrics arrive every 15 seconds and can expose short latency spikes that a longer window smooths out. Core metrics and ElastiCache Insights are free, while selected detailed metrics, PromQL API scans, and alarms incur charges. The walkthrough requires a node-based Valkey cluster in a supported Region; its Grafana guidance covers version 13 or later, with a separate Prometheus data source approach for version 12.4.

### Source excerpt

Amazon ElastiCache for Valkey now offers OpenTelemetry metrics, detailed monitoring, ElastiCache Insights, and PromQL. This post walks through one troubleshooting path: turn on detailed monitoring, find a hot shard, query with PromQL, catch a short latency spike, and create one alarm that watches every node.

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

## How Amazon ECS handles blue/green, canary, and linear deployments

DevFeed: [How Amazon ECS handles blue/green, canary, and linear deployments](<https://devfeed.tech/articles/how-amazon-ecs-handles-blue-green-canary-and-linear-deployments-143800.md>)

Original publisher: [Read original article](<https://thenewstack.io/amazon-ecs-deployment-strategies/>)

Author: Simon Gao

Published: 2026-11-19T16:00:00Z

Content type: article

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [blue-green deployment](<https://devfeed.tech/topics/blue-green-deployment.md>), [canary release](<https://devfeed.tech/topics/canary-release.md>), [traffic splitting](<https://devfeed.tech/topics/traffic-splitting.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Argo Rollouts](<https://devfeed.tech/topics/argo-rollouts.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-ecs](<https://devfeed.tech/tags/amazon-ecs.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [canary](<https://devfeed.tech/tags/canary.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud-services](<https://devfeed.tech/tags/cloud-services.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [green](<https://devfeed.tech/tags/green.md>), [linear](<https://devfeed.tech/tags/linear.md>), [linear-deployments](<https://devfeed.tech/tags/linear-deployments.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [sponsor-aws-marketplace](<https://devfeed.tech/tags/sponsor-aws-marketplace.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>)

### AI overview

Amazon ECS includes progressive deployment controls in its service deployment configuration and API. Rolling deployments replace tasks in batches and remain a suitable default, but rollback requires another rollout, so a bad version may keep serving traffic while alarms process. Blue/green keeps the old tasks ready during a configurable bake period of up to 24 hours, allowing rollback by shifting traffic back; it can require double compute capacity during deployment. ECS also supports linear traffic shifts in equal increments and canary shifts in two steps. Rollback and monitoring options include task health circuit breakers, CloudWatch alarms, StopServiceDeployment, and lifecycle hooks. Hooks can use Lambda to poll external monitoring such as Datadog, Splunk, or Grafana; a pause hook can instead trigger an EventBridge process that resumes deployment with ContinueServiceDeployment. The excerpt says strategies can work without a load balancer or listed network integrations, while lifecycle hooks have limited stages for rolling deployments and production traffic shift requires Lambda.

### Source excerpt

Deploying containers safely at scale can mean assembling your own system: traffic-splitting logic, alarm evaluation, rollback automation, approval gates. It's The post How Amazon ECS handles blue/green, canary, and linear deployments appeared first on The New Stack.

## Finding Amazon S3 cost savings with natural language using AWS Quick and S3 Tables

DevFeed: [Finding Amazon S3 cost savings with natural language using AWS Quick and S3 Tables](<https://devfeed.tech/articles/finding-amazon-s3-cost-savings-with-natural-language-using-aws-quick-and-s3-tables-143610.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/finding-amazon-s3-cost-savings-with-natural-language-using-aws-quick-and-s3-tables/>)

Author: Santosh Setty

Published: 2026-11-18T23:59:46Z

Content type: tutorial

Language: en

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

Topics: [Amazon S3 Tables](<https://devfeed.tech/topics/amazon-s3-tables.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [text2sql](<https://devfeed.tech/topics/text2sql.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-s3-tables](<https://devfeed.tech/tags/amazon-s3-tables.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-cloud-storage](<https://devfeed.tech/tags/aws-cloud-storage.md>), [aws-quick](<https://devfeed.tech/tags/aws-quick.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-savings](<https://devfeed.tech/tags/cost-savings.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [growth](<https://devfeed.tech/tags/growth.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [natural-language](<https://devfeed.tech/tags/natural-language.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [query](<https://devfeed.tech/tags/query.md>), [questions](<https://devfeed.tech/tags/questions.md>), [replication](<https://devfeed.tech/tags/replication.md>), [request](<https://devfeed.tech/tags/request.md>), [s3](<https://devfeed.tech/tags/s3.md>), [s3-tables](<https://devfeed.tech/tags/s3-tables.md>), [tables](<https://devfeed.tech/tags/tables.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Combining S3 Storage Lens metrics with object-level server access logs in S3 Tables lets AWS Quick answer natural-language questions about storage costs across buckets. Storage Lens provides bytes, object counts, and request metrics by storage class and prefix; access logs show object reads but not storage size. The walkthrough exports daily metrics to the aws-s3 table bucket, sends logs through CloudWatch Logs to aws-cloudwatch, then connects both to Quick. Example analyses identify cold prefixes, incomplete multipart uploads, noncurrent versions, cross-Region replication and reads, and rising GET traffic. Setup requires Quick Enterprise, and initial data may take 1-2 days to become useful; logs include sensitive requester and object details. Quick's findings are recommendations: verify the SQL or query in Athena and confirm retention needs before applying permanent expiration rules.

### Source excerpt

Across thousands of S3 buckets, the data you need to cut storage costs sits in different places. Learn how to bring Amazon S3 Storage Lens metrics and server access logs together in S3 Tables and query them with AWS Quick. Find cold data, wasted storage, replication overhead, and request growth by asking questions in natural language.

## How Airbnb uses cost per task to operate coding agents on Amazon Bedrock

DevFeed: [How Airbnb uses cost per task to operate coding agents on Amazon Bedrock](<https://devfeed.tech/articles/how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock-141280.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock/>)

Author: Alan Yao

Published: 2026-11-18T21:48:19Z

Content type: article

Language: en

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

Topics: [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [airbnb](<https://devfeed.tech/tags/airbnb.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [evals](<https://devfeed.tech/tags/evals.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [latency](<https://devfeed.tech/tags/latency.md>), [model-selection](<https://devfeed.tech/tags/model-selection.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [quotas](<https://devfeed.tech/tags/quotas.md>), [spending](<https://devfeed.tech/tags/spending.md>), [tasks](<https://devfeed.tech/tags/tasks.md>)

### AI overview

Airbnb combines task-based evaluations with Amazon Bedrock production metrics to select and revisit coding-agent models. It scores models and reasoning-effort settings on representative engineering tasks, pricing all uncached input, cache reads, cache writes, and output tokens across a task; these results guide defaults and effort ceilings. Production can diverge: one model scored better at similar eval cost, but its users later spent several times more because requests cost about three times as much and users sent about three times as many requests. A newer model later scored higher at roughly one sixth the task cost, and heavy users' spend fell to about a seventh with similar request volume. For operations, Airbnb tracks latency, token counts, derived output speed, throttles, and estimated quota usage. Quota admission reserves uncached input, cache writes, and max_tokens, so lowering an oversized max_tokens can improve admission headroom without changing final quota consumption for unchanged output. Gateway records, IAM tags, inference profiles, and invocation logs support aggregate spend attribution; logs require access controls and retention settings.

### Source excerpt

Airbnb runs evals on real engineering tasks and uses Amazon Bedrock observability to choose models for its coding agents and control production costs. This post shows how cost per task guides model selection, why production spending can differ from eval results, and how to monitor latency, manage quotas, and attribute spend.

## How to use Amazon Aurora DSQL audit logs

DevFeed: [How to use Amazon Aurora DSQL audit logs](<https://devfeed.tech/articles/how-to-use-amazon-aurora-dsql-audit-logs-141385.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-to-use-amazon-aurora-dsql-audit-logs/>)

Author: Koji Shinkubo

Published: 2026-11-18T21:33:01Z

Content type: tutorial

Language: en

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

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [athena](<https://devfeed.tech/tags/athena.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [configure](<https://devfeed.tech/tags/configure.md>), [database](<https://devfeed.tech/tags/database.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [field](<https://devfeed.tech/tags/field.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [post](<https://devfeed.tech/tags/post.md>), [query](<https://devfeed.tech/tags/query.md>), [records](<https://devfeed.tech/tags/records.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sql](<https://devfeed.tech/tags/sql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Aurora DSQL audit logging records configured SQL statement classes and delivers records to S3; it is off until both a destination and recording settings are configured. The article describes role-based scope, including READ/SELECT, and a setup that separates audit administration from DBA permissions. Records can identify the IAM role and database role, transaction, statement, and optionally bound values and row counts. Athena can query the S3 logs, while CloudTrail connection events can be joined by session ID to add client IP information; transaction IDs can also link audit records to CDC changes. Limits and tradeoffs include potentially high log volume and charges, no table- or column-level scope, no client IP or success/failure field in audit records, and recording statements from rolled-back transactions. The article recommends testing scope and volume before production and protecting sensitive log content through access controls, encryption, and retention settings.

### Source excerpt

Amazon Aurora DSQL audit logging records the SQL statements that run in your database and delivers them to Amazon S3. This post shows how to configure audit logging to meet regulatory requirements, explains what each recorded field proves in an audit, and shows how to query the logs in Amazon S3 with Amazon Athena.

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

## Build an AI-powered DBA assistant for Amazon Aurora and Amazon RDS with Kiro

DevFeed: [Build an AI-powered DBA assistant for Amazon Aurora and Amazon RDS with Kiro](<https://devfeed.tech/articles/build-an-ai-powered-dba-assistant-for-amazon-aurora-and-amazon-rds-with-kiro-138651.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-an-ai-powered-dba-assistant-for-amazon-aurora-and-amazon-rds-with-kiro/>)

Author: Narendra Tawar

Published: 2026-11-17T19:43:17Z

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>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [apply](<https://devfeed.tech/tags/apply.md>), [build](<https://devfeed.tech/tags/build.md>), [change](<https://devfeed.tech/tags/change.md>), [change-management](<https://devfeed.tech/tags/change-management.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [database](<https://devfeed.tech/tags/database.md>), [dba](<https://devfeed.tech/tags/dba.md>), [diagnostic](<https://devfeed.tech/tags/diagnostic.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [rds](<https://devfeed.tech/tags/rds.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Kiro can investigate Aurora PostgreSQL performance incidents in one interface by combining two MCP servers: the PostgreSQL server runs diagnostic queries and reads database details, while the CloudWatch server reads metrics, alarms, and logs. Database Insights load, top SQL, and wait events are also retrieved through read-only AWS CLI calls. Setup requires Kiro, Python 3.10+ and uv, AWS credentials with appropriate read permissions, and an Aurora cluster with Database Insights enabled. The assistant is read-only by default and recommends changes for the DBA to review and apply through change management. The article describes three safeguards: steering rules, a PostgreSQL read-only role, and IAM permissions that deny mutations. Its recommendations may need validation because it lacks historical performance data, runbooks, and environment-specific context. The example fix is applied manually after taking a snapshot, then checked with explain plans.

### Source excerpt

Learn how to build a DBA assistant with Kiro that investigates and resolves Amazon Aurora PostgreSQL performance incidents through natural language. Using two MCP servers, the agent reads Amazon CloudWatch metrics and Database Insights, runs diagnostic queries, and surfaces fixes you apply through your change management process.

## Three questions to ask about AI inference in Amazon EKS, and how Amazon CloudWatch answers them

DevFeed: [Three questions to ask about AI inference in Amazon EKS, and how Amazon CloudWatch answers them](<https://devfeed.tech/articles/three-questions-to-ask-about-ai-inference-in-amazon-eks-and-how-amazon-cloudwatch-answers-them-139426.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/three-questions-to-ask-about-ai-inference-in-amazon-eks-and-how-amazon-cloudwatch-answers-them/>)

Author: Jean Velez Torres

Published: 2026-11-17T18:52:53Z

Content type: tutorial

Language: en

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

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [vllm](<https://devfeed.tech/topics/vllm.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [cloudwatch-omni](<https://devfeed.tech/tags/cloudwatch-omni.md>), [costs](<https://devfeed.tech/tags/costs.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The Amazon CloudWatch Observability add-on for Amazon EKS joins DCGM GPU metrics with Kubernetes pod and namespace labels, letting teams attribute GPU use without a manual join. The post shows how accelerated compute insights, CloudWatch Omni, and PromQL queries can reveal GPU ownership and idle capacity, compare hardware activity with inference throughput and KV cache headroom, and associate health warnings or XID errors with workloads. In its test cluster, two A10G GPUs stayed allocated during nearly nine hours without requests: utilization fell to 0%, but vLLM-held memory stayed near 21,300 MiB per GPU. A model comparison found similar throughput and cost per token, while Qwen used more host CPU and memory and held nearly twice as many KV-cache tokens as Mistral; higher-load limits were not tested. The article also explains add-on configuration, PromQL alarms, and logging costs. Findings are limited to two g5.2xlarge instances with one GPU each; multi-node inference and other instance families were not tested.

### Source excerpt

GPUs are expensive and scarce. On a cluster shared by several AI teams, an idle GPU costs you twice: once on the bill, and again as capacity a team is waiting for. Three questions follow: which workload holds each GPU, how well it uses it, and which workloads are affected when one GPU goes bad. [...]

## Secure MCP integrations for AWS DevOps Agent with Amazon Bedrock AgentCore

DevFeed: [Secure MCP integrations for AWS DevOps Agent with Amazon Bedrock AgentCore](<https://devfeed.tech/articles/secure-mcp-integrations-for-aws-devops-agent-with-amazon-bedrock-agentcore-139361.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/secure-mcp-integrations-for-aws-devops-agent-with-amazon-bedrock-agentcore/>)

Author: Lakshmi Kumkala

Published: 2026-11-17T18:24:37Z

Content type: article

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [admin](<https://devfeed.tech/tags/admin.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-opensearch-service](<https://devfeed.tech/tags/amazon-opensearch-service.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [mcp-tools](<https://devfeed.tech/tags/mcp-tools.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [observability](<https://devfeed.tech/tags/observability.md>), [private](<https://devfeed.tech/tags/private.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [rotation](<https://devfeed.tech/tags/rotation.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

AWS DevOps Agent can connect to MCP servers directly or through Amazon Bedrock AgentCore Gateway. Direct registration suits one or two servers in a single account and supports private endpoints through VPC Lattice; each tool must use streamable HTTP and a supported authentication method, and admins classify tools as read-only, mutating, or destructive. AgentCore Gateway offers a single registration and SigV4 connection, centralizes backend credentials, and can apply Cedar policies, unified CloudWatch audit logs, and X-Ray tracing across targets. It is useful when servers or accounts multiply or shared policy and observability are needed; private Gateway targets add central controls, while a direct private connection requires less configuration. The article recommends checking native integrations and existing vendor or sample MCP servers before building a custom one, and starting with a read-only tool in a non-production agent space.

### Source excerpt

As you connect more Model Context Protocol (MCP) tools to AWS DevOps Agent, each one adds its own authentication, credential rotation, and audit overhead. This post shows how to extend AWS DevOps Agent with MCP tools securely using Amazon Bedrock AgentCore, so new tools inherit consistent security, access control, private connectivity, and observability.

## Investigate security data in place with Amazon CloudWatch and 7AI

DevFeed: [Investigate security data in place with Amazon CloudWatch and 7AI](<https://devfeed.tech/articles/investigate-security-data-in-place-with-amazon-cloudwatch-and-7ai-137735.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/investigate-security-data-in-place-with-amazon-cloudwatch-and-7ai/>)

Author: Kishore Vinjam

Published: 2026-11-17T01:30:00Z

Content type: tutorial

Language: en

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

Topics: [Agentic SOC](<https://devfeed.tech/topics/agentic-soc.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [AWS Security Hub](<https://devfeed.tech/topics/aws-security-hub.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>), [VPC Flow Logs](<https://devfeed.tech/topics/vpc-flow-logs.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>)

Tags: [act](<https://devfeed.tech/tags/act.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-security-hub](<https://devfeed.tech/tags/aws-security-hub.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [but](<https://devfeed.tech/tags/but.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [consider](<https://devfeed.tech/tags/consider.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [context](<https://devfeed.tech/tags/context.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-vulnerability](<https://devfeed.tech/tags/critical-vulnerability.md>), [data](<https://devfeed.tech/tags/data.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [management-and-governance](<https://devfeed.tech/tags/management-and-governance.md>), [management-tools](<https://devfeed.tech/tags/management-tools.md>), [monitoring-and-observability](<https://devfeed.tech/tags/monitoring-and-observability.md>), [monitoring-observability](<https://devfeed.tech/tags/monitoring-observability.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The walkthrough shows how to keep security telemetry in Amazon CloudWatch while enabling finding-driven investigations through 7AI. CloudWatch telemetry rules collect AWS logs across accounts, and centralization rules copy new arrivals to a Security Tooling account; pipelines can normalize supported AWS sources to OCSF and ingest third-party data through S3 staging or direct APIs. 7AI polls GuardDuty and Security Hub for findings, then queries CloudWatch on demand using read-only access. In the example, deployment logs and threat findings indicated that a vulnerable container image was stale and likely benign as an incident, while confirming the vulnerability was real and needed routine patching. The setup requires AWS Organizations, delegated administration, IAM permissions, and a 7AI tenant. Costs include log ingestion and storage; first resource discovery can take up to 24 hours, polling adds trigger delay, centralization excludes existing logs, and CloudWatch does not retain original third-party records.

### Source excerpt

Security teams don't struggle to get alerts. They struggle to get the context needed to act on them. Consider a common scenario: an AWS Security Hub finding reports a critical vulnerability in a container image in Amazon Elastic Container Registry. The finding says that a package is vulnerable, but not whether the image is running, [...]

## Best practices for deploying Amazon CloudWatch Omni at enterprise scale

DevFeed: [Best practices for deploying Amazon CloudWatch Omni at enterprise scale](<https://devfeed.tech/articles/best-practices-for-deploying-amazon-cloudwatch-omni-at-enterprise-scale-137733.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/best-practices-for-deploying-amazon-cloudwatch-omni-at-enterprise-scale/>)

Author: Raviteja Sunkavalli

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

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>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [api](<https://devfeed.tech/tags/api.md>), [applications](<https://devfeed.tech/tags/applications.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cloudwatch-omni](<https://devfeed.tech/tags/cloudwatch-omni.md>), [data](<https://devfeed.tech/tags/data.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-scale](<https://devfeed.tech/tags/enterprise-scale.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [management-tools](<https://devfeed.tech/tags/management-tools.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring-and-observability](<https://devfeed.tech/tags/monitoring-and-observability.md>), [monitoring-observability](<https://devfeed.tech/tags/monitoring-observability.md>)

### AI overview

Amazon CloudWatch Omni provides organization-wide observability through one IAM Identity Center sign-in domain, but telemetry must be centralized into monitoring accounts before spaces can query it. The article's enterprise pattern creates one space per business unit and Region boundary, routes AWS telemetry with CloudWatch centralization rules, and sends non-AWS telemetry directly to the matching regional OTLP endpoint. Rules process only new telemetry and do not backfill; creating a space backfills up to seven days of logs and traces, except data encrypted with customer-managed KMS keys. Spaces cannot query across one another, so use access grants and row-level data scopes for team boundaries within a space. Scopes filter logs and traces, not metrics, and do not hide fields such as prompts. Sensitive content therefore needs layered controls: redact span attributes before export, mask log patterns at ingestion, and tightly scope access to retained prompts. The article also notes that storage for centralized logs and spans is charged in the destination account, while OpenTelemetry metrics have no additional storage charge.

### Source excerpt

At enterprise scale, organizations run applications and AI agents side by side across hundreds of AWS accounts, several Regions, and often other clouds and on-premises data centers. Site reliability engineering (SRE) teams watch service latency, agent developers observe agent traces and evaluation scores, operation teams monitor alerts, and security reviews AWS API activity. When a [...]

## AWS observability maturity assessment: from guesswork to a blueprint

DevFeed: [AWS observability maturity assessment: from guesswork to a blueprint](<https://devfeed.tech/articles/aws-observability-maturity-assessment-from-guesswork-to-a-blueprint-137732.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/aws-observability-maturity-assessment-from-guesswork-to-a-blueprint/>)

Author: Nilo Bustani

Published: 2026-11-16T15:40:28Z

Content type: article

Language: en

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

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-and-machine-learning](<https://devfeed.tech/tags/ai-and-machine-learning.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [alarm](<https://devfeed.tech/tags/alarm.md>), [alerting](<https://devfeed.tech/tags/alerting.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-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.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>), [assessment](<https://devfeed.tech/tags/assessment.md>), [aws](<https://devfeed.tech/tags/aws.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [blueprint](<https://devfeed.tech/tags/blueprint.md>), [management-governance](<https://devfeed.tech/tags/management-governance.md>), [management-tools](<https://devfeed.tech/tags/management-tools.md>), [maturity](<https://devfeed.tech/tags/maturity.md>), [monitoring-and-observability](<https://devfeed.tech/tags/monitoring-and-observability.md>), [observability](<https://devfeed.tech/tags/observability.md>), [prioritization](<https://devfeed.tech/tags/prioritization.md>)

### AI overview

The open-source AWS Observability Assessment scores an AWS environment across logs, metrics, traces, dashboards and alerting, and organizational practices, then provides evidence-backed recommendations to prioritize improvements. Its model has Reactive, Proactive, and Autonomous stages; 52 read-only discovery checks map to 17 questions and produce category and overall scores in an interactive HTML report. It runs in AWS CodeBuild, provisioned by CloudFormation, with deployment taking about five minutes and scanning about fifteen. It supports single-account runs and multi-account scans through assumed read-only roles. One exception to its read-only API calls is the EC2 CloudWatch agent check, which uses Systems Manager ssm:SendCommand. The report is a point-in-time snapshot; the article suggests repeating scans to track changes. The sample account scored 1.1/4 overall, with logs identified as its highest-leverage starting point.

### Source excerpt

Introduction Most teams know they should have good observability. Few can answer the two questions that matter: How good is our observability posture today, and what should we fix first? Without an objective way to measure, prioritization defaults to intuition, tribal knowledge, and the most recent escalation. The service that paged someone last night gets [...]

## Production MLOps at GS Caltex with Amazon SageMaker Canvas, part 1

DevFeed: [Production MLOps at GS Caltex with Amazon SageMaker Canvas, part 1](<https://devfeed.tech/articles/production-mlops-at-gs-caltex-with-amazon-sagemaker-canvas-part-1-133425.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/production-mlops-at-gs-caltex-with-amazon-sagemaker-canvas-part-1/>)

Author: WonGu Rho

Published: 2026-11-13T23:22:09Z

Content type: article

Language: en

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

Topics: [MLOps](<https://devfeed.tech/topics/mlops.md>), [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [about](<https://devfeed.tech/tags/about.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>), [amazon-sagemaker-canvas](<https://devfeed.tech/tags/amazon-sagemaker-canvas.md>), [batch](<https://devfeed.tech/tags/batch.md>), [canvas](<https://devfeed.tech/tags/canvas.md>), [code](<https://devfeed.tech/tags/code.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [inference](<https://devfeed.tech/tags/inference.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [ml](<https://devfeed.tech/tags/ml.md>), [mlops](<https://devfeed.tech/tags/mlops.md>), [models](<https://devfeed.tech/tags/models.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [post](<https://devfeed.tech/tags/post.md>), [process](<https://devfeed.tech/tags/process.md>), [production](<https://devfeed.tech/tags/production.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

GS Caltex connects process engineers' validated SageMaker Canvas models and Data Wrangler flows to SageMaker Pipelines, where ML engineers configure preprocessing, model approval, Batch Transform inference, and scheduling. The handoff reuses validated assets while ML engineers supply production paths, execution order, and deployment configuration. An EventBridge rule can start batch runs every 30 minutes; unlike a continuously running real-time endpoint, Batch Transform releases compute after each job, though full workflow costs and runtime still need measurement. The article highlights practical constraints: inference data may lack a training target column, so a placeholder-and-drop approach is suitable only if the target does not affect features; fixed flow input paths can cause overlapping runs to conflict; and assembled predictions require row-order and count checks. GS Caltex reports deployment time fell from about a week to a few hours, with lower inference costs.

### Source excerpt

GS Caltex connects Amazon SageMaker Canvas to Amazon SageMaker Pipelines so process engineers' no-code models run in production. This post shows how ML engineers reuse validated preprocessing flows and models, cutting deployment from about a week to a few hours and running batch inference every 30 minutes.

## Architecture patterns for fast session startup on Amazon Bedrock AgentCore runtime

DevFeed: [Architecture patterns for fast session startup on Amazon Bedrock AgentCore runtime](<https://devfeed.tech/articles/architecture-patterns-for-fast-session-startup-on-amazon-bedrock-agentcore-runtime-133423.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/architecture-patterns-for-fast-session-startup-on-amazon-bedrock-agentcore-runtime/>)

Author: Evandro Franco

Published: 2026-11-13T22:02:39Z

Content type: article

Language: en

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

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [app startup](<https://devfeed.tech/topics/app-startup.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentcore-runtime](<https://devfeed.tech/tags/agentcore-runtime.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>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [environment](<https://devfeed.tech/tags/environment.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [fast](<https://devfeed.tech/tags/fast.md>), [first](<https://devfeed.tech/tags/first.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [image](<https://devfeed.tech/tags/image.md>), [keep](<https://devfeed.tech/tags/keep.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [post](<https://devfeed.tech/tags/post.md>), [request](<https://devfeed.tech/tags/request.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [session](<https://devfeed.tech/tags/session.md>), [startup](<https://devfeed.tech/tags/startup.md>)

### AI overview

AgentCore runtime V2 builds an initialized environment once, snapshots its memory and disk, then restores it in a fresh microVM for each session. Memory-held objects return ready, while image files are fetched on first read; init work therefore moves to deploy time, though create or update takes a few minutes and larger snapshots can increase restore time and memory cost. The post recommends measuring `Latency` and `OverheadLatency`, moving static setup into init, keeping dynamic and per-session values in the handler, and using build hooks for files or tools init cannot prepare. For sub-second interactive starts, pre-warm a session when the user opens the app; this can hide startup delay but uses a session even if the user never sends a prompt.

### Source excerpt

Amazon Bedrock AgentCore runtime V2 snapshots your initialized environment and restores it for each new session, so session start no longer grows with image size. This post explains how V2 starts a session, how to measure session start time, and four patterns to keep work off the first request.

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

## Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes-133437.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:09Z

Content type: article

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>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [pool](<https://devfeed.tech/tags/pool.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.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>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

RDS Proxy multiplexing for PostgreSQL is reduced when sessions are pinned, client identities fragment the pool, or transactions remain open. CloudWatch indicators help distinguish them: elevated session-pinned connections suggest pinning; many backend connections with low borrowing and pinning can indicate fragmentation; sustained borrowing and open transactions point to transactions held too long. Fixes include upgrading the PostgreSQL JDBC driver to 42.7.x or newer, removing application SET statements, setting Spark JDBC writes to isolationLevel=NONE, and using InitQuery for shared session defaults. Standardize username, database, and ApplicationName among clients that should share a pool, while preserving separate users when privilege or audit needs require them. Commit promptly or enable autocommit where explicit transaction control is unnecessary. PostgreSQL targets do not support the proxy's SET pinning filter, and CloudWatch gauges can miss short-lived borrow cycles.

### Source excerpt

RDS Proxy multiplexes many client connections across a small pool of database connections, but connection pinning, pool fragmentation, and uncommitted transactions can silently disable that benefit for PostgreSQL workloads. Part 1 shows how to recognize each condition with Amazon CloudWatch metrics and the fix that restores multiplexing.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor-133438.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:04Z

Content type: tutorial

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 CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [insights](<https://devfeed.tech/tags/insights.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [regression](<https://devfeed.tech/tags/regression.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

CloudWatch metrics can show that RDS Proxy multiplexing has degraded, but enhanced proxy logs help explain why and which connections are involved. CloudWatch Logs Insights queries summarize backend connection borrows, releases, and pins, or trace one connection's lifecycle. For user and ApplicationName attribution, the post correlates proxy TCP events with PostgreSQL connection logs using IP:port; this is a best-effort match that depends on a narrow time window and synchronized timestamps. Healthy multiplexing shows many borrows and releases per backend connection, few pins, and substantially fewer backend than client connections. The post recommends alarms for sustained pinning and an elevated backend-to-client connection ratio, with workload-specific baselines and a traffic floor. Enhanced logging produces detailed SQL text, adds log volume, cost, and possible proxy overhead, so restrict log access, use it temporarily, and disable it after diagnosis.

### Source excerpt

Metrics alone can't always pinpoint what is reducing RDS Proxy multiplexing for PostgreSQL. Part 2 shows how to use Amazon CloudWatch Logs Insights with enhanced proxy logs to find the root cause, what healthy multiplexing looks like in metrics and logs, and how to set up CloudWatch alarms that catch regression.

## Monitoring global traffic with AWS Cloud WAN Flow Logs

DevFeed: [Monitoring global traffic with AWS Cloud WAN Flow Logs](<https://devfeed.tech/articles/monitoring-global-traffic-with-aws-cloud-wan-flow-logs-134113.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/monitoring-global-traffic-with-aws-cloud-wan-flow-logs/>)

Author: Thaddeus Worsnop

Published: 2026-11-13T21:02:02Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [VPC Flow Logs](<https://devfeed.tech/topics/vpc-flow-logs.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [NAT and SNAT](<https://devfeed.tech/topics/nat-and-snat.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-data-firehose](<https://devfeed.tech/tags/amazon-data-firehose.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-wan](<https://devfeed.tech/tags/aws-cloud-wan.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cross](<https://devfeed.tech/tags/cross.md>), [edge](<https://devfeed.tech/tags/edge.md>), [global-network](<https://devfeed.tech/tags/global-network.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logs](<https://devfeed.tech/tags/logs.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [query](<https://devfeed.tech/tags/query.md>), [region](<https://devfeed.tech/tags/region.md>), [s3](<https://devfeed.tech/tags/s3.md>), [scopes](<https://devfeed.tech/tags/scopes.md>)

### AI overview

AWS Cloud WAN Flow Logs provide a core-network view of traffic across VPC and hybrid attachments, including Region, segment, attachment, NAT, and packet-drop context. Logs can be created at core-network, edge, or attachment scope and delivered to CloudWatch Logs, S3, or Data Firehose; Athena and CloudWatch Logs Insights support analysis. Records capture traffic at each in-scope attachment, so a flow may appear more than once; filtering for ingress or a single attachment can avoid double counting. Setup requires the core-network owner account, IAM permissions, active traffic, and AWS CLI 2.40.1 or later. Initial core-network or edge log creation briefly locks the core network in UPDATING; first attachment logs briefly update that attachment. Logs use a fixed one-minute interval and are immutable. Drops inside an inspection VPC are not marked as Cloud WAN drops and require firewall or appliance-interface logs to investigate.

### Source excerpt

AWS Cloud WAN Flow Logs capture flow-level traffic across your global network. Learn how to create flow logs at the core network, edge, and attachment scopes, publish them to Amazon CloudWatch Logs, Amazon S3, or Amazon Data Firehose, and query them with Amazon Athena and CloudWatch Logs Insights to analyze cross-segment and cross-Region traffic and drops.

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

## Cost attribution and controls for AI developer and productivity tools on Amazon Bedrock

DevFeed: [Cost attribution and controls for AI developer and productivity tools on Amazon Bedrock](<https://devfeed.tech/articles/cost-attribution-and-controls-for-ai-developer-and-productivity-tools-on-amazon-bedrock-132651.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/cost-attribution-and-controls-for-ai-developer-and-productivity-tools-on-amazon-bedrock/>)

Author: Aamna Najmi

Published: 2026-11-13T18:44:02Z

Content type: tutorial

Language: en

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

Topics: [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-developer](<https://devfeed.tech/tags/ai-developer.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [controls](<https://devfeed.tech/tags/controls.md>), [cost](<https://devfeed.tech/tags/cost.md>), [developer](<https://devfeed.tech/tags/developer.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [iam](<https://devfeed.tech/tags/iam.md>), [iam-identity-center](<https://devfeed.tech/tags/iam-identity-center.md>), [identity](<https://devfeed.tech/tags/identity.md>), [inference](<https://devfeed.tech/tags/inference.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [limits](<https://devfeed.tech/tags/limits.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [productivity-tools](<https://devfeed.tech/tags/productivity-tools.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [usage-limits](<https://devfeed.tech/tags/usage-limits.md>)

### AI overview

Amazon Bedrock can attribute inference spend to each federated user without changes to tool API calls: IAM Identity Center sessions carry the caller identity and optional organizational tags into CUR 2.0, where costs are aggregated by principal and usage type per export interval. CUR does not provide per-request cost; invocation logs or request metadata tags are needed for prompt-level detail. The setup requires an external IdP, a Bedrock permission set scoped to the endpoint and approved resources, caller identity enabled in a CUR 2.0 export, and activated cost allocation tags. The article distinguishes `bedrock-runtime` permissions from `bedrock-mantle` permissions and notes that tool-specific authentication settings can affect attribution. For controls, AWS Budgets are simplest but may lag up to a day; CloudWatch and Lambda offer 1-5 minute enforcement with suitable user-level instrumentation; DynamoDB quotas take effect at credential refresh; gateways can block per invocation but add latency and operational complexity.

### Source excerpt

Amazon Bedrock provides built-in, zero-instrumentation cost attribution that traces every inference call back to the IAM principal that made it. This post shows how to attribute per-user Bedrock costs for AI developer and productivity tools using IAM Identity Center, session tags, and CUR 2.0, and how to enforce per-user usage limits.

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