Cloud front is not getting applied on my personal website hosted on awsbeanstalk

If you have set up AWS CloudFront for your website hosted on AWS Elastic Beanstalk and are not seeing the CloudFront domain in the network requests when inspecting the page, there could be a few possible reasons for this:

1. Caching: CloudFront is a content delivery network (CDN) that caches your content at edge locations worldwide. When you access your website, CloudFront serves the content from its cache, reducing latency and improving performance. If you have recently set up CloudFront or made changes, it is possible that the content is still being served from the cache. Clear your browser cache or try accessing the website from a different device or network to see if CloudFront is being used.
2. DNS Propagation: Changes to DNS settings, such as pointing your domain to CloudFront, can take some time to propagate across the internet. It usually takes a few minutes to a few hours, depending on DNS provider settings and caching. During this propagation period, you may still see requests going directly to the Elastic Beanstalk endpoint. Be patient and allow some time for the DNS changes to fully propagate.
3. Origin Configuration: Ensure that your CloudFront distribution is correctly configured to use your Elastic Beanstalk application as the origin. Double-check that you have entered the correct origin domain name in the CloudFront configuration, and that it matches the URL of your Elastic Beanstalk environment. Verify that the origin settings in CloudFront are properly configured and pointing to the correct resource.
4. SSL Certificate: Confirm that you have correctly associated the SSL certificate from AWS Certificate Manager (ACM) with your CloudFront distribution. Make sure the certificate is issued for the domain name you are using, and that it is in the "Issued" state. Improper SSL certificate configuration can cause issues with HTTPS requests.
5. Distribution Status: Check the status of your CloudFront distribution to ensure it is in the "Deployed" state. If the distribution is still being created or is disabled, it may not be serving content yet.

Let me know if this helps you.