Back to source plugin

Export from AWS to Gremlin

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 Gremlin. 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

v25.5.0

Type

Source

Platforms
Date Published

Mar 26, 2024

Gremlin
gremlin
Official

Gremlin

This plugin is in preview.

This destination plugin lets you sync data from any CloudQuery source to a Gremlin compatible graph database such as AWS Neptune

Publisher

cloudquery

Repositorygithub.com
Latest version

v2.4.5

Type

Destination

Platforms
Date Published

Mar 26, 2024

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: "v25.5.0"
  tables: ["aws_ec2_instances"]
  destinations: ["gremlin"]
  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 Gremlin destination plugin

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

kind: destination
spec:
  name: "gremlin"
  path: "cloudquery/gremlin"
  registry: "cloudquery"
  version: "v2.4.5"
  spec:
    endpoint: "ws://localhost:8182"
    # Optional parameters
    # auth_mode: none
    # username: ""
    # password: ""
    # aws_region: ""
    # aws_neptune_host: ""
    # max_retries: 5
    # max_concurrent_connections: 5 # default: number of CPUs
    # batch_size: 200
    # batch_size_bytes: 4194304 # 4 MiB

Step 5. Run Sync

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

Be the first to know about new features.