-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use private AWS NTP service instead of outbound global #2123
Comments
thanks for pointing this out - we can't change the default at this time since that would be breaking, I have made a note for the next breaking release to make it the default. For now, I can add a variable to make this configurable |
This issue has been resolved in version 18.26.0 🎉 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a problem? Please describe.
Our network security folks only allow outbound 0.0.0.0/0 access on 80 and 443. NTP to 0.0.0.0/0 violates that rule.
Describe the solution you'd like.
Looks like AWS has a private NTP server.
https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/
Can we use that, please?
The text was updated successfully, but these errors were encountered: