Resource handler returned message: “Unable to complete request: runtime error: invalid memory address or nil pointer dereference”

Has anyone experienced this issue before? I am getting an error in CloudFormation.

AWS support has been utterly useless.

Possible Fix

It turns out this was an Internal Cloudformation issue, fixed by AWS Support allocating more resources to the MongoDB Third Party registry.

Elsewhere On TurboGeek:  How to Use and Create S3 Bucket on AWS

Richard.Bailey

Richard Bailey, a seasoned tech enthusiast, combines a passion for innovation with a knack for simplifying complex concepts. With over a decade in the industry, he's pioneered transformative solutions, blending creativity with technical prowess. An avid writer, Richard's articles resonate with readers, offering insightful perspectives that bridge the gap between technology and everyday life. His commitment to excellence and tireless pursuit of knowledge continues to inspire and shape the tech landscape.

You may also like...

1 Response

  1. 02/02/2024

    […] it was a great experience. However, I experienced lots of issues deploying into EU-WEST-1. The problems were caused by the Cloudformation building resources inside MongoDB AWS accounts, something I have zero control over. The support I […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Translate »