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 were to accidentally delete a production server, this would almost certainly impact your users and business. The 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 applied 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 compute region. This describes our core data centers that offer the full set of cloud computing services. They're designed with scale in mind and are ideal for larger production workloads or applications.

• Distributed compute region (Limited Availability). These centers deliver limited compute capabilities in difficult to reach locations that are under-served by traditional cloud providers. You can set up a compute instance in these regions. So you can target them to create an image.

Check out our detailed, Akamai Connected Cloud map.

📘

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. A captured image is stored as follows:

• The target compute instance is in a core compute region. The resulting image is stored in that same core compute region.

• The target compute instance is in a distributed compute region The image is stored in the core compute region that's geographically closest. For example, if you have a compute instance in the Houston, TX distributed compute region, an image taken of it is stored in the Dallas, TX core compute region.

Regions and uploaded custom images

When you upload a new custom image, you select a specific core compute region where you want it stored.

You can't upload an image to a distributed compute region.

Regions and recovery images

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

• A recovery image from a core compute region. The recovery image is stored in the same core compute region where its deleted compute instance was located.
• A recovery image from a distributed compute region. The recovery image is stored in the core compute region that is geographically closest to the distributed compute region.

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 compute regions or distributed compute regions.

Region support matrix

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:

• Create an image. Create a new image.
• List images. View all of your images.
• Get an image. View a specific image.
• Update an image. Update various setting for an existing image.
• Upload an image. Create a new private image instance and get the URL where you can upload image data.
• Replicate an image. Target an existing image and replicate it to another compute region.
• Delete an image. Delete an existing image.

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.