It exists in mainline Elasticsearch as well as the open fork and appears to exist in AWS's offering as well - AWS appears to have forcibly disabled it across the board for unknown reasons. I think it's probably an issue with the overall back-end architecture/implementation of their managed service.