--- title: "Using an AWS CloudFormation template to deploy a Network Security instance" slug: "using-an-aws-cloudformation-template-to-deploy-a-network-security-instance" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-10-02T13:43:22Z published: 2026-10-02T13:43:22Z canonical: "docs.trellix.com/using-an-aws-cloudformation-template-to-deploy-a-network-security-instance" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Using an AWS CloudFormation template to deploy a Network Security instance ### Note For more information about AWS CloudFormation, see the Amazon AWS CloudFormation documentation. The following table summarizes the steps to deploy a Network Security instance in AWS using a CloudFormation template. | Task | Description | | --- | --- | | **1**. Ensure that requirements are met. | [AWS requirements](/network-and-platform/docs/aws-requirements) | | **2**. Deploy the CloudFormation template to create the instance. | [Template and instructions](https://community.fireeye.com/CustomerCommunity/s/article/000003336) | | **3**. Start the instance and perform the initial configuration. | [Performing the initial Network Security configuration using AWS](/network-and-platform/docs/performing-the-initial-network-security-configuration-using-aws) | | **4**. Configure IP addressing for the monitoring interfaces on the Network Security instance. | [Configuring monitoring ports on the Network Security instance](/network-and-platform/docs/configuring-monitoring-ports-on-the-network-security-instance) | | **5**. *Inline mode*: Perform the procedures in a supported use case scenario. | [Deploying Network Security instances in AWS in inline mode](/network-and-platform/docs/deploying-network-security-instances-in-aws-in-inline-mode) | | **6**. *TAP or SPAN mode*: Create traffic mirror sessions to copy the traffic from network interfaces. | [Configuring traffic mirroring on AWS for TAP or SPAN mode](/network-and-platform/docs/configuring-traffic-mirroring-on-aws-for-tap-or-span-mode) | | **7**. *Optional*: Enable HTTP health checks for AWS network load balancing (NLB). | Enabling HTTP health checks for network load balancing on AWS | | **8**. *Optional*: If you determine your instance is too small or too large for your needs, you can change the instance type. | [Changing an AWS instance type](/network-and-platform/docs/changing-an-aws-instance-type) | ### Note Network interfaces are placed in the following VRF namespaces: - ether1, ether2—vrf0 - pether3, pether4—vrfA - pether5, pether6—vrfB - pether7, pether8—vrfC - pether9, pether10—vrfD For details about virtual routing and forwarding (VRF), see the "Layer 3 Forwarding Using VRF Instances" information in the *Network Security System Administration Guide*. :