Lambda Access

By default, Lambda’s support team will continue to have access to your cluster after hand-off. Unless you have strict security requirements, we recommend that you maintain Lambda’s cluster access until you familiarize yourself with the system and onboard new users. Doing so will enable Lambda to resolve issues faster, because our support engineers will be able to quickly log in and trouble shoot. Most customers do not revoke Lambda’s cluster access until several weeks after hand-off.

Ensuring Lambda maintains cluster access

If you’d like Lambda to retain access, ensure the following remain intact:

The lambda remains intact on the FortiGate SSL VPN system and not in a disabled state.
The following public key remains in /home/ubuntu/.ssh/authorized_keys of GPU and head nodes:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK8eOirmDVulbdcuQFXBcQ0KOFeEJGnP369J89jCtuWZ

Removing Lambda’s cluster access

To remove Lambda’s access to your cluster, simply disable the lambda user from the FortiNet admin web panel.