“ I have checked the documents of AWS for implemented amazon sqs queues for reliable message sending...

Amazon Simple Notification Services (Amazon SNS) now delivers to Amazon Data Firehose endpoints in Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich), Europe (Spain), Middle East (UAE). You can now use Amazon SNS to deliver notifications to Amazon Data Firehose (Firehose) endpoints for archiving and analysis. Through Firehose delivery streams, you can deliver events to AWS destinations such as Amazon Simple Storage Service (Amazon S3), Amazon Redshift, and Amazon OpenSearch Service, or to third-party destinations such as Datadog, New Relic, MongoDB, and Splunk. For more information, see Fanout to Firehose delivery streams. To get started, see the following resources: Create Firehose Stream in the Amazon Data Firehose Developer Guide. Subscribe a Firehose delivery stream to an Amazon SNS topic in the Amazon SNS Developer Guide. SNS pricing for deliveries to Amazon Data Firehose in the Amazon SNS Pricing Page. Blog post on how to use Amazon Data Firehose for archive and replay into an existing Serverless architecture.

Amazon SNS now supports Internet Protocol version 6 (IPv6) for API requests enabling you to communicate with Amazon SNS using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients using public endpoints. Amazon SNS is a fully managed messaging service that enables publish/subscribe messaging between distributed systems, microservices, and event-driven 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 SNS 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/sns.html for a full listing of our Regions. To learn more about Amazon SNS, please refer to our https://docs.aws.amazon.com/sns/latest/dg/welcome.html.  

Amazon SNS now supports in-place message archiving and replay for SNS FIFO topics in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. Topic owners can now set an archive policy, which defines a retention period for the messages published to their topic. Subscribers can then set a replay policy to an individual subscription, which triggers a replay of select messages from the archive, from a starting point until an ending point. Subscribers can also set a filter policy on their subscription to further select the messages in-scope for a replay. To get started, see the following resources: Message archiving and replay, in the Amazon SNS Developer Guide Archiving and replaying messages with Amazon SNS FIFO, in the AWS Compute Blog

Amazon Simple Notification Service (Amazon SNS) now supports message payloads up to 1 MiB, a 4x increase from the previous 256 KiB limit, so you can publish larger messages to your SNS topics. Amazon SNS is a fully managed pub/sub messaging service that enables you to decouple and scale microservices, distributed systems, and serverless applications. As workloads such as application integration, IoT, and generative AI increasingly exchange larger volumes of data in a single message, the previous 256 KiB limit required customers to offload or split payloads before publishing. With this launch, you can publish message payloads up to 1 MiB by setting the new MaximumMessageSize topic attribute on both SNS Standard and SNS FIFO topics. Topics with MaximumMessageSize set above 256 KiB support Amazon SQS, Amazon Data Firehose, and AWS Lambda subscriptions, with up to 100 total subscriptions per topic. Amazon SNS 1 MiB support is available today in all AWS Regions where Amazon SNS is available. To learn more about sending large payloads with Amazon SNS, see the Amazon SNS Developer Guide.

https://aws.amazon.com/sns/ now supports message payloads up to 1 MiB, a 4x increase from the previous 256 KiB limit, so you can publish larger messages to your SNS topics. Amazon SNS is a fully managed pub/sub messaging service that enables you to decouple and scale microservices, distributed systems, and serverless applications. As workloads such as application integration, IoT, and generative AI increasingly exchange larger volumes of data in a single message, the previous 256 KiB limit required customers to offload or split payloads before publishing. With this launch, you can publish message payloads up to 1 MiB by setting the new MaximumMessageSize topic attribute on both SNS Standard and SNS FIFO topics. Topics with MaximumMessageSize set above 256 KiB support Amazon SQS, Amazon Data Firehose, and AWS Lambda subscriptions, with up to 100 total subscriptions per topic. Amazon SNS 1 MiB support is available today in all AWS Regions where Amazon SNS is available. To learn more about sending large payloads with Amazon SNS, see the https://docs.aws.amazon.com/sns/latest/dg/large-message-payloads.html.   

こんにちは。 ソーイ株式会社、Webエンジニア2年目の村上です。 AWS上のアプリケーションから基盤モデルを利用する場合、簡単に生成AIモデルを呼び出せるAmazon Bedrockを使う機会も多いと思います。 使いやすくて便利なのはそうなのですが、Bedrockは従量課金...

