The Delivery Address is the component of an Engine that 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.
To get started with creating a new Delivery address, click the + sign in the upper left of the control panel to create an new Engine.
Delivery Address on Shared Domain Name
When an Engine is generated during the setup of a new ImageEngine account or when a new Engine is created without opting for a custom delivery address, an Engine with a valid Delivery Address is automatically established. This Delivery Address is configured to support HTTPS by default through a shared SSL/TLS certificate. The standard format of this default Delivery Address is *.cdn.imgeng.in, where the asterisk (*) symbol denotes a distinct randomly-generated prefix. For instance, it could appear as example.cdn.imgeng.in or aabbccdd.cdn.imgeng.in.
Setting Up a Custom Delivery Address with HTTPS
Consider creating a customized Delivery Address on your domain for a cleaner-looking implementation. For example images.example.com. This will allow you to have the Delivery Address be an Address of your choosing, rather than one we create for you.
Upgrade to either our Growth or Pro plans to enable the custom Delivery Address option.
- Notes
- Before starting to add a Delivery Address, ensure you have access to your DNS provider so you can add CNAME records for a validation certificate and the delivery address.
- Your custom Delivery Address will NOT be ready to serve traffic until the following steps are completed and display "enabled" in the interface.
Here is an overview of the Custom Delivery Address with HTTPS Process:
Getting started with setting up the Custom Delivery address
When creating a new engine with a custom Delivery Address, the Engine overview will guide you through the necessary steps to enable HTTPS. Once all needed DNS changes have propagated, the custom Delivery Address will be ready for use on your site.
Enable HTTPS by Adding a Validation Record to DNS
Before routing traffic to the new custom Delivery Address, you must add a CNAME DNS record with the validation record provided in the engine's overview in your DNS to verify the SSL certificate to validate the HTTPS certificate.
ImageEngine will generate a validation record certificate 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 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 must keep this record in the DNS for as long as the certificate is needed.
You may click the "Check DNS record" button to check if the record is correctly added and available.
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! This is outside of ImageEngine's control.
HTTPS Pending
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.
HTTPS Enabled
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: images.foo.com.imgeng.in.
In other words, any request made to the addressimages.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.
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.
See also how you can use Cloudflare workers to enable Client Hints and point traffic to ImageEngine
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.
Troubleshooting:
A correct setup for images.example.com as a Delivery Address would look like this when executing the dig command:
$ 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:
$ nslookup images.example.com
Name: images.example.com.imgeng.in
Aliases: images.example.com
Comments
0 comments
Article is closed for comments.