Skip to content

Commit e29208e

Browse files
authored
[Updated] Cloud Firewall docs for NodeBalancer functionality (linode#6716)
* [Updated] Cloud Firewall docs for NodeBalancer functionality * [Updated] Update Cloud Firewall Status guide with new screenshots
1 parent fb45550 commit e29208e

File tree

22 files changed

+138
-93
lines changed

22 files changed

+138
-93
lines changed

.vscode/settings.json

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
{
2+
"git.autorefresh": false
3+
}

docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshooting Firewall Issues on Compute Instances
33
description: This guide presents troubleshooting strategies for Compute Instances that may be unresponsive due to issues caused by a firewall.
44
keywords: ["Linode troubleshooting", "Cloud Firewall", "Firewall","troubleshoot"]
55
published: 2020-08-04
6-
modified: 2023-03-14
6+
modified: 2023-11-01
77
modified_by:
88
name: Linode
99
bundles: ['troubleshooting']
@@ -38,24 +38,24 @@ Ensure that your Compute Instance is powered on and running.
3838

3939
## Is there a Cloud Firewall Assigned to my Compute Instance?
4040

41-
If you are using Cloud Firewall, then it's important to verify which Cloud Firewall(s) your Compute Instance is assigned to and to check its Cloud Firewall rules.
41+
If you are using Cloud Firewalls, then it's important to verify which Cloud Firewall(s) your Compute Instance is assigned to and to check its Cloud Firewall rules. Likewise, if your Compute Instance is sitting behind a NodeBalancer, you may want to investigate whether or not that NodeBalancer is assigned to any Cloud Firewalls. Note that only inbound rules apply to NodeBalancers.
4242

4343
1. Log into [Cloud Manager](https://cloud.linode.com) and select **Firewalls** from the menu.
4444

45-
1. The Firewalls Listing page displays a list of all the Cloud Firewalls currently active on your account.
45+
1. The Firewalls listing page displays a list of all the Cloud Firewalls currently active on your account.
4646

47-
1. Find the Compute Instance you are troubleshooting under the **Linodes** column to determine which Cloud Firewall(s) is assigned to it.
47+
1. Find the Compute Instance or NodeBalancer you are troubleshooting under the **Services** column to determine which Cloud Firewall(s) is assigned to it.
4848

49-
1. Next, check the **Status** column to confirm that the Cloud Firewalls is **Enabled**.
49+
1. Next, check the **Status** column to confirm that the Cloud Firewall is **Enabled**.
5050

51-
![firewall-home](firewall-listing-non-cmr.png)
51+
![firewall-home](firewall-listing-non-cmr.jpg)
5252

53-
1. If the Cloud Firewall is enabled, check what rules are currently active by clicking on the label of the Cloud Firewall. This takes you to your Cloud Firewall's **Rules** page.
53+
1. If the Cloud Firewall is enabled, check to see which rules are currently active by clicking on the label of the Cloud Firewall. This takes you to your Cloud Firewall's **Rules** page.
5454

55-
1. The **Rules** page displays a list of all of the Cloud Firewall rules that are filtering your Compute Instance's network traffic. If you notice that the Cloud Firewall rules do not allow traffic for a specific service's port that you are troubleshooting, you may consider [updating your rule's](/docs/products/networking/cloud-firewall/get-started/#edit-cloud-firewall-rules) to allow connections for that port.
55+
1. The **Rules** page displays a list of all of the Cloud Firewall rules that are filtering your service's network traffic. If you notice that the Cloud Firewall rules do not allow traffic for a specific service's port that you are troubleshooting, you may consider [updating your rule's](/docs/products/networking/cloud-firewall/get-started/#edit-cloud-firewall-rules) to allow connections for that port.
5656

5757
{{< note >}}
58-
If the Cloud Firewall is assigned to more than one Compute Instance, modifying the Cloud Firewall rules affect all Compute Instances assigned to the Cloud Firewall.
58+
If the Cloud Firewall is assigned to more than one Compute Instance or NodeBalancer, modifying the Cloud Firewall rules affect all services assigned to the Cloud Firewall.
5959
{{< /note >}}
6060

6161
{{< note >}}

docs/products/networking/cloud-firewall/_index.md

+10-8
Original file line numberDiff line numberDiff line change
@@ -3,39 +3,41 @@ title: Cloud Firewall
33
title_meta: "Cloud Firewall Product Documentation"
44
description: "Linode Cloud Firewall offers a simple interface to protect your web apps. It is scalable security in seconds, allowing you to create custom firewall rules, making security more accessible."
55
bundles: ['debian-security', 'centos-security', 'network-security']
6-
modified: 2022-07-13
6+
modified: 2023-11-01
77
tab_group_main:
88
is_root: true
99
title: Overview
1010
weight: 10
1111
cascade:
1212
date: 2020-11-10
13-
product_description: "A free cloud-based firewall service that makes it easy to secure network traffic to and from Compute Instances."
13+
product_description: "A free cloud-based firewall service that makes it easy to secure network traffic."
1414
aliases: ['/guides/platform/cloud-firewall/','/platform/cloud-firewall/']
1515
---
1616

17-
Linode’s Cloud Firewall is a robust cloud-based firewall solution available at no additional charge for Linode customers. Through this service, you can create, configure, and add stateful network-based firewalls to any Linode Compute Instance.
17+
Linode’s Cloud Firewall service is a robust cloud-based firewall solution available at no additional charge for Linode customers. Through this service, you can create, configure, and add stateful network-based firewalls to Linode Compute Instances and NodeBalancers.
1818

1919
## Enhanced Security
2020

21-
A Cloud Firewall sits between a Compute Instance and the Internet and can be configured to filter out unwanted network traffic before it even reaches your server. Defend your apps and services from malicious attackers by creating rules to only allow traffic from trusted sources. Firewall rules can filter traffic at the network layer, providing fine-grained control over who can access your servers.
21+
A Cloud Firewall sits between a service (Compute Instance or NodeBalancer) and the Internet and can be configured to filter out unwanted network traffic before it even reaches your server. Defend your apps and services from malicious attackers by creating rules to only allow traffic from trusted sources. Firewall rules can filter traffic at the network layer, providing fine-grained control over who can access your servers.
2222

2323
## Simple Interface
2424

25-
Control inbound and outbound traffic using the [Linode API](/docs/api/networking), [Linode CLI](/docs/products/tools/cli/get-started/) or [Cloud Manager](https://www.linode.com/products/cloud-manager/). Each interface can be integrated into your workflow for seamless control over firewall rules. Cloud Firewall make security more accessible and enables you to secure your network traffic without needing to learn complicated software or even access the command line.
25+
Control inbound and outbound traffic using the [Linode API](/docs/api/networking), [Linode CLI](/docs/products/tools/cli/get-started/) or [Cloud Manager](https://www.linode.com/products/cloud-manager/). Each interface can be integrated into your workflow for seamless control over firewall rules. The Cloud Firewall service makes security more accessible and enables you to secure your network traffic without needing to learn complicated software or access the command line.
2626

2727
## Scalable Security in Seconds
2828

29-
Stay protected as your network grows. Effortlessly apply the same ruleset across multiple Compute Instances. This saves time as you no longer need to manually configure internal software on each server.
29+
Stay protected as your network grows. Effortlessly apply the same ruleset across multiple Compute Instances and NodeBalancers. This saves time as you no longer need to manually configure internal software on each server.
3030

3131
## Pricing and Availability
3232

3333
Cloud Firewalls are available at no charge across [all regions](https://www.linode.com/global-infrastructure/).
3434

3535
## Limits and Considerations
3636

37-
- Cloud Firewalls are **compatible with all Linode Compute Instances**. They are not currently directly supported on other Linode services, such as NodeBalancers or Object Storage.
38-
- A Cloud Firewall can be attached to multiple Compute Instances but a Compute Instance can only be attached to one *active* (enabled) Cloud Firewall at a time.
37+
- Cloud Firewalls are **compatible with Linode Compute Instances and NodeBalancers**. They are not currently directly supported on other Linode services, such as Object Storage.
38+
- A Cloud Firewall can be attached to multiple services (Compute Instances or NodeBalancers), but a service can only be attached to one *active* (enabled) Cloud Firewall at a time.
39+
- A Cloud Firewall’s inbound and outbound rules are applied to Compute Instances, but only inbound rules are applied to NodeBalancers.
40+
- When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer's public IP, not the IPs of the backend nodes. This means you may also want to add individual backend nodes to a Cloud Firewall to protect any additional exposed IP addresses.
3941
- Cloud Firewall rules are applied to traffic over the public and private network but are not applied to traffic over a private [VLAN](/docs/products/networking/vlans/).
4042
- A maximum of **25 rules** can be added to each Cloud Firewall (both Inbound and Outbound rules combined).
4143
- A maximum of **255 IP addresses (and ranges)** can be added to each Cloud Firewall rule.

docs/products/networking/cloud-firewall/get-started/index.md

+13-5
Original file line numberDiff line numberDiff line change
@@ -7,27 +7,35 @@ tab_group_main:
77
aliases: ['/platform/cloud-firewall/getting-started-with-cloud-firewall/','/guides/getting-started-with-cloud-firewall/']
88
keywords: ["firewall", "cloud firewall", "security", "securing"]
99
tags: ["cloud manager","linode platform","security","networking"]
10-
modified: 2022-07-14
10+
modified: 2023-11-01
1111
---
1212

13-
Linode's free Cloud Firewall service can be used to create, configure, and add stateful network-based firewalls to Linode services. A Cloud Firewall is independent of the service it is attached to and can be applied to multiple services.
13+
Linodes free Cloud Firewall service can be used to create, configure, and add stateful network-based firewalls to Linode services. A Cloud Firewall is independent of the service it is attached to and can be applied to multiple services. Cloud Firewalls are compatible with Linode Compute Instances and NodeBalancers.
1414

1515
## Create a Cloud Firewall
1616

17-
There are two main options to consider when deciding how to protect your Linode Compute Instances: installing a firewall software on your system or using Linode's Cloud Firewall service. While both are robust solutions, a major benefit to using Cloud Firewalls is the ease of configuration. Cloud Firewalls can be created and managed through the Cloud Manager, Linode CLI, or Linode API.
17+
There are two main options to consider when deciding how to protect your Linode Compute Instances: installing firewall software on your system or using Linode's Cloud Firewall service. While both are robust solutions, a major benefit to using Cloud Firewalls is the ease of configuration. Cloud Firewalls can be created and managed through the Cloud Manager, Linode CLI, or Linode API.
1818

1919
- [Create a Cloud Firewall](/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/)
2020

2121
- [Comparing Cloud Firewalls to Linux Firewall Software](/docs/products/networking/cloud-firewall/guides/comparing-firewalls/)
2222

23+
{{< note >}}
24+
NodeBalancers do not support the installation of firewall software. If you wish to configure inbound firewall rules for your NodeBalancer, we recommend using the Cloud Firewall service.
25+
{{< /note >}}
26+
2327
## Manage Firewall Rules
2428

2529
A Cloud Firewall analyzes traffic against a set of user-defined rules. The firewall can be configured to implicitly *accept* or *drop* all *inbound* or *outbound* traffic. Individual rules can be added to further accept or drop specific traffic, such as over certain ports or to/from a certain IP address.
2630

2731
- [Manage Cloud Firewall Rules](/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/)
2832

33+
{{< note >}}
34+
Outbound firewall rules are not applied to NodeBalancers.
35+
{{< /note >}}
36+
2937
## Apply to Compute Instances
3038

31-
To start using a Cloud Firewall to protect your services, you can apply it to Compute Instances. Each Cloud Firewall can be applied to multiple Compute Instances, but a Compute Instance can only belong to a single Cloud Firewall.
39+
To start using a Cloud Firewall to protect your services, you can apply it to Compute Instances or NodeBalancers. Each Cloud Firewall can be applied to multiple services, but a service can only belong to a single Cloud Firewall.
3240

33-
- [Apply a Cloud Firewall to a Compute Instance](/docs/products/networking/cloud-firewall/guides/apply-to-compute-instances/)
41+
- [Apply a Cloud Firewall to a Service](/docs/products/networking/cloud-firewall/guides/apply-to-service/)

docs/products/networking/cloud-firewall/guides/apply-to-compute-instances/index.md

-32
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: "Apply Firewall Rules to a Service"
3+
description: "Learn how to add and remove services from Cloud Firewalls."
4+
aliases: ['/products/networking/cloud-firewall/guides/assign-firewall/', '/products/networking/cloud-firewall/guides/apply-to-compute-instances/']
5+
authors: ["Linode"]
6+
modified: 2023-11-01
7+
---
8+
9+
Each Cloud Firewall can be applied to multiple services (Compute Instances or NodeBalancers). Use the steps below to view and modify the services utilizing a Cloud Firewall.
10+
11+
1. Log into your [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu.
12+
13+
1. From the **Firewalls** listing page, click on the Cloud Firewall that you would like to use. This takes you to the **Rules** page for that Firewall.
14+
15+
1. Click either the **Linodes** or **NodeBalancers** tab to see a list of the respective services currently using the Cloud Firewall.
16+
17+
![Screenshot of the list of Compute Instances attached to the Cloud Firewall](compute-instances-attached-to-firewall.jpg)
18+
19+
## Add a Service
20+
21+
To add a service to this firewall, select either the **Linodes** or **NodeBalancers** tab, and click on the **Add Linodes/NodeBalancers to Firewall** button. In the form that appears, select the desired service from the dropdown menu and click **Add**. Once added, all rules configured on the Cloud Firewall are applied to the selected service. Note that only inbound rules are applied to NodeBalancers.
22+
23+
{{< note >}}
24+
You can apply the Cloud Firewall to more than one Linode service at a time. Repeat this process to add additional Compute Instances or NodeBalancers.
25+
{{< /note >}}
26+
27+
{{< note type="alert" >}}
28+
If [Network Helper](/docs/products/compute/compute-instances/guides/network-helper/) has been disabled on your Compute Instance and the internal networking configuration uses DHCP for IPv4 address assignment, some additional firewall rules are necessary. You must edit the Cloud Firewall to allow DHCP traffic through port 67 and 68. If needed, a full list of IP addresses for our DHCP servers can be found in our [DHCP IP Address Reference Guide](/docs/guides/dhcp-ip-address-reference/).
29+
{{< /note >}}
30+
31+
## Remove a Service
32+
33+
To remove a Compute Instance or NodeBalancer, locate the service within the list and click the **Remove** link. Once removed, the rules configured on the Cloud Firewall are no longer applied to the service and, as such, the service may be less protected against malicious traffic or attacks.

0 commit comments

Comments
 (0)