Eventbridge Scheduler Issue

0

I have come across an issue which is likely to be a configuration problem at my end. In December I set up a lambda function with a site scraper, it pulls a specific piece of information from the site. I then created a schedule through eventbridge to do this every 10 minutes. (It will eventually happen once a week but for this I used 10mins because I wanted to test it). I also created a topic in SNS with a text message being the way I would get the information.

To summarise, I have an eventbridge schedule, that triggers a lambda function which then triggers an SNS topic to send me a text message. Pretty simple and it worked.

Fast forward to now and it no longer works. I changed a bit of the lambda function code to have a cleaner output when it came to receiving text messages.

I have gone back to the start with it and deleted all triggers. I have set up new schedules and even new rules, created new topics but I no longer get any text messages.

I'm in the UK but have deployed in us-east-1. I'm at a loss at the moment to what the problem may be. I have noticed when I try to create a new rule based on a schedule it takes me to the new eventbridge scheduler page. I have done that still wont work. I also tried with setting up a rule and have it set to 1 minute just to test but still nothing.

I have the SNS topic on asyncronous and on success of the trigger rather than failure. Like I said it worked previously right up until yesterday. I reverted back to the old code and its still no longer working.

I have checked the logs and it seems the scheduler is triggering the lambda but nothing from the amazon sns side.

EDIT - I had a look on Amazon SNS I have a delivery rate of 0.51%, almost 900 have failed at the time of writing this. EDIT - Edit 2, I think the problem may be my SMS quota has been reached. I have another question though. Would I be better setting this up in the UK, would it reduce costs?

Thanks

1 Answer
2

You can configure a Delivery status logging in the SNS for further investigation.

About quotas, you can go to console.aws.amazon.com/servicequotas/ and find SNS For example, there is an "SMS Message Spending in USD" with a default value "1", The maximum amount, in USD, that an AWS account can spend on sending SMS messages.

You can adjust it if it is the root cause

About pricing:

Usually N.Virginia is cheaper than European regions. For example, if we look at EC2 pricing (t3.medium) us-east-1 N.Virginia $0.0416 eu-west-2 London $0.0472 eu-west-1 Ireland $0.0456

But SNS and Lambda prices are the same now for the mentioned regions.

profile picture
EXPERT
answered a year ago
profile picture
EXPERT
Artem
reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions