AWS t2* instances

qibin.tan's Avatar


07 Mar, 2017 05:02 AM

Hi, I've created a new role using HVM images in AWS so that I can use the t2* instances. After I created the new role successfully and launch it on a farm, a t2 medium ubuntu-14.04-based-hvm instance can launch successfully.

But after I configure the role to use Chef server to boot up, a 'certificate verify failed' error shows. It seems like the certificate verify failed between the instance and my Chef server. But When I use Scalr existing images instead of the images I created, they work fine with my Chef server and there is no such issue. PS: I've added my Chef server to the Scalr correctly. Attached is the screen shots and log error. It's so much appreciated if someone can help me with this issue.

Thanks ahead.

  1. Support Staff 1 Posted by Marat Komarov on 07 Mar, 2017 07:59 PM

    Marat Komarov's Avatar

    Looks like you're using self-signed SSL certificate for your Chef server.
    There is a difference how particular chef-client versions handle SSL verification. Chef-client >= 12.0 enforces SSL verify while < 12.0 does not.

    You should disable SSL verification on Bootstrap with Chef tab.


  2. 2 Posted by qibin.tan on 07 Mar, 2017 09:00 PM

    qibin.tan's Avatar

    Hi, Marat.
    Thank you for your solution. This solved my problem definitely. Thank you again.

    Best Regards,

  3. qibin.tan closed this discussion on 07 Mar, 2017 09:01 PM.

  4. qibin.tan re-opened this discussion on 07 Mar, 2017 09:01 PM

  5. qibin.tan closed this discussion on 07 Mar, 2017 09:01 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac