As the hosting operator, you can give your customers the connection details for their running Linux server through PD AWS Lightsail. This guide explains the control to enable, the client-area steps your customers follow and the checks your team can make when access fails.

Before you start

Check Client: Connection details in the package’s module options for the service you intend to offer this access to. Confirm that the instance is provisioned and Running. Your customer then signs in to the Blesta client area and opens that service.

Have an SSH client available on your computer. A terminal on macOS or Linux can use the connection command shown by the service. Windows users should use an SSH client configured for the downloaded key’s format.

Keep the downloaded private key private. It is an access credential, not an attachment to paste into a support ticket.

Customer steps: get the correct connection details

The following steps take place on the customer’s computer and in their client area:

1. Open your Lightsail service’s management page in the client area.
2. Check the instance’s name, region and running state so you are working with the intended server.
3. Choose Connection details.
4. Read the server address and SSH username shown for this instance. Use those values rather than guessing the username from an example.
5. Download the private key provided for this service and save it in a private location on your own computer.
6. Follow the key-permission instructions in the dialog, then copy its SSH command. Adjust the local key-file location if you saved it somewhere different.
7. Run the command in your local SSH client. Check any host-key prompt against the server fingerprint obtained through a trusted channel before accepting it.

The connection dialog supplies the instance-specific command and key filename. On a Unix-style system, its permission step restricts access to the downloaded key before the SSH client uses it.

Check the result

A successful connection opens a shell on the intended server. Check its hostname before making changes, and close the session when finished.

These steps use your own SSH client. The separate browser-console feature is another access method with its own service settings; you do not need it enabled to use a working direct SSH connection.

If SSH does not connect

If your customer cannot see Connection details, check Client: Connection details in the package’s module options and the affected service’s controls. If the instance is pending or stopped, check that state before treating the result as an SSH authentication failure.

A timeout calls for checking the server address, network reachability and whether its firewall allows your connection. A permission-denied result calls for checking the displayed username, the correct service key and the key file’s permissions. Do not replace the provider account’s AWS credentials to fix a customer SSH login.

A shell login failure may concern the customer’s SSH client, the server’s SSH configuration or its network rules. If the module shows the correct connection details, investigate those layers using your normal hosting-support process. Do not treat every SSH login failure as a module defect.

AWS also provides terminal-based Lightsail SSH guidance.

See the PD AWS Lightsail overview for Blesta for the service-management context.