amazon-sns

问题 At the moment our team is getting AWS SNS messages regarding pull requests, branch changes etc as JSON embedded in an email, which means, without line-breaks, etc, a JSON structure wrapped to the width of the mail message. That's OK, but makes it difficult for people to read at a glance what's occurred, and, thus, easy to ignore. Is there a way to have it arrive better formatted? I looked through the SNS options and did some googling and found this -- Sending html content in AWS SNS(Simple

问题 In RabbitMQ, one can create an exchange, then bind it to multiple queues, each with a routing key. This enables messaging architectures like this: message_x / | \ foo-msg_q bar-msg_q msg-logger_q Clients publish messages to the message_x exchange, which routes only messages with routing key "foo" to the foo-msg_q queue, only messages with the routing key "bar" to the bar-msg_q queue, and all messages to msg-logger_q queue. I'm having trouble figuring out how to do this in AWS. My first

问题 I have a nodejs lambda that has an SQS queue as an event, which is subscribed to an SNS topic. The lambda looks like this: 'use strict'; import { Handler } from 'aws-lambda'; const myLambda: Handler = async (event: any = {}) => { let incomingMessage = JSON.stringify(event.Records[0].body); console.log('Received event:', incomingMessage); # log1 console.log('parsed event',JSON.parse(incomingMessage)); # log2 var type = JSON.parse(JSON.stringify(incomingMessage)).Type; console.log('Message

问题 I have a nodejs lambda that has an SQS queue as an event, which is subscribed to an SNS topic. The lambda looks like this: 'use strict'; import { Handler } from 'aws-lambda'; const myLambda: Handler = async (event: any = {}) => { let incomingMessage = JSON.stringify(event.Records[0].body); console.log('Received event:', incomingMessage); # log1 console.log('parsed event',JSON.parse(incomingMessage)); # log2 var type = JSON.parse(JSON.stringify(incomingMessage)).Type; console.log('Message

问题 I have requested a dedicated long code . But Whenever I send SMS to this Dedicated long code with Keywords , nothing is happening. I am not receiving any automated response messages (Response messages setup in the AWS Pinpoint Console). The dedicated number is for INDIA and region is AWS MUMBAI REGION . I have also created SNS which is not at all getting triggered for incoming SMS for this dedicated number. I will provide additional details, if wanted. Please guide me to debug this issue. 来源：

问题 The tutorial for Windows Phone 7 push notifications says that to implement Push Notifications, you need to call Microsoft Push Notification service which manages the sending of the notification to WP7 devices. Does that imply that to send an AMZ SNS message, I need to create an intermediary web service that routes the SNS message to Microsoft Push Notification service? What are the options for Android and iOS devices? 回答1: Android has cloud-to-device-messaging (c2dm), which is a labs project

问题 While reading the SNS FAQ part concerning the retrying behaviour with Lambda functions, I've encountered the following statement: Q: What happens to Amazon SNS messages if the subscribing endpoint is not available? Lambda: If Lambda is not available , SNS will retry 2 times at 1 seconds apart, then 10 times exponentially backing off from 1 seconds to 20 minutes and finally 38 times every 20 minutes for a total 50 attempts over more than 13 hours before the message is discarded from SNS. As

问题 I developed a web application which serves a html page when user visits the link and displays some data according to keywords entered. Now data is being populated on the go, so I want to model something like when a new piece of data is stored(in elastic search) a SNS notification is generated which is shown to the person who is viewing the webpage. I got the SNS notification working, but I am stuck on the part that how do I display this notification on the front end? Can I do something like

问题 Email NOOB here. Planning to use Amazon SES for transaction email. Trying to understand how to handle emails that bounce or get marked as spam. SES automatically adds bounce/complaint recipients to the suppression list. What I read about suppression list: Suppression list is a list of recipient addresses that Amazon SES blocks because the addresses have caused a hard bounce for any Amazon SES sender within the past 14 days....If you try to send an email to an address on the suppression list,

问题 Can we subscribe an Amazon SNS topic using an AWS Lambda function? 回答1: Yes. With help of sns.subscribe() Please keep in mind: dont forget to confirm it sns.confirmSubscription() 回答2: If you mean can you use a message from a SNS topic as the trigger for a lambda function, then the answer is yes. If you mean can you write a lambda function that adds a subscription to an SNS topic then the answer is yes. Towards the bottom are links for the language-specific AWS SDKs. Your Lambda function would