-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed connecting to SNS: Profile "..." not found! #183
Comments
Or is it simply a missing |
Got the same problem on another machine running |
Yep, boto 2.28.0 works, but 2.29.0 and 2.29.1 both fail. |
@ulsa I dont suppose you could tell me how to install boto version 2.28.0 while this bug is fixed in 2.29.0? Thanks |
I can release a forced version lock in Dynamic DynamoDB later today. Will Br, Sent from my phone
|
excellent ;) |
Meanwhile, you can install using:
|
This is fixed and released in 1.15.1. |
@sebdah, I'm one of the maintainers of Boto. Boto 2.29.x fixed a bug where invalid AWS credential profile names were silently ignored (specifically boto/boto@af80944 as part of the AWS shared credential support), and I believe that this change has highlighted a bug in Dynamic DynamoDB. The line in the stack trace above that looks suspect to me is:
You seem to be creating an SNS connection and passing in ~/.boto[Credentials]
aws_access_key_id = 'my-default-key'
aws_secret_access_key = 'my-default-secret'
[profile foo]
aws_access_key_id = 'my-foo-key'
aws_secret_access_key = 'my-foo-secret' You would use it like so: >>> import boto.sns
>>> sns = boto.sns.connect_to_region('us-east-1', profile='foo')
>>> sns.aws_access_key_id
'my-foo-key' I would strongly advise against forcing an older version of Boto as a solution to this issue, and instead fix the SNS instantiation in Dynamic DynamoDB to not pass an ARN to the |
Thanks for pointing this out @danielgtaylor! I'll reimplement this so that the connection handlers fetch and use the credentials rather than the profile ARN from the metadata. |
Further discussion and coding on this will be done in #188. |
I suddenly, after having it working fine for weeks, get problems starting dynamic-dynamodb. Seems that it doesn't find the instance profile:
However, the instance profile is there:
I have tried using 1.13.0, 1.14.0 and 1.15.0. I do
pip install --upgrade dynamic-dynamodb
.Can it be a problem with boto?
$ pip list | grep boto boto (2.29.1) botocore (0.42.0)
The text was updated successfully, but these errors were encountered: