Menu
I've set up everything according to the documentation:
For the certificate provisioning process to proceed, all of the following conditions must be met:
- The DNS records for your domain must reference the IP address of your load balancer's target proxy,
- Your target proxy must reference the Google-managed certificate resource.
- Your load balancer configuration must be complete, including the creation of a forwarding rule.
With a correct configuration the total time for provisioning certificates is likely to take from 30 to 60 minutes.
It's been 2 hours.
244
To replace the SSL certificate for an HTTPS load balancerOpen the Amazon EC2 console at https://console.aws.amazonaws.amazonAmazon Web Services, Inc. (AWS) is a subsidiary of Amazon that provides on-demand cloud computing platforms and APIs to individuals, companies, and governments, on a metered pay-as-you-go basis. These cloud computing web services provide distributed computing processing capacity and software tools via AWS server farms.https://en.wikipedia.org › wiki › Amazon_Web_ServicesAmazon Web Services - Wikipedia.com/ec2/ . On the navigation pane, under Load Balancing, choose Load Balancers. Select your load balancer. On the Listeners tab, for SSL Certificate, choose Change.
If the certificate is not used on an ELB, use the IAM tools as mentioned in other answers. If it is, then you shouldn't delete it from IAM, but instead should set the new, correct one for the ELB then delete the unused certificate(s) using the IAM tools.
I managed to get a reply from someone via https://issuetracker.google.com/issues/117900454. I was ignorantly using Cloud DNS' "CNAME" to point to my IP address instead of using an "A" record. Everything is working now.
198
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
