Skip to main content
Route outbound traffic from your Managed BYOC account through AWS Network Firewall so you can inspect and filter it. The firewall is yours: you choose how it’s deployed and you control its rules. This applies to outbound traffic only. To filter inbound traffic, use custom WAF rule groups.

Choose a setup

You configure Network Firewall with settings in the bootstrap you run in your Managed BYOC account. The bootstrap’s instructions walk you through setting them. Use this page to choose a setup and confirm the right settings are set for it. See the settings reference for every setting. Pick one of three setups: You can add Network Firewall during your initial deployment or later. To add it or change setups later, update the settings and re-run the bootstrap. Superblocks wires the firewall into your instance at the next deployment.

Bring your own firewall

Use a Network Firewall you already deploy and manage. Managed BYOC routes outbound traffic from each availability zone’s public subnet through your firewall endpoint instead of directly to the internet gateway. This applies to both the control plane and data planes. The bootstrap creates the Managed BYOC VPC, so set up the firewall in this order:
  1. Run the bootstrap without any firewall settings. This creates the Managed BYOC VPC.
  2. Deploy your Network Firewall with an endpoint in the Managed BYOC VPC for each availability zone Managed BYOC uses.
  3. Set your firewall endpoint for each availability zone, keyed by AZ ID. Use AZ IDs such as usw2-az1, not AZ names such as us-west-2a. For example:
  4. Re-run the bootstrap. Superblocks wires the firewall into your instance at the next deployment.
Your firewall rules must allow the required outbound domains, or Managed BYOC can’t reach the services it depends on. Don’t turn on the bootstrap-managed firewall when you bring your own. The two setups can’t be combined.

Bootstrap-managed firewall

Have the bootstrap create the firewall for you. It creates firewall subnets and endpoints in the Managed BYOC VPC and routes outbound traffic, and the return traffic from the internet gateway, through them. It filters control plane traffic only, not traffic from data planes.
  1. Turn on the bootstrap-managed firewall.
  2. Give each availability zone a firewall subnet with exactly one IPv4 CIDR. For example:
  3. Run the bootstrap. Superblocks wires the firewall into your instance at the next deployment.
The firewall policy starts by passing all traffic. You manage the rules yourself in AWS, outside the bootstrap, and re-running the bootstrap doesn’t overwrite them. Your rules must allow the required outbound domains. To have the bootstrap enforce an allowlist for you instead, use the default allowlist.

Use the default allowlist

With a bootstrap-managed firewall, you can have the bootstrap enforce the Superblocks default allowlist. Outbound control plane traffic is then blocked unless it’s going to an allowed domain. Traffic from data planes isn’t filtered. For example:
To see the allowlist the firewall is enforcing, read the bootstrap’s network_firewall output. For example:

Increase the rule group capacity

AWS fixes a rule group’s capacity when it’s created. Raise the rule group capacity setting before adding enough extra domains to exceed it. Changing the capacity replaces the rule group, so make the change in two steps:
  1. Turn off the default allowlist and re-run the bootstrap.
  2. Set the new capacity, turn the default allowlist back on, and re-run the bootstrap.

Required outbound domains

The Managed BYOC control plane needs to reach these domains. The default allowlist includes all of them. If you manage your own rules, allow them yourself. Replace <region> with your Managed BYOC AWS region. Also allow the domains your deployment reaches beyond the Superblocks platform, such as your identity provider, the APIs and databases your apps connect to, and any observability destinations you send telemetry to.

Bootstrap settings reference