unSkript Documentation
Free SandboxBlogGitHubSlack Community
  • What is unSkript?
  • Guides
    • Contribute to Open Source
    • Getting started
      • Sign Up/Install
      • Authentication
        • Okta configuration
          • Okta Groups Sync
      • Create a Proxy
      • Add Credentials to Connect your Resources
      • Key Terms
  • RunBooks
    • Prebuilt xRunBooks
      • xRunBooks for CloudOps
      • xRunBooks for Cost Optimization
      • xRunBooks for DevOps
      • xRunBooks for IAM
      • xRunBooks for SecOps
      • xRunBooks for SRE
      • xRunBooks for Troubleshooting
    • Creating RunBooks
      • Importing unSkript xRunBooks
      • Create a xRunBook
      • Add an Action
      • Connecting Actions
      • Create a RunBook Input Parameter
      • Create a Credential
      • Writing Notes
      • Running XRunBooks
        • Running RunBooks with Approvals
      • Schedules
      • xRunBook Executions
      • Alarms
        • Create an Alarm Webhook
          • Webhooks for onprem installations
        • Create a Grafana Alert
        • Attaching runbooks to alarms
      • Folders
      • RunBook Outputs
  • Actions
    • What is an Action?
    • Create Custom Actions
    • Create Actions with AI
    • Actions
      • Action Configuration
        • Configure Action Inputs
        • Add Action Inputs
        • Action Output
        • Action Iterator
          • Using Iterators
        • Action Poll
        • Action Start Condition
      • Anatomy of an Action
    • Prebuilt Actions
  • Healthchecks
    • What is a HealthCheck?
    • Create a HealthCheck
      • Create a HealthCheck Folder
      • Adding Checks
    • HealthCheck Parameters
    • Running HealthChecks
    • HealthCheck Remediation
  • Workflows
    • What is a Workflow?
  • Connnecting
    • Connectors
      • Airflow
        • Airflow Actions
      • AWS
        • AWS Actions
          • AWS Cloudwatch Actions
          • AWS EC2 Actions
          • AWS ECS Actions
          • AWS EKS Actions
          • AWS ELB Actions
          • AWS IAM Actions
          • AWS Postgres Actions
          • AWS RDS Actions
          • AWS RedShift Actions
          • AWS S3 Actions
          • AWS VPC Actions
      • Azure
        • Azure Actions
      • ChatGPT
        • ChatGPT Actions
      • Datadog
        • Configuring webhook in Datadog
        • Datadog Actions
          • Datadog Alert Actions
          • Datadog Metrics Actions
          • Datadog Monitor Actions
      • Elasticsearch
        • Elasticsearch Actions
      • GCP
        • GCP Actions
          • GCP Bucket Actions
          • GCP GKE Actions
          • GCP IAM Actions
          • GCP VM Actions
      • Github
        • Github Actions
      • Grafana
        • Grafana Actions
      • Hadoop
        • Hadoop Actions
      • Jenkins
        • Jenkins Actions
      • Jira
        • Jira Actions
      • Kafka
        • Kafka Actions
      • Kubernetes
        • K8s Actions
      • MongoDB
        • MongoDB Actions
      • MS SQL
        • MSSQL Actions
      • MySQL
        • MySQL Actions
      • Netbox
        • Netbox Actions
      • Nomad
        • Nomad Actions
      • OpenSearch
        • opensearch Actions
      • Pingdom
        • Pingdom Actions
      • Postgres
        • Postgres Actions
      • Prometheus
        • Prometheus Actions
      • Redis
        • Redis Actions
      • REST
        • REST Actions
      • SalesForce
        • SalesForce Actions
      • Slack
        • Slack Actions
      • Snowflake
        • Snowflake Actions
      • Splunk
        • Splunk Actions
      • SSH
        • SSH Actions
      • Stripe
        • Stripe Actions
      • Terraform
        • Terraform Actions
      • Zabbix
    • Proxies
      • Environment
        • RunBooks Across Environments: ServiceIDs
      • unSkript Proxy
      • AWS Proxy
      • GCP Proxy
    • Secret store
      • Vault
  • Tooling
    • Role Based Access Control
      • RBAC Roles
    • API reference
      • Authentication
      • Endpoints
        • Executions
        • RunBooks
        • Schedules
    • Command Line Tool
    • Notifications
  • Fundamentals
    • Jupyter Notebook 101
  • Use Cases
    • DevOps
    • SRE
  • Open source
    • Runbooks.sh
    • Contribute to Open Source
  • Lists
    • AWS Service Quota list
Powered by GitBook
On this page
  • Credentials
  • Credentials as a Variable

Was this helpful?

  1. Connnecting

Connectors

PreviousWhat is a Workflow?NextAirflow

Last updated 1 year ago

Was this helpful?

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 , , , , , , , ,

  • Observability services like , , , , , ,

  • CI/CD platforms such as , , ,

  • Infrastructure services such as , , ,

  • Utilities like , ,

  • Any API or application with a or 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 , 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 to learn more.

Redis
MySQL
Snowflake
MongoDB
Kafka
Postgresql
Hadoop
MSSQL
Splunk
Grafana
Datadog
Zabbix
Pingdom
OpenSearch
Elasticsearch
Prometheus
Jenkins
Jira
GitHub
Terraform
AWS
GCP
K8S
Azure
Airflow
Slack
Stripe
REST API
SSH
principles of least privilege
environments