Skip to main content
NetApp Knowledge Base

How to configure StorageGRID to work with IP based for third-party Layer 7 load balancers

Views:
1,340
Visibility:
Public
Votes:
3
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • StorageGRID Appliances
  • StorageGRID 11.4 or later
  • IP based

Description

  • This article applies to StorageGRID 11.4.0 or later if you are using one or more external Layer 7 load balancers, such as NGINX or HAProxy, and an S3 bucket or group policies that are IP-based, StorageGRID must determine the real sender's IP address.
  • If an external (third party) Layer 7 load balancer is used to route requests to the Storage Nodes, StorageGRID needs to determine the real sender’s IP address. It does this by looking at the X-Forwarded-For (XFF) header, which is inserted into the request by the load balancer.
  • As the X-Forwarded-For header can be easily spoofed in requests sent directly to the Storage Nodes, StorageGRID needs to ensure that each request is being routed by a trusted Layer 7 load balancer. If StorageGRID cannot trust the source of the request, it will ignore the X-Forwarded-For header.
  • In StorageGRID 11.4 or later, a new Grid Management API has been added to allow a list of trusted external Layer 7 load balancers to be configured. This new API is private and is subject to change in future StorageGRID releases.

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.