#AmazonSqs
Amazon Kinesis Data Streams announces queues to simplify and reduce costs of real-time processing

https://aws.amazon.com/kinesis/data-streams/ now supports queues, a simpler and more cost-effective way to process a stream. Because queues track the delivery ...

#AWS #AmazonKinesisStreams #AmazonSqs
Amazon Kinesis Data Streams announces queues to simplify and reduce costs of real-time processing
https://aws.amazon.com/kinesis/data-streams/ now supports queues, a simpler and more cost-effective way to process a stream. Because queues track the delivery state of each record, your consumer instances receive records instead of leasing shards, acknowledge each record when processing is complete, and scale beyond the number of shards. Kinesis Data Streams consumers can reduce the cost of processing data by up to 43% by using queues instead of the Kinesis Client Library. You no longer run a DynamoDB table or custom metrics, and you use compute more efficiently. Queues in Kinesis Data Streams are powered by Amazon SQS. Built on that foundation, a queue delivers records at least once, redelivers records your consumers do not acknowledge, and provides built-in dead-letter handling for records that keep failing. Each queue publishes its own CloudWatch metrics, so you can scale consumer instances on records waiting to be received and alarm on records that repeatedly fail. Use queues for applications that process each record independently, such as log processing, order fulfillment, and notifications. Use a stream consumer when processing one record depends on the records before it, such as live analytics, personalization, and anomaly detection. You ingest data once and let each application consume records through a queue or directly from the stream, with no change to your producers or existing stream consumers. For point-to-point messaging between application components, start with Amazon SQS. Choose queues in Kinesis Data Streams when the same records are needed by multiple applications. Queues are available for data streams in On-demand capacity mode. For regional availability, see https://docs.aws.amazon.com/streams/latest/dev/consuming-with-queues.html#queues-supported-regions. To get started, see the https://docs.aws.amazon.com/streams/latest/dev/consuming-with-queues.html, install the https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/analytics-skills/managing-amazon-kinesis-data-streams from the Agent Toolkit for AWS, read the https://aws.amazon.com/blogs/big-data/reduce-the-complexity-and-cost-of-real-time-processing-with-queues-in-amazon-kinesis-data-streams/, and see the https://aws.amazon.com/kinesis/data-streams/pricing/.
aws.amazon.com
November 18, 2026 at 3:05 AM
🆕 Amazon Kinesis Data Streams adds queues to simplify real-time processing, cutting costs by up to 43% without DynamoDB or custom metrics. SQS-powered queues scale beyond shards and offer built-in dead-letter handling, ideal for independent record processing …

#AWS #AmazonKinesisStreams #AmazonSqs
Amazon Kinesis Data Streams announces queues to simplify and reduce costs of real-time processing
Amazon Kinesis Data Streams now supports queues, a simpler and more cost-effective way to process a stream. Because queues track the delivery state of each record, your consumer instances receive records instead of leasing shards, acknowledge each record when processing is complete, and scale beyond the number of shards. Kinesis Data Streams consumers can reduce the cost of processing data by up to 43% by using queues instead of the Kinesis Client Library. You no longer run a DynamoDB table or custom metrics, and you use compute more efficiently. Queues in Kinesis Data Streams are powered by Amazon SQS. Built on that foundation, a queue delivers records at least once, redelivers records your consumers do not acknowledge, and provides built-in dead-letter handling for records that keep failing. Each queue publishes its own CloudWatch metrics, so you can scale consumer instances on records waiting to be received and alarm on records that repeatedly fail. Use queues for applications that process each record independently, such as log processing, order fulfillment, and notifications. Use a stream consumer when processing one record depends on the records before it, such as live analytics, personalization, and anomaly detection. You ingest data once and let each application consume records through a queue or directly from the stream, with no change to your producers or existing stream consumers. For point-to-point messaging between application components, start with Amazon SQS. Choose queues in Kinesis Data Streams when the same records are needed by multiple applications. Queues are available for data streams in On-demand capacity mode. For regional availability, see Supported AWS Regions. To get started, see the developer guide, install the Kinesis Data Streams skill from the Agent Toolkit for AWS, read the launch blog, and see the pricing page.
aws.amazon.com
November 18, 2026 at 2:41 AM
🔎 THE QUEUE THAT SAVED THE FRONT DOOR

