amazon-sns

问题 I'm trying to understand whether I need SQS in my workflow if someone can help explain. In my app, when an action is taken, it submits info to SNS topic which invokes LAMBDA to do some processing. This is working great as it is. When I do research online, it seems that people are using SQS in this stack as well where SNS would put info on SQS and then SQS would then invoke LAMBDA. I guess what I'm trying to understand is the need for SQS in this. What value doe that add or in other words,

问题 I'm in the process of rebuilding a PHP app in Node.js on top of the Express framework. One part of the application is a callback url that an Amazon SNS notification is posted to. The POST body from SNS is currently read in the following way in PHP (which works): $notification = json_decode(file_get_contents('php://input')); In Express I have tried the following: app.post('/notification/url', function(req, res) { console.log(req.body); }); However, watching the console, this only logs the

问题 I'm in the process of rebuilding a PHP app in Node.js on top of the Express framework. One part of the application is a callback url that an Amazon SNS notification is posted to. The POST body from SNS is currently read in the following way in PHP (which works): $notification = json_decode(file_get_contents('php://input')); In Express I have tried the following: app.post('/notification/url', function(req, res) { console.log(req.body); }); However, watching the console, this only logs the

问题 I would like to send an SMS message from an AWS Lambda function using the boto3 publish method to notify the user of issues via SMS. My lambda function is written in Python and I am using the boto3 module. My lambda function has full rights to SNS. I have this code, sns = boto3.client('sns') sns.publish( PhoneNumber = '+11234567890', Message = 'Simple text message' ) According to the boto3 documentation, the publish method accepts the following parameters, response = client.publish( TopicArn=

问题 On my site I'd like to do push notifications of comments like Stackoverflow does. Amazon SNS/SQS seems to provide a framework to do this but I'm having difficulty finding any code/explanation on the web for anything beyond a "hello world" equivalent. From reading the AWS SNS/SQS documentation it looks like I need the following: logic: post comment/answer to a new question create topic (for first comment/answer only) publish message subscribe to topic PHP on the page where comments are posted

问题 I am a little confused about this migration path, as described in a recent aws blog post, and its aftermath: It seems like quite a bit of trouble to have to rely on all my users to update in a timely fashion so that GCMSenderIDs can be attached to my existing parse data along with modified/valid device tokens. Also, what happens to new installations after the migration is complete? In the guide it says no changes need to be made to client side code, but doesn't this require that the SNS sdk

问题 I am using Aws SNS to send notification, and sending notifications to different topics and is working perfectly. When i publish notification, i got array like object(Aws\Result)#84 (1) { ["data":"Aws\Result":private]=> array(2) { ["MessageId"]=> string(36) "************-7a29-591f-8765-************" ["@metadata"]=> array(4) { ["statusCode"]=> int(200) ["effectiveUri"]=> string(40) "https://sns.ap-southeast-1.amazonaws.com" ["headers"]=> array(4) { ["x-amzn-requestid"]=> string(36) "***********

问题 I am developing REST API application on Symfony3. I want to register mobile devices and send direct push notifications to them. For example, when one user sends feedback to another, that second user will get push notification. With Amazon SNS is it possible not to broadcast, but directly notify individual device from server? 回答1: yes, is possible, you create a platform and then you can create multiple 'Endpoints' wich represent a devices in SNS with the corresponding token or device id. then

问题 I have a simple key-value pair collection in my mongo database, it holds configuration details for my web-app and it's read by each EC2 instance started by the ElasticBeanstalk autoscaling (1-10 instances). Almost every JAXRS service endpoint causes a read from the mongo config collection and I want to stop reading values directly from the DB to lighten the load on the database. My plan is to read the value once, store it in an in-memory dictionary then use the value from the dictionary

问题 I have followed all the steps mentioned in the official documentation. I am able to register device tokens in the application endpoint list successfully. The message has been published to registered tokens. The delivery status says success (status code 200) in cloud watch console. But the device isn't able to receive notifications in iOS devices. What could be the reason? Note : I have enabled notification settings in devices and ios project. 回答1: Double check the Message format setting. I