Re: issue #14, this PR changes FlowLogsReader such that it honors the user's region configuration.
According to the boto3 documentation, you may try to initialize boto3.client without a region specified if the AWS_DEFAULT_REGION environment variable is set or if the ~/.aws/config file has a default region set.
FlowLogsReader now behaves like this:
If you request a region, it uses that one
If you don't request a region, it tries to use the environment or profile default
If you don't request a region, and there's no environment or profile, it uses us-east-1.
@hjacobs, I presume this will fix your issue? I will merge this, create a new release, and close #14 if so.
hjacobs
commented
9 years ago
Re: issue #14, this PR changes
FlowLogsReadersuch that it honors the user's region configuration.According to the boto3 documentation, you may try to initialize
boto3.clientwithout a region specified if theAWS_DEFAULT_REGIONenvironment variable is set or if the~/.aws/configfile has a default region set.FlowLogsReadernow behaves like this:us-east-1.@hjacobs, I presume this will fix your issue? I will merge this, create a new release, and close #14 if so.