Skip to main content

Manual asset creation

Explore how to create and add assets directly within your JupiterOne workspace to bring in new assets to your workspace or enrich existing entries with additional information.

Add an asset

Out of the box, JupiterOne supports over 90 different asset classifications or defined assets. For a comprehensive list of these defined assets, see the JupiterOne data model. Each of these defined assets features its own relevant properties in addition to the common properties shared across assets.

You can manually add any type of defined asset by navigating to the Asset section of your workspace and selecting Add new asset (the + sign). From there:

  1. Choose the type of asset you wish to create.
  2. Define the Type for the asset. This defines the source of the asset source. For example, an AWS resource may be of type aws_instance or aws_s3_bucket or aws_iam_user.
  3. Provide a Display Name for the asset. This determines how it will be displayed within the asset view. The asset’s Name value will default to the Display Name unless a separate Name value is provided.
  4. Optionally, provide a Summary, Description, and Classification for the asset.
  5. Add any relevant Defined Properties or desired Custom Properties, more information on asset properties can be found here.
  6. Provide any relevant tags through which the asset can be filtered or tracked.
  7. Click Save once all desired values have been provided for the asset.

Once created, you’ll be able to view and interface with your newly created asset within your Asset workspace.

Bulk upload assets

Additionally, JupiterOne offers support for bulk uploading assets within the Assets section of the dashboard. This allows you the ability to upload or update assets and relationships within your JupiterOne workspace in quantity.

To initiate a bulk upload, navigate to the Assets app in JupiterOne. Select Add new asset (the + sign), and drag your asset file into the window to begin the import.


Note that bulk upload supports ingestion of JSON, YAML, and CSV files. Ensure that your file formatting adheres to our bulk upload schema.

Scopes for bulk upload

You will be prompted to select (or enter a new) "scope" for the upload. A scope identifies relationships to update or delete during diffing. It is important to note that previously existing entities/relationships within the same scope that no longer exist in your latest upload will be deleted.

Bulk upload relationships

When uploading assets, you'll also need to consider the relationships between the assets you are uploading, and potentially relationships they may have to existing entities.

Bulk upload relationships across scopes

You can additionally create relationships between assets that already exist within your JupiterOne workspace. This is helpful for enriching your data within JupiterOne and allows you to create relationships between assets you own or have uploaded and assets that might already exist or are being managed by an integration.