Connect your AWS account.
Instances run in your account and bill to it. One stack, one role, deletable any time.
One-click setup
about 1 minute1
Open the CloudFormation link
It pre-fills one stack,
velobyte-…, in us-east-1 with a connection ID unique to this sign-in.2
Tick the acknowledgement and click Create stack
AWS creates the role
VelobyteAccess-velobyte-…. It trusts Inferoptimal only together with your connection ID. No keys are exchanged.3
Come back here
The stack reports back and this page flips to Connected by itself. If it has not within a few minutes, enter your account ID below.
Where endpoints launch and quota is read; the stack itself lives in us-east-1 and works in every region.
Status
Checking…1
Not connected
no stack yet
2
Connecting
waiting for the stack
3
Connected
—
Role—
Stack—
Role check—
GPU quota in us-east-1
connect to read it| Family | Model | Quota | Per instance | State | |
|---|---|---|---|---|---|
| Connect your account to read its quotas. | |||||
vCPU quota per instance family and region, read live from AWS Service Quotas.
What the role can and cannot do
Read the templateShow the permissions
Can
- 01See which instance types your account can launch in the chosen region, and read your Service Quotas.
- 02File a quota increase request on your behalf.
- 03Launch, stop and terminate instances it tags
velobyte=1, and read their status. - 04Create one security group tagged
velobyte=1and admit HTTPS to it from Cloudflare's address ranges only.
Cannot
- 01Read S3, databases, secrets or any data in the account.
- 02Touch instances it did not launch, create key pairs, or change attributes of existing resources.
- 03Change IAM beyond the Service Quotas service-linked role, or see your prompts: those travel from Cloudflare straight to your instance.
- 04Survive deletion. Delete the
velobyte-…stack and every permission goes with it.