Stay organized with collections
Save and categorize content based on your preferences.
A mirroring deployment is a zonal deployment of a producer's third-party
appliances. Mirroring deployment acts as a backend to an internal passthrough Network Load Balancer,
providing network services on the traffic mirrored from the consumer networks.
The mirroring deployments are grouped in mirroring deployment groups
across different locations within a project for easier consumption and
management.
This document provides a detailed overview of mirroring deployments and
their capabilities.
Specifications
A mirroring deployment is a project-level resource created at the zonal-level.
You can deploy only one mirroring deployment per zone and group.
Each mirroring deployment is associated with a mirroring deployment group.
You can associate a mirroring deployment with exactly one deployment group.
A mirroring deployment references the forwarding rule that points to the
backend services where the third-party appliances are deployed to provide
mirroring services. This forwarding rule handles the traffic sent to the
mirroring deployment. The forwarding rule must use the network specified
in the mirroring deployment group.
Each mirroring deployment is uniquely identified by a URL with
the following elements:
Project ID: ID of the project.
Location: scope of the mirroring deployment. Location is always
set to the zone it resides in.
Name: mirroring deployment name in the following format:
A string 1-63 characters long
Includes only lowercase alphanumeric characters or hyphens (-)
Must start with a letter
To construct a unique URL identifier for a mirroring deployment, use the
following format:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Mirroring deployments overview\n\nA *mirroring deployment* is a zonal deployment of a producer's third-party\nappliances. Mirroring deployment acts as a backend to an internal passthrough Network Load Balancer,\nproviding network services on the traffic mirrored from the consumer networks.\n\nThe mirroring deployments are grouped in mirroring deployment groups\nacross different locations within a project for easier consumption and\nmanagement.\n\nThis document provides a detailed overview of mirroring deployments and\ntheir capabilities.\n\nSpecifications\n--------------\n\n- A mirroring deployment is a project-level resource created at the zonal-level.\n\n- You can deploy only one mirroring deployment per zone and group.\n\n- Each mirroring deployment is associated with a mirroring deployment group.\n You can associate a mirroring deployment with exactly one deployment group.\n\n- A mirroring deployment references the forwarding rule that points to the\n backend services where the third-party appliances are deployed to provide\n mirroring services. This forwarding rule handles the traffic sent to the\n mirroring deployment. The forwarding rule must use the network specified\n in the mirroring deployment group.\n\n- Each mirroring deployment is uniquely identified by a URL with\n the following elements:\n\n - **Project ID**: ID of the project.\n - **Location**: scope of the mirroring deployment. Location is always set to the zone it resides in.\n - **Name** : mirroring deployment name in the following format:\n - A string 1-63 characters long\n - Includes only lowercase alphanumeric characters or hyphens (-)\n - Must start with a letter\n\n To construct a unique URL identifier for a mirroring deployment, use the\n following format: \n\n projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/locations/\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e/mirroringDeployments/\u003cvar translate=\"no\"\u003eDEPLOYMENT\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: ID of the project\n\n - \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: zone of the mirroring deployment\n\n - \u003cvar translate=\"no\"\u003eDEPLOYMENT\u003c/var\u003e: name of the mirroring deployment\n\n For example, project `2345678432` in zone `us-east1-a` with mirroring\n deployment `example-mirroring-deployments` has the following unique\n identifier: \n\n projects/2345678432/locations/us-east1-a/mirroringDeployments/example-mirroring-deployments\n\nIdentity and Access Management roles\n------------------------------------\n\nIdentity and Access Management (IAM) roles govern the following actions for managing the\nmirroring deployments:\n\n- Creating a mirroring deployment in a project\n- Modifying or deleting a mirroring deployment\n- Viewing details about a mirroring deployment\n- Viewing all the mirroring deployments configured in your project\n\nThe following table describes the roles that are necessary for each step.\n\nQuotas\n------\n\nTo view quotas associated with mirroring deployments, see\n[Quotas and limits](/network-security-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- [Create and manage mirroring deployments](/network-security-integration/docs/out-of-band/configure-deployments)\n- [Mirroring deployment groups overview](/network-security-integration/docs/out-of-band/deployment-groups-overview)\n- [Create and manage mirroring deployment groups](/network-security-integration/docs/out-of-band/configure-deployment-groups)"]]