Skip to main content

What’s New

Qrvey 8.7
Version 8.7 of the Qrvey platform is now available to customers! This version includes new features including area charts, the ability to pivot and export data, as well as numerous bug fixes and performance improvements.
Learn More
Qrvey 8.6
Version 8.6 of the Qrvey platform is now available to customers. This version includes several new feature enhancements and performance improvements.
Learn More
Required Update for 8.5.1
Attention 8.5.1 customers: for any 8.5.1 instance deployed prior to 08/05/2024, an update is required to ensure you are running the latest images.
Learn More
Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
Version: 8.0

AWS FAQs

Q: What are the options and correct process of connecting to an AWS RDS?

A: There are 2 components in Qrvey that connect to a data source and download data. The first one is an ECS container running on an EC2 instance called qrvey*microservice_ECSInstance and the second one is a Lambda function called *_dataload_drDataSourcePump.

Both of these components should be able to connect to your data source. For example, if you are using an RDS with restricted access, have a look at this document for more details. If your data source is outside of AWS and can only be restricted using IP addresses, then you can configure a VPC with a private subnet and Internet/NAT gateway to get a static IP for Lambda functions.


Q: How can I speed up my data load?

A: Data load times mostly depend on the Elasticsearch cluster. Since there is a cost associated with Elasticsearch, we normally create the minimum resources possible, however, you can always scale up based on your needs. Currently, we are using 1 node t2.small (10GB). If you want to increase processing speed, we recommend going with 3 node t2.small or trying higher-cost options like the t2.medium or m4.large instances. You can refer to this document on how to make that change.


Q: I created users but the activation e-mails never arrived in their e-mail address. They have even checked the spam folder.

A: This is probably because your AWS account is in Sandbox mode for Simple Email Service (SES). AWS blocks email going out from SES, which means you need to submit a ticket to AWS to enable the access within one day. To submit the ticket please go to

AWS SES console, click on the **Sending Statistics** menu option, and follow the link from the warning message to request a limit increase.

Q: The installation process created 8 EC2 instances. Is that supposed to happen?

A: Yes. At the moment this is standard for all installations, however, it will change in the near future as we are constantly improving our architecture and planning to remove the EC2 instances.


Q: How do I know if my Elasticsearch cluster is short on space?

A: There are 2 ways to monitor the Elasticsearch cluster.

  1. Using Admin Center:
    i. Login to Admin center using your AWS IAM credentials.
    ii. Click on the DataRouter section.
    iii. Review the node usage in the Elasticsearch section at the bottom. It shows the total vs used space and then per node.

  2. AWS Elasticsearch console
    i. Login to your AWS account with a user that has permissions to access Elasticsearch domains.
    ii. Select “Dashboard” tab from the top-left menu.
    iii. You can review the free storage space in the table for your Elasticsearch cluster.