Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Fastly credentials

Each setup method requires you to pass in credentials generated in Fastly. Gather these credentials before you move on.

A user with the Superuser role in Fastly must perform this task.

Create a Fastly automation API token

1. In Fastly, click on your account name in the top navigation bar and select Account.

2. Click API tokens.

3. Click Create Token.

4. On the Create a Token page, give the new API token a name (such as “ConductorOne”).

5. In the Type area of the page, select Automation token and fill out the form as follows:

   • Role: Select Engineer
   • TLS management: leave the box unchecked
   • Scope: Select Read-only access
   • Access: Select the relevant services or all services, as appropriate
   • Expiration: If you set an expiration date, remember that the connection with ConductorOne will fail if the token expires.

6. Click Create Token.

7. The new token is generated. Carefully copy and save the token.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Fastly cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Fastly credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Fastly and click Add.

3. Choose how to set up the new Fastly connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Paste the automation API token into the API token field.

8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Fastly connector is now pulling access data into ConductorOne.

Set up a Fastly cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Fastly and ConductorOne.

See the ConductorOne Fastly integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Fastly self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Fastly credentials generated by following the instructions above

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Fastly connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Fastly connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Fastly connector deployment:

Secrets configuration

# baton-fastly-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-fastly-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Fastly credentials
  BATON_ACCESS_TOKEN: <Fastly API token>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-fastly.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-fastly
  labels:
    app: baton-fastly
spec:
  selector:
    matchLabels:
      app: baton-fastly
  template:
    metadata:
      labels:
        app: baton-fastly
        baton: true
        baton-app: fastly
    spec:
      containers:
      - name: baton-fastly
        image: ghcr.io/conductorone/baton-fastly:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-fastly-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-fastly
   

2. Apply the secret configuration:

   kubectl -n baton-fastly apply -f baton-fastly-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-fastly apply -f baton-fastly.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-fastly}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Fastly connector to. Fastly data should be found on the Entitlements and Accounts tabs.

That’s it! Your Fastly connector is now pulling access data into ConductorOne.