Connectors

In order to interact with your cloud infrastructure, unSkript has to be able to connect to your cloud tooling.

Connectors securely handle your Cloud credentials without exposing them in the code. Using credentials allows unSkript's RunBooks to interact with your systems. \

unSkript supports the following Connectors-

• Data services like Redis, MySQL, Snowflake, MongoDB, Kafka, Postgresql, Hadoop, MSSQL, Splunk

• Observability services like Grafana, Datadog, Zabbix, Pingdom, OpenSearch, Elasticsearch, Prometheus

• CI/CD platforms such as Jenkins, Jira, GitHub, Terraform

• Infrastructure services such as AWS, GCP, K8S, Azure

• Utilities like Airflow, Slack, Stripe

• Any API or application with a REST API or SSH connectivity

The full list can be seen in the left navigation, and the links point to set up instructions to establish your connection.

Credentials

Credential types vary depending on the Authentication pathways provided by the connector: API tokens, keys & secrets, JSON config files. etc. Each Connector page has details on how to add your credentials for that platform.

There may be times where there are multiple credentials to one Connector (Some xRunBooks or Actions may require different permissions, and using the principles of least privilege, it may be better to have different credentials.

Credentials as a Variable

To reuse an xRunBook across multiple environments, the credential can be set as a serviceID. This of a serviceID as a variable. In each unSkript environment, assign a credential to the serviceID. When the xRunBook is run in an environment - the credential with that serviceID is used to run the Actions.

For example, if there are 2 environments: dev and production, each with different AWS credentials. If the credentials in dev and production have the same serviceID, each Action in a RunBook can use the serviceId variable for authentication. A new Runbook input parameter "environment" is added. Specifying "Dev" will use the dev credentials, while using "production will use the production serviceID credentials.

Head to the section on environments to learn more.