Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update intro to akamai cdn app #508

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update intro to akamai cdn app #508

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 25 additions & 3 deletions docs/dedicated/akamai/cdn.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@ title: Setting up Akamai CDNs
sidebar_label: Akamai CDN
---

When running managed dedicated on the Akamai Cloud, you need to set up 2 CDNs,
one for your API endpoint deployments, and one for your developer portal.
When running managed dedicated on the Akamai Cloud, you will configure the
Akamai CDN to serve your API Gateway and Developer Portal.

This document outlines the configurations you need to add to your Akamai CDNs to
set them up to access your API gateway and developer portal.
Expand All @@ -14,7 +14,29 @@ the
[Akamai docs](https://techdocs.akamai.com/property-mgr/docs/know-your-around)
for more details.

### Prerequisites
## Domains

Before you configure the CDN for your API Gateway and Developer Portal, you will
to decide how you would like your domains to be setup. Generally, you will
provision two types of domains - a static domain for production and wildcard
domains for preview environments.

For preview environments, you will use wildcard domains so that each environment
(i.e. each Git branch) will have its own subdomain. For example, you might use
`*.api.example.com` for the API gateway and `*.dev.example.com` for the
developer portal. This will allow you to have URLs for each environment like
`https://my-environment-123.api.example.com` and
`https://my-environment-123.dev.example.com`.

For production, you will want to use friendly domains like `api.example.com` and
`developers.example.com`. Some customers also choose to host environments list
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: "Some customers also choose to host environments list" should be "Some customers also choose to host environments like"?

staging on custom domains as well. This is up to you, just let your Zuplo
account manager know how you would like to set up your domains.

The setup for both configurations is the same, but the domain name and
certificates will be different.

## Prerequisites

1. Provision the domains that you would like these CDNs to have and certificates
for those domains. You will need a domain for the API gateway, as well as a
Expand Down
Loading