SSH Keys in WPShift

SSH keys are essential for secure communication between your local machine and remote servers. In WPShift, you can add SSH keys at the workspace level, ensuring they are automatically applied to any new servers created within that workspace. However, SSH keys added to the workspace do not retroactively apply to existing servers—they will only be added to servers created after the key has been added.

How SSH Keys Work in WPShift

When you add SSH keys to your workspace, WPShift ensures they are automatically deployed to all new servers you create in that workspace. This streamlines the setup process, allowing you and your team to access servers securely without needing to manually add keys to each individual server.

Key Points

  • Automatic Addition to New Servers: Once an SSH key is added to a workspace, it will be automatically installed on any new servers created in that workspace from that point forward.
  • No Impact on Existing Servers: If a server already exists before the SSH key is added to the workspace, the key will not be added to those servers. You'll need to manually add the key to any existing servers if required.
  • Centralized Management: Manage SSH keys from one location, ensuring consistency across all new servers without repetitive configuration steps.

Adding SSH Keys to Your Workspace

To add an SSH key to your workspace, follow these steps:

  1. Navigate to Workspace Settings:
    In your WPShift dashboard, go to the workspace where you'd like to add SSH keys. Under Workspace Settings, click on SSH Keys.

  2. Add a New SSH Key:
    A form will appear where you can enter the public SSH key. Make sure to give the key a recognizable name (e.g., "John’s Work Laptop") for easy management later.

  3. Confirm and Save:
    After entering the public key, click Save. The key will now be added to the workspace and automatically applied to all newly created servers.

Managing Existing Servers

If you want to add an SSH key to a server that was created before the key was added to the workspace, you will need to manually install it on that server.

Best Practices for SSH Key Management

To ensure your workspace remains secure and efficient, consider these best practices:

  • Remove Unused Keys: If a team member leaves or you no longer use a particular machine, make sure to remove the associated SSH key from the workspace.
  • Use Descriptive Key Names: When adding SSH keys, use names that help you quickly identify the key’s owner or device (e.g., "John's MacBook Pro" or "DevOps Laptop").

By leveraging workspace-level SSH key management in WPShift, you can streamline secure access to all newly created servers and minimize the risk of unauthorized access to your infrastructure.