这个问题的原因是缺少正确的IAM权限。为了解决这个问题,您需要为您的AWS账户添加正确的IAM权限。以下是一些代码示例,您可以在此基础上建立自己的权限策略:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "neptune-db:BatchAddVertices", "neptune-db:BatchDeleteVertices", "neptune-db:BatchAddEdges", "neptune-db:BatchDeleteEdges" ], "Resource": "" }, { "Effect": "Allow", "Action": [ "iam:GetUser", "iam:ListAttachedUserPolicies", "iam:ListPolicies", "iam:ListAttachedRolePolicies" ], "Resource": "" } ] }
您可以将这个策略添加到IAM中,并将所需的角色分配给您使用批量加载的IAM用户或IAM角色。