An SSH public key may be supplied for access. The private key stays on a device or protected key store you control.
Before you start
Use the access and features actually assigned to your account. Keep a rollback or recovery route before changing existing service settings.
Steps
- Create a dedicated supported key with a passphrase, for example using ssh-keygen with the ed25519 key type.
- Give the onboarding workflow only the public key file ending in .pub.
- Test the key while keeping an existing recovery path available.
- Revoke a lost key through the supported control or authorized_keys management, then test that it no longer works.
Verify the result
The new key authenticates and a revoked key is rejected. Keep private keys out of tickets, demos, shared folders and source control.
Help and related information
Contact support, service status, and Customer Access. Never send passwords or recovery codes.