いわさです先日AmazonSNSがアップデートされメッセージのアーカイブとリプレイという新しい機能が使えるようになりました上記アップデートアナウンスでは障害シナリオからの回復などがユースケースとして挙げ

AmazonSNSってSNSとほぼ関係ないじゃん。紛らわしい名前つけんな。

https://aws.amazon.com/sns/ now supports sending push notifications in the AWS Europe (Spain) Region.  Amazon SNS is a fully managed pub/sub service that provides message delivery to multiple endpoints, including AWS Lambda, Amazon SQS, Amazon Data Firehose, HTTP, SMS (via AWS End User Messaging), push notifications, and email. With this launch, customers in the Europe (Spain) Region can use Amazon SNS to send push notifications to the following supported push notification services: Amazon Device Messaging (ADM), Apple Push Notification Service (APNs), Baidu Cloud Push (Baidu), Firebase Cloud Messaging (FCM), Microsoft Push Notification Service for Windows Phone (MPNS), and Windows Push Notification Services (WNS).  With this expansion, Amazon SNS now supports sending push notifications from 25 regions. For the full list of regions from which you can send push notifications, see https://docs.aws.amazon.com/sns/latest/dg/sns-mobile-push-supported-regions.html in the Amazon SNS Developer Guide. For more information, see the https://docs.aws.amazon.com/sns/latest/dg/sns-mobile-application-as-subscriber.html.

Customers that use https://aws.amazon.com/sns/ in the Asia Pacific (New Zealand) and Asia Pacific (Taipei) Regions can now send text messages (SMS) to subscribers in more than 200 countries and territories. Amazon SNS is a fully managed pub/sub messaging service that enables message delivery to multiple endpoints including AWS Lambda, Amazon SQS, Amazon Data Firehose, mobile devices, and email. With this launch, customers using SNS in these Regions can send SMS messages via AWS End User Messaging. Amazon SNS now supports the ability to send SMS in 32 AWS Regions. More information: To learn more about sending SMS messages with SNS, visit https://docs.aws.amazon.com/sns/latest/dg/sns-mobile-phone-number-as-subscriber.html. For the list of supported countries and regions, visit https://docs.aws.amazon.com/sms-voice/latest/userguide/phone-numbers-sms-by-country.html.

https://aws.amazon.com/sns/ now supports notification delivery to Amazon Data Firehose endpoints in three additional AWS Regions, Asia Pacific (Taipei), Asia Pacific (Thailand) and Mexico (Central) Regions. You can now use Amazon SNS to deliver notifications to Amazon Data Firehose (Firehose) endpoints for storage and analysis. Through Firehose delivery streams, customers can deliver events to AWS destinations such as Amazon Simple Storage Service (Amazon S3), Amazon Redshift, and Amazon OpenSearch Service, or to third-party destinations such as Datadog, New Relic, MongoDB, and Splunk. To get started, see the following resources: https://docs.aws.amazon.com/sns/latest/dg/sns-firehose-as-subscriber.html in the Amazon SNS Developer Guide. https://docs.aws.amazon.com/firehose/latest/dev/basic-create.html in the Amazon Data Firehose Developer Guide. https://aws.amazon.com/sns/pricing/#Standard_topics in the Amazon SNS Pricing Page.

