Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Firewall: whitelist Netlicensing Services IP address(-es) #44

Closed
r-brown opened this issue Mar 12, 2022 · 1 comment
Closed

Firewall: whitelist Netlicensing Services IP address(-es) #44

r-brown opened this issue Mar 12, 2022 · 1 comment
Labels
question Further information is requested

Comments

@r-brown
Copy link
Member

r-brown commented Mar 12, 2022

Question

When the services are calling the validation url (https://go.netlicensing.io/core/v2/rest), sometimes the request gets blocked, because it is on a new ip address.
Could you provide us a range of ip addresses that you are using, so we can update the our security settings

@r-brown r-brown added the question Further information is requested label Mar 12, 2022
@r-brown
Copy link
Member Author

r-brown commented Mar 12, 2022

Public NetLicensing Services use the dynamic IP range provided by AWS (which allow us flexible deployment and better scaling). So, there is no stable static IP address available for NetLicensing.

Please refer to the AWS IP address ranges

We advise specifying the ranges for "eu-west-1" region in your FW whitelist policies; as this is the region we use to deploy NetLicensing services. AWS uses the above ranges to assign one of the available IPs dynamically.

@r-brown r-brown closed this as completed Mar 12, 2022
@Labs64 Labs64 locked and limited conversation to collaborators Oct 30, 2023
@r-brown r-brown converted this issue into discussion #126 Oct 30, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question Further information is requested
Development

No branches or pull requests

1 participant