In order to perform a successful connection to you Aeries instance, we just need the following information and that's it!

  1. API Key: This API Key can be found or generated in the settings of the instance with an Admin account
  2. Base URL:  The base URL is the same as your Aeries web login, except without "/Login.aspx". For those using the Aeries hosted service, this could be "https//{district}.asp.aeries.net/admin". For those with an on-premises installation, an example could be "https://{your-domain}.com/aeries. Please do not include a trailing "/".

Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information:

  • First Name                                          First Name Alias
  • Home Phone                                      Last Name
  • Last Name Alias                                 Mailing Address
  • Mailing Address City                         Mailing Address State
  • Mailing Address Zip Code                Mailing Address Zip Ext
  • Middle Name                                      Middle Name Alias
  • Parent Email Address                        Parent Guardian Name
  • Residence Address                            Residence Address City
  • Residence Address State                  Residence Address Zip Code
  • Residence Address Zip Ext               Sex
  • Student Email Address                      Student Mobile Phone
  • Student Number

How does our Aeries Connector works.

The below graphic explains the various nodes involved in the transition of data from your Aeries instance to AlertFind.


Detailed Steps Explaining Above Graphic:

  1. Aeries Connector fetches User information stored in your instance API.
  2. Based on your chosen frequency, our connector running on AWS Lambda, fetches data from Aeries instance.
  3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
  4. 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 Above Graphic:

  1. Node 5: Refers to Apache Cassandra Cluster which store the data for execution purposes. It has a TTL of 7 days after workflow execution has finished.
  2. Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
  3. 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.

Did this answer your question?