Traffic surged. The system bent instead of breaking.

NestedCerts.com #AmazonSQS #Decoupling #Scalability
November 10, 2026 at 12:02 AM
✅ DECOUPLE PRESSURE FROM PROGRESS

Use queues to absorb uneven work. Define visibility timeouts, retries, poison-message handling, and a dead-letter path as part of the original design.

NestedCerts.com #AmazonSQS #Decoupling #Scalability
November 10, 2026 at 8:02 AM
🧩 USE QUEUES TO ABSORB UNEVEN WORK

Define visibility timeouts, retries, poison-message handling, and a dead-letter path as part of the original design.

NestedCerts.com #AmazonSQS #Decoupling #Scalability
November 10, 2026 at 3:01 AM
ムゲイの体内にAmazonSQS導入して体内に入ってくる食べ物をストックさせて、Lambda関数にキューをキャッチさせて胃に転送されるようにしてぇ〜
October 27, 2026 at 11:41 PM
Colas de trabajo node.js: la guía para emails diferidos

Descubrí cómo implementar colas de trabajo node.js para programar envíos de email con retraso de forma simple y escalable. ¡Probalo en tu proyecto hoy!

#nodejs #bullmq #amazonsqs #cronjobs #vercel
Colas de trabajo node.js: la guía para emails diferidos
BullMQ, SQS, Temporal o REST: qué cola de trabajo node.js elegir para programar emails diferidos sin duplicados ni cron jobs rotos.
donweb.news
October 24, 2026 at 2:00 AM
✍️ New blog post by GargeeBhatnagar

Implemented Amazon SQS Queues for Reliable Message Sending and Receiving and Integrated Amazon SNS to Publish Notifications

#aws #amazonsqs #amazonsns #users
Implemented Amazon SQS Queues for Reliable Message Sending and Receiving and Integrated Amazon SNS to Publish Notifications
“ I have checked the documents of AWS for implemented amazon sqs queues for reliable message sending...
dev.to
September 27, 2026 at 10:14 AM
🚀 Just launched: CocoIndex now supports real-time incremental processing from #AmazonS3 with #AmazonSQS. If your AI agent needs fresh data in production systems, take a look (with end to end example).

📖 Dive in: cocoindex.io/blogs/s3-inc...
🌟Repo: github.com/cocoindex-io...

