Site Survey

This page describes the data collection process prior to deploying Reblaze.

Objective

To collect information and data to ensure a successful deployment.

Scoping

List of domains

  • A site may have multiple domains eg. www.example.com and exmaple.com. As long as the application and origin/upstream are the same it can be referred to as the same site under the Reblaze configuration.

Regions

  • List all regions that the site should be served from and how traffic is split across regions. This includes Geolocation DNS, DR settings, etc.

Configuration and Flow

Traffic flow:

  • Understand the devices and services that take part in the network flow. Create a traffic flow description diagram that explains all components in front of Reblaze instances and between the application and Reblaze instances.

Affinity requirements:

  • Understand how a session is routed between application instances, if applicable:

    • None

    • Cookies

    • IP Address

    • Other

L7 requirements:

  • Any layer 7 actions that are required to be performed by Reblaze. For example, adding/editing headers toward the client or toward the origin (like x-forwarded-for), adding/editing cookies, any routes decisions based on headers/args/cookies.

Known blacklist/whitelists:

  • Any RBL lists such as restricted countries/ASN/SIDNor any external list that Reblaze should prepare an ACL for.

DNS Records:

  • DNS Records that need to be modified, if there is any need to manipulate DNS.

Specific API URLs:

  • Any URLs that are a known API path that we can map.

User Accounts:

  • A list of Reblaze users and their associated permissions (Admin/Viewer) and contact details.

Cache Settings:

  • Any cache-control header setting, matched by URL if they require overwriting of cache-control headers based on URL matching.

Alerts:

  • List of rules/events and destinations (email/hooks) that send notifications.

List of Bots/Non-Browser Applications:

  • If your application serves non-browser clients (for example, monitoring service, application API, etc.) or uses various bots.

Anything Else:

  • Any other relevant information that may impact implementation (such as rate limits, client certificates, etc.).

Timeline

This is a typical timeline for onboarding, from the overview til the active mode:

Below is a sample table to assist data collection in accordance to the checklist above.

Domains / Apps

Origin (IP/FQDN)

Stickiness

Regions

L7 Policy

Routes

Reference materials

PreviousConfigure the Reblaze PlatformNextOnboarding in the AWS Marketplace

Last updated