Closed cpnetdev closed 3 years ago
Thank for this. It appears there was an update to the Neptune Base Stack. The ability to associate a role for bulk loading was added as a native parameter for the Neptune cluster resource in CloudFormation. With that, a change was pushed to associate the role with the native parameter. This then broke the custom CloudFormation resource that was part of this stack for doing that same function. I'm removing the custom CloudFormation resource from the root stack and will be pushing an update here soon.
I just tried deploying the stack again, and it worked! I was also able to delete the stack. I'm hoping to find some time to redeploy this and play with it on the weekend. ... Thanks!
I'm trying to deploy the Cloudformation script using the AWS Cloudformation dashboard found at the links in this repo. My AWS account is in US East 2, and I'm clicking the corresponding link (
https://us-east-2.console.aws.amazon.com/cloudformation/home?region=us-east-2#/stacks/create/review?templateURL=https://s3.amazonaws.com/aws-admartech-samples-us-east-2/identity-resolution/templates/identity-resolution.yml&stackName=Identity-Graph-Sample
).I've tried several times, but it always fails and rolls back with a timeout error at the
AddIamRoleToNeptuneStack
step. When I dig into the logs, I see the following error:I just started using Terraform, and don't have any experience with Cloudformation. I'm also pretty green when it comes to IAM, VPC's etc. However, when I check our IAM roles, I see no role with
Neptune
orGraph
in the name, so I assume this conflicting role only exists temporarily while Cloudformation is running, or it exists in someone else's account? I believe I have permissions to see all of the roles in our AWS account. Thanks for any help!