The lifecycle config in the template referenced by another template in the identity graph solution here

Gave me the following error:

2020-05-13 15:35:37 UTC-0700 NeptuneNotebookInstance CREATE_FAILED Notebook Instance Lifecycle Config 'arn:aws:sagemaker:us-west-2:XXX:notebook-instance-lifecycle-config/neptunenotebookinstancelifecycleconfig-7fpg6wxfzxq4' for Notebook Instance 'arn:aws:sagemaker:us-west-2:XXXX:notebook-instance/neptunenotebookinstance-kuhtgb3nwlns' took longer than 5 minutes. Please check your CloudWatch logs for more details if your Notebook Instance has Internet access.

In the template could we just cat the stuff commands into a script, chmod +x it and then nohup that execution? or create a cloudformation wait condition somewhere?

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:

[ERROR] DBClusterRoleAlreadyExistsFault: An error occurred (DBClusterRoleAlreadyExists) when calling the AddRoleToDBCluster operation: Role ARN arn:aws:iam::087756882422:role/Identity-Graph-Sample-Neptun-NeptuneLoadFromS3Role-Z2KDEBED48SM is already associated with DB Cluster: neptunedbcluster-a1epw1ieprh8. Verify your role ARN and try again.
Traceback (most recent call last):
  File "/var/task/index.py", line 18, in handler
    addIamRole(dbClusterId, iamRoleArn)
  File "/var/task/index.py", line 37, in addIamRole
    RoleArn=iamRoleArn
  File "/var/runtime/botocore/client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/var/runtime/botocore/client.py", line 676, in _make_api_call
    raise error_class(parsed_response, operation_name)

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 or Graph 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!

The current version of the notebooks have visualizations using networkx. These visualizations are currently not working as the default version for networkx has been upgraded to 2.4 within SageMaker Notebook instances. The code that generates the visualizations needs to be refactored to support networkx 2.4. In the meantime, you can downgrade networkx to 2.3 to fix the issues.