Today, https://aws.amazon.com/end-user-messaging/ launched self-service short code, and long code registration for 18 additional countries, helping developers to onboard to dedicated numbers which enables them to correctly configure SMS messaging for their applications. The new countries supported for long codes include Australia, Austria, Chile, Denmark, Finland, Hong Kong, Italy, Netherlands, Norway, Poland, Spain, Sweden, United Kingdom, Hungary, and Portugal. The new countries supported for short codes include Chile, Finland, Germany, India, Netherlands, Spain, United Kingdom, and United States. Phone numbers and sender IDs act as an extension of a business's brand, and mobile carriers and governments worldwide have implemented SMS registrations as a form of "know your customer" check to protect end-users from unwanted and spam messages. By registering, application developers ensure a higher level of deliverability and ensure their use-cases comply with local rules and regulations, avoiding message filtering. Previously, customers needed to open a support case to request these short code and long code forms, but now they can self-service via the AWS Management Console or programmatically via the APIs, saving time-to-onboard. The registration support is available in all commercial regions where AWS End User Messaging is generally available.  

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 SNS now supports high-throughput mode for SNS FIFO topics, with default throughput matching SNS standard topics across all regions. When you enable high-throughput mode, SNS FIFO topics will maintain order within message group, while reducing the de-duplication scope to the message-group level. With this change, you can leverage up to 30K messages per second (MPS) per account by default in US East (N. Virginia) Region, and 9K MPS per account in US West (Oregon) Region and Europe (Ireland) Region, and request quota increases for additional throughput in any region. Amazon SNS FIFO topics provides message ordering, message grouping, and de-duplication when delivering to Amazon SQS queues. By default, SNS FIFO topics provide 300 MPS per message group ID, and 3K MPS per topic, and topic level de-duplication. To get higher throughput, you can distribute your messages across message groups, and enable high-throughput mode by setting the FifoThroughputScope topic attribute to MessageGroup. We now have increased default limits for SNS FIFO topics across all commercial and the AWS GovCloud (US) Regions. To get started, see the following resources: https://docs.aws.amazon.com/sns/latest/dg/fifo-high-throughput.html, in the Amazon SNS Developer Guide https://docs.aws.amazon.com/general/latest/gr/sns.html, in the AWS General Reference.

Today, AWS End User Messaging launched self-service Sender ID registrations for 19 additional countries, helping developers correctly configure SMS messaging for their applications. The new countries include Australia, Belarus, Egypt, India, Indonesia, Jordan, Kenya, Kuwait, Kazakhstan, Philippines, Qatar, Russia, Saudi Arabia, Singapore, Sri Lanka, Thailand, Turkey, United Arab Emirates, Vietnam, and Zambia. Phone numbers and sender IDs act as an extension of a business's brand, and mobile carriers and governments worldwide have implemented SMS registrations as a form of "know your customer" check to protect end-users from unwanted and spam messages. By registering, application developers ensure a higher level of deliverability and ensure their use-cases comply with local rules and regulations, avoiding message filtering. Previously, customers needed to open a support case to request these sender IDs, but now they can self-service via the AWS Management Console or programmatically via the APIs, saving time-to-onboard. The registration support is available in all commercial regions where AWS End User Messaging is generally available.  

Amazon Simple Notification Service (Amazon SNS) now supports sending push notifications in the AWS Europe (Spain) Region.  Amazon SNS is a fully managed pub/sub service that provides message delivery to multiple endpoints, including AWS Lambda, Amazon SQS, Amazon Data Firehose, HTTP, SMS (via AWS End User Messaging), push notifications, and email. With this launch, customers in the Europe (Spain) Region can use Amazon SNS to send push notifications to the following supported push notification services: Amazon Device Messaging (ADM), Apple Push Notification Service (APNs), Baidu Cloud Push (Baidu), Firebase Cloud Messaging (FCM), Microsoft Push Notification Service for Windows Phone (MPNS), and Windows Push Notification Services (WNS).  With this expansion, Amazon SNS now supports sending push notifications from 25 regions. For the full list of regions from which you can send push notifications, see Supported Regions and Countries in the Amazon SNS Developer Guide. For more information, see the Amazon SNS push notifications documentation.

Customers that use Amazon Simple Notification Service (Amazon SNS) in the Asia Pacific (New Zealand) and Asia Pacific (Taipei) Regions can now send text messages (SMS) to subscribers in more than 200 countries and territories. Amazon SNS is a fully managed pub/sub messaging service that enables message delivery to multiple endpoints including AWS Lambda, Amazon SQS, Amazon Data Firehose, mobile devices, and email. With this launch, customers using SNS in these Regions can send SMS messages via AWS End User Messaging. Amazon SNS now supports the ability to send SMS in 32 AWS Regions. More information: To learn more about sending SMS messages with SNS, visit Mobile text messaging with Amazon SNS. For the list of supported countries and regions, visit Supported countries and regions.