#OpenSource #Data
Real-time data transformation pipeline with Amazon S3 bucket, SQS and CocoIndex | CocoIndex
Build real-time data transformation pipeline with S3 and CocoIndex.
cocoindex.io
May 30, 2025 at 5:38 AM
#うひーメモ
2023-11-29 01:09:14
[アップデート]Amazon SQS が FIFO 高スループットモードのスループットのクォータが1秒あたり最大 70,000 トランザクションを処理できるようになりました
#技術系ブログ等
#アップデート
#amazonsqs
#fifo
[アップデート]Amazon SQS が FIFO 高スループットモードのスループットのクォータが1秒あたり最大 70,000 トランザクションを処理できるようになりました
はじめにこんにちはAWS事業本部コンサルティング部の和田響です皆さんreInvent盛り上がってますかこの記事ではAmazonSQSにおいてFIFOの高スループットのクォータプカについて記載します
dev.classmethod.jp
November 28, 2023 at 4:09 PM
#うひーメモ
2023-11-28 13:12:55
[アップデート] Amazon SQS DLQ のリドライブ送信先に FIFO タイプのキューが指定できるようになりました!
#技術系ブログ等
#アップデート
#amazonsqs
#amazonsqsdlq
[アップデート] Amazon SQS DLQ のリドライブ送信先に FIFO タイプのキューが指定できるようになりました!
こんにちはCX事業本部のヒョンジェですよりAmazonSQSのDLQDeadLetterQueueのリドライブ送信先をFIFOFirstInFirstOut
dev.classmethod.jp
November 28, 2023 at 4:12 AM
#うひーメモ
2023-11-20 12:02:52
Amazon SQS の新機能 – AWS SDK を更新してレイテンシーを削減
#AWS
#amazonsqs
#awssdk
#ソフトウェアコンポーネント
Amazon SQS の新機能 – AWS SDK を更新してレイテンシーを削減
AmazonSQSではソフトウェアコンポーネント間でメッセージの送受信をあらゆる規模で実行することができ
aws.amazon.com
November 20, 2023 at 3:02 AM
#うひーメモ
2023-11-19 15:02:00
【学習メモ】SQS拡張クライアントライブラリとは
#Program
#amazo
#amazonsqs
#クライアント
【学習メモ】SQS拡張クライアントライブラリとは
SQS拡張クライアントライブラリとは・通常のSQSキューのデータサーズ制限はKBだが運用上それを超えたい場合の対応法である・大量のAmazonSQSメッセージを管理するにはAmazo
qiita.com
November 19, 2023 at 6:02 AM
#うひーメモ
2023-11-17 16:10:09
Amazon SQSのデータイベントがCloudTrailで記録可能になりました
#技術系ブログ等
#amazonsqs
#amazon
#amazonsqsan
Amazon SQSのデータイベントがCloudTrailで記録可能になりました
年月日付けのアップデートでAWSCloudTrailがAmazonSQSSimpleQueueServiceのデータイベントのログ記録をサポートしましたAmazonSQSan
dev.classmethod.jp
November 17, 2023 at 7:10 AM
#うひーメモ
2023-11-10 18:02:52
Amazon SQS をイベントソースとした AWS Lambda 関数のより高速なポーリングスケールアップの紹介
#AWS
#amazonsqs
#antonaleksandrov
#awslambda
Amazon SQS をイベントソースとした AWS Lambda 関数のより高速なポーリングスケールアップの紹介
この投稿はプリンシパルソリューションアーキテクトのAntonAleksandrovとシニアプロダクトマ
aws.amazon.com
November 10, 2023 at 9:02 AM
#うひーメモ
2023-10-25 23:06:15
EC2からAmazon SQSにメッセージを送り、RDSのDBに保存する方法
#Program
#amazonsqs
#そのため
#メッセージ
EC2からAmazon SQSにメッセージを送り、RDSのDBに保存する方法
内容ECからAmazonSQSを経由してRDSにデータを保存する方法をまとめますRDSのダウンタイム中にRDSに保存処理をしようとするとエラーになりそのデータが失われますそのためダ
qiita.com
October 25, 2023 at 2:06 PM
Feed: "Java Code Geeks"
By: Yatin Batra on Friday, November 14, 2025
Mocking AmazonSQS in Unit Tests
Java mock amazonsqs unit tests: Learn how to mock AmazonSQS in Java unit tests for effective and isolated testing.
www.javacodegeeks.com
November 15, 2025 at 5:33 AM
🚀 Data Volumes Are Growing—Now Amazon #SQS Message Sizes Are, Too! 🚀

Amazon SQS now supports individual message payloads up to 1MiB. This is a fourfold increase from the previous 256KiB limit.

#AWS #AmazonSQS #Data #Messaging #EventDriven #Serverless
Amazon SQS increases maximum message payload size to 1 MiB - AWS
Discover more about what's new at AWS with Amazon SQS increases maximum message payload size to 1 MiB
aws.amazon.com
August 5, 2025 at 4:43 PM
Amazon SQS expands IPv6 support to the AWS GovCloud (US) Regions

https://aws.amazon.com/pm/sqs/now allows customers to make API requests over Internet Protocol version 6 (IPv6) in the AWS GovCloud (US) Regions. The new endpoints have also been validated under the Federal Infor...

