Combining certificates from AWS Certificate Manager and AWS API Gateway

Is the website caching an old certificate?
For example, if the web server is Apache, etc., wouldn't deleting the cache part solve the problem?

This is the answer which solved my issue instantly, but unfortunately I cannot credit the person who answered it as it is not listed as one of answers... but was emailed to me.
The error you are seeing (NET::ERR_CERT_DATE_INVALID) indicates that the SSL/TLS certificate presented by the API Gateway has expired, and the browser is refusing to establish a secure connection to the website. To solve this issue, you need to update the SSL/TLS certificate used by the API Gateway. You can do this by requesting a new certificate from AWS Certificate Manager and associating it with the API Gateway. Here are the steps you can follow: Request a new SSL/TLS certificate from AWS Certificate Manager for your domain. You can do this from the Certificate Manager console. Make sure the new certificate covers the domain name(s) used by your API Gateway. Once the certificate is issued and validated, go to the API Gateway console and select the API Gateway that needs to be updated. Click on the "Custom Domain Names" tab, and then select the domain name associated with the API Gateway. Click on the "Edit" button next to the "Security" section, and then select the new SSL/TLS certificate from the dropdown menu. Click "Save" to update the API Gateway configuration. Once the new certificate is associated with the API Gateway, the SSL/TLS certificate error should be resolved. Regarding the difference between the expired certificate and the current valid certificate, it's possible that the expired certificate was associated with an older version of the API Gateway, and the new certificate was created after some changes were made to the API Gateway. However, as long as the new certificate covers the domain name(s) used by the API Gateway, it should be sufficient for securing the connections to the API Gateway.