Integrations

The integrations page in StarOps allows you to connect, view, and manage the integration with your organizations AWS, Github and Slack accounts. In this docs section we have divided this into three steps.

Find the integration settings from the left navigation menu:

To do this follow these directions for each of the three key integrations (AWS, GitHub and Slack). It is important to note that only AWS is a required integration for running OneShot workflows:

Integration Step 1 - AWS (Required)

StarOps integration uses CloudFormation stack to create an IAM role for StarOps to discover and configure your EKS resources for model deployments. Today StarOps supports both mulitple AWS accounts and multiple EKS clusters.

To view this tutorial step by step please click here

You can delete the stack and remove the StarOps role at any time from your account. You can delete the stack via the UI.

Integration Step 2 - GitHub (Optional)

StarOps connects to your GitHub account via our GitHub app. See Below Tutorial Video for step by step instructions

Permissions In order to be able to open pull requests StarOps will need Read access to metadata Read and write access to administration and code

Repository access options: You can give the app permission to view all repositories in your organization, which will include any repos created in the future. Give access to selected repositories. If you need to update this list you can do so in your organizations manage apps section.

No matter which option you choose, you can always create a new repository when opening a pull request in StarOps.

To view this tutorial step by step please click here

Integration Step 3 - Slack (Optional)

StarOps connects to your Slack organization via our a standard Slack integration app. See Below Tutorial Video for step by step instructions

To view this tutorial step by step please click here