#AWS #AmazonSqs
Amazon SQS expands IPv6 support to the AWS GovCloud (US) Regions
https://aws.amazon.com/pm/sqs/now allows customers to make API requests over Internet Protocol version 6 (IPv6) in the AWS GovCloud (US) Regions. The new endpoints have also been validated under the Federal Information Processing Standard (FIPS) 140-3 program. Amazon SQS is a fully managed message queuing service that enables decoupling and scaling of distributed systems, microservices, and serverless applications. With this update, customers have the option of using either IPv6 or IPv4 when sending requests over dual-stack public or VPC endpoints. Amazon SQS now supports IPv6 in all Regions where the service is available, including AWS Commercial, AWS GovCloud (US) and China Regions. For more information on using IPv6 with Amazon SQS, please refer to our https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dual-stack.html. 
aws.amazon.com
November 14, 2025 at 10:05 PM
Amazon EventBridge now supports targeting SQS fair queues

Amazon EventBridge now supports Amazon SQS fair queues as targets, enabling you to build more responsive event-driven applications. You can now leverage SQSs improved message distribution across consumer groups and miti...

#AWS #AmazonSqs
Amazon EventBridge now supports targeting SQS fair queues
Amazon EventBridge now supports Amazon SQS fair queues as targets, enabling you to build more responsive event-driven applications. You can now leverage SQSs improved message distribution across consumer groups and mitigate the noisy neighbor impact in multi-tenant messaging systems. This enhancement allows EventBridge to send events directly to SQS fair queues. With fair queues, multiple consumers can process messages from the same tenant at the same time, while keeping message processing times consistent across all tenants. The Amazon EventBridge event bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. SQS fair queues automatically distribute messages fairly across consumer groups, preventing any single group from monopolizing queue resources. When combined with EventBridge's event routing capabilities, this creates powerful patterns for building scalable, multi-tenant applications where different teams or services need equitable access to event streams. To route events to an SQS fair queue, you can select the fair queue as a target when creating or updating EventBridge rules through the AWS Management Console, AWS CLI, or AWS SDKs. Be sure to include a MessageGroupID parameter, which can be specified with either a static value or JSON path expression. Support for Fair Queue and FIFO targets is available in all AWS commercial and AWS GovCloud (US) Regions. For more information about EventBridge target support, see our https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-targets.html. For more information about SQS Fair Queues, see the SQS https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-fair-queues.html. 
aws.amazon.com
November 13, 2025 at 8:05 PM
Amazon SQS now supports FIPS 140-3 enabled interface VPC endpoint

Amazon SQS now supports VPCE endpoints that have been validated under the Federal Information Processing Standard (FIPS) 140-3 program. You can now easily use AWS PrivateLink with Amazon SQS for regulated worklo...

#AWS #AmazonSqs
Amazon SQS now supports FIPS 140-3 enabled interface VPC endpoint
Amazon SQS now supports VPCE endpoints that have been validated under the Federal Information Processing Standard (FIPS) 140-3 program. You can now easily use AWS PrivateLink with Amazon SQS for regulated workloads that require a secure connection using a FIPS 140-3 validated cryptographic module. FIPS compliant endpoints help companies contracting with the US federal government meet the FIPS security requirement to encrypt sensitive data in supported regions. To create an interface VPC endpoint that connects to an Amazon SQS FIPS endpoint, see https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-internetwork-traffic-privacy.html. The new capability is available in all AWS Commercial Regions in the United States and Canada. To learn more about FIPS 140-3 at AWS, visit https://aws.amazon.com/compliance/fips/.  
aws.amazon.com
May 8, 2025 at 7:05 PM
Amazon SQS now supports Internet Protocol Version 6 (IPv6)

Amazon SQS now supports Internet Protocol version 6 (IPv6) for API requests enabling you to communicate with Amazon SQS using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack client...

