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

CentOS, Chrony, and AWS Ports

· 52CE 我爱测

I'm wondering how to properly configure AWS security to allow chrony to sync system time on a CentOS 7 instance. I was running an earlier version of CentOS 7, which used chrony 1.29.1, and it worked with the below settings. Insta…

问题原文

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

I'm wondering how to properly configure AWS security to allow chrony to sync system time on a CentOS 7 instance.

I was running an earlier version of CentOS 7, which used chrony 1.29.1, and it worked with the below settings.

Instance Security Group: Outgoing UDP on port 123

Network ACL: Incoming UDP on port 123, and outgoing UDP on port 123.

However, when running yum update, or launching a new instance with the latest CentOS 7 release, which includes chrony 2.1.1, I can only get it to sync with the below configuration.

Instance Security Group: Outgoing UDP on port 123

Network ACL: Incoming UDP on all ports, and outgoing UDP on port 123.

What's going on here? Do I really need to allow incoming UDP on all ports for the network ACL now? Is this safe? I'm going to assume yes, because my security group doesn't allow incoming UDP traffic unless it previously established an outgoing connection, right?

Thanks.

已采纳解答

原帖链接 · John Mahowald · CC BY-SA 3.0

No, because acquisitionport can be configured.

Even if the software didn't allow for such convenience, and a firewall didn't allow the return traffic of a flow, you still could open just a ephemeral port range and keep well known services closed.

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

资料来源与适用范围

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

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

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