Set up a Fastly connector

Capabilities

Resource	Sync	Provision
Accounts
Roles
Services

Gather Fastly credentials

Configuring the connector 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

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

Click API tokens.

Click Create Token.

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

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 C1 will fail if the token expires.

Click Create Token.

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

Done. Next, move on to the connector configuration instructions.

Configure the Fastly connector

To complete this task, you’ll need:

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

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for Fastly and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Paste the automation API token into the API token field.

Click Save.

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

Done. Your Fastly connector is now pulling access data into C1.

Follow these instructions to use the Fastly connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Fastly connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

In the Settings area of the page, click Edit.

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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Fastly credentials
  BATON_ACCESS_TOKEN: <Fastly API token>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

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: public.ecr.aws/conductorone/baton-fastly:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-fastly
        envFrom:
        - secretRef:
            name: baton-fastly-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. 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.

Done. Your Fastly connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Fastly connector

Capabilities

Gather Fastly credentials

Create a Fastly automation API token

Configure the Fastly connector

Resources

Step 1: Set up a new Fastly connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Fastly credentials

​Create a Fastly automation API token

​Configure the Fastly connector

​Resources

​Step 1: Set up a new Fastly connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Fastly credentials

Create a Fastly automation API token

Configure the Fastly connector

Resources

Step 1: Set up a new Fastly connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector