Amazon Neptune Construct Library
---AWS CDK v1 has reached End-of-Support on 2023-06-01. This package is no longer being updated, and users should migrate to AWS CDK v2.
For more information on how to migrate, see the Migrating to AWS CDK v2 guide.
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 Neptune is a purpose-built, high-performance graph database engine. This engine is optimized for storing billions of relationships and querying the graph with milliseconds latency. Neptune supports the popular graph query languages Apache TinkerPop Gremlin and W3C’s SPARQL, enabling you to build queries that efficiently navigate highly connected datasets.
The @aws-cdk/aws-neptune package contains primitives for setting up Neptune database clusters and instances.
import aws_cdk.aws_neptune as neptune
Starting a Neptune Database
To set up a Neptune database, define a DatabaseCluster. You must always launch a database in a VPC.
cluster = neptune.DatabaseCluster(self, "Database",
vpc=vpc,
instance_type=neptune.InstanceType.R5_LARGE
)
By default only writer instance is provisioned with this construct.
Connecting
To control who can access the cluster, use the .connections attribute. Neptune databases have a default port, so
you don't need to specify the port:
cluster.connections.allow_default_port_from_any_ipv4("Open to the world")
The endpoints to access your database cluster will be available as the .clusterEndpoint and .clusterReadEndpoint
attributes:
write_address = cluster.cluster_endpoint.socket_address
IAM Authentication
You can also authenticate to a database cluster using AWS Identity and Access Management (IAM) database authentication; See https://docs.aws.amazon.com/neptune/latest/userguide/iam-auth.html for more information and a list of supported versions and limitations.
The following example shows enabling IAM authentication for a database cluster and granting connection access to an IAM role.
cluster = neptune.DatabaseCluster(self, "Cluster",
vpc=vpc,
instance_type=neptune.InstanceType.R5_LARGE,
iam_authentication=True
)
role = iam.Role(self, "DBRole", assumed_by=iam.AccountPrincipal(self.account))
cluster.grant_connect(role)
Customizing parameters
Neptune allows configuring database behavior by supplying custom parameter groups. For more details, refer to the following link: https://docs.aws.amazon.com/neptune/latest/userguide/parameters.html
cluster_params = neptune.ClusterParameterGroup(self, "ClusterParams",
description="Cluster parameter group",
parameters={
"neptune_enable_audit_log": "1"
}
)
db_params = neptune.ParameterGroup(self, "DbParams",
description="Db parameter group",
parameters={
"neptune_query_timeout": "120000"
}
)
cluster = neptune.DatabaseCluster(self, "Database",
vpc=vpc,
instance_type=neptune.InstanceType.R5_LARGE,
cluster_parameter_group=cluster_params,
parameter_group=db_params
)
Adding replicas
DatabaseCluster allows launching replicas along with the writer instance. This can be specified using the instanceCount
attribute.
cluster = neptune.DatabaseCluster(self, "Database",
vpc=vpc,
instance_type=neptune.InstanceType.R5_LARGE,
instances=2
)
Additionally it is also possible to add replicas using DatabaseInstance for an existing cluster.
replica1 = neptune.DatabaseInstance(self, "Instance",
cluster=cluster,
instance_type=neptune.InstanceType.R5_LARGE
)
Automatic minor version upgrades
By setting autoMinorVersionUpgrade to true, Neptune will automatically update
the engine of the entire cluster to the latest minor version after a stabilization
window of 2 to 3 weeks.
neptune.DatabaseCluster(self, "Cluster",
vpc=vpc,
instance_type=neptune.InstanceType.R5_LARGE,
auto_minor_version_upgrade=True
)
Metadata
Release files for aws-cdk.aws-neptune 1.204.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws-cdk.aws-neptune-1.204.0.tar.gz | 173.8 kB | Without provenance | Details for aws-cdk.aws-neptune-1.204.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_cdk.aws_neptune-1.204.0-py3-none-any.whl | Python 3 | none | any | Details for aws_cdk.aws_neptune-1.204.0-py3-none-any.whl |
Total release size: 347.3 kB
Release files / aws-cdk.aws-neptune-1.204.0.tar.gz
| Download URL | aws-cdk.aws-neptune-1.204.0.tar.gz |
|---|---|
| Size | 173.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eaa7bd693ddaa6ab14325a7a59d224dc3609704050adbd0be4d507e35ecdadd3
|
|
BLAKE2b-256 checksum How to use checksums |
211f89a8993e782d028ca983fec065aef3146ba11e06c3f1f230bcf638798337
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / aws_cdk.aws_neptune-1.204.0-py3-none-any.whl
| Download URL | aws_cdk.aws_neptune-1.204.0-py3-none-any.whl |
|---|---|
| Size | 173.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6ee4fe8006f34a038797db756a979e05cd2804d09f40294aa406adc74585c51
|
|
BLAKE2b-256 checksum How to use checksums |
6e69ef2a5e4a934ed8a6d3372d39a8908811233cac3219ee2361d29bf8cf1f3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for aws-cdk.aws-neptune 1.204.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.