#AWS #AmazonSqs
Amazon SQS now supports Internet Protocol Version 6 (IPv6)
Amazon SQS now supports Internet Protocol version 6 (IPv6) for API requests enabling you to communicate with Amazon SQS using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients using public endpoints. Amazon SQS is a fully managed message queuing service that enables decoupling and scaling of distributed systems, microservices, and serverless applications. The addition of IPv6 support provides customers with a vastly expanded address space, eliminating concerns about address exhaustion and simplifying network architecture for IPv6-native applications. With simultaneous support for both IPv4 and IPv6 clients on SQS public endpoints, customers can gradually transition from IPv4 to IPv6-based systems and applications without needing to switch all systems at once. This enhancement is particularly valuable for modern cloud-native applications and organizations transitioning to IPv6 as part of their modernization efforts. To learn more on best practices for configuring IPv6 in your environment, visit the whitepaper on https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html in AWS. This feature is now available in all AWS commercial Regions, including AWS China Regions, and can be used at no additional cost. See https://docs.aws.amazon.com/general/latest/gr/sqs-service.html for a full listing of our Regions. To learn more about Amazon SQS, please refer to our https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html.  
aws.amazon.com
April 21, 2025 at 7:05 PM
Amazon EventBridge expands IAM execution role support to all targets

Amazon EventBridge expands execution role support to AWS Lambda, Amazon SNS, and Amazon SQS event bus targets, making this feature available for all tar...

#AWS #AmazonEventbridge #AwsGovcloudUs #AmazonSqs #AmazonSns #AwsLambda
Amazon EventBridge expands IAM execution role support to all targets
Amazon EventBridge expands execution role support to AWS Lambda, Amazon SNS, and Amazon SQS event bus targets, making this feature available for all target types. We recommend configuring execution roles for all your EventBridge targets to benefit from consistent permissions policies and dedicated invocation throttle limits. Amazon EventBridge Event Bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. An execution role is an AWS Identity and Access Management (IAM) role that EventBridge assumes when invoking a target, giving you fine-grained control over which AWS services and resources EventBridge can access. The expansion to Lambda, SNS, and SQS targets allows consistent permissions across all EventBridge targets, enables setting permissions for multiple targets within a single IAM policy, and can help manage throughput by using your account-specific limits. This feature is available in all AWS Regions, including AWS GovCloud (US). To learn more, please visit our https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-use-identity-based.html#eb-target-permissions or get started in the https://console.aws.amazon.com/events/.
aws.amazon.com
March 11, 2025 at 6:05 PM
Amazon EventBridge announces direct delivery to cross-account targets

Amazon EventBridge Event Bus now allows you to deliver events directly to AWS services in another account. This feature enables you to use multiple accounts to improve security and streaml...

#AWS #AmazonEventbridge #AmazonSqs
Amazon EventBridge announces direct delivery to cross-account targets
Amazon EventBridge Event Bus now allows you to deliver events directly to AWS services in another account. This feature enables you to use multiple accounts to improve security and streamline business processes while reducing the overall cost and complexity of your architecture. Amazon EventBridge Event Bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. This launch allows you to directly target services in another account, without the need for additional infrastructure such as an intermediary EventBridge Event Bus or Lambda function, simplifying your architecture and reducing cost. For example, you can now route events from your EventBridge Event Bus directly to a different team's SQS queue in a different account. The team receiving events does not need to learn about or maintain EventBridge resources and simply needs to grant IAM permissions to provide access to the queue. Events can be delivered cross-account to EventBridge targets that support resource-based IAM policies such as Amazon SQS, AWS Lambda, Amazon Kinesis Data Streams, Amazon SNS, and Amazon API Gateway. Direct delivery to cross-account targets is now available in all commercial AWS Regions. To learn more, please read our https://aws.amazon.com/blogs/compute/introducing-cross-account-targets-for-amazon-eventbridge-event-buses/ or visit our https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-service-cross-account.html. Pricing information is available on the EventBridge https://aws.amazon.com/eventbridge/pricing/.
aws.amazon.com
January 21, 2025 at 9:05 PM