The Images service lets you store complete disk images in the cloud for quick access in the future.

Retain a disk

Manually capture an image from an existing compute instance's disk, or upload one from an image file you created, outside of ​Akamai​. Both are what we refer to as a Custom Image. For example, you could pre-configure a disk with the exact software and settings you need for your applications and workloads what's known as a "golden image"and then save it as a custom image. You can quickly deploy that custom image to a new or existing compute instance in the future. This saves you the time required to manually set up your entire system after each deployment.

Custom images don't expire and they remain on your account until you manually delete them.

📘

Images aren't intended to serve as a full backup solution. For more comprehensive backups, including automated backups, consider using our Backup Service.

Recover a deleted compute instance

If you accidentally deleted a production server, it would almost certainly impact your users and business. Our Images tool helps with this by automatically saving a temporary Recovery Image on your account after you delete one from a compute instance. You can quickly restore the disk from the recovery image. We offer this service as a convenience. You should adopt a well-rounded backup strategy that involves multiple solutions.

Recovery images have a defined expiration date. After this date, Cloud Manager automatically deletes them. The expiration timeline is typically equal to the number of hours the compute instance was active, up to 21 days.

Regions and images

When you create a new image, it’s stored in a specific compute region. We offer multiple region types to best administer your compute instances. Review these sections to understand how regions can apply to your images.

Region types

There are two region types to consider:

  • Core region. This describes our core data centers that offer the full set or majority of our cloud computing services. They're designed with scale in mind and are ideal for larger production workloads or applications.

  • Distributed Compute region. Also referred to as a distributed location, this data center offers limited computing services in underrepresented geographic areas. You can set up a compute instance in these regions, so you can target them to create a custom image.

Check out our detailed, Akamai Connected Cloud map.

📘

Distributed Compute regions is Limited Availability

You need Distributed Compute region support on your account to maintain compute instances in a Distributed Compute region.

Regions and captured custom images

You can capture an image from an existing compute instance. We store the image using our Object Storage service. There are three scenarios where regions can affect how you capture:

  • The compute instance is in a core region that supports Object Storage. The image is captured and stored in that same region.
  • The compute instance is in a core region that doesn't support Object Storage. The image is captured and stored in a core region that supports Object Storage and is geographically closest to it.
  • The compute instance is in a Distributed Compute region. The image is captured and stored in a core region that supports Object Storage and is geographically closest to it.

Regions and uploaded custom images

When you upload a new custom image, you select a specific core region where you want it stored. Only core regions that support our Object Storage service can be used to store an uploaded image.

You can't upload an image to a Distributed Compute region.

Regions and recovery images

A recovery image can be automatically created when you delete a disk from a compute instance. They’re stored as follows:

  • Core region. The recovery image is stored in the same core region where its deleted compute instance was located. Recovery images are not stored using our Object Storage service, so Object Storage availability in a core region doesn't apply.
  • Distributed Compute region. Recovery images are not currently supported for compute instances in Distributed Compute regions.

🚧

If you delete a disk on a compute instance in a Distributed Compute region, a recovery image is not generated. Ensure you want to delete a disk before you complete the operation.

Deploy an image to a region

You can deploy a custom or recovery image to any compute region you have access to. This includes both core regions or Distributed Compute regions.

Region support matrix

TaskCore region w/ Object StorageCore region w/out Object StorageDistributed Compute region
Capture a custom imageYes.Yes.Yes.
Store a captured imageYes. The captured image is stored in the same core region where it was taken.No. The captured image is stored in the core region that supports Object Storage, and is geographically closest.No. The captured image is stored in the core region that supports Object Storage, and is geographically closest.
Upload a custom imageYes. You pick a specific core region where you want to store the image.No. You can't store an uploaded image in a core region that doesn't support Object Storage. (These regions aren't available for selection when uploading an image.)No. You can't upload a custom image to a Distributed Compute region.
Save a recovery imageYes. This happens automatically when a compute instance is deleted from a core region.Yes. This happens automatically when a compute instance is deleted from a core region.No. Distributed Compute regions don't support recovery images.
Store a recovery imageYes. The recovery image is stored in the same core region where it was deleted. Recovery images don't use Object Storage.Yes. The recovery image is stored in the same core region where it was deleted. Recovery images don't use Object Storage.No. Distributed Compute regions don't support recovery images.
Deploy an imageYes. You can deploy a stored image to any core region.Yes. You can deploy a stored image to any core region.Yes. You can deploy a stored image to any Distributed Compute region.

Recommended workloads

Here are some example workloads where the Images service might help you:

  • If you're a web or software agency that deploys similar starter configurations for clients.
  • If you have development workflows that require the same base image for all developers or applications.
  • If you have workflows that use cloud-computing distributions other than those provided by Akamai Cloud Computing

Pricing

  • Custom Images. You need to manually create these. They cost $0.10/GB per month.
  • Recovery Images. Cloud Manager generates these automatically after you delete a compute instance. They're provided at no charge, but have a limited lifecycle.

Technical specifications

Specifications and requirements vary, based on how you create an image:

  • Capture an Image. This describes the process of targeting an existing compute instance to create the image.

  • Upload an Image. This describes the process of creating an image "instance," and manually uploading your own disk image to it.

Developer resources

Linode API

Linode’s API v4 lets you programmatically manage the full range of our products and services. It offers several operations you can use to interact with your images:

Linode CLI

The Linode CLI is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use and install the Linode CLI to get started.