Neptune#
Client#
- class Neptune.Client#
A low-level client representing Amazon Neptune
Amazon Neptune is a fast, reliable, fully-managed graph database service that makes it easy to build and run applications that work with highly connected datasets. The core of Amazon Neptune is a purpose-built, high-performance graph database engine optimized for storing billions of relationships and querying the graph with milliseconds latency. Amazon Neptune supports popular graph models Property Graph and W3C’s RDF, and their respective query languages Apache TinkerPop Gremlin and SPARQL, allowing you to easily build queries that efficiently navigate highly connected datasets. Neptune powers graph use cases such as recommendation engines, fraud detection, knowledge graphs, drug discovery, and network security.
This interface reference for Amazon Neptune contains documentation for a programming or command line interface you can use to manage Amazon Neptune. Note that Amazon Neptune is asynchronous, which means that some interfaces might require techniques such as polling or callback functions to determine when a command has been applied. In this reference, the parameter descriptions indicate whether a command is applied immediately, on the next instance reboot, or during the maintenance window. The reference structure is as follows, and we list following some related topics from the user guide.
import boto3 client = boto3.client('neptune')
These are the available methods:
- add_role_to_db_cluster
- add_source_identifier_to_subscription
- add_tags_to_resource
- apply_pending_maintenance_action
- can_paginate
- close
- copy_db_cluster_parameter_group
- copy_db_cluster_snapshot
- copy_db_parameter_group
- create_db_cluster
- create_db_cluster_endpoint
- create_db_cluster_parameter_group
- create_db_cluster_snapshot
- create_db_instance
- create_db_parameter_group
- create_db_subnet_group
- create_event_subscription
- create_global_cluster
- delete_db_cluster
- delete_db_cluster_endpoint
- delete_db_cluster_parameter_group
- delete_db_cluster_snapshot
- delete_db_instance
- delete_db_parameter_group
- delete_db_subnet_group
- delete_event_subscription
- delete_global_cluster
- describe_db_cluster_endpoints
- describe_db_cluster_parameter_groups
- describe_db_cluster_parameters
- describe_db_cluster_snapshot_attributes
- describe_db_cluster_snapshots
- describe_db_clusters
- describe_db_engine_versions
- describe_db_instances
- describe_db_parameter_groups
- describe_db_parameters
- describe_db_subnet_groups
- describe_engine_default_cluster_parameters
- describe_engine_default_parameters
- describe_event_categories
- describe_event_subscriptions
- describe_events
- describe_global_clusters
- describe_orderable_db_instance_options
- describe_pending_maintenance_actions
- describe_valid_db_instance_modifications
- failover_db_cluster
- failover_global_cluster
- get_paginator
- get_waiter
- list_tags_for_resource
- modify_db_cluster
- modify_db_cluster_endpoint
- modify_db_cluster_parameter_group
- modify_db_cluster_snapshot_attribute
- modify_db_instance
- modify_db_parameter_group
- modify_db_subnet_group
- modify_event_subscription
- modify_global_cluster
- promote_read_replica_db_cluster
- reboot_db_instance
- remove_from_global_cluster
- remove_role_from_db_cluster
- remove_source_identifier_from_subscription
- remove_tags_from_resource
- reset_db_cluster_parameter_group
- reset_db_parameter_group
- restore_db_cluster_from_snapshot
- restore_db_cluster_to_point_in_time
- start_db_cluster
- stop_db_cluster
Paginators#
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are:
- DescribeDBClusterEndpoints
- DescribeDBClusterParameterGroups
- DescribeDBClusterParameters
- DescribeDBClusterSnapshots
- DescribeDBClusters
- DescribeDBEngineVersions
- DescribeDBInstances
- DescribeDBParameterGroups
- DescribeDBParameters
- DescribeDBSubnetGroups
- DescribeEngineDefaultParameters
- DescribeEventSubscriptions
- DescribeEvents
- DescribeGlobalClusters
- DescribeOrderableDBInstanceOptions
- DescribePendingMaintenanceActions
Waiters#
Waiters are available on a client instance via the get_waiter method. For more detailed instructions and examples on the usage or waiters, see the waiters user guide.
The available waiters are: