Create Global Edge

Available in Classic and VPC

This section describes how to create a Global Edge from the NAVER Cloud Platform console.
To create a Global Edge, you first create a profile and then create an edge that belongs to it, and there are 2 ways to create an edge: Quick Start and Self Integration.

• Quick Start: Create an edge with a simple setup.
• Self Integration: Create a customized edge by configuring the details of the edge yourself.

Create profile

To create a profile:

1. From the NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Click [Create profile] on the Management page.
3. Enter the profile name on the Create profile page.
   • You can use letters, numbers, hyphens (-), and underscores (_) within a range of 3 to 35 characters.
4. Click [Complete].
   • This directs you to the Management page with the created profile selected.

Create an edge with Quick Start

To create an edge using Quick Start:

1. From the NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Select the profile to create an edge from the Profile dropdown list at the top of the page.
3. Click [Create edge].
4. Once the Edge settings page appears, select Quick Start, and then click [Next].
5. Proceed with the following steps in order:
   • 1. Deployment configuration
   • 2. Origin configuration
   • 3. Caching
   • 4. Creation completed

1. Deployment configuration

Configure the default settings for the edge that you want to deploy.

• Edge name: Enter the edge name.
  • You can use letters, numbers, hyphens (-), and underscores (_) within a range of 3 to 35 characters.
• Service Protocol HTTPS: Choose whether to use HTTPS for content requests (recommended). HTTPS encrypts data transmitted between the server and browser.
• Service domain: Set the domain that you will use to access the service by clicking on a link or entering the URL in the browser.
  • Use NAVER Cloud Platform domain: Use the automatically generated domain in the format "random number.edge.naverncp.com".
  • Use customer's domain: Use a domain other than NAVER Cloud Platform domain. You must enter the domain to use.
    • If you selected Service Protocol HTTPS, click [Register certificate] and register your SSL certificate.
• Service region: configure the edge server region to enable caching and transfer of content.
  • If you select Korea or Japan, content caching and delivery can only be done through the edge servers located in the selected country.
  • If you select Global, content caching and transfer can be done through edge servers located around the world over NAVER Cloud and partner networks.

2. Origin configuration

Specify the location where the content origin is stored.

• Select origin: Select the origin type.
  • NCP Object Storage: Configure Object Storage, NAVER Cloud Platform service, as the origin.
  • NCP Load Balancer: Configure Load Balancer, NAVER Cloud Platform service, as the origin.
  • NCP API Gateway: Configure API Gateway, NAVER Cloud Platform service, as the origin.
  • External origin domain: Configure an external server IP (IPv4) or a domain as the origin.
• Forward Host Header: Set the host header to forward to the origin.
  • Incoming Host Header: Name of the host for the last user of a website or app, which is used in connecting between the client and Global Edge's edge server (for example, www.navercloud.com).
  • Origin Hostname: Origin's host name, which uses the domain defined in the Origin Server Hostname field (for example, example.kr.object.ncloudstorage.com).
  • Custom: Use user-defined value.
• Set origin protocol: Specify the port for the origin server that the edge server will use for HTTP and HTTPS requests.
  • HTTP's standard port is 80, and HTTPS' standard port is 443.
  Note

  Allowable origin port numbers:
  72; 80-89; 443; 488; 591; 777; 1080; 1088; 1111; 1443; 2080; 7001; 7070; 7612; 7777; 8000-9001; 9090; 9901-9908; 11080-11110; 12900-12949; 45002;

• Origin path: Specify the directory path to add to the requests for the origin.
  • When the origin is example.navercloud.com, the origin path is /image/, and the request is my_img/example.jpg, the origin call becomes example.navercloud.com/image/my_img/exmaple.jpg.
• Origin failover: The edge server fails over to another origin based on specific response codes.
  Note

  Response status code values
  404, 500, 502, 503, 504

3. Caching

Configure how you want to control the cache.

• Default Caching (30 days): Caches all objects, and sets the Time-to-Live (TTL) of the cache to 30 days.

4. Creation completed

After reviewing the settings, click [Complete edge creation] at the top of the page.

• The created edge will be added to the list and deployed automatically.
• It may take several minutes to tens of minutes for an edge to be deployed.

Create an edge with Self Integration

To create an edge using Self Integration:

1. From the NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Select the profile to create an edge from the Profile dropdown list at the top of the page.
3. Click [Create edge].
4. Once the Edge settings page appears, select Self Integration, and then click [Next].
5. Enter the edge name, and then click [Next].
   • You can use letters, numbers, hyphens (-), and underscores (_) within a range of 3 to 35 characters.
6. Click each setting listed in the left of the page to configure the detailed settings manually.
   • Deployment settings
   • Origin settings
   • Cache settings
   • Rule builder
   • Optimization
   • Access control
   • Complete settings

Deployment settings

Configure the default settings for the edge that you want to deploy.

Service settings

The service configuration items are as follows:

Global Edge Logging

Global Edge Logging allows you to log request information for each object and store it in Object Storage.
Detailed items are as follows:

Origin settings

Configure the origin of the content to be cached.

Origin settings

The origin configuration items are as follows:

