Skip to content

Accessing and Using CloudFlare

Users that have been provisioned can access Cloudflare directly at https://dash.cloudflare.com.

  1. Ping @gitlab-org/production-engineering/foundations to add the user to the okta-cloudflare-users Google group. If they are unavailable, IT can help provision this piece. You can reach out to IT using the #it_help channel or tagging @gitlab-com/gl-security/corp/helpdesk in the issue.
  2. If the team member needs to be added to the GitLab.com Cloudflare account: (usually Production Engineering or Scalability SREs)
    1. Open a merge request adding the user to https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/blob/main/environments/cloudflare/users.tf
      1. Assign the role based on the access request or baseline entitlements (SREs receive Administrator access as baseline).
    2. The user will automatically receive an invite once the change is applied.
      1. If the user does not accept the invite before expiration, a state drift will occur and the change will need to be applied again.
  3. If the team member should be added to the Dedicated Cloudflare accounts (for SREs on the Dedicated Teams), they should open an MR against the Dedicated Cloudflare Organization project
  1. Remove user from Google group if they have not already been removed.
  2. Remove user from https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/blob/main/environments/cloudflare/users.tf.
  3. If applicable: Remove user from Dedicated Cloudflare Organization.

Cloudflare: Overview

Managing Traffic (blocks, allowlists and abuse mitigation)

Section titled “Managing Traffic (blocks, allowlists and abuse mitigation)”

Cloudflare: Managing Traffic

Cloudflare Workers

Should we need to call Cloudflare, we were given these numbers to reach out to for help.

Those numbers are documented in https://gitlab.com/gitlab-com/gl-security/runbooks/-/blob/master/sirt/infrastructure/cloudflare.md