In this quickstart, you enable mlytics multi-CDN solution by creating a new CDN profile. After you have created a site, you can start delivering content to your customer. Besides, this quickstart includes how to adding CDN platforms, manage security policy, and more after the site is created.
In this article
- Log in to the mlytics portal
- Create a new CDN profile
- Add CDN platforms to CDN profile
- Manage security policies (optional)
- Manage geolocation policies (optional)
1. Log In
Log in with your email and password. Enter the CAPTCHA then click Login
2. Create a new CDN profile
A CDN profile is a container for CDN settings and profiles, usually it is a fully qualified domain (FQDN).
1. In the mlytics portal, in the upper right, select Add Site. The Add Site pane appears
2. For the CDN profile settings, use the values specified in below table:
3. Select Confirm to save the profile to your dashboard for later setup.
4. You will see the CDN profile in the site list and call for next action to add CDN Platform.
3. Add CDN platforms to a new CDN profile
After you've created a CDN profile, you can add CDN platform to the profile
1. In mlytics portal, select your newly created CDN profile in the site list. If you can't find it, select Home in the navigation bar on left.
2. Select Add Platform. After add platform is selected, a page listed with CDN platforms appears.
3. Choose the platform you want to deploy. CDN platform has two options to deploy:
For Managed CDN, platform is setup via mlytics API integration. The degree of integration is high, you can manage policy and configuration via mlytics portal.
For BYOP, shorted for Bring Your Own Platform. Platform is setup via CNAME integration. The integration is lower than Managed CDN, you can geo loadbalancing for BYOP platform but not push policies over there.
4. After choose the platform, select Next in the bottom left.
If you choose BYOP, it means you have CDN deployed on the platform, please input corresponding CNAME in the textbox.
5. Check the box and select Next
6. You will be redirected to Home and the CDN profile is being deployed. You can check the process by moving mouse cursor to the deployment status column.
7. If any of the platform is completed, you can start to use the Multi CDN. Let's select the Settings of the newly created profile.
8. In Settings->General, you can see the settings of the CDN profile.
9. Please change your DNS to map to CNAME under the Site Info. In this example, we will change `www.cdnnailuj.com` to CNAME `rg7pn6em.cdn.mlycdn.com` in DNS. Our DNS is managed in AWS Route53.
10. Once DNS change is made, your traffic will be directed to mlytics Multi-CDN.
4. Managed security policies (Optional)
1. Select Security in settings page, you will see security policies for your CDN profile.
Security Policies are grouped into 4 categories, namely
XSS Rule Setting: WAF policy against cross-site scripting
SQL Injection Rule Setting: WAF policy against SQL Injection
Generic Injection Rule Setting: WAF policy against generic injection
DDoS Protection: Policy against DDoS attack
2. Manage the WAF policy is pretty straight forward, toggle the Enable bottom to turn on/off policy. Default Action is simulate, description of Action is as below:
Simulate: When WAF rule is hit, log the attack but still let it pass. It is useful to reduce false positive
Block: When WAF rule is hit, log the attack and block the request.
Pass: No logging and let the request pass. It equals to turn off the rule.
3. Manage the DDoS policy is similar to WAF policy:
Network Layer: DDoS to L3/L4 is auto protected and regardless of attack size and duration.
Application Layer: Application layer protects your domain from application attack like botnet, cc attack or even user mimicking. Toggle the ON/OFF button to manage the policy.
Challenge & Response: The Security Level uses the propitiatory algorithm to determine reputation of a visitor to decide whether to present a challenge. The reputation is calculated by an internal algorithm on our end and ranges from 0 to 100. Here's what each Security Level means with regard to the visitor reputation:
- Under Attack -- score > 0
- HIGH -- score > 10
- MEDIUM -- score between 11-25
- LOW -- score between 26-75
- ESSENTIALLY OFF -- score > 75
5. Managed geolocation policy (Optional)
1. Select ActiveRoute in settings page, you will see geo location policies for your CDN profile.
Location: The geo location end-user visitor comes from. We offer city level control for China. State level control for U.S and Country level control for other regions.
Network: ISP that the end-user / visitor belongs to.
Platform: Current selection of CDN by our RUMBLE based orchestration
Override: Auto means no override. User can choose their preferred platform here and it will override RUMBLE orchestration.
2. Let's take example. We want to let visitors from Hong Kong to use cloudflare:
- Input "hongkong" in the textbox on top of table.
- Region of "Asia/Hong Kong" will appear.
- Choose "Cloudflare" in override and select Update in action tab.
To learn about the reporting to your CDN, please stay tuned for upcoming tutorials.