Unable to add EC2 compute resource in fresh Foreman installation

I am seeing the following text in the production.log file when attempting
to add an EC2 compute resource:

Started PUT "/compute_resources/test_connection" for 10.0.2.2 at 2015-02-21 01:15:58 +0000
Processing by ComputeResourcesController#test_connection as /
Parameters: {"utf8"=>"✓", "authenticity_token"=>"zim8BQuf4A8dlCmvh5KKcgQ4kfR4S1lQIkU9DpPEKI0=", "compute_resource"=>{"name"=>"EC2-US-EAST", "provider"=>"EC2", "description"=>"", "user"=>"[FILTERED]", "password"=>"[FILTERED]"}, "fakepassword"=>"[FILTERED]", "cr_id"=>"null"}
CR_ID IS null
String does not start with the prefix 'encrypted-', so Foreman::Model::EC2 EC2-US-EAST was not decrypted
String does not start with the prefix 'encrypted-', so Foreman::Model::EC2 EC2-US-EAST was not decrypted
String does not start with the prefix 'encrypted-', so Foreman::Model::EC2 EC2-US-EAST was not decrypted
String does not start with the prefix 'encrypted-', so Foreman::Model::EC2 EC2-US-EAST was not decrypted
String does not start with the prefix 'encrypted-', so Foreman::Model::EC2 EC2-US-EAST was not decrypted
Operation FAILED: Unable to verify certificate, please set Excon.defaults[:ssl_ca_path] = path_to_certs, ENV['SSL_CERT_DIR'] = path_to_certs, Excon.defaults[:ssl_ca_file] = path_to_file, ENV['SSL_CERT_FILE'] = path_to_file, Excon.defaults[:ssl_verify_callback] = callback (see OpenSSL::SSL::SSLContext#verify_callback), or Excon.defaults[:ssl_verify_peer] = false (less secure).
Rendered common/500.html.erb (3.0ms)
Completed 500 Internal Server Error in 999ms (Views: 3.5ms | ActiveRecord: 1.3ms)

Hi,

Did you ever find a solution to this issue?
I'm in the same boat.

Bren