How to Set-up HTTPS for Links for Click Tracking

Background

This tutorial will cover how to configure HSTS-compatible click tracking, meaning links.[YOUR_DOMAIN].com go through SSL/TLS. https://links.[YOUR_TOP_LEVEL_DOMAIN].com needs to reroute to https://links.iterable.com, where we set cookies on the URL for tracking purposes before redirecting back to your domain.

The reason for this setup is that links.iterable.com lives behind an AWS ELB. Currently the only way to support SSL on ELB is via a custom CloudFront Distribution, because it supports SNI and is able to proxy dynamic content to any origin server. Another option might be a server-less API Gateway + Lambda setup, but that won't be explored in this tutorial. 

Setup

Generate an SSL Certificate

1. Generate an SSL certificate for the domain (i.e. links.YOUR_DOMAIN.com) which you want to CNAME to links.iterable.com. We recommend doing this through AWS Certificate Manager due to the convenience, but you can use another service as well. You can learn about how to do that here.
2. Continue to the next step once you've approved the certificate

Create a new CloudFront Distribution

1. Go to https://console.aws.amazon.com/cloudfront/ and click “Create Distribution”
2. Select “Web” as your delivery method
3. Origin Settings
1. Origin Domain Name: links.iterable.com
2. Origin Path: leave blank
3. Origin ID: ELB-linkslb-1505033010
4. Origin SSL Protocols: check all but SSLv3 (don't select this due to POODLE vulnerability) (default)
5. Origin Protocol Policy: HTTPS Only
6. HTTP Port: 80 (default)
7. HTTPS Port: 443(default)
4. Default Cache Behavior
   • If using Iterable's unsubscribe page, allow POST as well (otherwise resubscribe requests from the page will fail)
1. Viewer Protocol Policy: HTTP and HTTPS (default)
2. Allowed HTTP Methods: GET, HEAD, OPTIONS, PUT, POST, DELETE
3. Cache Based on Selected Request Headers: All
4. Minimum TTL: 0 (default)
5. Maximum TTL: 31536000 (default)
6. Default TTL: 86400
7. Forward Cookies: All
8. Query String Forwarding and Caching: Forward all, cache based on all
9. Smooth Streaming: No (default)
10. Restrict Viewer Access: No (default)
11. Lambda Function Associations: leave blank
5. Distribution Settings
   • Choose the certificate that you created through ACM or through another service
1. Price Class: Use All Edge Locations (default)
2. AWS WAF Web ACL: None (default)
3. Alternate Domain Names (CNAMEs): links.[YOUR_DOMAIN].com (i.e. links.mysite.com)
4. SSL Certificate: Custom SSL Certificate
5. Custom SSL Client Support: Only Clients that Support Server Name Indication (SNI)
6. Security Policy: TLSv1.2
7. Supported HTTP Versions: HTTP/2, HTTP/1.1, HTTP/1.0 (default)
8. Default Root Object: leave blank
9. Logging: Off (default)
10. Bucket for Logs: leave blank
11. Log Prefix: leave blank
12. Cookie Logging: Off (default)
13. Enable IPv6: Enable
14. Distribution State: Enabled (default)
15. Click “Create Distribution” once everything looks good.

Wrap up

1. On the “CloudFront Distributions” page, you should see your distribution in an “In Progress” status with a spinning arrow.
2. Once that changes to “deployed”, copy the URL of your CloudFront distribution from “Domain Name” under the “General” tab of your distribution. You will need this for the “Deploy” step.
3. Go to Settings > Mail Domains in Iterable and add links.[YOUR_DOMAIN].com as a tracking domain. Set that tracking domain as default.
4. Also be sure to contact support@iterable.com to toggle on the "Use HTTPS".

Confirm correct configuration

1. Use the openssl command line tool to confirm correct configuration
2. openssl s_client -servername [CNAME] -connect [CLOUDFRONT_DISTRO_URL]:443
3. If you don't see an output that contains your certificate, double-check your CloudFront Distribution settings.

Deploy

1. Set a CNAME record in your DNS settings
1. links.[YOUR_DOMAIN].com CNAME [YOUR_CF_URL]
2. i.e.: links.mysite.com CNAME d49jhgak555.cloudfront.net
2. After about 1 hour, navigating to https://links.mysite.com should redirect to the Iterable app.

Note: If you are using Amazon Route 53, it is possible to use an alias record (A record) instead of a CNAME record as noted in this documentation. If you plan to use an alias record (A record) instead of a CNAME record, you will need to ensure that you are passing through the User-Agent header. This will allow you to track and record device information.