Amazon Simple Notification Services (Amazon SNS) now supports notification delivery to Amazon Data Firehose endpoints in three additional AWS Regions, Asia Pacific (Taipei), Asia Pacific (Thailand) and Mexico (Central) Regions. You can now use Amazon SNS to deliver notifications to Amazon Data Firehose (Firehose) endpoints for storage and analysis. Through Firehose delivery streams, customers can deliver events to AWS destinations such as Amazon Simple Storage Service (Amazon S3), Amazon Redshift, and Amazon OpenSearch Service, or to third-party destinations such as Datadog, New Relic, MongoDB, and Splunk. To get started, see the following resources: Fanout to Firehose delivery streams in the Amazon SNS Developer Guide. Create Firehose Stream in the Amazon Data Firehose Developer Guide. SNS pricing for deliveries to Amazon Data Firehose in the Amazon SNS Pricing Page.

Amazon SNS now supports Internet Protocol version 6 (IPv6) for API requests enabling you to communicate with Amazon SNS using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients using public endpoints. Amazon SNS is a fully managed messaging service that enables publish/subscribe messaging between distributed systems, microservices, and event-driven 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 SNS 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 SNS, please refer to our Developer Guide.

Today, AWS End User Messaging launched self-service short code, and long code registration for 18 additional countries, helping developers to onboard to dedicated numbers which enables them to correctly configure SMS messaging for their applications. The new countries supported for long codes include Australia, Austria, Chile, Denmark, Finland, Hong Kong, Italy, Netherlands, Norway, Poland, Spain, Sweden, United Kingdom, Hungary, and Portugal. The new countries supported for short codes include Chile, Finland, Germany, India, Netherlands, Spain, United Kingdom, and United States. Phone numbers and sender IDs act as an extension of a business's brand, and mobile carriers and governments worldwide have implemented SMS registrations as a form of "know your customer" check to protect end-users from unwanted and spam messages. By registering, application developers ensure a higher level of deliverability and ensure their use-cases comply with local rules and regulations, avoiding message filtering. Previously, customers needed to open a support case to request these short code and long code forms, but now they can self-service via the AWS Management Console or programmatically via the APIs, saving time-to-onboard. The registration support is available in all commercial regions where AWS End User Messaging is generally available.

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 SNS now supports high-throughput mode for SNS FIFO topics, with default throughput matching SNS standard topics across all regions. When you enable high-throughput mode, SNS FIFO topics will maintain order within message group, while reducing the de-duplication scope to the message-group level. With this change, you can leverage up to 30K messages per second (MPS) per account by default in US East (N. Virginia) Region, and 9K MPS per account in US West (Oregon) Region and Europe (Ireland) Region, and request quota increases for additional throughput in any region. Amazon SNS FIFO topics provides message ordering, message grouping, and de-duplication when delivering to Amazon SQS queues. By default, SNS FIFO topics provide 300 MPS per message group ID, and 3K MPS per topic, and topic level de-duplication. To get higher throughput, you can distribute your messages across message groups, and enable high-throughput mode by setting the FifoThroughputScope topic attribute to MessageGroup. We now have increased default limits for SNS FIFO topics across all commercial and the AWS GovCloud (US) Regions. To get started, see the following resources: High Throughput FIFO topics, in the Amazon SNS Developer Guide Service Quotas for Amazon SNS, in the AWS General Reference.

Today, AWS End User Messaging launched self-service Sender ID registrations for 19 additional countries, helping developers correctly configure SMS messaging for their applications. The new countries include Australia, Belarus, Egypt, India, Indonesia, Jordan, Kenya, Kuwait, Kazakhstan, Philippines, Qatar, Russia, Saudi Arabia, Singapore, Sri Lanka, Thailand, Turkey, United Arab Emirates, Vietnam, and Zambia. Phone numbers and sender IDs act as an extension of a business's brand, and mobile carriers and governments worldwide have implemented SMS registrations as a form of "know your customer" check to protect end-users from unwanted and spam messages. By registering, application developers ensure a higher level of deliverability and ensure their use-cases comply with local rules and regulations, avoiding message filtering. Previously, customers needed to open a support case to request these sender IDs, but now they can self-service via the AWS Management Console or programmatically via the APIs, saving time-to-onboard. The registration support is available in all commercial regions where AWS End User Messaging is generally available.