When dealing with HTTPS certificate errors in AWS Canary runs, it's important to understand that simply ignoring these errors is not recommended as it can pose security risks. However, if you absolutely need to proceed despite certificate issues for testing purposes, there are a few approaches you can try:

1. Ensure you're using the latest version of the AWS Synthetics library, as improvements and bug fixes are regularly released.

2. Instead of setting ignoreHTTPSErrors globally or in the page.goto function, try setting it when launching the browser:

const browser = await synthetics.getPage({
    browserOptions: {
        ignoreHTTPSErrors: true
    }
});

3. If you're using a custom certificate or a self-signed certificate, you may need to add it to the trusted certificates list for your Canary. This can be done by including the certificate in your Canary's script and adding it to the Node.js trusted certificates.

4. Check if the certificate issue is related to an expired or misconfigured certificate on the target website. If so, addressing the root cause would be the best solution.

5. If the issue persists, you may need to implement a custom error handling mechanism in your Canary script to catch and handle the specific HTTPS errors you're encountering.

Remember that ignoring HTTPS errors should only be done in controlled testing environments and never in production scenarios, as it can expose your application to security vulnerabilities. If you continue to face issues after trying these approaches, consider reaching out to AWS Support for further assistance tailored to your specific use case.

Sources
AWS Certificate Manager Resources | Certificate Management | Amazon Web Services
Improper certificate validation | Amazon CodeGuru, Detector Library
Enabling and disabling HTTPS - AWS Elemental Conductor Live