Back to source plugin

Export from AWS to Neo4j

CloudQuery is an open-source data integration platform that allows you to export data from any source to any destination.

The CloudQuery AWS plugin allows you to sync data from AWS to any destination, including Neo4j. It takes only minutes to get started.

AWS
aws
Official
Open-core

AWS

The AWS Source plugin extracts information from many of the supported services by Amazon Web Services (AWS) and loads it into any supported CloudQuery destination. Some tables are marked as premium and have a price per 1M rows synced.

Publisher

cloudquery

Repositorygithub.com
Latest version

v26.1.0

Type

Source

Platforms
Date Published

Neo4j
neo4j
Official

Neo4j

This plugin is in preview.

This destination plugin lets you sync data from a CloudQuery source to a Neo4j database

Publisher

cloudquery

Repositorygithub.com
Latest version

v5.1.9

Type

Destination

Platforms
Date Published

MacOS Setup

Step 1. Install CloudQuery

brew install cloudquery/tap/cloudquery

Step 2. Log in to CloudQuery CLI

Logging in is required to use premium plugins and premium tables in open-core plugins.

cloudquery login

Step 3. Configure AWS source plugin

You can find more information about the configuration in the plugin documentation

kind: source
spec:
  # Source spec section
  name: aws
  path: cloudquery/aws
  registry: cloudquery
  version: "v26.1.0"
  tables: ["aws_ec2_instances"]
  destinations: ["neo4j"]
  spec:
    # Optional parameters
    # regions: []
    # accounts: []
    # org: nil
    # concurrency: 50000
    # initialization_concurrency: 4
    # aws_debug: false
    # max_retries: 10
    # max_backoff: 30
    # custom_endpoint_url: ""
    # custom_endpoint_hostname_immutable: nil # required when custom_endpoint_url is set
    # custom_endpoint_partition_id: "" # required when custom_endpoint_url is set
    # custom_endpoint_signing_region: "" # required when custom_endpoint_url is set
    # use_paid_apis: false
    # table_options: nil
    # scheduler: shuffle # options are: dfs, round-robin or shuffle
    # use_nested_table_rate_limiting: false 
    # enable_api_level_tracing: false

Step 4. Configure Neo4j destination plugin

You can find more information about the configuration in the plugin documentation

kind: destination
spec:
  name: "neo4j"
  path: "cloudquery/neo4j"
  registry: "cloudquery"
  version: "v5.1.9"
  spec:
    connection_string: "${NEO4J_CONNECTION_STRING}"
    username: "${NEO4J_USERNAME}"
    password: "${NEO4J_PASSWORD}"
    # Optional parameters:
    # batch_size: 1000 # 1K entries
    # batch_size_bytes: 4194304 # 4 MiB

Step 5. Run Sync

cloudquery sync aws.yml neo4j.yml
Subscribe to product updates

Be the first to know about new features.