Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Configure Managed Integrations - AskJ1 Community
<main> <article class="userContent"> <p>To get started using the JupiterOne (J1) platform, you must first pull your data into J1. The more data, the more powerful the J1 capabilities become.</p> <p>There are multiple, managed integrations available, out-of-the-box, for turnkey configuration.</p> <p>All integrations have a set of common configuration fields in addition to the ones that are unique to the integration.</p> <p>For each integration you configure you must provide:</p> <ul><li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Account Name</code> - an alias that uniquely identifies the configuration.</li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Description</code> - a description of the configuration.</li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Polling Interval</code> - determines how often you want J1 to ingest the data. The options are: <ul><li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">DISABLED</code> - the configuration only runs if manually triggered by a user or via API</li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">THIRTY_MINUTES</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">ONE_HOUR</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">FOUR_HOURS</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">EIGHT_HOURS</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">TWELVE_HOURS</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">ONE_DAY</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">ONE_WEEK</code></li> </ul></li> </ul><p>Each integration has a slightly different mechanism for authentication as required by the provider. For example, the AWS integration uses an IAM role and assume role trust policies for access. Other integrations may use an API key/token, OAuth, or Basic Auth.</p> <p>Additional options are also available for each integration. Common options include:</p> <ul><li><p><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Tag with Account</code> - if you want to tag the data from this integration with the <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Account Name</code> of this configuration.</p></li> <li><p><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Tag as Production</code> - adds a tag indicating this is production data.</p></li> </ul><p>Depending on the integration, there may be other choices in the additional options section.</p> <p>This video shows an example of how to configure an AWS integration.</p> <p><img src="https://us.v-cdn.net/6035534/uploads/6P49I3XUMLVT/j1-aws-config-720p.gif" alt="configure-video" class="embedImage-img importedEmbed-img"></img></p> <p>For details on other integrations, see the respective documentation under <strong>Managed Integrations</strong>.</p> <h2 data-id="other-data">Other Data</h2> <p>In addition, you can upload data outside of these managed integrations using the JupiterOne <a rel="nofollow" href="https://jupiterone.vanillacommunities.com/kb/articles/792-jupiterone-node-js-client-and-cli">API client or CLI</a>. This feature allows you to centrally track, monitor, and visualize any of your data, such as on-premise systems and security and compliance artifacts!</p> </article> </main>
.png)