Would love to specify the vpc when spinning up a neptune cluster. Seems like the current instance only gets created under the default vpc.
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
resource "aws_neptune_cluster" "default" {
cluster_identifier = "neptune-cluster-demo"
engine = "neptune"
backup_retention_period = 5
preferred_backup_window = "07:00-09:00"
skip_final_snapshot = true
iam_database_authentication_enabled = true
apply_immediately = true
vpc_id = ${var.aws_vpc_id}
}
Thanks for raising this @rjay98.
It's not clear from the documentation, but the way to assign a Neptune cluster (and similarly for any other AWS database) to a VPC is to create an aws_neptune_subnet_group which references subnets from the VPC and then assign the subnet group to the Neptune cluster.
I'm going to close this issue, but I've created #15344 to fix our documentation.
I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
Most helpful comment
Thanks for raising this @rjay98.
It's not clear from the documentation, but the way to assign a Neptune cluster (and similarly for any other AWS database) to a VPC is to create an
aws_neptune_subnet_groupwhich references subnets from the VPC and then assign the subnet group to the Neptune cluster.I'm going to close this issue, but I've created #15344 to fix our documentation.