PHZ for Sagemaker API not correct

[sandrich]

Describe the bug
When deploying SageMaker VPC endpoints, the wrong Route53 PHZ are created causing the error

App Creation failed with exception: Could not connect to the endpoint URL: "https://api.sagemaker.eu-west-1.amazonaws.com/"

The change was introduced in e8f3d71

To Reproduce
Define VPC Endpoint for sagemaker.api and sagemaker.runtime

This creates PHZ for api.sagemaker.eu-west-1.sagemaker.aws and runtime.sagemaker.eu-west-1.sagemaker.aws

Expected behavior
It should create PHZ for api.sagemaker.eu-west-1.amazonaws.com and runtime.sagemaker.eu-west-1.amazonaws.com as defined in https://docs.aws.amazon.com/general/latest/gr/sagemaker.html

Please complete the following information about the solution:

• Version: v1.11.0
• Region: eu-west-1
• Was the solution modified from the version published on this repository?
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the services this solution uses?
• Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

[bo1984]

Hi @sandrich! Thank you for making us aware of this and for utilizing the Landing Zone Accelerator on AWS (LZA) solution. This has been addressed and will be included in our 1.12 release that's aimed for end of March as of now. In the meantime, if you need to bypass this misconfiguration of the private hosted zone associated with the VPC Endpoint; for VPCs that need to make private access to the Amazon Sagemaker control plane, you can provision a VPC interface endpoint (through the LZA) for those particular VPC(s).