Custom CDN grayed out

Hello again @samarart27

From https://aws.amazon.com/certificate-manager/
AWS Certificate Manager is a service that lets you easily provision, manage, and deploy public and private Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates for use with AWS services and your internal connected resources.

The Amazon SSL certificate is used by the cloudfront distribution and does not change the SSL certificate on your website.

You can request a new certificate for netfactotum.com from the plugin itself, verify& add to the plugin.

OK, your solution creates in AWS Certificate manager a new certificate for *.netfactotum.com. Did it and already verified by DNS, but I didn’t want that type of global certificate for any subdomain and that’s why I already had on the AWS CM a certificate for cdn.netfactotum.com and IN USE by my distribution and working well with the plugin.

Anyway, I did it… disable, reset, liste and added my distribution again… option for cdn.netfactotum.com still grayed out…

Then went into my distribution and changed the certificate in use from my cdn.netfactotum.com to the newly not wished for *.netfactotum.com

Again, disable, reset, list, added my newly modified distribution that has the new certificate and the option to activate cdn.netfactotum.com is still grayed out…

@samarart27 I will reiterate again, the ACM certificate does not affect your live website and sub domains.

Here’s what you need to do get this working
Visit SSL Manager page
Enter Access ID and Secret Key
Click List Certificate
You should see a message ‘SSL Certificate can now be used with Cloudfront CDN. Proceed to Cloudfront Setup’

Return to the AWS CDN page
Disable the CDN
Reset the CDN
Reload the Page
Select I would like to use a custom CDN domain. The certificate ARN field will be auto populated
Click Create Distribution. This will not create a new distribution but will update the plugin with the info needed
Click the green check mark icon
The button should be enabled.

OK, thanks again… it’s your plugin, I like it,donated to it and now it’s working like before but just to be clear, I would like to list the following comments:

The “create distribution” that doesn’t actually create one in this case and just populates the ssl resource is a bit misleading…

While already having a working certificate from Amazon and distribution and now having to create a new wildcard certificate just for this, validate it by adding a new DNS entry and of course, following the above instructions, seems to be a bit much for a plugin update, but hey, it’s an overhaul of it I guess…

And just to add, your last instructions solved the problem, but in my case (I don’t know if any other upgrading user will have this issue), I checked my distribution and had to change manually inside it the certificate I had with the newly created one… If I didn’t do that, the newly created certificate was not going to renew itself because it wasn’t in use….

Best regards…

Thanks for the update @samarart27

I deliberately kept the option for wildcard SSL since that gives you the opportunity to use the same cert in case you would like to switch the custom CDN domain name.

I will try to frame the sentence in a better manner so that it is not misleading

Lastly, I understand that its too many steps for a plugin update. As a existing user of the plugin, you would understand the difference between this and the previous versions.

Thanks again for using the plugin and providing valuable feedback.