boto/boto — Issue #402: rds.connect_to_region "works" with incorrect secret_key
Author: atodorov
Created: 2011-11-12 21:58:34+00:00
State: open

This code:

>>> rds_conn = boto.rds.connect_to_region(region_name='us-east-1', aws_access_key_id='XXXXXXX, aws_secret_access_key='YYYYYY')

where YYYY is NOT the full secret key worked and returned a valid object. While similar code from the ec2 module didn't:

>>> ec2_conn = boto.ec2.connect_to_region(region_name='us-east-1', aws_access_key_id='XXXXXXX, aws_secret_access_key='YYYYYY')

I found the error by accidentally passing a secret key that was missing the last characters.

rds_conn seemed to work with the wrong key in the sense that it didn't indicate the error right away. OTHO ec2_conn failed and returned the error right away.

Both modules differ in behavior. Should be unified.