KeyError: 'IAMCertificateId' on new distribution about certbot-s3front HOT 10 CLOSED

I fixed this problem locally by updating installer.py with the following code change:

if cf_cfg['DistributionConfig']['ViewerCertificate']['IAMCertificateId'] == self.certificate_id:
  return;

to

if 'IAMCertificateId' in cf_cfg['DistributionConfig']['ViewerCertificate'] and cf_cfg['DistributionConfig']['ViewerCertificate']['IAMCertificateId'] == self.certificate_id:
  return;

from certbot-s3front.

Also confirming that this is still not in pip but @plancast's update works perfectly.

from certbot-s3front.

Not sure it is evident from the log, but certbot had created and uploaded the cert at this point. I was able to manually go into the CF dist and update the dist to use the uploaded cert and the cert is valid and works.

from certbot-s3front.

Same here. On the default configuration, the xml returned has the following section:

<ViewerCertificate>
    <CloudFrontDefaultCertificate>true</CloudFrontDefaultCertificate>
    <MinimumProtocolVersion>TLSv1</MinimumProtocolVersion>
    <CertificateSource>cloudfront</CertificateSource>
  </ViewerCertificate>

Where the script is looking for IAMCertificateId.

As mentioned, the cert is properly stored in the IAM user's server certificates and can be installed manually. After the first one is setup, installing (and therefore I think renew as well) through the script works as expected.

from certbot-s3front.

Facing the same issue with a new CF distribution.

from certbot-s3front.

@plancast do you want to send a PR for that change? it is a bug that I didn't test the latest version with a new distro.

from certbot-s3front.

Had the same problem. @plancast's changes made it work.

The changes don't seem to have been propagated to the pip registry yet.

from certbot-s3front.

@dlapiduz Would bumping the version number up to 0.4.2 cause PyPI to update its sources? I'm facing the same issue where it fails with KeyError: 'IAMCertificateId' using the pip installed package which currently is built from the source as it was on Jul 23, 2018.

from certbot-s3front.

@dlapiduz First, thanks for the awesome plugin. But it does still not seem to exist in pip. Had to manually patch it to get it work.

from certbot-s3front.

Hi folks, I just bumped the version and pushed to PyPi. Apparently the old CI system is not working anymore so I had to set up a new one...

from certbot-s3front.