Amazon SNS announces support for setting content-type request headers for HTTP/S notifications

Amazon Simple Notification Service (Amazon SNS) now supports setting content-type request headers for HTTP/S notifications. This enables your topic subscribers to create a DeliveryPolicy that specifies the content-type value that Amazon SNS assigns to their HTTP/S notifications, such as application/json, application/xml, or text/plain. With this launch, applications can receive their notifications in a more predictable format.

Amazon SNS is a messaging service for Application-to-Application (A2A) and Application-to-Person (A2P) communication. The A2A functionality provides high-throughput, push-based, many-to-many messaging between distributed systems, microservices, and event-driven serverless applications. These applications include Amazon Simple Queue Service (SQS), Amazon Kinesis Data Firehose, AWS Lambda, and HTTP/S endpoints. The A2P functionality enables you to communicate with your customers via mobile text messages (SMS), mobile push notifications, and email notifications.

Amazon SNS HTTP content-type header support is available in all public AWS Regions and the AWS GovCloud (US) Regions. You can start using this new capability today, via the AWS Management Console, AWS Software Development Kit (SDK), Amazon SNS Command Line Interface (CLI), and the Amazon SNS Application Programming Interface (API). You may also provision your DeliveryPolicy for an Amazon SNS subscription via AWS CloudFormation.

To learn more about Amazon SNS content-type request headers for HTTP/S notifications, see the following:

• Creating an HTTP/S delivery policy
• Amazon SNS HTTP/HTTPS headers
• Amazon SNS fanout to HTTP/S endpoints