This article will explain the core concepts of an Engine, including how to create a new engine, with and without a custom delivery address, and the available settings for engines.

Key terms

Engine: an Engine is a relationship among the Delivery Address, ImageEngine Address, and Origin to handle requests and deliver optimized images.

Delivery Address: A Delivery Address is a URL that can be used to access Images for use through ImageEngine.

The Delivery address is used in an image URL, either replacing the original domain name or by prefixing the entire original URL. For more on usage, please see the Implementation overview article! For platform-specific integration guides, please see that section of our support guides

Standard and Pro account users gain the ability to customize the Delivery Address to be a subdomain of a domain that they own.

For instance, if the website is "mycoolwebsite.com", a delivery address such as "images.mycoolwebsite.com" could be created.

If the Delivery Address is not customized, then the Delivery Address is identical to the ImageEngine Address.

ImageEngine Address: The ImageEngine Address handles your account’s images on the imgeng.in domain, and ends with our *.Imgeng.in domain
The ImageEngine Address is the same as the delivery address unless it is a custom address. In this case, the ImageEngine Address must be used in a DNS CNAME record that will pass requests from the custom Delivery Address to the ImageEngine Address.

Origin: Each Engine has an origin, where the images are hosted or stored. The images can be on a web server accessible via HTTP or HTTPS, or cloud-based storage.
ImageEngine does not require you to move or upload images anywhere.

For more on engines please see this article: Image Origins

Graphically, this is what the environment looks like, assuming a customized delivery address:

Create a New Engine

To create a new Engine, go to the Engines list and click on the “Create Engine” button.

You can also use the + sign button in the top left of the navigation bar:

The Create a new engine screen will appear:

Define an Origin

Upon creating a new engine, the first thing that must be done is to select an Origin.

If there are no Origins present, one must be created before the Engine may be created. In the case of multiple pre-existing origins, they may be selected from the drop-down list.

You may always adjust the origin associated with the Engine later if needed!

For more discussion of origins, their creation, and settings please see this article: Image Origins

Complete engine configuration

Once you have entered the required information for the origin, click "Create Engine" at the bottom of the form.

This will create an address in the following pattern that is immediately ready for use:

https://xxyyzz.cdn.imgeng.in

In the case of using an ImageEngine-generated address for serving images, the SSL certificate for *.imgeng.in covers the address and HTTPS is immediately available. No additional steps are required to use the Delivery address as HTTPS, and you may immediately proceed to implement the Engine on your site.

These are the only two steps required to create a basic engine. For additional settings, such as

Modify the Origin in use by the Engine
Allowing Origin Prefixing
CORS Management
Prioritizing Regions

See their sections later in this article.

If you require a customized address, keep reading!

Optional: Choose whether to automatically generate a delivery address (Standard and Pro only)

Standard and Pro level subscriptions have access to creating Engines with Custom Delivery Addresses.

If your account is a Basic Level trial or subscription, this option does not appear, upgrade your subscription to gain access to this feature.

If a custom Delivery Address is not required, leave the delivery address creation option to generate the delivery address 'automatically", and click confirm to proceed.

This will create an address in the following pattern that is immediately ready for use:

https://xxyyzz.cdn.imgeng.in

NOTE: If you do not use the option to automatically create the address, additional steps will be required to use HTTPS. This will involve making changes to your website’s Domain Name Server (DNS), and must be done by someone with administrative access to that system.

Activating a Custom Delivery address.

If you wish to proceed with a custom address, provide an address for a subdomain under your control, and submit the form.

For instance, if you are implementing ImageEngine on Foo.com, you might use a subdomain such as media.foo.com, or images.foo.com

When an Engine with a custom Delivery Address is newly created, the engine overview will show the following message: "Engine is not ready to serve traffic!"

To resolve this message, you will need to

Add a DNS record for the TLS/SSL Certificate
Add a CNAME record for the Delivery address back to its ImageEngine address

Sound confusing? No worries. We have helpfully provided the specific record names and values that you will need to add to the DNS in the engine’s overview!

You can find the steps for completing the custom delivery address set up in the Delivery Address article

Please see the Implementation Overview and Delivery Address for further implementation information.

Verify Implementation

After creating a new engine, a label will be present that states "Implementation not verified'. This does not mean that the engine is not ready for use, but rather that ImageEngine has not yet received inbound requests from your engine. Once the engine has received greater than 10 MB this label will disappear, and be replaced with a green label that states "verified".

The message may also be cleared proactively by using the verify implementation tool in the Setup steps by submitting the URL of a page that has your Engine in use, or by using the option to skip verification.

Modifying Optional Engine Settings

The Settings for an Engine can be accessed from the “All Engines” screen:
From a specific engine’s overview page, you can access the Engine’s Edit menu:

Or from the navigation bar after expanding the menu for the engine:

Engine options

Here you may change several options for the engine:

Modify the Origin in use by the Engine
Allowing Origin Prefixing
CORS Management
Prioritizing Regions
Engine Deletion

Modify the Origin in use by the Engine

An Engine must be connected to an Origin to allow its delivery address to serve images.

Allow Origin Prefixing

“Origin Prefixing” is a feature that allows an engine’s Delivery Address to prefix any other image URL on the internet. For example, if the Delivery Address registered is `img.foo.com` you can put this in front of any other URL resolving to an image: //img.foo.com/https://www.website.com/image.png. This may be a convenient feature for testing, or in cases where it is impractical to modify only the domain of an image’s URL.
if you wish to restrict access to this feature, provide a list of Origin hostnames that can be allowed for prefixing. If the prefixed image URL is not from one of the provided Origins, ImageEngine will throw an error, adding security to the prefixing feature by preventing illegitimate usage.

Permitting Origin prefixing is disabled by default.
For more information on prefixing as an implementation strategy, please see the Implementation Overview article.

CORS Management

Cross-Origin Resource Sharing (CORS (external link)) is a security feature based on HTTP-headers which is meant to indicate which Origins should be allowed to assess resources on a server. By default, this feature is enabled.

In this section, the allowed Origins, methods, and headers are specified. Multiple Origins can be entered. ImageEngine will respond with only one Origin if there is a match between the actual Origin and the list of allowed Origins. The Origin should usually be * or the domain name of your website, for example, https://foo.com.
The “Suggest Values” button sets liberal values that will most likely work for your site but will also allow other Origins access. The default selection is only "GET"
Any headers defined here will overwrite the same headers returned from the Origin server.

“Origins allowed to access resources on this Engine”, will populate the Access-Control-Allow-Origin response header. Read More (external link)
“HTTP methods allowed” will populate the Access-Control-Allow-Methods response header. This Defaults to “GET” Read More (external link)
“Allowed HTTP request headers” will populate the Access-Control-Allow-Headers.
Multiple values must be comma-separated. For example, x-requested-with, content-type. Read More (external link)
“Lifetime of a “preflight” request” populates the Access-Control-Max-Age response header. Read More (external link)

Other CORS-related headers such as Access-Control-Allow-Credentials or Access-Control-Expose-Headers should be added if using a custom HTTP response header.

Prioritize Region

These two fields offer our engineering team insight into what geographic regions will be served with this engine. We will use this information to better understand how it will be used and to adjust elements of our CDN to improve performance.

Delete Engine

At the bottom of the screen, you will find the option to delete the engine.

WARNING: There is no method to recover a deleted engine. Please be certain that there is no traffic being served using the engine before deletion. If the Engine is deleted while there are still Images using it, the links will break and serve 404s.

Creating and Managing Engines