Skip to main content

What’s New

Qrvey 9.1
Qrvey Version 9.1 is now available! This release introduces numerous features, enhancements, bug fixes, and performance improvements.
Learn More
Qrvey 9.0
Qrvey Version 9.0 is now available! This release introduces multi-platform hosting (Azure & AWS), a redesigned Dashboard, extensive widget customizations, and numerous features, enhancements, bug fixes, and performance improvements.
Learn More
Qrvey 8.8
Qrvey Version 8.8 (LTS) is now available to customers! This version supports FIPS for GovCloud and includes tons of bug fixes and performance improvements.
Learn More
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.8

Prepare Your AWS Account

Qrvey is deployed to your AWS account using a CloudFormation template, which automates the setup of all required AWS services. Follow the steps below to prepare your AWS environment for deployment.

Step 1: Create an AWS Account

If you already have an AWS account, skip to Step 2.

  1. To create a new AWS account:

Step 2: Create a Cross-Account IAM Role

This step is required if the Qrvey team will perform the deployment. Skip if you are deploying yourself. This creates an IAM role in your AWS account for Qrvey deployment.

  1. Log in to the AWS Console.
  2. Select your region.
  3. Go to AWS IAM.
  4. Click Roles in the menu.
  5. Click Create Role and configure:
    • Choose Another AWS Account.
    • Enter the AWS Account ID provided by Qrvey (e.g., 6381xxxxxxxx).
    • (Recommended) Check Require MFA for this role.
  6. Attach the AdministratorAccess policy.
    This permission is needed for deployment, but can be removed after the platform is deployed (1–2 days). For limited access, use the permissions in this policy document.
  7. Enter a name and add tags (optional).
  8. Click Create Role.
  9. Go to Roles > [Role Name] to view details.
  10. Copy the link to switch roles in console URL.
  11. Send this AWS IAM Role URL to Qrvey’s deployment team.
    Sample email body (send to help@qrvey.com):
IAM Crossaccount role URL: https://signin.aws.amazon.com/switchrole?roleName=QrveyxxxxxRole&account=9653xxxxxxxx

Step 3: (Optional) Create a New VPC

Qrvey can be deployed into an existing VPC and subnets, supporting various combinations of public and private subnets. For simplicity, use the Default VPC or create a new one:

  1. Log in to the AWS console.
    Ensure your user has permissions to create a VPC and related resources.
  2. Select the AWS region for deployment.
  3. Go to the AWS VPC Service Console.
  4. Click Create VPC to open the wizard.
  5. Select:
    • Resources to create: VPC and more
    • Name tag auto-generation: Enter a name for reference.
    • IPv4 CIDR block: Choose a unique block (minimum /26). Avoid overlaps if planning VPC peering.
    • Number of Availability Zones (AZs): Select 2 or more.
    • Customize AZs: Change or leave as default.
    • Number of public subnets: Match the number of AZs.
    • Number of private subnets: At least 2 if using private subnets for database connections.
    • Customize subnets CIDR block: Adjust or leave as default.
    • NAT gateways ($): For private subnets, select at least one AZ (for production, one per AZ is recommended).
    • Leave other settings as default.
  6. Review settings and click Create VPC.
    Wait for the VPC to be created.
  7. In the Subnets tab, find your new VPC.
  8. For each public subnet, enable Auto-assign public IPv4 address:
    • Select a subnet.
    • Click Actions > Edit subnet settings.
    • Toggle on Enable auto-assign public IPv4 address.
    • Click Save. Step3.8.b

Step 4: Move SES out of Sandbox (Optional)

  1. Follow AWS documentation to create a verified Domain identity.
  2. Follow AWS documentation to Request Production Access to move your account out of the SES Sandbox.

Final Step

Once deployment is complete and verified, Qrvey’s deployment team will email you the following:

  • Account Credentials:
    • Composer:
      • API Key
    • Admin Portal:
      • Username
      • Access Key
    • Data Router:
      • API Key
      • S3 Bucket
    • Widgets:
      • Launcher URL
      • ANView URL
    • Elasticsearch URL