-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NeptuneStack failed to create #320
Comments
We are currently working on releasing a fix for this. As a workaround, you can edit the |
Svozza I have been trying to figure out exactly how to implement the provided workaround however I am not having much luck. When you import the Cloudformation template I don’t see an option to be able to edit the nested neptune.template. I have also tried uploading the contents of the cfn folder from this github to my own S3 bucket and then tried deploying the main.template after modifying neptune.template but then the stack fails to build as it looks like it doesn’t resolve the variables in main.template. Also I notice there are some zip files that some of the other templates are referencing. Any guidance you can provide is much appreciated. |
The easiest way to get it working is the do a local build. Clone the repo, make the changes to the template and follow the instructions here: https://github.com/awslabs/workload-discovery-on-aws#deploying-a-local-build. |
Local build Failed on TaskStack stack
Template: discovery-crawler.template
|
This issue has arisen before but I've never been able to reproduce it for some reason. To unblock yourself, just comment out that custom resource in the cfn template and reupload it. All it means is that if you uninstall, you'll have to manually delete the ECR repository. |
The fix for the Neptune issue has now been released. You can download the updated template here: https://aws.amazon.com/solutions/implementations/workload-discovery-on-aws/. |
If your issue relates to the Discovery Process, please first follow the steps described in the implementation guide Debugging the Discovery Component
Describe the bug
Creation of WDNeptuneDBCluster failed
The Parameter Group workload-discovery-neptune-cluster-parameter-group with DBParameterGroupFamily neptune1 cannot be used for this instance. Please use a Parameter Group with DBParameterGroupFamily neptune1.2 (Service: AmazonNeptune; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 43e211aa-5f07-40a6-af07-4ffc2d3b6f87; Proxy: null)
To Reproduce
Steps to reproduce the behavior:
Run main.template
Expected behavior
NeptuneStack created successful
Screenshots
The text was updated successfully, but these errors were encountered: