search

joseph-holland / lambda-graffiti-monkey

An AWS Lambda function to run Graffiti Monkey
Apache License 2.0
15 stars 8 forks source link

Regarding tagging at regions EU-WEST-3 and EU-NORTH-1. #16

Closed siva123git closed 5 years ago

siva123git commented 5 years ago

Hi! I am trying to tag all regions from lambda function in ohio region but every region seems to be working fine, as soon as it comes to EU-WEST-3 aka Paris and EU-NORTH-1 aka Stockholm it starts shooting errors. I am not able to understand why.

Error i get for eu-west-3: 2019-02-28 09:29:55,537 - root - INFO - Loading function 2019-02-28 09:29:55,537 - graffiti_monkey.core - INFO - Connecting to region eu-west-3 using profile None 2019-02-28 09:29:55,537 - graffiti_monkey.core - INFO - Getting list of all volumes 2019-02-28 09:29:55,537 - root - ERROR - Error: Graffiti Monkey encountered the following error: 'NoneType' object has no attribute 'get_all_volumes'

Error i get for eu-north-1: 2019-02-28 09:29:55,537 - root - INFO - Loading function 2019-02-28 09:29:55,537 - graffiti_monkey.core - INFO - Connecting to region eu-north-1 using profile None 2019-02-28 09:29:55,537 - graffiti_monkey.core - INFO - Getting list of all volumes 2019-02-28 09:29:55,537 - root - ERROR - Error: Graffiti Monkey encountered the following error: 'NoneType' object has no attribute 'get_all_volumes'

can you please help me here?

cubagithub commented 5 years ago

Hi siva123git. Did you reconfigure the Lambda to run against all regions, or did you just use the standard zip and configure each region individually?

sangeetharajaram commented 5 years ago

Hi!. I'm facing the same problem and in both the cases ( modifying the code to run in multiple regions or configuring the region name in environment variable), we are receiving the same error.

siva123git commented 5 years ago

Hi @cubagithub. I tried both cases. In both the cases it's throwing the same error for "eu-north-1" and "eu-west-3" regions.

siva123git commented 5 years ago

hey @cubagithub. We got it. It was boto package problem. The endpoints.json in boto package was not updated with new regions in it. Sorry for bothering you..