Timeframe for disabled Cloud Front distribution to refresh

When you disable a CloudFront distribution, it can take some time for the changes to propagate across all edge locations. The process typically follows these steps:

1. After disabling the distribution, its status will change to "In Progress" while CloudFront propagates the changes.

2. You'll need to wait until the status changes to "Deployed" and the State shows as "Disabled". This process can take anywhere from a few minutes to several hours, depending on the size and complexity of your distribution.

3. Once the distribution is fully disabled, your origin (likely your S3 bucket or web server) should start serving content directly again, bypassing CloudFront.

However, it's important to note that simply disabling the CloudFront distribution may not immediately restore access to your website. You may need to:

1. Ensure your DNS settings are updated to point directly to your origin server instead of the CloudFront distribution.

2. Check that your origin server (S3 bucket or web server) is correctly configured and accessible.

3. Clear your browser cache or try accessing the site from a different device or network to ensure you're not seeing cached results.

If you're still experiencing issues after the distribution is fully disabled and you've checked these points, you may need to investigate further into your origin server configuration or DNS settings.

Regarding your HTTPS setup, if you're having trouble with the CloudFront distribution, you might want to consider other options for adding SSL to your website, such as using a service like Let's Encrypt or configuring SSL directly on your web server if you're not using S3 for hosting.
Sources
Module 6 - Test your setup and clean up your project resources
Static site not displaying updates even if cloudfront distribution url is showing changes | AWS re:Post