> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/isd-spinnaker/opsmx-intelligent-software-delivery-isd-platform-spinnaker/release-notes/additional-resources/previous-releases/isd-3.10/opsmx-intelligent-software-delivery-platform/opsmx-isd-setup/integrations/available-integrations.md).

# Available Integrations

{% hint style="info" %}
This is an older version of the document. To view the most recent version of the document, click [here](https://docs.opsmx.com/products/opsmx-intelligent-software-delivery-platform/system-setup/data-sources/available-integrations).
{% endhint %}

### Amazon S3

The following figure depicts the information to be supplied to add Amazon S3 as an integration.

![](/files/-MgfY9w-Hs5qjy9yOmzu)

Following are the fields:

* *Account Name: Name of the Amazon account to operate on*
* *Access Key ID: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at* [*http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default*](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
* *Secret Access Key: Your AWS Secret Key*
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*
* *Group and permission: Enable all access to all the groups for this.*

{% hint style="info" %}
Note: To select a group, click on the drop-down arrow under select group.
{% endhint %}

### Artifactory

The following figure depicts the information to be supplied to add Artifactory as an integration.

![](/files/-MgfZihqJsxhwTdbz0js)

Following are the fields:

* *Account Name: Name of the Artifactory account to operate on*
* *Host URL: The base url your Artifactory search is reachable at*
* *Repo: The repo in your Artifactory to be searched*
* *Repo Type: The package type of repo in your Artifactory to be searched*
* *Group ID: The group id in your Artifactory to be searched*
* *Authentication Type: Select the user authentication mode for Artifactory*
* *User Name: Provide Artifactory user name*
* *Token / Password: Provide Artifactory token or password, based on the authentication type selected*
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*
* *Read Permissions: A user must have at least one of these roles in order to view this build search or use it as a trigger source*
* *Write Permissions: A user must have at least one of these roles in order to be able to run jobs on this build search*
* *Group and Permission: Enable all access to all the groups for this.*

### Bitbucket

The following figure depicts the information to be supplied to add Bitbucket as an integration.

![](/files/-Mgf_XCHaxE0R5265kZd)

Following are the fields:

* *Account Name: Name of the Bitbucket account to operate on*
* *Authentication Type: Select the user authentication mode for Bitbucket*
* *User Name: Provide Bitbucket user name*
* *Token / Password: Provide Bitbucket token or password depending on the authentication type selected*
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*
* *Group and Permission: Enable all access to all the groups for this.*

### GitHub

The following figure depicts the information to be supplied to add GitHub as an integration.

![](/files/-MgfafvXrMtiSRvDBoha)

Following are the fields:

* *Account Name: Name of the GitHub account to operate on*
* *Token: Provide GitHub token*
* *User Name: Provide GitHub user name*
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*
* *Group and Permission: Enable all access to all the groups for this.*

### GitAPI

The following figure depicts the information to be supplied to add GitAPI as an integration.

![](/files/-Mgfb95k0yeYH3O_QDeS)

Following are the fields:

* *Account Name: Name of the Git account to operate on*
* *Token: Provide the token for the Git-API account*
* *URL: Provide the base URL for the Git API instance (Example: htts\://api.github.com)*

### Jenkins

The following figure depicts the information to be supplied to add Jenkins as an integration.

![](/files/-MgfbUeDSB_clqJOhkpF)

Following are the fields:

* *Account Name: Name of the Jenkins account to operate on*
* *Host URL:* Host URL for the Jenkins instance you are connecting to
* *Authentication Type:* Select the type of authentication mechanism you want to use to get authenticated to Jenkins server
* *User Name:* Provide the username on the Jenkins server
* *Token / Password:* Provide the token or password, depending on the authentication type selected
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*
* *Read Permissions:* 
* *Write Permissions:* 

### JIRA

The following figure depicts the information to be supplied to add JIRA as an integration.

![](/files/-MgfboZ_woeOuxuWOwmS)

Following are the fields:

* *Account Name: Name of the JIRA account to operate on*
* *Email: Provide the email ID of the Atlassian user*
* *Token: Provide the password of the Atlassian user*
* *Host URL: Provide Atlassian Host URL (for both Cloud or On-prem Atlassian)*
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*

### AppDynamics

The following figure depicts the information to be supplied to add AppDynamics as an integration.

![](/files/-MgfcIShJUkeLUKxQWdo)

Following are the fields:

* *Account Name: Name of the AppDynamics account to operate on*
* *Controller Host:*
* *Temporary Access Token:*
* *Use TLS / SSL:*

### AWS Cloudwatch

The following figure depicts the information to be supplied to add AWS CloudWatch as an integration.

![](/files/-MgfcZK-QYjyBUPS5SZL)

Following are the fields:

* *Account Name: Name of the AWS Cloudwatch account to operate on*
* *Access Key ID: The default access key used to communicate with AWS Cloudwatch*
* *Secret Access Key: The default secret key used to communicate with AWS Cloudwatch*

### Datadog

The following figure depicts the information to be supplied to add DataDog as an integration.

![](/files/-MgfcrH0J9lvOZZYCyRa)

Following are the fields:

* *Account Name: Name of the Datadog account to operate on*
* *API Key: Your organizations unique Datadog API key. See* [*https://app.datadoghq.com/account/settings#api*](https://app.datadoghq.com/account/settings#api)
* *Application Key: Your Datadog application key. See* [*https://app.datadoghq.com/account/settings#api*](https://app.datadoghq.com/account/settings#api)

### Graphite

The following figure depicts the information to be supplied to add Graphite as an integration.

![](/files/-MgfdI2cDrJ1YpU3ezYq)

Following are the fields:

* *Account Name: Name of the Graphite account to operate on*
* *End Point: URL of the endpoint of Graphite*

### NewRelic

The following figure depicts the information to be supplied to add New Relic as an integration.

![](/files/-MgfdXjad_wr0a7URtDO)

Following are the fields:

* *Account Name: Name of the New Relic account to operate on*
* *API Key: Your account’s unique New Relic Insights API key. See* [*https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api*](https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api)*.*
* *Application Key: Your New Relic account id. See* [*https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id*](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id)*.*

### Prometheus

The following figure depicts the information to be supplied to add Prometheus as an integration.

![](/files/-MgfeFS01iCYH0rmrUvJ)

Following are the fields:

* *Account Name: Name of the Prometheus account to operate on*
* *End Point: The base URL to the Prometheus server*
* *User Name: Provide Prometheus User Name*
* *Password: Provide Prometheus Password*

### Splunk

The following figure depicts the information to be supplied to add Splunk as an integration.

![](/files/-MgfeWBmLcxUyH_YEdwD)

Following are the fields:

* *Account Name: Name of the Splunk account to operate on*
* *Splunk URL: The base URL to the Splunk server*
* *User Name: Provide Splunk user name*
* *Password: Provide Splunk password*
* *Splunk Dashboard URL: Provide URL of the Splunk dashboard*

### Stackdriver

The following figure depicts the information to be supplied to add Stackdriver as an integration.

![](/files/-Mgff4Maph4T-X3m1EtT)

Following are the fields:

* *Account Name: Name of the Stackdriver account to operate on*
* *Encrypted Key File: A path to a Google JSON service account that has permission to publish metrics.*

### ElasticSearch

The following figure depicts the information to be supplied to add ElasticSearch as an integration.

![](/files/-Mgffuc9n27BD48u0TDZ)

Following are the fields:

* *Account Name: Name of the Elastic account to operate on*
* *Elastic End Point: End of the Elasticsearch URL for the account to operate on*
* *User Name: Provider the user name for the ElasticSearch instance*
* *Password: Provider the password for the ElasticSearch instance*
* *Kibana End Point: Endpoint URL for the Kibana instance*
* *Kibana User Name: Provide the username for the Kibana instance*
* *Kibana Password: Provide the password for the Kibana instance*

### SumoLogic

The following figure depicts the information to be supplied to add SumoLogic as an integration.

Following are the fields:

![](/files/-MgfgMKJXUPX1i3gNJ4X)

* *Account Name: Name of the Sumologic account to operate on*
* *Access ID:*
* *Access Key:*
* *Zone:*

### Slack

The following figure depicts the information to be supplied to add Slack as an integration.

Following are the fields:

![](/files/-Mgfgdi96jupjCVEZ8cd)

* *Account Name: Name of the Slack account to operate on*
* *Bot Name: Provide the name of your slack bot*
* *Token: Provide the slack bot token*
* *Connect to Spinnaker: Enable the selection & Select the spinnaker instance you want to associate this account to*

### OPA (Open Policy Agent)

The following figure depicts the information to be supplied to add OPA (Open Policy Agent) as an integration.

Following are the fields:

![](/files/-MgfguBZNy3B0KxM--Ml)

* *Account Name: Name of the OPA account to operate on*
* *End Point: Provide the URL of the OPA server*

### AquaWave

The following figure depicts the information to be supplied to add AquaWave as an integration.

Following are the fields:

![](/files/-MgfhKDwwk5_fRmFz5G-)

* *Account Name: Name of the Aquawave account to operate on*
* *User Name: Provide the username for Aqua wave*
* *Bearer Token: Provide the bearer token for Aqua wave*

### HCL AppScan

The following figure depicts the information to be supplied to add HCL AppScan as an integration.

Following are the fields:

![](/files/-Mgfhb2WOGJdaEIIuEwk)

* *Account Name: Name of the HCL Appscan account to operate on*
* *Bearer Token: Provide the bearer token for HCL Appscan*

### SonarQube

The following figure depicts the information to be supplied to add SonarQube as an integration.

Following are the fields:

![](/files/-Mgfi4HEoYHkcifV_Ja6)

* *Account Name: Name of the Sonarqube account to operate on*
* *Host URL: Provide the host URL of the SonarQube Server*
* *Token: Provide the token to access the SonarQube server*

### Autopilot

The following figure depicts the information to be supplied to add Autopilot as an integration.

Following are the fields:

![](/files/-MgfiHuCc-YS7ZS40VEs)

* *Account Name: Name of the account to operate on*
* *User Name: Provide the user name with which you would access the OES verification services*

###