You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The certificate was generated correctly but not configured for the distribution.
An unexpected error occurred:
botocore.errorfactory.NoSuchDistribution: An error occurred (NoSuchDistribution) when calling the GetDistributionConfig operation: The specified distribution does not exist.
Please see the logfiles in /var/log/letsencrypt for more details.
I have verified that the distribution config can be obtained with aws command line tool using the same credentials that I am using for running certbot-s3front. Can you please help?
Also, once the certificate is uploaded through this plugin, will it appear in AWS Certificate Manager (ACM)?
The text was updated successfully, but these errors were encountered:
I had a similar problem when renewing. The certificate was uploaded, but the distribution wasn't updated to use the newly uploaded certificate and I had to do that manually afterwards.
Also, once the certificate is uploaded through this plugin, will it appear in AWS Certificate Manager (ACM)?
No, the certificate is in IAM rather than ACM. You can find the ID with aws iam list-server-certificates. I couldn't find it anywhere on the IAM console.
The certificate was generated correctly but not configured for the distribution.
An unexpected error occurred:
botocore.errorfactory.NoSuchDistribution: An error occurred (NoSuchDistribution) when calling the GetDistributionConfig operation: The specified distribution does not exist.
Please see the logfiles in /var/log/letsencrypt for more details.
I have verified that the distribution config can be obtained with aws command line tool using the same credentials that I am using for running certbot-s3front. Can you please help?
Also, once the certificate is uploaded through this plugin, will it appear in AWS Certificate Manager (ACM)?
The text was updated successfully, but these errors were encountered: