About Google Compute Engine
- What is Google Compute Engine? What can it do?
- Google Compute Engine is an Infrastructure-as-a-Service product offering flexible, self-managed virtual machines hosted on Google. Google Compute Engine includes Linux based virtual machines running on KVM, local and durable storage options, and a simple REST based API for configuration and control. The service integrates with Cloud platform technologies such as Google Cloud Storage, Google App Engine, and Google BigQuery to extend beyond the basic computational capability to create more complex and sophisticated applications.
- How does pricing and purchasing work?
- Google Compute Engine charges based on compute instance, storage, and network use. We offer several compute configurations of 1, 2, 4, 8, and 16 virtual core VMs to pick from, charged hourly. Compute power cost is based on how many VMs you want to use. Storage cost is calculated based on the amount of data you store. Network cost is calculated based on amount of data transferred between VMs communicating with each other and with the Internet. For more information, review our pricesheet.
- Can you explain more about the value of Google Compute Engine?
- We measure the compute power in GCEUs. Based on our benchmarks, one GCEU is at least as powerful as the CPU capacity of a 1.0-1.2 GHz 2007 Opteron. Our analysis of on-demand pricing for similarly configured instance types shows that our customers get significant cost savings with one of the lowest total cost of ownership in the industry.
- How do Google App Engine and Google Compute Engine relate to each other?
- We see the two as being complementary. For example, Google App Engine allows users to control Google Compute Engine cores and offers a web facing front end for Google Compute Engine data processing applications.
- How do I get started?
- Sign up for the service. Once you have completed the sign up process, visit the Overview page to start learning about Google Compute Engine.
Billing and support
- Where can I send feedback?
- For billing-related questions, you can send questions to the appropriate
For general questions unrelated to billing, you can email the Google Compute Engine discussion group, at email@example.com.
- Do your prices include tax?
- No, the price sheet does not include tax.
- Do you offer paid support?
- Yes, we offer paid support for enterprise customers. For more information, contact our sales organization.
- Do you offer a Service Level Agreement (SLA)?
- Yes, we offer a Google Compute Engine SLA.
- How can I authenticate to the Google Compute Engine API?
- You can authenticate to Google Compute Engine using OAuth 2.0.
- What are service accounts?
- Service accounts are special accounts that belong to a project. These
accounts can be used to authorize Google Compute Engine to act on behalf of the
user to access non-sensitive information (a service account is never used to
access user-information). Service accounts simplify the process of
authenticating from Google Compute Engine to other services by handling the
authorization process for the user.
Google offers many types of service accounts, but commonly, users will want to use Google Compute Engine service accounts or Google Developers Console service accounts.
- How do I create a service account?
- To create a service account, create your instance with the
--scopesflag. See service accounts for more information.
- What are projects?
- A project is a container for all Google Compute Engine resources. Each project is a totally compartmentalized world; projects do not share resources, can have different owners and users, are billed separately, and are not any more accessible to each other than your home computer is accessible to your neighbor's computer.
- How can I create a project?
- You can create projects using the Google Developers Console.
- What is the difference between a project number and a project ID?
- Every project can be identified in two ways: the project number or the project ID. The project number is automatically created when you create the project, whereas the project ID is created by you, or whoever created the project. The project ID is optional for many services, but is required by Google Compute Engine. For more information, see the Project resource.
- Where can I find my project ID?
- You can find your project ID on the Google Developers Console, which provides a list of your projects and their project IDs upon entry.
- Can I add Google Compute Engine to an existing project?
- No. Currently, Google Compute Engine can only be enabled for new projects.
- Where can I request more quota for my project?
- By default, all Google Compute Engine projects have default quotas for various resource types. However, these default quotas can be increased on a per-project basis. If you reach the limit for your resources and need more quota, please fill out the quota change request form.
- What kind of machine configuration (memory, RAM, CPU) can I choose for my instance?
- Google Compute Engine offers several configurations for your instance. To list
the available configurations, run
gcloud compute machine-types list.
- if I accidentally delete my instance, can I retrieve it?
- No, it is not possible to retrieve a deleted instance.
- What operating systems can my instances run on?
- Google Compute Engine supports a number of operating systems. You can also choose to import your own image, or build your image and run it on Compute Engine. For more information, see Building a Google Compute Engine image.
- What are the available zones I can create my instance in?
- You can find the current list of zones by running
gcloud compute zones list. More zones will be added as they become available.
- How do I find out how much quota I have used or have left?
gcloud compute project-info describeto lists project information, including quotas, for the project with the Google Compute Engine service enabled. Run
gcloud compute regions describe REGIONto see regional quota information.
- What kind of (virtual) CPU do I have running on my instance?
cat /proc/cpuinfoin your instance to see what CPU that instance is running on.
- How can I send outbound emails from a Google Compute Engine instance?
- Generally, Google Compute Engine blocks outbound traffic through these blocked ports. However, you can set up a mail gateway through Google using ssmtp. For more information, see the networking documentation.
- How can I get the source code for the software included in Google Compute Engine images?
- Google builds images based on well-established open source Linux distributions.
As such, users can use standard mechanisms from within the virtual machine to
download the source for any part of the system.
There currently isn't an automated way to download CentOS source RPMs. However, you can download these from the CentOS source page.
- Do I need to sign up for Google Cloud Storage in order to be able to store my images externally?
- Yes, to store images externally, you need to sign up for Google Cloud Storage.
- I was using GCEL images and I don't see them now. Where are they?
- We have deprecated GCEL images and recommend using Debian images.
- How do I choose the right size for my persistent disk?
- Persistent disk performance scales with the size of the persistent disk. Use the persistent disk performance chart to help decide what size disk works for you. If you're not sure, read the documentation to decide how big to make your persistent disk.
- What steps does Google take to protect my data?
- See Disk Encryption.
- Can I attach my persistent disk to more than one instance?
- Yes, you can attach your persistent disk in read-only mode to multiple instances. Note that you currently you cannot attach a persistent disk to multiple instances in read-write mode. For more information on maintenance windows, see Scheduled Maintenance.
- When should I use persistent disks versus Google Cloud Storage?
- Both persistent disks and Google Cloud Storage can both be used to store
files but are very different offerings. Google Cloud Storage is a massive file
designed to store extremely large amounts of relatively static data which can
be accessed globally, include from Compute Engine virtual machine
The following chart provides some information about the characteristic specialties of each offering and what they are best used for.
Google Cloud Storage Persistent Disk Characteristics
- Global accessibility (including non-Compute Engine systems)
- Accessible read-write from many systems
- Multi-PB scale buckets
- How to use
- REST interface; higher latency than locally attached block storage
- Write semantics include insert and overwrite file only
- Offers versioning
- Files implicit in Google Cloud Storage
- Accessibility in one zone only and only by Compute Engine instances
- Mounted read-write by one instance or read-only by many Compute Engine instances
- 10 TB volume limit
- How to use
- SCSI interface; lower latency
- Write semantics are transactional - random edits
- No versioning; continuous edits
- Must format a filesystem to make usable for files
- Content distribution for mobile, consumer, gaming, and SaaS
- Rich media
- Read-only input for parallelizable HPC work (e.g rendering, oil & gas, and genomics)
- Backup and archival
- Hadoop (via GHFS)
- Compute Engine boot devices
- Raw block datastore to build
- SQL servers (e.g. MySQL)
- NoSQL servers (e.g. Cassandra/Mongo)
- Fileservers (e.g. Gluster)
- Key value store persistence (e.g. Redis)
- Where can I find Compute Engine IP ranges?
- Google Cloud Platform uses a large range of IP addresses, which change
over time. For historical reasons, Google Cloud Platform publishes its list
of public IP addresses in an SPF record for
When you need the literal IP addresses for Google Cloud Platform, use one of the common DNS lookup commands (
host) to retrieve the TXT records for the domain
$ nslookup -q=TXT _cloud-netblocks.googleusercontent.com 220.127.116.11
This returns a list of the domains included in Google's SPF record, such as:
_cloud-netblocks1.googleusercontent.com, _cloud-netblocks2.googleusercontent.com, _cloud-netblocks3.googleusercontent.com
Next, look up the DNS records associated with those domains, one at a time:
$ nslookup -q=TXT _cloud-netblocks1.googleusercontent.com 18.104.22.168 $ nslookup -q=TXT _cloud-netblocks2.googleusercontent.com 22.214.171.124 $ nslookup -q=TXT _cloud-netblocks3.googleusercontent.com 126.96.36.199
The results of these commands contain the current range of addresses.
- Do I have the option of using a regional data center in selected countries?
- Yes, Compute Engine offers data centers in the United States, Europe, and Asia. These data center options are designed to provide low latency connectivity options from those regions.
- How can I tell if a zone is offline?
- There is a Service Status page in the
Google Developers Console that shows the status of all
of our zones. In addition, you can get the status of zones through our command
line tool by running
gcloud compute zones list.
- When does my custom startup script run?
- Startup scripts run last during the boot process, at the very end of the BSD init system.
- What are infrastructure maintenance events?
- Google Compute Engine may periodically need to perform scheduled maintenance on zones that may affect your instances. By default, all instances are configured so that these maintenance events are transparent to your applications and work loads. This may cause some performance degradation but your instances will remain online through the maintenance event. For more information, see Scheduled Maintenance.
- How often do scheduled infrastructure maintenance events happen?
- Infrastructure maintenance events don't have a set interval between occurrences, but generally happen once every couple of months.
- How do I know if an instance will be undergoing a infrastructure maintenance event?
- Shortly before a maintenance event, Compute Engine changes a special
attribute in a virtual machine's metadata server before any attempts to live
migrate or terminate and restart the virtual machine as part of a pending
infrastructure maintenance event. The
maintenance-eventattribute will be updated before and after an event, allowing you to detect when these events are imminent. You can use this information to help automate any scripts or commands you want to run before and/or after a maintenance event. For more information, see the Transparent maintenance notice documentation.