Anti-DDoS onboarding guide

Welcome to GLAD! This guide walks you through the steps required to configure your account for optimal traffic protection.

Two ways to onboard. Account setup and the initial ACL whitelisting (steps 1–4) require coordination with the i3D.net Live Ops team. From there, list and armor management can be driven either by your developers via the GLAD API or with hands-on support from i3D.net Live Ops, whichever fits your operational model. See Warden: How it works for the technical model your integration should target.

Create your GLAD account

The first step in the process is to create your GLAD account.

1. Request account creation: Your GLAD account will be created.

2. API token: After your account is created, you will receive an API token.

3. Create your IP lists: You will need to prepare a whitelist and a blacklist of IP addresses. Afterwards, provide us with the IPs that will access the API.

4. The NetOps team will whitelist these IPs at the ACL (Access Control List) level to grant API access.

Collaborate with the GLAD team

When you work with the GLAD team, they will assist you on configuring armors within Warden for you.

1. Align on traffic protection: With this crucial step, you work with the GLAD team to identify the traffic that requires protection.

2. Provide the following traffic details:

   • TCP/UDP Protocols

   • Ports

   • Bare Metal IP information

   • Bytematching details (if applicable)

3. Commence a dry run (Traffic fingerprint):

   • We will set up test armors to monitor your traffic.

   • This allows us to accurately configure the parameters for production.

API integration

1. Whitelist IPs through the API: The GLAD team will enable you to share your whitelisted IPs.

2. Use GLAD API: Utilize the POST lists function from the GLAD API to share your whitelisted IPs.

Configure Warden armor

1. IP protection: Provide a list of IPs that need protection.

2. Packet per Second (PPS) threshold: Set the greylist PPS limit for non-whitelisted, non-blacklisted traffic. This value is enforced per individual IP within the armor prefix, not shared across the prefix as a whole. A starting point of 10,000 PPS per IP is reasonable for most game server workloads; the ideal value depends on your server's normal traffic from unauthenticated sources. If you need help establishing a baseline, contact i3D.net support — we can provide weekly traffic analysis to guide your configuration. See armor configuration templates for further sizing guidance.

3. Protocol configuration: Configure the protocol for UDP or TCP traffic. If you are protecting both, create 2 separate armors.

Result

You have now configured your GLAD account for optimal traffic protection. If you have any questions or need more assistance, please contact our support team.

Related topics

• Attack types overview

• DDoS category attack types