Questions tagged with Amazon Simple Notification Service (SNS)
Content language: English
Sort by most recent
Hi all,
In our application, we send reminder emails to our customers one day before their reservation at exactly 1AM. This means, that we may need to send a 100 or even more emails at once, to different email addresses. We have a scheduled Node JS function, which uses the AWS SDK in our backend to do this.
Currently, my maximum send rate is 14 emails per second.
So my question is how do I go about preventing to exceed the maximum sending rate per second?
We have an HTTPS endpoint configured as a subscriber. We configured delivery logs to cloud watch. In the cloud watch logs i am seeing the following error message.

Our HTTPS API is working fine but the error message says **IO Exception in HttpClient ** . Is this problem in sns end or on My Server side?
Hi There,
Tool: AWS Connect Agent
Wondering if it is possible to be notified via text (sms) or email that a call is in the queue?
In case the agent is away from his desk.
Thanks,
Dan
I can't receive the verification email for my SNS topic. Please help!
Best,
~Kwasi
My organization has already got a sender ID from TRAI. Do I need to request for Sender ID again through a support ticket, to send SMS using SNS in India?
Hello forum,
I am facing a weird issue and that is not consistent. I have a SQS FIFO Queue subscribed to SNS FIFO topic. I have added a filter policy to receive only specific messages (messages with specific attributes) on SQS FIFO Queue. This setup is working fine.
But since last few weeks Im facing an issue where the SQS FIFO Queue suddenly stops receiving any messages. This occurred around 5 to 6 times since last three weeks.
Please find the observations below for the tests performed to confirm that there is no issue with SNS (publishing on SNS FIFO topic successfully) and the issue is with same SQS FIFO Queue -
1. I created one other SQS FIFO Queue with different name but same configurations (i.e. subscribing to same SNS FIFO topic with same filter policy). I observed that the new SQS FIFO Queue immediately starts receiving messages but the old SQS FIFO Queue is unable to receive message.
2. If I subscribe the existing SQS FIFO Queue to other SNS FIFO topic and publish on the SNS FIFO topic, the existing SQS FIFO queue did not receive any message. While another SQS FIFO Queue subscribed to this SNS FIFO topic was receiving the published messages.
3. I also observed that the old SQS FIFO Queue stars receiving messages automatically after couple of hours.
4. If I delete this SQS FIFO Queue and create a new with same name and configurations, the new SQS FIFO Queue starts receiving messages immediately.
5. All SQS FIFO Queues are being affected for one specific SNS FIFO topic. And to this SNS FIFO topic Im publishing from AWS Lambda.
6. For other SNS FIFO topic to SQS FIFO Queue is not at all affected and its working fine all the time.
I have already tried [this](https://repost.aws/questions/QURhOWYtseQ6Ovy6GGpSTnTw/sqs-not-receiving-sns-message) but it's of no use.
Has anyone faced similar issue and help me with this.
```
Deploying sns to stage dev (us-east-1)
✖ Stack sns-dev failed to deploy (2s)
Environment: darwin, node 19.3.0, framework 3.26.0, plugin 6.2.2, SDK 4.3.2
Credentials: Local, "default" profile
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
User: arn:aws:iam:::{user} is not authorized to perform: cloudformation:DescribeStacks on resource: arn:aws:cloudformation:us-east-{}:stack/sns-dev/* because no permissions boundary allows the cloudformation:DescribeStacks action
```
Hello community
to allow sending SMS to Singapore it is needed to request this via the form below.
What, if we don't have a local representative in Singapore but have users that need to get the one-time-code (OTC) for MFA?
*'If you are the exact entity who is registering through SGNIC we require the following form: Amazon Singapore Sender ID LOI - TEMPLATE.docx'*
Thanks for helping !
Regards
A
How does kibana send the automatically generated report to my mailbox by email, my Elastic
It is "Amazon OpenSearch Service". Only the alarm set in the "Alerting" function has the function of sending emails. Can I add a PDF report attachment to the content of the email?
The default email content is
Monitor {{ctx.monitor.name}} just entered alert status. Please investigate the issue.
Trigger: {{ctx.trigger.name}}
Severity: {{ctx.trigger.severity}}
@timestamp: {{ctx.results.0.hits.hits.0._source.@timestamp}}
event.action: {{ctx.results.0.hits.hits.0._source.event.action}}
error.message: {{ctx.results.0.hits.hits.0._source.error.message}}
count: {{ctx.results.0.hits.total.value}}
soure.ip: {{ctx.results.0.hits.hits.0._source.source.ip}}
source.geo.country_name: {{ctx.results.0.hits.hits.0._source.source.geo.country_name}}
how should I write to get the report of my dashboard
SNS confirmation emails are sent out with a JSON body but the content-type is 'text/plain' where it should be application/json so the body can be parsed by built-in parsers.
Eg. in Python Flask if you try to use request.get_json() on the confirmation request it returns a 400 Bad Request as Flask won't parse the body if the content-type is wrong.
Please fix!
Hi,
I am working with mqtt client. And I am using CPP implementation for that. I want to use ULID in one of my request message. I am not getting how to do it.
Can you please help me in that?
I have a toll phone number in AWS Pinpoint (registered and in production mode) to send Transactional messages and since a few days ago our clients in Costa Rica are not receiving the messages (however in October the messages arrived successfully). In my SNS dashboard the SMS to Costa Rica are in Sent state (we contact in Costa Rica with a Mobile Phone carrier and no restrictions were detected in our clients phone numbers). Where is the point when the flow is broke? or I have to pay to AWS for a technical support plan to report this issue in the infrastructure, a wrong behavior that is not a bad implementation of the user, is a service that a day starts to work in an unexpected way? Also some other users in this forum are reported similar issues in the last days.