Accessing a site after associating with it a certificate

Based on the information provided, there are a few potential issues that could be causing the "503 Service Temporarily Unavailable" error when trying to access your site:

1. Certificate mismatch: The certificate you've attached is for the domain "hacknot.net". However, you're trying to access the load balancer URL directly (https://load-balancer-1112113474.us-west-1.elb.amazonaws.com). This mismatch between the certificate domain and the accessed URL can cause security errors.

2. DNS configuration: To properly use the SSL certificate, you need to create a CNAME record that points your domain (hacknot.net) to the load balancer URL. This allows you to access the site using your domain name, which matches the certificate.

3. Load balancer or target group issues: The 503 error suggests that the load balancer is unable to forward requests to healthy targets. This could be due to misconfigured target groups, unhealthy instances, or security group settings that prevent traffic from reaching your instances.

To resolve these issues:

1. Ensure your DNS is properly configured with a CNAME record pointing hacknot.net to your load balancer URL.

2. Access your site using the domain name that matches your certificate (https://www.hacknot.net/secured-cloud-services/).

3. Check your load balancer's target group to ensure there are healthy instances available to handle requests.

4. Verify that the security groups for both the load balancer and the EC2 instances allow the necessary inbound traffic.

5. Review your application logs to see if there are any application-level errors causing the 503 response.

Regarding direct support from Amazon, unless you have a support plan that includes direct technical support, you typically won't be able to discuss issues directly with Amazon support or visit a support center. However, if you have an appropriate support plan, you can open a support case through the AWS Management Console for more personalized assistance.

If you continue to face issues after checking these points, it may be helpful to engage with the AWS community on forums like AWS re:Post or consider upgrading your AWS support plan for more direct assistance.
Sources
Accessing our site after installing the load balancer | AWS re:Post
Not able to access my secure site | AWS re:Post
Troubleshoot the "503 Service Unavailable error" | AWS re:Post

Can you provide more information on your back end? Where are you assigning the SSL Cert? Cloudfront or ALB etc? Target groups Listerner Rules