Make sure there is no cached copy of an old/incorrect cert on the Parent
or Child AWS node of your Jamf Pro instance. This would contribute to
the inconsistent behavior (whenever the node with cached cert tries to
service the request). This is a know...
