Questions tagged with Amazon Simple Notification Service (SNS)
Content language: English
Sort by most recent
**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?
Receiving error when trying to add Event Notification for SQS via CDK: botocore.exceptions.ClientError: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration
Error: **botocore.exceptions.ClientError: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation** Hello AWS, I am currently working on a project where I am working with a third party team. The team has an SQS that all of our buckets have an event notification for. I currently added a new bucket and I am receiving this error when I try to deploy it via CDK. The team does not seem to be to well familiar with AWS but I asked if I have permissions to call the SQS and they said yes. Is there a way to confirm this on my end? Or is is there documentation on the configuration the team needs to set up for their SQS Que? If so, is there any other problems that could cause this error message? I'm confident it's on the third party team ends because this is done through our CDK stack and everything else works fine. But I do want to know I am updating an existing stack, before our bucket did not send via event notifications but was created. Any solutions or troubleshooting will help. One source I found on stackoverflow except it's for lambda: https://stackoverflow.com/questions/36973134/cant-add-s3-notification-for-lambda-using-boto3
production access is persistently denied access to my website I verified my e-mails I sent e-mail example I use a 3rd party software to process complaints and feedback, this software works with s.n.s. I explained my usage status already we have a ready system that continues to send mailchimp with mailchimp our domain name is clean why they do not understand why they do not accept us. case id 12067400461
I'm using cognito and I would like to send forgot password verification codes using SMS. Doing so using emails works, but I would like to switch to SMS. I have moved my SNS out of sandbox and my account is active in production mode in my specified region. Also I have requested an increase of spend limit and this was granted and I again updated the new value on SNS and on pinpoint. On trying to send an SMS, I get the following message on cloudwatch: "Your account requires additional review prior to being able to send SMS messages. Please create a support ticket with an explanation of your use case. https://console.aws.amazon.com/support/cases#/create?issueType=service-limit-increase&limitType=service-code-sns-text-messaging" I don't see where the problem is considering I followed the documentations on how to use SNS. Kindly assist.
Generate specific parameters to appear in SNS email notification in CloudWatch Alarm for a Log Group
I am able to create a CloudWatch alarm that gets triggered from a Metric Filter of "ERROR" in a log group, however, I need to add specific parameters to the email notification that the CW alarm generates. I have created a SNS Topic and SNS Subscription to generate the notification but I cannot figure out how to add the below parameters to the email. I attempted to use Powershell command to do this but received an error of "Delivery protocol [email] does not support raw message delivery." From doing research, it appears that I need to create a Lambda function to do this. I am looking for guidance on how to structure the Lambda function to grab the raw data from the metric filter in the log group and sends that information in an email when the ERROR Cloudwatch Alarm is triggered. * "@@t" - time * "SourceContext" - the context of the occurred error * "MachineName" - server name * "@log" - the log group name Thank you,
I need to configure lambda function subscription across multiple accounts. These lambda functions are used for log ingestion to a third party application. I need a solution that works across different accounts . Right now these lambda functions subscriptions are per account therefore not a centralized solution.
I have approved all the templates both transactional and promotional message thorugh Indian DOT. Transactional message are being send successfully but when I try to send message using Amazon console "publish text message" than it is not sending. It is saying "Phone carrier has blocked your message" while this is approved template with proper entitity id and template id. Please guide me how to resolve it.
FlexMatch sends various notifications described [here](https://docs.aws.amazon.com/gamelift/latest/flexmatchguide/match-events.html). I have a service getting these messages via SQS polling. The event payloads in the messages are serialized to JSON. Are there models defined for these events in the Java AWS SDK 2.0? I sure cannot find them. Are you supposed to roll your own models to deserialize and work with these events?
We send data message push notifications to Android devices via SNS and we would like to make use of analytics labels to improve message delivery statistics viewable within Firebase. These analytics labels are only supported in the V1 Cloud Messaging API, not the legacy version. Which version of the API does SNS use? And if it's the legacy version, are the plans to migrate to V1? Thanks, Mikael
I am sharing my release message notification on Slack via SNS, EventBridge and Lambda functions. I have accomplished it successfully, but we do not get the commit message or PR link or the PR details which triggers the deploy. Is it possible already in someway? Or is there some feature in progress? Or is it not possible? Also, my repository is in BitBucket.
Hello, We are in need to call lambda function within our organizations AWS account from Vendor's AWS account based on SNS notification. Currently we have roles and permissions configured in such way that we can call / use vendor's AWS resources but they can't access our's and at the same time we don't want to open it to them. What should be our best path to make this communication work? Thank You, Yogesh