Hi, in a nutshell, yes it is possible... but requires re-architecting to:
curl --> API Gateway --> SNS
Review the following Link: https://www.alexdebrie.com/posts/aws-api-gateway-service-proxy/
Here are the steps outlined in the link above
We created an SNS topic to receive messages and set up a subscription on that topic to forward all messages to a cell phone. We set up our basic API Gateway resources, including a REST API, a resource (/ingest) and a method (POST) on that resource. We made an IAM role that could be assumed by API Gateway and gave permission to publish messages to our SNS topic. We configured an integration to our SNS topic from our REST API’s resource and method. This integration included a request mapping template, a response mapping template, and a method response. We deployed our REST API to make it live, then sent an HTTP request using curl. We received the message on our cell phone, indicating that it was successfully published to our SNS topic.
Hope this helps.
[CodeArtifact] Missing Authentication Token using Curl.asked 6 months ago
How to create subscription from an SNS to another SNSAccepted Answerasked 5 months ago
AWS Sns Publish method is not working when application deployed using docker containerasked 6 months ago
configservice subscribe requires sns-topic, but console does notasked 3 years ago
IoT Events: Publish IoT Topic action with dynamic topic nameasked 4 months ago
Pinpoint - Two-Way SMS to Another Account SNS Topicasked 9 months ago
Issue sending email updates to encrypted SNS topicasked 3 years ago
Publish to SNS topic using curlasked 3 years ago
Cloudformation: connect lambda to an exisitng SNS topic ?asked 3 years ago
While trying to create an SNS subscription, after choosing a topic, all protocols except SQS disappearasked 4 months ago