{
  "schema_version": 2,
  "id": "operate/rc/security/database-security/network-security",
  "title": "Network security",
  "url": "https://redis.io/docs/latest/operate/rc/security/database-security/network-security/",
  "summary": "",
  "tags": [
    "docs",
    "operate",
    "rc"
  ],
  "last_updated": "2026-09-25T14:59:57+01:00",
  "page_type": "content",
  "content_hash": "7bec36326cae81f758fe36d03233585eb203984d70fe817c3324fc6e7a3b38ff",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "Redis Cloud supports two types of network security: database-level CIDR allow lists and [VPC](#virtual-private-clouds)-wide CIDR allow lists.\n\nThese features are available in most Redis Cloud configurations, as shown here:\n\n| Cloud provider | VPC peering | IP restrictions |\n|:-------------------:|-------------|-----------------|\n| AWS | Redis Cloud Pro | Paid Redis Cloud Essentials and Redis Cloud Pro |\n| Google Cloud | Redis Cloud Pro | Paid Redis Cloud Essentials and Redis Cloud Pro |\n| Azure | Redis Cloud Pro | Redis Cloud Pro |"
    },
    {
      "id": "ip",
      "title": "IP and subnet restrictions",
      "role": "content",
      "text": "You can restrict database access to a configurable\nset of source IP addresses and subnets. This is roughly equivalent\nto using [iptables](https://en.wikipedia.org/wiki/Iptables) to limit access to a host.\n\nTo restrict a database to a specific set of source IP addresses or subnets, see [Configure CIDR allow list](https://redis.io/docs/latest/operate/rc/security/cidr-whitelist)."
    },
    {
      "id": "virtual-private-clouds",
      "title": "Virtual private clouds",
      "role": "content",
      "text": "A [Virtual Private Cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC) is an isolated set of resources within a [public cloud](https://en.wikipedia.org/wiki/Cloud_computing#Public_cloud), usually having its own subnets and VLAN.\n\nRedis Cloud Pro databases are almost always deployed in a Redis VPC. In most cases, you'll need to create a [VPC peering connection](https://redis.io/docs/latest/operate/rc/security/vpc-peering) to access these databases. A VPC peering connection allows unrestricted network access between two VPCs.\n\nConnection creation and supported features vary by public cloud provider. Learn more about VPC usage for [AWS](#vpcs-with-aws), [Google Cloud](#vpcs-with-google-cloud), and [Azure](#vpcs-with-azure)."
    },
    {
      "id": "vpcs-with-aws",
      "title": "VPCs with AWS",
      "role": "content",
      "text": "Subscriptions that run on AWS support two VPC options. To ensure that that you can securely connect to your database, you need to [create a VPC peering connection](https://redis.io/docs/latest/operate/rc/security/vpc-peering#aws-vpc-peering).\n\nIf you create a VPC peering connection, you can also [configure a CIDR allow list](https://redis.io/docs/latest/operate/rc/security/cidr-whitelist) to allow connections only from specific IP address blocks or security groups."
    },
    {
      "id": "vpcs-with-google-cloud",
      "title": "VPCs with Google Cloud",
      "role": "content",
      "text": "Subscriptions that run on Google Cloud *require* a VPC peering connection. See [Google Cloud VPC peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering#gcp-vpc-peering) to learn how to set up VPC peering for Google Cloud."
    },
    {
      "id": "vpcs-with-azure",
      "title": "VPCs with Azure",
      "role": "content",
      "text": "When you request a Redis Cloud Annual subscription, all databases will be deployed in your own Azure VPC."
    }
  ],
  "examples": []
}