In order to perform a successful connection to your SFTP/FTP , we just need the below information and that's it!
- SFTP/FTP hostname
- Path where the files are stored
NOTE: if the customer chooses to use our SFTP, we'll provide the details.
Once we have a successful connection, it will enable us to populate your AlertFind instance with the information that you send to us in the file.
How does our SFTP/FTP Connector works :
The below graphic explains the various nodes involved in the transition of data from your SFTP/FTP location to AlertFind.
Detailed Steps Explaining Above Graphic :
- You upload the files to your SFTP/FTP.
- Based on your chosen frequency, our SFTP/FTP connector running on AWS Lambda fetches the files stored in your SFTP/FTP location.
- At this stage, data is transformed into a CSV.
- The CSV is compressed to a Zip file and sent to AlertFind API via the AlertFind connector running on AWS lambda.
Data Storage Nodes in The Graphic Above:
- Node 5 : Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution has finished.
- Node 6 : Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
- Data Safety :All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 validated hardware security modules.
We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.