Questions tagged with Amazon Simple Notification Service (SNS)
Content language: English
Sort by most recent
I am try create a archtecture in Learner Lab with IoT core and I want send a message on email.
I use this https://docs.aws.amazon.com/iot/latest/developerguide/iot-sns-rule.html of base tutorial, but when I click in create role show this for me
We need to understand how the SNS message body filter functionality is working. we are having one use case like our project SQS consumer will provide the SNS filter policy after that we need to subscribe to SNS with filter policy to test it. is there any logic available in AWS SDK to test the SNS filter policy without subscribe to SNS.
Basically we are expecting is there any functionality available to test the SNS filter policy before subscribe to SNS like regular expression validation.
I want to delete my Amazon Simple Notification Service (Amazon SNS) topic subscription. My email address that used to subscript this is invalid.
I went to AWS official page to find the solution. It syas " If subscriptions are in the Deleted or Pending Confirmation status when you delete their topic, then you can't manually remove the subscriptions from your account. You must wait three days for Amazon SNS to automatically remove the subscriptions from your account."
When I went to my AWS subscription, today is fourth day, the subscription is still there and I can't delete it.
The topic has been deleted but the pending subscription can't be delete.
What should I do?
Completely green here .. I can't add a destination phone number for sandbox use. Yes my console state I am using a sandbox. When I attempt to add a number I get an error stating that stating not having an origination number. This is the sandbox, am I missing something?
I am associating this,lack of, sandbox number to the fact I can't get text message when I run the SDK example but I do get emails
Thanks for the help
I'm attempting to integrate a Google Chat webhook with the SNS https protocol but am having difficulty.
command1:
aws sns subscribe --topic-arn arn:aws:sns:us-east-1:123456789012:MyTopic --protocol https --notification-endpoint 'https://chat.googleapis.com/v1/spaces/AAAAaikfLEo/messages?key=<your-key>&token=<your-token>'
output:
{
"SubscriptionArn": "pending confirmation"
}
Here are the cloud monitoring logs.
{
"notification": {
"messageId": "0b72f18b-4267-4766-9196-58sckdsjwswf",
"topicArn": "arn:aws:sns:us-east-1:123456789012:MyTopic",
"timestamp": "2023-03-11 05:57:32.278"
},
"delivery": {
"deliveryId": "0b72f18b-4267-4766-9196-58sckdsjwswf",
"destination": "https://chat.googleapis.com/v1/spaces/AAAAaikfLEo/messages?key=<your-key>&token=<your-token>",
"providerResponse": "Bad Request",
"dwellTimeMs": 62,
"statusCode": 400
},
"status": "SUCCESS"
}
I tried other commands as well, but they were ineffective.
command2:
aws sns subscribe \
--topic-arn arn:aws:sns:us-east-1:123456789012:MyTopic \
--protocol https \
--notification-endpoint 'https://chat.googleapis.com/v1/spaces/AAAAaikfLEo/messages?key=<your-key>&token=<your-token>' \
--attributes '{"http":{"defaultContentEncoding":"UTF-8","headers":{"Content-Type":"application/json"}}}'
error:
Parameter validation failed:
Invalid type for parameter Attributes.http, value: OrderedDict([('defaultContentEncoding', 'UTF-8'), ('headers', OrderedDict([('Content-Type', 'application/json')]))]), type: <class 'collections.OrderedDict'>, valid types: <class 'str'>
not greeting the error in command1 but receiving no response
However, the status code in the logs is 400, so I'm not sure what the error is; it could be about the header or something else.
I'm trying to create S3 event notification to SNS topic from an existing S3 bucket. I'm receiving "Unable to validate the following destination configurations".
Initially I thought the issue was with the SNS topic Access Policy and tried different troubleshooting suggestions, such as this video https://www.youtube.com/watch?v=RjSW75YsBMM, but nothing worked.
I'm using the following policy:
```
{
"Version": "2012-10-17",
"Id": "example-ID",
"Statement": [
{
"Sid": "Example SNS topic policy",
"Effect": "Allow",
"Principal": {
"Service": "s3.amazonaws.com"
},
"Action": [
"SNS:Publish"
],
"Resource": "SNS-topic-ARN",
"Condition": {
"ArnLike": {
"aws:SourceArn": "arn:aws:s3:*:*:bucket-name"
},
"StringEquals": {
"aws:SourceAccount": "bucket-owner-account-id"
}
}
}
]
}
```
Then I decided to focus on the S3 bucket part of the equation and created brand new bucket with exactly the same configuration, switched the SourceArn in the policy with the new bucket's arn and the event notification was successfully created.
What could be the reason for a given SNS topic with a given policy to work with one S3 bucket, but not with another?
I am getting the below error message when I try to delete the SNS delete notification. I have deleted the SNS topic associated to it and the email. Is there a way to delete the SNS by itself as it's still pending confirmation.
Couldn't send confirmation request.
Error code: NotFound - Error message: Topic does not exist
Hello.
I'm trying to set up sending one-time passwords via SMS for Asia Pacific (Sydney), but I've run into a problem that I can't create an Australian (+61) phone number via Pinpoint using the Request phone number button. I tried to change the console region to Sydney but it didn't help.
Please tell me how to create an Australian phone number or can I use another country number for this or do I need to do it through 10DLC campaigns.
Required steps for creating SNS notification from cloudwatch log group for rds
Hi!
I use FluentSMTP to connect to AmazonSES. I am sending a newsletter test email, but received this email from AWS:
"From: <MAILER-DAEMON@us-east-2.amazonses.com>
Date: vie, 24 feb 2023 a la(s) 13:45
Subject: Delivery Status Notification (Failure)
An error occurred while trying to deliver the mail to the following recipients:"
The message does not state any error code or reason for the error, and I can't find any info about the errors within my account.
For some email addresses, emails arrive just fine. For others, the same error message as above.
I recently built a brand new website (same domain name) for what I had registered with SES. It resides on the same server, though different Wordpress application. All the DNS records appear correct and I have three separate CNAME DKIM records for amazonses.
The test emails from FluentSMTP send just fine and their support tells me the issue is with AmazonSES.
Any idea how I can fix the issue? Thanks!
Hi,
We're using SNS to send HTTP requests to our endpoint. That's how we record delivered, sent, bounced, etc.
If we send 500,000 emails this means we will receive 500,000 requests. I wonder whether is it possible to bulk this? It would be great if there is something like this:
```
{"items": [{"messageId": 123"}, {"messageId": 456}]}
```
I haven't been able to find such solution.
Thanks,
Nedim
**Can I use my own phone number as an origination number for SNS?**
I'm testing out SNS and would like messages sent to my phone, ideally from my own number.
When filling out this process, it seems like I'm required to buy a new number in pinpoint in order to set this up.
Is there anyway I can just register my own number?
asked a month ago