大网数据广告活动
服务器运维问答

How do I deny access by source IP when behind Amazon ELB or other proxy

· 52CE 我爱测

Nginx has a nice feature that enables you to restrict access to resources by source IP address. However, I've noticed that may not work in situation where nginx is behind a proxy or load balancer. In my case the Amazon ELB. I wan…

问题原文

原帖链接 · hookenz · CC BY-SA 3.0

Nginx has a nice feature that enables you to restrict access to resources by source IP address.

However, I've noticed that may not work in situation where nginx is behind a proxy or load balancer. In my case the Amazon ELB.

I want to provide a status page for datadog agent and the Amazon ELB health checks. So I want to allow local connections and those from the ELB but deny everything else.

The following does not work as expected as it allows traffic originating outside the ELB to access the status page as well. The reason being because the IP will appear to originate from the ELB and the allow rules don't look at the headers to determine the real source of the request. Is there a way to tell nginx what source IP to use to determine allow/deny rules?

location /status {
    stub_status;
    access_log off;
    allow 127.0.0.1;
    allow 10.0.0.0/16;
    deny all;
}

已采纳解答

原帖链接 · hookenz · CC BY-SA 3.0

As pointed out by Michael Hampton. I can use the Real IP Module. I wasn't aware of it.

The following worked.

http { 
    real_ip_header X-Forwarded-For;
    set_real_ip_from 0.0.0.0/0;
}

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-03-09)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。