These tasks are required to deploy BIG-IP® VE in the Google Cloud Platform environment. When you are done, you should be able to send traffic to your application servers through BIG-IP VE.
These tasks are documented in detail later in this guide.
|1||Create firewall rules||You can add firewall rules to your network before you deploy, or to the instance
itself, during or after the deployment.
|2||Deploy BIG-IP VE||Go to Cloud Launcher and select the F5 image you want to deploy.|
|3||Change the external IP to static||When you deploy BIG-IP VE, the external IP address is ephemeral, meaning it changes when BIG-IP VE is rebooted. Change the external IP to static ().|
|4||SSH to BIG-IP VE and set admin password||Use SSH to connect to the BIG-IP VE instance and set an admin password, which will be
used to connect to the Configuration utility.
|5||Log in to the BIG-IP Configuration utility and license, provision BIG-IP VE||Use the admin account to log in to the BIG-IP Configuration utility (https://<public-ip-address:8443>). Then license and provision BIG-IP VE.|
|6||In the BIG-IP Configuration utility, create a pool and virtual server||Create a virtual server, which provides a destination for your inbound web traffic and points to the pool of web servers.|
This management interface may be accessible to the Internet, so ensure it is secure.
For more information about how to connect, see https://cloud.google.com/compute/docs/instances/connecting-to-instance.
A separate web page opens.
BIG-IP VE logs you out.
|Name||A unique name|
|Destination Address/Mask||BIG-IP VE's internal IP address|
|SSL Profile (Client)||clientssl|
|SSL Profile (Server)||serverssl|
|Source Address Translation||Auto Map|
SSH keys are required to connect to an instance of BIG-IP VE.
If you use any of the Google tools (Open in browser window, View gcloud command), keys are created automatically for you. They are copied to BIG-IP VE while they are valid. When they expire, they are removed from BIG-IP VE.
By default, all non-expired keys listed inhave access to the BIG-IP VE instance. You can change this by editing the instance and blocking project-wide keys.
Keys are created and used slightly differently, depending on how you decide to connect.