amazon-sns

When I use CloudWatch alarm to trigger an AutoScaling action, it repeatedly trigger the ASG actions. In other words, a subsequent set of N Alarms with state ALARM will trigger N actions on ASG. This behavior was not observed for a SNS action, instead it's triggering only within the 1st event when the Alarm changes from OK to ALARM. Is it possible achieve the same action behavior on SNS similar to ASG? An Amazon CloudWatch alarm will only trigger an Amazon SNS notification when the alarm enters the ALARM state . That is, it triggers only once, and only when moving from something that isn't

I am running this code to send a sms message with Twilio... client.messages.create( to=form.phone.data, from_="+1xxxxxxxxxx", body="This is a text message" My application is hosted on AWS Lambda using Python's Zappa. The problem is that I need to be able to schedule this message to be sent 10 minutes in the future. Zappa offers task execution but their documentation is unclear for how something like this should be done. Thanks for the help. This isn't something Zappa directly supports at this time. You'll need to perform a hack of some sort around the available scheduling system. Schedule an

I'm writing a web application that has steadily increasing traffic through the day. I'd like to create an Alarm that can detect if my read / write limits have reached a certain percentage (like 80%), and then increase that limit. I will then decrease it again at midnight. I've tried creating an Alarm - "Average" seems a bit useless and is always 1.0. "Sum" is more useful so I assume i should use this. I also assume i should use Consumed Write/Read Capacity at the metric name. Problems: Sum seems to use an absolute value of "Count" for its limits. If my DynamoDB is set to 100 writes, and i

I have Lambda function when invoked it creates SNS topic, adds subscribers to it and then publishes a message to it. After publishing the messages it deletes the topic. The name of the topic to be created and the subscribers are supplied to the lambda function as payload. Sometimes it works and sometimes it fails with Task timed out after x seconds I have increased the lambda timeout and still same issue. I dug a little and found out that sns.createTopic(params, function(err, data) { if(err) { console.log('Error Creating SNS Topic:',err); } else { console.log('SNS Topic Created Successfully:'

I have an AWS lambda function that I created via apex. I've also created a SNS topic and a subscription through terraform. My topic is: arn:aws:sns:ap-southeast-1:178284945954:fetch_realm_auctions I have a subscription: arn:aws:sns:ap-southeast-1:178284945954:fetch_realm_auctions:2da1d182-946d-4afd-91cb-1ed3453c5d86 with a lambda type and the endpoint is: arn:aws:lambda:ap-southeast-1:178284945954:function:wowauctions_get_auction_data I've confirmed this is the correct function ARN. Everything seems wired up correctly: I trigger SNS manually: aws sns publish --topic-arn arn:aws:sns:ap

I am facing an issue. My main motive is to send an email whenever there is state change happened to ec2 instances. I tried cloud watch events directly with SNS and its work also but the email template which I am receiving is not having the proper information to understood. I was expecting Server name and its IP in the email template which SNS does not give me the option to modify it. So What I am thinking is to involve lambda so that cloudwatch events to monitor EC2 instances state change and give input to Lambda which will have customized email template which is then invoke SNS to send email