November 2015 CloudHub update – now with self-service static IPs

November 10 2015

0 comments 0
motif

The November 2015 CloudHub update allows users to allocate static IPs for their cloud integration applications. If you have applications that need whitelisting, or are subject to network security rules that require a fixed address, then this update will allow you to self service these static IPs without having to raise a support ticket with MuleSoft users will now see a new setting on their application settings page, under the “Static IPs” tab. 

StaticIPsBlog-Image1

The new setting allows a user to set a static IP for the application, and it also shows the number of static IPs allocated to the current Business Group. By default, the number of static IPs allocated to an Anypoint organization is twice the number of production vCores in the organization’s subscription. Administrators can choose to divide this overall entitlement between different Business Groups, similar to how they divide the vCores capacity.

 If a user has global deployment enabled, s/he can allocate static IPs in the different supported CloudHub regions, and if they do so, their application settings will reflect the different static IPs that have been allocated in different regions.

StaticIPsBlog-Image2

If an application has static IPs reserved in multiple regions, it will pick up the IP from whichever region it is deployed to – which allows the user to pre-configure IP rules for multiple regions for disaster recovery (DR) scenarios. The user can also release a static IP that has been allocated to an application in order to free up some of their overall static IP allocation capacity.

The static IP self service feature adds a key new capability to the toolkit of CloudHub users, by allowing them to configure and manage the network security for their applications, in a scalable and resilient fashion.

Related Documents

  1. CloudHub R45 release notes
  2. CloudHub documentation

We'd love to hear your opinion on this post