Installation Prerequisites
As you prepare to install Qrvey within your current or a new AWS environment, there are a few items to be aware of prior to installation.
AWS Region Support
Qrvey has architected a system that combines roughly two dozen AWS services creating a scalable and cost-effective solution. As a result, we recommend deploying Qrvey into regions that have full support for these services. The regions that have been certified by our internal testing teams and have full support for every AWS service include:
- N. Virginia (us-east-1)
- Ohio (us-east-2)
- Oregon (us-west-2)
- Ireland (eu-west-1)
- Frankfurt (eu-central-1)
- London (eu-west-2)
- Sydney (ap-southeast-2)
- Singapore (ap-southeast-1)
- Mumbai (ap-south-1)
As AWS region support continues to evolve and expand, Qrvey may also be deployed in regions not listed above, provided all the core services are supported. If you have questions about regions that the Qrvey team has not yet certified, please contact Qrvey support at help@qrvey.com.
In the North American geo, the following regions do not have complete support for every service used by Qrvey, but you can still use Qrvey within these regions with the following limitations:
Region | Service(s) Missing | Limitation |
---|---|---|
N. California (us-west-1) | Comprehend | Text analysis - Used in Data Profiling and Transformations. |
Amazon Location Service | Mapping (Resources will be created in another AWS region | |
Canada (Central) (ca-central-1) | Rekognition | Image and Video analysis |
S. America (Sao Paulo) (sa-east-1) | Comprehend | Text analysis - Used in Data Profiling and Transformations. |
Rekognition | Image and Video analysis | |
GovCloud (US) (us-gov-west-1) | Amazon Location Service | Mapping |
The following regions are missing services that Qrvey relies upon and are NOT supported at this time.
Region | Service(s) Missing | Limitation |
---|---|---|
GovCloud (US-East) (us-gov-east-1) | Comprehend | Text analysis - Used in Data Profiling and Transformations. |
Rekognition | Image and Video analysis | |
Simple Email Service (SES) - Automated Deployment | Requires manual setup - Cloudformation is not able to configure SES. | |
Amazon Location Service | Mapping | |
CodePipeline | Deployment of software version updates |
AWS Account Settings
Before deploying Qrvey Platform, please check the following in your AWS account to make sure the following are available:
- We recommend for our default trial configuration to use the Default VPC with at least 2 public subnets for each availability zone of that region. If you require the use of a non-default VPC or other private subnet configurations, let us know and we can help you with this configuration.
- Ensure there are at least 24 S3 buckets available. (AWS sets a default limit of 100, you may need to increase the limit in your account.)
- If you are using a new AWS account, please confirm the Service Quota for AWS Lambda Concurrent executions. Usually the Applied Quota Value is set to 1,000, but, in some new accounts, it’s set to 10. Qrvey deployment requires the limit to be at least 100, but 800+ is recommended. Also, we have noticed that when Concurrent executions are limited to 10, the Max memory size is also limited to 3,008MB, while the default is 10,240MB. Please contact AWS support to get these limits increased before doing the install.
- For some new accounts, we have seen that the number of Concurrent Code builds is set to 1, which results in the installer taking longer than expected.
- To avoid an interruption of service, contact AWS to disable Lambda recursive loop detection. For more information, see Disabling Lambda Recursive Loop Detection.
AWS Role Access
During trial evaluations, Qrvey can perform the installation on your behalf within your AWS account. To install Qrvey within your AWS account, a “cross-account” role must be created. This role MUST have “admin” access to run the Cloudformation template necessary to run the Qrvey deployment. The role can be removed after the deployment process is completed.
Other Notes
The application uses AWS SES to send out all transactional emails from the platform. AWS SES is in SANDBOX mode by default. Please, open a support ticket with AWS to move your account out of Sandbox mode.