This page covers the basics you'll want to know before provisioning your first resource on Lightspeed Cloud: how to log in, and how your account is structured.
Logging in
Go to cloud.lightspeedhosting.com.au and sign in with the credentials provided in your initial welcome email. If you've forgotten your password, use the password reset feature on the login page.
Accounts and users
Every customer on Lightspeed Cloud has an account in the self-service portal. If you're working with a team, you can add additional users under your account so colleagues can log in and manage resources without sharing a single login. Each user can be given a role that controls what they're allowed to do - for example, a read-only role for someone who just needs visibility into running resources, versus full access for an administrator on your team.
Two-factor authentication
You can add a second factor to your login from your account settings, either a TOTP authenticator app (Google Authenticator, Authy, etc.) or a static PIN. Once enabled, you'll be prompted for the second factor after your password on every login.
We'd recommend enabling this for any user with more than read-only access, particularly anyone who can create, resize or delete resources.
API access
If you want to automate against Lightspeed Cloud - Terraform, a custom script, or your own tooling - you can generate an API key and secret key pair from your account settings, instead of authenticating with your portal username and password. Requests are signed with the secret key, so it never needs to be sent over the wire.
Keep the secret key somewhere safe once it's generated - treat it the same way you would an SSH private key or a cloud provider credential, since anyone holding it can act on your account within that user's permissions. If a key pair is ever compromised, regenerate it from the same account settings page to invalidate the old one immediately.
Resource limits and quotas
Your account has limits on how much you can provision at once - for example, a maximum number of VMs, total CPU cores, total RAM, public IPs, volumes, snapshots, templates, VPCs and networks. These limits exist to keep usage in line with your plan, and are why a deploy might be refused with a "resource limit exceeded" error even though you'd expect it to succeed.
You can view your current usage against each limit from your account settings. If you're consistently hitting a limit, get in touch and we can raise it for you.
Next steps
Once you're logged in, head to Virtual Machines to launch your first instance.