Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

VPC, subnets and Availability Zones

Configure your AWS VPC to integrate Qlik within your environment.

A Virtual Private Cloud (VPC) is a logically isolated network that enables you to control how AWS resources, such as databases and compute instances, connect to each other and the internet. Each VPC is created within a single AWS region.

Subnets are subdivisions of a VPC used to organize and host resources such as Amazon EC2 instances. Subnets can be:

  • Public: Allow direct access to the internet.

  • Private: Restricted to internal communication within the VPC.

Each subnet is created within a specific Availability Zone. For example, in the us-east-1 region, you can create subnets in us-east-1a, us-east-1b, and us-east-1c.

Availability Zones (AZs) are physically isolated data centers within a region. Distributing resources across multiple AZs improves application availability and fault tolerance. It is a best practice to provision resources across at least two Availability Zones to ensure high availability and fault tolerance.

Information noteSubnets created in the VPC configuration must have a valid route that provides outbound internet access. If the subnet is not public, a private subnet should allow outbound access via a NAT/internet gateway.

The relationship between the VPC, subnets, and AZs, ensures that:

  • A VPC is scoped to a single AWS region and spans all Availability Zones within that region.

  • Subnets are bound to individual Availability Zones, providing the ability to distribute resources across zones.

  • You can use this structure to deploy resources across multiple AZs within a VPC to enhance availability and resilience.

Creating a VPC

To create your VPC, do the following:

  1. In the AWS console, go to VPC, Your VPCs.

  2. Click Create VPC and configure it:

    • Resources to create: Select VPC and more.

    • Number of Availability Zones: Click on the number you require.

    • Number of public subnets: Set the required number of subnets.

    • Number of private subnets: Ensure the value is set to 0.

    For each subnet, ensure the parameter Auto-assign public IPv4 address is set to Yes.

  3. Click Create VPC.

    When the VPC has been created, the list of entities is shown.

  4. Make a note of the VPC ID, and CIDR range of the VPC.

  5. Make a note of subnet IDs that were created.

  6. Click each subnet to discover its Availability Zone, and make a note. 

You should now have:

  • A VPC ID.

  • The CIDR range of the VPC

  • The list of subnets and the Availability Zone of each subnet.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here