By default, the CloudJiffy Platform provides users with Shared Load Balancer, which represents a single entry point for all of the users’ applications, located at a hardware node. However, for more secure and effective work with the production environments, it is recommended to get and process the requests using Public IP address, which allows to form a direct connection between the Internet and specific server within the environment.
It can be attached to any instance in the environment with the application (except Maven), representing more stable solution with less risk to be affected by other application. Also, it opens access to such features as FTP add-on, Custom SSL, WebSockets, etc.
Internet Protocol version 4 (IPv4) is the fourth revision in the development of the Internet Protocol (IP) and the first version of the protocol to be widely deployed.
Internet Protocol version 6 (IPv6) is the most recent IP version, which is an evolutionary upgrade of IPv4 and is designed to fulfill the need of more addresses, provide better multicast routing and simplify processing by routers
In order to bind an external IP address to the required node, I need to choose it within the Environment topology window and turn the Public IPv4 / IPv6 switch on at its central frame.
In order to find the allocated IP, expand the appropriate server string for the list of added nodes to be displayed.
The first row will be the private IP. The second row will have the address of external IPv4 and the third row will have the address for IPv6.
For an environment that is already created, I can also find the option to add/remove Public IP by expanding the environment and reaching to the node for which I want to add/remove the IPs and clicking on the add/ remove option.
- IPv4 service is paid, wherein the cost is taken for every hour of using each Public IPv4.
- IPv6 is free of charge and is only available in India location.
- If I have Public IP enabled for any node in my environment, I can't swap domains for it.