Deploying a Cloud Server is easy. Simply select a server image and a server size and you'll be up and running in minutes. Our server images use standard Windows or Linux operating systems with full root/administrator access, giving you the freedom to configure your Cloud Server however you'd like.
- Geographic options: Choose the data center in which you want your servers deployed, making it easy to establish infrastructure in multiple geographic locations using a single provider
- Complex infrastructure made easy: Provision infrastructure in minutes, without long-term commitments, using our self-service UI or automate your deployment and maintenance tasks with our full-feature REST API
- Wide range of images: Choose from almost 100 server images from “vanilla” OS distributions to pre-built application stacks provided by GoGrid Exchange partners; or, if you like, build and save your own custom images
- Unparalleled standards: Best CPU and I/O performance in the industry, real VLANs and contiguous static IP addresses, high-performance SSD options
- Note: Windows OS versions 2008 and before have an 8 core limit (this is a Windows OS limitation). Windows OS version 2012 and later no longer have this limitation and customers get the full core allocation listed below.
Standard Cloud Server Sizes
|X-Small||0.5 GB||1||25 GB|
|Small||1 GB||1||50 GB|
|Medium||2 GB||2||100 GB|
|Large||4 GB||4||200 GB|
|X-Large||8 GB||8||400 GB|
|XX-Large||16 GB||16||800 GB|
|XXX-Large||24 GB||24||1,200 GB (1.2TB)|
SSD Cloud Server Sizes
|Cloud Server||RAM||Cores||SSD Storage|
|Small SSD||2 GB||2||80 GB|
|Medium SSD||4 GB||4||160 GB|
|Large SSD||8 GB||8||320 GB|
|X-Large SSD||16 GB||16||640 GB|
|2X-Large SSD||32 GB||28||1,280 GB (1.2 TB)|
|4X-Large SSD||64 GB||40||2,000 GB (2.0 TB)|
Raw Disk Cloud Server Sizes
|Cloud Server||RAM||Cores||JBOD Storage|
|Large||8 GB||4||1 x 4 TB|
|X-Large||16 GB||8||3 x 4 TB|
|2X-Large||32 GB||16||6 x 4 TB|
|4X-Large||64 GB||32||12 x 4 TB|
|8X-Large*||128 GB||32||24 x 4 TB|
|16X-Large Dedicated*||240 GB||40||45 x 4 TB|
(*)Contact Sales if you're interested in these options.
High RAM Cloud Server Sizes
|Cloud Server||RAM||Cores||SSD Storage|
|X-Large||16 GB||4||40 GB|
|2X-Large||32 GB||8||40 GB|
|4X-Large||64 GB||16||40 GB|
|8X-Large||128 GB||28||40 GB|
|16X-Large||256 GB||40||40 GB|
Data Center Availability
Standard Cloud Servers are available in all data centers. High-Performance Cloud Servers are available in US-West-1.
Supported Operating Systems
You can find supported OSs here.
Some of our larger Cloud Servers (SSD / Raw Disk / High RAM)only support a limited set of Operating Systems.
|x64 OS||64 GB RAM||128 GB RAM||240 / 256 GB RAM|
SSD Cloud Servers
GoGrid SSD Cloud Servers work well for high I/O use cases. These servers offer options with higher RAM capacities than our standard servers (up to 64 GB) and higher storage capacity on attached high-performing SSDs. All these servers run on our high-performance fabric, which provides for 10 Gbps of redundant public and private network traffic. They are also optimized for our Block Storage service. They are available as hourly, monthly, or annual servers. These servers work best for:
- Caching Servers
- NoSQL applications (like Riak and MongoDB)
- Application servers that require high and consistent I/O
- Applications that require high-performance block storage
High RAM Cloud Servers
GoGrid High RAM Cloud Servers are designed for applications that can take advantage of large available memory and don't require much local storage. You can deploy up to 256GB of RAM. Local storage is on high I/O SSD and is fixed at 40GB for all High RAM Cloud Servers. All these servers run on our high-performance fabric, which provides for 10 Gbps of redundant public and private network traffic. They are also optimized for our Block Storage service. They are available as hourly, monthly, or annual servers. These servers work best for:
- Caching Services
- NoSQL Databases that can use a lot of memory (e.g. MongoDB)
- Application servers that require high and consistent I/O but not much local storage
- Applications that require high-performance block storage
Raw Disk Cloud Servers
Raw Disk Cloud Servers are designed to work with distributed applications that don’t require RAID because failover and redundancy are handled at the application layer. Raw Disk Cloud Servers offer massive storage at the expense of isolated redundancy. Your application must be able to handle replication across multiple nodes to compensate for this deficiency. A common example of this situation is Hadoop. Hadoop Data Nodes are often deployed on servers with JBOD because data is automatically replicated across multiple nodes. SSD or Standard Cloud Servers can be used as the Name Node. Raw Disk Cloud Servers can also be used for:
- Cluster computing - when large raw storage is important, such as when using Hadoop
- Large storage arrays – any software that is designed to replicate objects or files across nodes can leverage these servers to store a massive amount of data
Like SSD Cloud Servers, Raw Disk Cloud Servers are built on our High-Performance Fabric. These servers will have a redundant 10 Gbps public and private network. Each volume is a dedicated physical disk. It's also optimized for Block Storage if you require more capacity. All the disks are attached but not mounted. You should follow the instructions below to format and mount your Raw Disk volumes. Note that when saving your Cloud Server as a MyGSI, only the logical volume (and not the JBODs) are saved. The logical volume (the OS drive) is SEPARATE from the Raw Disks. Therefore any failures on the Raw Disks will have NO impact on the OS.
Configuring your JBODs
To find your volumes run fdisk –l. You should see them attached as devices. They will appear as 4TB devices because all the attached raw disks are that size. It most cases, the first volume will be called “/dev/xvdfa” and each volume will be an iteration of that (e.g. xvdfb, xvdfc). You may also see some that start with "hd" - in that scenario your first raw disk volume will be "/dev/hdc".
Disk /dev/xvdfa: 4000.8 GB, 4000787030016 bytes255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/xvdfa doesn’t contain a valid partition table
You’ll see an entry similar to this for all disks attached to your cloud server.
If you're just using these volumes as a data disk (which is the expected usage for Hadoop), then you can just format the drive and not create a partition. If you do need to create a partition, follow the instructions below. To format the drive, enter this command:
Mounting the Drive
You’ll need to create a new location for the new drive on the file system. For example, you can create a directory called “mydisk1”.
Once you have the directory created, then you can mount your disk:
mount /dev/xvdfa /mydisk1
You should now be able to read and write files in your mydisk1 directory. If you run df- h then you will see your drive and the mydisk1 mount point.
Making the Drive Permanent
The steps above are core to getting the new device up and running, but if you want the drive to mount automatically following reboots, you'll need to add a line to your “/etc/fstab” file.
/dev/xvdfa /mydisk1 ext4 defaults,nobootwait,noatime 0 0
This is a slight change from the typical “fstab” entry - nobootwait prevents Linux from stalling the boot if the share doesn't exist. “0 0” means no automatic backup (if activated on your cloud server) and no automatic file system check. If you leave both of these options turned on, it’ll cause the cloud server to stall. Noatime prevents reads from turning into unnecessary writes which helps improve performance (this is an optional setting, typically recommended for Hadoop).
Reboot and verify that you still see the drive and mount point. The easiest way is to just run df –h. It will look like this:
Filesystem Size Used Avail Use% Mounted on /dev/xvda2 36G 1.3G 33G 4% / udev 7.8G 12K 7.8G 1% /dev tmpfs 3.2G 224K 3.2G 1% /run none 5.0M 0 5.0M 0% /run/lock none 7.9G 0 7.9G 0% /run/shm /dev/xvda1 184M 42M 133M 25% /boot /dev/xvdfa 3.6T 196M 3.4T 1% /mydisk1
Partition the drive (optional)
One you have found your disk, you can create one or more partitions on the disk. Although it’s common to use fdisk to partition and format drive, fdisk only supported 2 TB partitions. In order to create a partition that is 4 TB large, you’ll need to use GNU parted. In general, Hadoop is expecting to have a partition that is the size of the entire disk. If you get get an error when attempting to use parted, it may not be installed.
Centos / Red Hat
# sudo yum install parted
Ubuntu / Debian
# sudo apt-get install parted
parted /dev/xvdfa GNU Parted 2.3 Using /dev/xvdfa Welcome to GNU Parted! Type 'help' to view a list of commands. (parted)
First make sure to create a GPT partition table with the mklabel command:
(parted) mklabel GPT Warning: The existing disk label on /dev/sdb will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? yes (parted)
Create the partition by entering the following command:
(parted) mkpart Partition name? Partition type? primary/extended? primary File system type? [ext2] Start? 0% End? 100%
For partition name, you can a value or leave it blank. For partition type you'll most likely want to enter primary, however you'll most likely not get prompted for that when your partition is set to GPT. Although it will prompt for a file system (ext2), mkpart doesn’t lay down the file system so just hit enter. For the start and end, it will accept percentages. Enter 0% for start and 100% for end to create a partition that spans the entire drive. Once your partition is created (xvdfa1)then you can lay down a file system. If you're using these cloud servers for Hadoop, ext3 has been extensively tested (it's been publicly tested on Yahoo's cluster) but ext4 should also work (and should have better performance with large files).
Follow the mounting and /etc/fstab instructions described above. The only difference is that you'll reference the partition (xvdfa1) instead of the volume.
GoGrid Cloud Servers can be accessed via the console. This feature is available via the Grid View and List View on the management console. This option is helpful if you're locked out of your server or need to run diagnostics on the machine. You'll need to log in to the GoGrid management console, select the Cloud Server you want to access with the console, and click on the console button. You'll still need to log in as either root or administrator to access the server.
- When you're finished with your session, make sure to log off to prevent others from accessing your servers.
- Only Super User and System User roles can access the console.
- We recommend using Firefox, Chrome, or Safari 6.0 and higher for console access.
- The session is designed to timeout after a certain period for security reasons.
- This feature is designed only to grant access to Cloud Servers via the GoGrid management console.
- You must disable your pop-up blocker to use the console from Grid and List Views.
You can copy MyGSIs to multiple data centers by opening a Support ticket from the management console. For more information see MyGSI Migration.
- Please see the pricing page for current pricing information.
- Please see the billing page for current information related to billing.
See the Cloud Server User Manual for details on deploying a Cloud Server.
See our Support page for information on contacting GoGrid for any questions or issues that arise.
Frequently Asked Questions
- Can I use my own server image?
Yes. See the MyGSI feature to build out images to your liking.
- I want Windows, but I have no interest in IIS or MS SQL. I suppose I could get either server type and just turn off the services I don’t need, and install what I want (PostgreSQL, Java, etc.)?
Yes, you have full Administrator access to your Windows server, which means you can enable or disable the services you want, as well as install other third party applications.
- Can I scale the RAM of an existing Cloud Server?
Yes. You can scale your RAM by following the instructions in the Cloud Server User Manual.
- How do I change the name of one of my servers in the management console?
Once you’ve deployed a server, there is no option for changing its name in the management console; however, you can always change the machine name on the server itself.
- I'm not seeing all the cores that my server is supposed to be allocated.
Cloud Servers with Windows Server OS version 2008 and earlier deployed with 16 GB RAM or 24 GB are assigned 8 cores.
- How do I configure a private IP on my Cloud Server?
If your account has Private Network Automation (PNA) enabled, then all new servers you deploy will have a private IP address assigned. If you don't have PNA enabled, then you can manually enter a private IP address from your private IP block. See the Assigning Static IPs page for information on how to do so. It's the same process for Cloud Servers.
- I'm an existing customer and my Cloud Servers are not being assigned private IPs. Why?
You need to have PNA enabled to have private IP assigned to them. If you're an existing customer and want this feature, please file a Support ticket. Note that even when you have PNA enabled, only new servers have IPs assigned. Your existing servers will remain unchanged.
- Can I order more IP addresses?
Yes, but we have a policy limit of 8 IPs per server deployed. Public (IPV4) Internet addresses are a scarce resource. There is only a limited amount of public IP space available, and GoGrid is committed to helping use that space efficiently. You can file a request for additional IPs through the management console. Any increases will be specific to the region for which they've been requested and the per server limit still applies. You must keep the minimum number of servers running in your account while you have these additional IPs.
- Can I have more than one IP per server for web hosting?
We require that users implement name-based virtual hosts to host multiple domains off of a single server. An exception is made for multiple SSL sites.
- Can I console into GGDS?
Console access is designed for Cloud Servers. You cannot console into GGDS. If you need this type of access, contact Support and request KVM over IP.
- What is the warning I see when I log into the console?
This is just a reminder that you need to log off your server and not just close the console window. Closing the console window doesn't automatically log you off your server. You need to do that yourself. The session does time out, but only after a specified period of time.
- Can I have more than one console session open to one machine?
Not at this time.
- Can I mount an ISO image via the console?
No, that is not a feature of this product.
- I've locked myself out of my server accidentally by blocking SSH. Can console help me?
Yes, you can access your server via the console if you've accidentally blocked your SSH port via a firewall. If you're using GoGrid's Firewall Service, you can unblock that port by editing the security group associated with that the Cloud Server.
- I forgot the password to my server. Can I get in via console?
You still need to enter your password to access a server via the console, so you won't be able to get in this way.
- I can't seem to console into Ubuntu 12!
Our Ubuntu 12 image does not allow console support out of box. It will have console support in a future release. You'll currently see a blank screen. If you'd like to enable console support for your Ubuntu 12 cloud server, please execute the following shell commands as root on the target server:cat > /etc/init/tty1.conf <<ENDOFCONFIG # tty1 - getty # # This service maintains a getty on tty1 from the point the system is # started until it is shut down again. start on stopped rc RUNLEVEL= and ( not-container or container CONTAINER=lxc or container CONTAINER=lxc-libvirt) stop on runlevel [!2345] respawn exec /sbin/getty -8 38400 tty1 ENDOFCONFIG initctl start tty1
Once this is executed, you can use our console functionality on your Ubuntu 12 cloud server!
- I don't see the console button.
You may be using an unsupported browser. We recommend using Firefox, Chrome, or Safari version 6.0 and higher. Internet Explorer is currently not supported.
- Can I boot Windows into Safe Mode?
Yes, if you reboot your Windows Cloud Server you should see the boot screen where you will have the option of booting into safe mode. This may not work on all versions of Windows.
- When I console into Ubuntu or Debian, I sometimes see a blank screen. What do I do?
Press "Enter" and you will be presented with the login prompt.
- When I console into my server, I see a warning that it is not compatible with the console. What do I do?
This particular server may need to be migrated. Contact support for help.
SSD Cloud Servers
- Can I use the Dynamic Load Balancers with the SSD Cloud Servers?
Yes, you can use SSD Cloud Servers as real servers behind a DLB. However, because the the DLB is on the standard network, your traffic to that SSD Server will be at 1 Gbps and NOT 10 Gbps.
- What does it mean that the SSD and Raw Disk Cloud Servers are optimized for Block Storage?
Block Storage is network attached so the speed of the network impacts performance. The SSD and Block Storage Cloud Servers use the high-performance fabric that has a very fast connection to Block Storage that is physical local so there is more bandwidth and fewer hops than with standard Cloud Servers.
- Can I deploy the Small SSD Cloud Server on Windows?
The Small SSD Cloud Server doesn't support Windows 2008/2012 at this time.
Raw Disk Cloud Servers
- Can I deploy Windows on the Raw Disk Cloud Servers?
Not at this time. Raw Disk supports x64 Linux.
- How will the Raw Disk Cloud Server storage appear in the OS?
Each disk allocated to a Cloud Server will appear as a separate volume.
- I don't see the 8X-Large or 16X-Large Raw Disk Cloud Server in the management console. How do I order it?
Contact Sales if you are interested in ordering these options.
- Are the Raw Disk volumes an allocation from a block device?
No, each Raw Disk volume is a dedicated physical disk that is direct attached to the Cloud Server.
- I don't see my Raw Disks.
Each Raw Disk volume is attached but not formatted or mounted. Follow the Raw Disk instructions to format and mount a Raw Disk volume.
- Can I configure my Raw Disk volumes with RAID?
Each Raw Disk volume is direct attached so there is no hardware RAID controller. You can apply a software RAID, but you'll need to use a Cloud Server that has more than one volume attached.
- When I save to a MyGSI, is the data on the JBODs saved also?
No, the MyGSI process only saves the logical volume (the OS disk).
- Can I RAM scale Raw Disk Cloud Servers?
Yes, you can RAM scale HOURLY Raw Disk Cloud Servers. In some cases, there will not be enough capacity to successfully complete the scale and the process will not complete.
- Can I attach a block device to my Raw Disk Cloud Server?
The Raw Disk Cloud Servers are on a fabric that is optimized for block storage. However, attaching block storage devices are not supported at this time.
- Can I deploy a MyGSI that I saved from another server?
Yes, but only other Raw Disk MyGSIs. MyGSIs from other servers like Standard Cloud Servers and SSD Cloud Servers can't be deployed as Raw Disk Cloud Servers. You can deploy a MyGSI saved from a Raw Disk Cloud Server to other server flavors (Standard and SSD). This matrix documents this functionality.
- I can't seem to deploy larger than 32GB on Debian 10 x64.
This currently a limitation of that version of Debian. If you need to deploy Debian on a larger Raw Disk Cloud Server, try Debian 12.
High RAM Cloud Servers
- Can I deploy Windows on the High RAM Cloud Servers?
Not at this time. High RAM supports x64 Linux.
- How can I get more storage for my High RAM Cloud Server?
All High RAM Cloud Servers have storage set at 40GB SSD. If you require more storage, you can attach a Block Storage volume range in size from 100 MB to 12 TB.