Compute
Compute is one virtual machine on dedicated cores, launched through an API shaped like Amazon EC2, so the tooling you already have works unchanged.
Compute resources
Section titled “Compute resources”User guide What a machine is made of, how to go from an account to something running, how to choose a shape, and what you have to do yourself.
Developer guide Developer-focused information about using the compute API: endpoint and region, credentials, making and signing requests, pagination, idempotency, error handling, and code examples in five tools.
API reference Every operation in detail — request parameters, response elements, and the errors each can return, with sample requests and responses.
Cheat sheet Every command on one page: setup, launch, connect, storage, teardown, and the four errors you will actually hit.
What is on the shelf
Section titled “What is on the shelf”Instance types Every shape we sell, its size and root disk, and the AWS, GCP, Azure, Alibaba, IBM and OVH names that match it exactly.
Machine images The operating systems on offer, the login user for each, and what “the name rolls” means for your pipeline.
Networking The network, subnet and router your account is given, the default VPC on top of them, security groups, and where addresses come from.
Instance metadata and user data
How a machine learns who it is, the config drive every instance gets, and why a
launch that reports running is not a machine that works.
Related
Section titled “Related”Block storage — volumes to attach, and what the disk underneath actually is.
Quotas and limits — what a new account may consume, and what is not capped at all.
Catalog and availability — what is for sale and whether it is in stock right now.
Platform conventions — authentication, errors, pagination, idempotency and identifiers, which every service assumes.