Wrong region in log message for instance profile authentication #170

Closed
sebdah opened this Issue May 20, 2014 · 0 comments

Projects

None yet

1 participant

@sebdah
Owner
sebdah commented May 20, 2014

@ulsa reported the following in #166.


Noticed something weird that might be unrelated to this problem. Forgot to set region on command-line, so all connections were to us-east-1. But it still said my table name matched, it could read all four table names from AWS, and it managed to get the read provisioning for the matching table. That shouldn't have worked, right?

$ sudo dynamic-dynamodb --table dev-OneDynamoDBTable-1NZQE9XTDXD81 ...
2014-05-20 07:24:20,309 - dynamic-dynamodb - DEBUG - Connected to SNS in us-east-1
2014-05-20 07:24:20,349 - dynamic-dynamodb - DEBUG - Connected to DynamoDB in us-east-1
2014-05-20 07:24:20,485 - dynamic-dynamodb - DEBUG - Connected to CloudWatch in us-east-1
2014-05-20 07:24:20,549 - dynamic-dynamodb - DEBUG - Table dev-OneDynamoDBTable-1NZQE9XTDXD81 match with config key dev-OneDynamoDBTable-1NZQE9XTDXD81
2014-05-20 07:24:20,550 - dynamic-dynamodb - DEBUG - Table dev-TwoDynamoDBTable-TIC25BS7EPSE did not match with config key dev-OneDynamoDBTable-1NZQE9XTDXD81
2014-05-20 07:24:20,550 - dynamic-dynamodb - DEBUG - Table dev-ThreeDynamoDBTable-1TL5MPJ9HNBSN did not match with config key dev-OneDynamoDBTable-1NZQE9XTDXD81
2014-05-20 07:24:20,551 - dynamic-dynamodb - DEBUG - Table dev-FourDynamoDBTable-1LHSXXAPI9TRS did not match with config key dev-OneDynamoDBTable-1NZQE9XTDXD81
2014-05-20 07:24:20,567 - dynamic-dynamodb - DEBUG - dev-OneDynamoDBTable-1NZQE9XTDXD81 - Currently provisioned read units: 10

@sebdah sebdah added this to the 1.14.x milestone May 20, 2014
@sebdah sebdah self-assigned this May 20, 2014
@sebdah sebdah closed this May 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment