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. 

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 Amazon Simple Queue Service (Amazon 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 developer guide.

🆕 Amazon SQS now supports IPv6 in AWS GovCloud (US) Regions, offering dual-stack public or VPC endpoint options. New endpoints validated under FIPS 140-3. Available in all regions where SQS operates. For details, see the developer guide.

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

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 documentation. For more information about SQS Fair Queues, see the SQS documentation.

🆕 Amazon EventBridge now supports SQS fair queues, enabling scalable, multi-tenant event-driven apps with fair message distribution and consistent processing times. Use AWS Management Console, CLI, or SDKs to route events. Available in all commercial and GovCloud (US) regions.

#AWS #AmazonSqs

AWS Enhancements Check out the latest enhancements to NServiceBus support for AWS. All of these updates aim to give you more control, fewer surprises, and a smoother experience when building distributed message-based…

New in NServiceBus! Got an #AmazonSQS native integration scenario? Maybe payloads coming from other SQS service via SNS? We now promote SQS message attributes to full NServiceBus headers so you can more easily do things with them.

AWS Enhancements Check out the latest enhancements to NServiceBus support for AWS. All of these updates aim to give you more control, fewer surprises, and a smoother experience when building distributed message-based…

New in NServiceBus! Now you can use #CloudflareR2 to store large message bodies in #AmazonSQS systems, which may be more cost effective for your system.

AWS Enhancements Check out the latest enhancements to NServiceBus support for AWS. All of these updates aim to give you more control, fewer surprises, and a smoother experience when building distributed message-based…

New in NServiceBus! You can reserve space in #AmazonSQS messages for headers (think @OpenTelemetry, @datadoghq, etc.) before the message becomes "large" and needs to be stored in #AmazonS3. Now it's even easier to add telemetry!

AWS Enhancements Check out the latest enhancements to NServiceBus support for AWS. All of these updates aim to give you more control, fewer surprises, and a smoother experience when building distributed message-based…

New in NServiceBus! We now automatically prevent duplicate message processing in #AmazonSQS by extending message visibility timeouts as needed, eliminating a common source of race conditions and data corruption.

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

🚀 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

Real-time data transformation pipeline with Amazon S3 bucket, SQS and CocoIndex | CocoIndex Build real-time data transformation pipeline with S3 and CocoIndex.

🚀 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

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

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 Internetwork traffic privacy in Amazon SQS. 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 FIPS 140-3 Compliance.

🆕 Amazon SQS now supports FIPS 140-3 compliant VPC endpoints for secure, regulated workloads. Easily use AWS PrivateLink in all US and Canada regions to encrypt sensitive data for federal government contracts. For details, see Amazon SQS documentation.

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

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 IPv6 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 here for a full listing of our Regions. To learn more about Amazon SQS, please refer to our Developer Guide.

🆕 Amazon SQS now supports IPv6, allowing dual-stack clients to use IPv6 or IPv4 for API requests. This aids IPv6 transition and offers a vast address space, enhancing cloud-native applications. Available in all AWS regions at no extra cost.

#AWS #AmazonSqs

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

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 documentation or get started in the AWS Management Console.

🆕 Amazon EventBridge now supports IAM roles for all targets like Lambda, SNS, and SQS, ensuring consistent permissions and dedicated throttle limits, enhancing control and management. Available globally.

#AWS #AmazonEventBridge #AwsGovcloudUs #AmazonSqs #AmazonSns #AwsLambda

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

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 blog post or visit our documentation. Pricing information is available on the EventBridge pricing page.

🆕 Amazon EventBridge announces direct delivery to cross-account targets

#AWS #AmazonEventBridge #AmazonSqs

Amazon Managed Service for Apache Flink now delivers to Amazon SQS queues Today, AWS announced support for a new Apache Flink connector for https://aws.amazon.com/sqs/. The new connector, contributed by AWS for the Apache Flink open source project, adds Amazon Simple Queue Service as a new destination for Apache Flink. You can use the new connector to send processed data from Amazon Managed Service for Apache Flink to Amazon Simple Queue Service messages with Apache Flink, a popular framework and engine for processing and analyzing streaming data. Amazon Managed Service for Apache Flink makes it easier to transform and analyze streaming data in real time with Apache Flink. Apache Flink is an open source framework and engine for processing data streams. Amazon Managed Service for Apache Flink reduces the complexity of building and managing Apache Flink applications and integrates with Amazon Managed Streaming for Apache Kafka (Amazon MSK), Amazon Kinesis Data Streams, Amazon OpenSearch Service, Amazon DynamoDB streams, Amazon S3, custom integrations, and more using built-in connectors. Amazon Simple Queue Service offers a secure, durable, and available hosted queue that lets you integrate and decouple distributed software systems and components. Amazon SQS offers common constructs such as deal-letter queues and cosrt allocation tags. You can learn more about https://docs.aws.amazon.com/managed-flink/latest/java/flink-1-20.html and https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/welcome.html in our documentation. To learn more about open source Apache Flink connectors visit the https://nightlies.apache.org/flink/flink-docs-stable/docs/connectors/datastream/sqs/. For Amazon Managed Service for Apache Flink and Amazon Simple Queue Service region availability, refer to the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/.

Amazon Managed Service for Apache Flink now delivers to Amazon SQS queues

Today, AWS announced support for a new Apache Flink connector for https://aws.amazon.com/sqs/ The new connector, contributed by AWS for the Apache Flin...

#AWS #AmazonSqs #AwsGovcloudUs #AmazonManagedServiceForApacheFlink

Amazon Managed Service for Apache Flink now delivers to Amazon SQS queues Today, AWS announced support for a new Apache Flink connector for Amazon Simple Queue Service. The new connector, contributed by AWS for the Apache Flink open source project, adds Amazon Simple Queue Service as a new destination for Apache Flink. You can use the new connector to send processed data from Amazon Managed Service for Apache Flink to Amazon Simple Queue Service messages with Apache Flink, a popular framework and engine for processing and analyzing streaming data. Amazon Managed Service for Apache Flink makes it easier to transform and analyze streaming data in real time with Apache Flink. Apache Flink is an open source framework and engine for processing data streams. Amazon Managed Service for Apache Flink reduces the complexity of building and managing Apache Flink applications and integrates with Amazon Managed Streaming for Apache Kafka (Amazon MSK), Amazon Kinesis Data Streams, Amazon OpenSearch Service, Amazon DynamoDB streams, Amazon S3, custom integrations, and more using built-in connectors. Amazon Simple Queue Service offers a secure, durable, and available hosted queue that lets you integrate and decouple distributed software systems and components. Amazon SQS offers common constructs such as deal-letter queues and cosrt allocation tags. You can learn more about Amazon Managed Service for Apache Flink and Amazon Simple Queue Service in our documentation. To learn more about open source Apache Flink connectors visit the official website. For Amazon Managed Service for Apache Flink and Amazon Simple Queue Service region availability, refer to the AWS Region Table.

🆕 Amazon Managed Service for Apache Flink now delivers to Amazon SQS queues

#AWS #AmazonSqs #AwsGovcloudUs #AmazonManagedServiceForApacheFlink

Amazon SQS increases in-flight limit for FIFO queues from 20K to 120K Amazon SQS increases the in-flight limit for FIFO queues from 20K to 120K messages. When a message is sent to an SQS FIFO queue, it is added to the queue backlog. Once you invoke a receive request on the FIFO queue, the message is now marked as in-flight and remains in-flight until a delete message request is invoked. With this change to the in-flight limit, your receivers can now process a maximum of 120K messages concurrently, increased from 20K previously, via SQS FIFO queues. If you have sufficient publish throughput and were constrained by the 20K in-flight limit, you can now process up to 120K messages at a time by scaling your receivers. The increased in-flight limits is available in all commercial and the AWS GovCloud (US) Regions where SQS FIFO queues are available. To get started, see the following resources: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/high-throughput-fifo.html, in the Amazon SQS Developer Guide https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/quotas-fifo.html, in the Amazon SQS Developer Guide

Amazon SQS increases in-flight limit for FIFO queues from 20K to 120K

Amazon SQS increases the in-flight limit for FIFO queues from 20K to 120K messages. When a message is sent to an SQS FIFO queue, it is added to the queue backlog. Once you invoke a receive req...

#AWS #AmazonSqs #AwsGovcloudUs

Amazon SQS increases in-flight limit for FIFO queues from 20K to 120K Amazon SQS increases the in-flight limit for FIFO queues from 20K to 120K messages. When a message is sent to an SQS FIFO queue, it is added to the queue backlog. Once you invoke a receive request on the FIFO queue, the message is now marked as in-flight and remains in-flight until a delete message request is invoked. With this change to the in-flight limit, your receivers can now process a maximum of 120K messages concurrently, increased from 20K previously, via SQS FIFO queues. If you have sufficient publish throughput and were constrained by the 20K in-flight limit, you can now process up to 120K messages at a time by scaling your receivers. The increased in-flight limits is available in all commercial and the AWS GovCloud (US) Regions where SQS FIFO queues are available. To get started, see the following resources: High-Throughput SQS FIFO queues, in the Amazon SQS Developer Guide SQS FIFO queue quotas, in the Amazon SQS Developer Guide

🆕 Amazon SQS increases in-flight limit for FIFO queues from 20K to 120K

#AWS #AmazonSqs #AwsGovcloudUs