Origin failover

Origin failover is a feature that forwards requests to a backup origin server according to the code when the origin server fails to respond.
Click [Create] to set up forwarding rules. Detailed items are as follows:

Cache settings

Configure how you want to control the cache.

Default Caching

The default cache settings for all objects are as follows:

Negative TTL(s)

Using Negative TTL(s) caches error responses from the origin server, reducing the load on the origin server.
When you click the toggle button to turn on the feature, it is applied by default for 10 seconds to 4xx and 5xx HTTP code responses.

Bypass Query String

By using bypass query string, requested URLs that contain specific strings are not cached and are bypassed to the origin server. To configure settings:

1. Click the Bypass Query String toggle button to turn on the feature.
2. Enter the string that will be used as the bypass criterion in the query string input field and click the empty space around the field once to recognize the string.
   • Repeat this process to enter multiple strings.
3. Click [Save] after entering all the desired strings.
   • After saving, you can click [Edit] to edit the strings if necessary.

Cache Key Hostname

When configuring cache keys, you can select the host name to use. Detailed items are as follows:

Cache key Ignore Query String

By default, query strings are not used in the cache key, but you can control object types by changing whether or not the strings are included or by allowing only specific strings to be used. Detailed items are as follows:

Ignore case sensitivity in cache keys

Generally, origins are considered to be case-sensitive with respect to the URL's path and file name.
When caching requests, the edge server determines how to handle the case sensitivity of URLs.
Some origin servers, like those using Microsoft IIS, do not differentiate between uppercase and lowercase. If the origin does not distinguish between uppercase and lowercase, activate this feature.

Remove Vary Header

If the response from the origin server contains a Vary header instead of Accept-Encoding, the edge server will not cache the response.
If you turn on the feature by clicking the toggle button, the origin server will respond with a Vary header, but the Vary header will be removed to allow the object to be cached when the actual content is the same.

Edge Auth

To prevent unauthorized sharing of content, you can generate a one-time token and configure it to respond to authenticated requests only. To configure settings:

1. Click the Edge Auth toggle button to enable the feature.
2. Select your preferred authentication method between Signed URL and JWT.
   • Signed URL: Embed authentication information in the URL, allowing all clients to access it.
   • JWT: Generate a JSON token with authentication information and place it in the HTTP header to identify the client.
3. Enter the desired name in the Token name input field and click [Create] in the token key field.
   • The token will be generated and displayed.
   • Every time you click [Create], the key value of the token changes.

Rule builder

Configure how to create detailed cache rules and control content.

Detailed cache rules

You can set rules for caching objects on the edge server.
You can click [Add cache rules] to add up to 10 rules. Detailed items are as follows:

You can also click the [Advanced settings] button to set more detailed rules.

When you save the cache rule, a list of rules is generated.

• You can easily view the saved content in the list.
• The priority is automatically applied in the order in which they are saved. To change the priority, click or , or drag .
• To edit the saved rule, click to edit and click [Save].
• To delete the saved rule, click .

Managed rules

When using CDN services, you can configure frequently used features. Detailed items are as follows:

HTTP Header Modification

You can set it to redefine HTTP headers that are transferred when making a request to the origin server or when responding to a client. To configure settings:

1. Click [Modify HTTP Header].
2. Select the type of header to override.
   • Modify Origin Request Header: Redefine the HTTP header transferred when forwarding requests to the origin server.
   • Modify Client Response Header: Redefine the HTTP header transferred when responding from the server to the client.
3. Enter the rule.
   • Rule Name: Enter the rule name.
   • Rule Configuration: Configure rule details.
     • Action: Select the action to perform from add, edit, and delete.
     • Header Name: Enter the HTTP header to be targeted by the action.
     • Value: If you selected add or edit, enter the header value to apply.
4. Click [Save].
   • The rules are saved and a list is created.
   • To edit the saved rule, click to edit and click [Save].
   • To delete the saved rule, click .

Optimization

Configure ways to improve performance when transferring content to users.

Zip transfer

Using zip transfer enables content to be transferred faster by applying zip when transferring content to client browsers or devices that support Gzip or Brotli zip.
By clicking on the toggle button to turn on the feature, you can specify the Gzip or Brotli header in the Accept-Encoding to zip the content.

• Zip transfer support extension: css, js, json, xml, html, ttf, otf, woff, woff2, and eot

Large file transfer

Using large file transfer allows content to be transferred in pieces instead of a single file when requesting content from the origin server, improving origin offloading.
When you turn on the feature by clicking on the toggle button, optimization for large file transfers will be applied.

Header Max Size

Specifies the maximum size of a Request Header that the platform can handle.
The default is 16K for a single header and 32K for all headers.

Access control

Adjust the range of access to the edge.
You can create a whitelist or blacklist and add 3 types of access control conditions.

• Whitelist: Allow access for requests that match the conditions.
• Blacklist: Reject access for requests that match the conditions.

Complete settings

After reviewing the settings, click [Complete settings] at the top of the page.

• The created edge will be added to the list and deployed automatically.
• It may take several minutes to tens of minutes for an edge to be deployed.
• To preview the settings, click [Preview settings].