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

Was this helpful?

  1. Guides
  2. Getting started

Sign Up/Install

Use our free Cloud sandbox, or install the Open Source Docker Image

PreviousGetting startedNextAuthentication

Last updated 2 years ago

Was this helpful?

To get up and running on your unSkript journey quickly, we've created two options:

  1. A local install using the the open source Docker image.

  2. A free sandboxed version of our Cloud product.

unSkript is an open source project. We love PRs, stars and more - checkout our .

Docker:

The fastest way to get the open source version of unSkript running is via our Docker container.

With Docker, you can get up and running in two steps (and just one if you already have Docker up and running!)

  1. Clone out GitHub Repository (In this case we are installing in $HOME.)

    cd $HOME
    git clone https://github.com/unskript/Awesome-CloudOps-Automation 
    cd Awesome-CloudOps-Automation
  2. In the terminal, run the following command (if you installed the GitHub in a different location - change line 2 appropriately):

    docker run -it -p 8888:8888 \
     -v $HOME/Awesome-CloudOps-Automation/custom:/data \
     -v $HOME/.unskript:/unskript \
     -e ACA_AWESOME_MODE=1 \
     --user root \
     docker.io/unskript/awesome-runbooks:latest

Your installation will be available to use at:

Note: the -e ACA_AWESOME_MODE=1 allows for syncing data between docker and your local machine, and the two -v commands indicate where the data (RunBooks and Actions) and unskript (credentials) will be stored.

Omitting these three lines will result in a "read-only" version of unSkript.

Kubernetes:

Here are the steps to launch the unSkript Docker image in k8s:

  • Deploy using the following command (the Yaml file is in our GitHub repository)

kubectl apply -f unskript-oss-k8s-deployment.yaml
  • To access the jupyter server, you will have to enable port-forwarding using

kubectl port-forward <pod corresponding to this deployment> -n <k8s namespace> 8888:8888&

unSkript offers a free cloud sandbox that can be easily accessed in your browser.

  1. On the sign up screen, you may either use Google to sign in, or you can use your email address to create an account (this will require email verification).

Once you have verified your account, you'll be walked through a overview of the platform where you will create a xRunBook in three steps:

  1. Create a xRunBook This step will walk you through the creation of a xRunBook

    1. First you'll create a xRunBook with a name, optional description and the Proxy you created in the first step.

    2. Next we'll open the editor to begin creating the xRunBook.

    3. xRunBooks are built by combining Actions. In the walkthrough we'll add the MongoDB Find Document Action from the installed Actions, by searching for the term, and then dragging the Action into our xRunbook.

    4. Now you are ready to run your first xRunBook. Click Run Action to just run the Action, or you can click the Run XRunBook to run the entire RunBook. A list of movies will be the output.

    5. Now you are ready to create your own xRunBooks!

You should be able to go to and access runbooks as explained

You can read more about how to configure unSkript on the .

Visit , and click the signup button at the top right of the page

(these are used to store your credentials and xRunBooks). In the cloud demo, you can only have unSkript hosted proxies.

We'll connect your environment to a MongoDb database for the demo.

Configure your Action. Each Action can be . We've created a default configuration for this Action, but you'll need to add Credentials to the MongoDB.

http://127.0.0.1:8888/awesome
http://127.0.0.1:8888/lab/tree/Welcome.ipynb
https://github.com/unskript/Awesome-CloudOps-Automation
GitHub README page
unSkript.com
Establish a proxy environment
Connect a Resource/Add Credentials
configured in many ways
GitHub
image-text