The Delivery Address is the address pointing to ImageEngine which you’ll use in your
<img> tags to refer to images. Delivery Addresses may be on a shared domain (
imgeng.in) or customized using a domain you own.
Delivery Address on Shared Domain Name
When an Engine is created upon signing up for a new ImageEngine account, or when a new engine is created without selecting the option to create a custom delivery address, an engine with a valid Delivery Address will be created which is ready to serve traffic. This ImageEngine Delivery Address supports HTTPS out of the box through a shared SSL/TLS certificate. This default Delivery Address is structured as
*.cdn.imgeng.in, where the wildcard (
*) is a unique randomly-generated prefix. For example
By default, the Delivery Address and the ImageEngine Address are identical. Since this Delivery Address is on a shared domain name (.imgeng.in), it must be used in the prescribed format (
example.cdn.imgeng.in), and NOT with any other domain name.
Therefore, you may consider customizing the Delivery Address to one from your domain. For example
images.example.com. For this, you will need to upgrade to either our Standard or Pro plans for a custom Delivery Address with HTTPS option.
Setting Up a Custom Delivery Address with HTTPS
Standard and Pro plans allow users to add custom Delivery Address with HTTPS support.
Note: Before starting the process to add a Delivery Address, make sure you have access to your DNS provider so you can add CNAME records for a validation certificate and the delivery address.
When a new engine with a custom Delivery Address is created, the engine overview will guide you with the necessary steps to Enable HTTPS.
Your custom Delivery Address will NOT be ready to serve traffic until the following steps is completed and verified.
To complete the STEP 1, you will need to
- Add a CNAME DNS record with the validation record provided in the engine's overview in your DNS to verify the SSL certificate.
Once the record is added, it may take some time for it to propagate across the internet.
Click the "Check DNS record" button to check if the record is correctly added and available.
Once the SSL verification record is added and available, the next step is available:
- Add a CNAME DNS record to your DNS to define your custom Delivery Address as an alias to the ImageEngine Address.
Once the DNS changes have propagated, the custom Delivery Address will be ready for use on your site.
Custom Delivery Address with HTTPS Process:
Enable HTTPS by Adding Validation Record to DNS
Before routing traffic to the new custom Delivery Address, you will need to validate the HTTPS certificate.
ImageEngine will generate a certificate validation record for you.
A typical certificate validation record looks like this:
Record Name: _f6df6b5d07c31ab619bf0240cxxxxxxx.images.example.com.
Record Type: CNAME
Record Value: _5419a68cba3exxxxxxxxx4511fae90a4.olprtlswtu.acm-validations.aws.
The Validation record may take a short period of time to generate. If it is not appearing for your Delivery Address after an hour please notify our support team, who will be able to provide you with the needed information.
Copy the record name and value from your engine's overview and add them to your DNS. You will need to keep this record in the DNS for as long as the certificate is needed.
Note: Please make sure to include the period at the end of each record. If your DNS Provider does not permit a period to be added, it may be assumed that they will add the base domain automatically. In such cases, you will not need to include the base domain in your record entry.
Note: The certificate verification process may take up to 48 hours!
ImageEngine will ping your DNS to attempt to verify the certificate information. Once ImageEngine verifies the certificate from at least one of its edge servers, you will see an “HTTPS Pending” status indicator. ImageEngine needs to verify the certificate from all of its edge servers before the process is complete. This process may take up to 72 hours. Feel free to contact us if you need more information.
Once ImageEngine has completed the validation process, you will see the status indicator change to HTTPS Enabled.
Add CNAME to DNS
Once the “Enable HTTPS” section changes to showing “HTTPS Enabled”, it is time to add a CNAME record to your DNS that links your Custom Delivery Address (your domain) to its ImageEngine Address.
For example, add the Delivery Address
images.foo.com as an alias of the ImageEngine Address it is associated with:
In other words, any request made to the address
images.foo.com must resolve to
images.foo.com.imgeng.in. This is achieved by creating a CNAME record in your DNS for your custom Delivery Address, pointing to the corresponding
*.imgeng.in ImageEngine Address.
The DNS records are managed by your DNS provider, which may be your domain registrar or another provider.
Note for Cloudflare users:
It is recommended to use the DNS only option when name servers are managed by Cloudflare. This option is toggled when clicking the cloud in the row of the domain name in the Cloudflare dashboard.
Custom Delivery Address Ready
After you add the CNAME record to your DNS, and update your image references in the HTML to use the custom delivery address, traffic will start to flow to ImageEngine via HTTPS.
The status indicator will change to say that the engine is ready to serve traffic.
A correct setup for
images.example.com as a Delivery Address would look like this when executing the
$ dig images.example.com ;; ANSWER SECTION: images.example.com. 59 IN CNAME images.example.com.imgeng.in.
If you do not have
digon your workstation, there are some web-based methods to run the query, such as https://toolbox.googleapps.com/apps/dig/#CNAME/. Ensure that CNAME is selected from the list of options, enter the domain name (the trailing dot will be automatically appended), and the lookup will be executed automatically.
You can also use
$ nslookup images.example.com Name: images.example.com.imgeng.in Aliases: images.example.com