AWS-SNS-Listener

Details

ID	`AWS-SNS-Listener`
Provider	Amazon
Category	Messaging and Conferencing
From Version	6.10.0
Docker Image	`demisto/fastapi:0.125.0.10158186`
Supported Modules	Agentix XSIAM

README

Amazon Simple Notification Service (SNS) is a managed service that provides message delivery from publishers to subscribers.
This integration was integrated and tested with version January 2024 of AWS-SNS-Listener.

Configure AWS-SNS-Listener in Cortex

Parameter	Description	Required
Long running instance	Integration is long running by default
Listen Port	Runs the service on this port from within Cortex XSOAR. Requires a unique port for each long-running integration instance. Do not use the same port for multiple instances. Note: If you click the test button more than once, a failure may occur mistakenly indicating that the port is already in use.	False
Username	Uses basic authentication for accessing the list. If empty, no authentication is enforced. (For Cortex XSOAR 8 and Cortex XSIAM) Optional for engines, otherwise mandatory.	False
Password		False
Endpoint	Set the endpoint of your listener. example: /snsv2	False
Certificate (Required for HTTPS)	(For Cortex XSOAR 6.x) For use with HTTPS - the certificate that the service should use. (For Cortex XSOAR 8 and Cortex XSIAM) Custom certificates are not supported.	False
Private Key (Required for HTTPS)	(For Cortex XSOAR 6.x) For use with HTTPS - the private key that the service should use. (For Cortex XSOAR 8 and Cortex XSIAM) When using an engine, configure a private API key. Not supported on the Cortex XSOAR or Cortex XSIAM server.	False
Store sample events for mapping	Because this is a push-based integration, it cannot fetch sample events in the mapping wizard. After you finish mapping, it is recommended to turn off the sample events storage to reduce performance overhead.	False
Use system proxy settings		False

Commands

You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.

Configuration parameters

longRunning — Long running instance
credentials — Username
endpoint — Endpoint
certificate — Certificate (Required for HTTPS)
key — Private Key (Required for HTTPS)
store_samples — Store sample events for mapping
proxy — Use system proxy settings
longRunningPort — Listen Port (required)

Commands (0)

This integration defines no commands.

Source

AWSSNSListener.py AWSSNSListener_test.py AWSSNSListener.yml AWSSNSListener_description.md

Download History Raw

## AWS-SNS-Listener Help

In order to configure the AWS-SNS-Listener

XSOAR6

* http: configure an endpoint and a free port for the internal long running server.
* https: In addition to http configuration please add a CA certificate and private
* key AWS-SNS works only with CA certificates.
* Another option is via engine. 
   
Configuring the subscriber on AWS-SNS UI is straightforward:
```http/https://<instance-name_or_IP>:<port>/<endpoint_configured>```
For more general information on long running integrations on XSOAR6:
[XSOAR6 Long Running](https://xsoar.pan.dev/docs/reference/articles/long-running-invoke)

XSOAR8 or XSIAM:

* The instance should be configured to run only on HTTPS. 
* The instance is using the HTTPS certificate of the server.
* Please set a user and password (can be global via long running integrations configurations)
* or local for this integration only.
   
Configuring the subscriber on AWS-SNS UI:
```https://<username>:<password>@ext-<cortex-xsoar-address>/xsoar/instance/execute/<instance-name>/<endpoint>```

example:
```https://user:pass@ext-myxsoar-address/xsoar/instance/execute/My-AWS-SNS-Listener-Instance/sns_ep```

For more info on long running integrations on XSOAR8 or XSIAM:
[XSOAR8 or XSIAM Long Running](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Administrator-Guide/Forward-Requests-to-Long-Running-Integrations)

### Notes:
- Specify the endpoint without special characters i.e /
- The endpoint configured in AWS and in XSOAR must be the same.