AWS API endpoint still supports TLS 1.0 & 1.1?

Using API Gateway, I have an API endpoint which is used in our application for various purposes. We are not using a custom domain name for this API and use POST and OPTIONS request to trigger a Lambda function that returns the response sent back to the user through the API. The API endpoint is regional. My company's cybersecurity team found that this endpoint allowed TLS 1.0 and 1.1 and mandated that we updated the API to raise the minimum support to TLS 1.2. Running nmap and sslscan can be used to verify that this is indeed true:

https://aws.amazon.com/blogs/security/tls-1-2-required-for-aws-endpoints/ shows that the 1.0 and 1.1 protocols should have been deprecated after 06/28/2023, yet they are still showing up from our scans. Has AWS extended the deadline to deprecate these? What changes can I make to ensure that the API endpoint only allows TLS 1.2 and above? I have browsed through all the API settings but I can't seem to find anything to control this. Most of the related material I could find online was for custom domain name APIs, which we do not intend to use and the customer solution is deployed and running and changes can not be made. At the bare minimum, I want to make sure that my team is complying with cybersecurity's mandate of only supporting TLS 1.2 or above protocols asap.