Introduction

This article provides the FlexNet Operations Cloud IP addresses for network block or IP address allow list.

Need to Know

A new set of network blocks is being used by FlexNet Operations Cloud services. The networks block addresses differ based on the deployment environment your FlexNet Operations Cloud is hosted on.

Best Practices

If you use an IP allow list, we advise using IP blocks instead of individual IP addresses as the IP addresses for a given connection may change from one call to the next. We strongly recommend sharing the following IP blocks with your IT team to add to your network block.

For FlexNet Operations Cloud ALM instances:

IPv4:

• AWS NAM: 185.146.155.0/24

IPv6:

• AWS NAM: 2620:122:f003::/48

-OR-

NOTE: It is no longer necessary to specify an IP address block for the Disaster Recovery (DR) environment.

For FlexNet Operations Cloud LLM instances:

We are in the process of migrating FlexNet Operations LLM to AWS. We advise adding the following IP blocks to your network block to prepare for the upcoming migration.

IPv4:

• AWS NAM: 185.146.155.0/24

IPv6:

• AWS NAM: 2620:122:f003::/48

-OR-

NOTE: It is no longer necessary to specify an IP address block for the Disaster Recovery (DR) environment.

For any API integrations responses are sent from the below IPs.  These IPs may also need to be allowed so that responses may be received.

52.43.135.7
44.235.13.37
54.148.227.21

Frequently Asked Questions

Understanding IP Allow Listing for FlexNet Operations Cloud

Q: Why do we need to allow list these blocks?

A: If your organization, or your customers, operate strict firewall rules then you should allow these IP address blocks.

Q: Who should we speak to about allow listing?

A: You should discuss your needs with your IT administrators, who typically maintain these allow list rules. If you require further information, please contact Revenera Technical Support.

Q: Which FlexNet Operations Cloud services are affected if an allow list is configured?

A: All services can be impacted if you are using an allow list. Examples include:

• Your employees connecting to the Producer Portal UI
• Your end customers connecting to the Customer Portal UI
• Your CRM system calls FNO Web Services
• Your end customers' devices or Local License Servers making call-home or synchronization connections to FNO
• Your end customers' devices connecting to Cloud License Servers to make Capability Requests

Q: Why do we need to configure an entire block – can't we just allow the IP address associated with the end point we use?

A: Our advice has always been to configure the block. When we move to AWS, this is even more important, because AWS does not allocate static IP addresses; the IP address allocated to a URL can change dynamically.

Understanding the AWS Migration's Affect on FlexNet Operations Cloud Allow Listing

Q: When will these changes take place?

A: The IP addresses were assigned on 2022-11-23 and as FlexNet Operations services were migrated over to the new AWS environment, we reminded customers to add these IP blocks to their network block to ensure continued access to FlexNet Operations services.

Q: Why can't you continue to use the old IP address blocks indefinitely instead of using the new IP address blocks?

A: Using the legacy IP address blocks involves complex routing rules which will impact performance, and so we must move to the new blocks  as part of the AWS migration.

Q: What will happen if the addresses are not added to the allow list?

A: If you or your customers impose strict firewalls rules, FlexNet Operations and its services may not be accessible.