Introduction When you running your workloads on any public cloud, protecting your network, data, instance from prying eyes and hands is one of the most important things. But whenever you need to access public services offered by a cloud, one has to go through the internet. When your data is going through the internet, your network/instance(if not using NAT) and data are exposed to the public. Is there a way to access public services offered by a public cloud safely, securely and with the same performance and high availability? So if you are using Oracle Cloud Infrastructure(OCI), look no further, your answer is Service Access Gateway(SGW). OCI users can access all these services directly from their Virtual Cloud Network(VCN) with private Subnet without any NAT, IGW by using SGW(No need to go to the internet). All traffic for these services is routed through OCI's internal network, thus protecting your data/network/instance. How to set up an SGW? This section explains
IBM Cloud Load Balancer(CLB) Introduction. They have couple of other LBaaS services but here we are going talk to about the Cloud Load Balancers. IBM introduced a new Cloud Load Balancer, which is equal to Amazons AWS (elasticity, ssl termination and L7/Application load balancing, auto recovery etc etc). All these in one LBaaS unlike AWS. IBM CLB offers couple of variations which user can apply at the time of CLB creation. For e.g. Select which data center one wants to create the CLB in. User can select a private CLB or Public CLB. Public CLB can be reached from the public networks where as private CLB can only reached within ones private network. For Public CLB one can select which public VLAN one can use. There is an option to use the IBMs public VLAN where customer doesn't have any control or user can select to get the public VAN from their own account, where customer have absolute control over it. Which private VLAN to use. Customize CIPHER for SSL HTTPS support