[cs615asa] AWS credentials
Roy Vaccaro Jr.
rvaccaro at stevens.edu
Wed Apr 6 22:13:09 EDT 2016
I should have been more specific about my problem. I am using boto to
interface with AWS. Boto is supposed to read ~.aws/credentials to get the
pertinent key information to even make an aws connection before even
spinning up an instance. What I found is though the boto documentation
specifies that it will read the credentials file it does not. It will read
the ~/.boto file for the key info. I found a workaround that works for
me. I was more curious if other folks were using any of the programming
interfaces for AWS besides standard shell and they had similar issues.
Thanks for all the good info though.
On Wed, Apr 6, 2016 at 9:39 PM, Avineshwar Singh <asingh16 at stevens.edu>
> One more thing.
> If a volume-id is specified, that means it is already existing in some
> availability zone (with or w/o FS). Hence, the instance has to be created
> in that availability zone but not every ami-id is supported in every zone.
> There should be a query of volume's zone and then choose an instance to
> create, in that availability zone.
> And that is bad.
> On 6 April 2016 at 18:52, Avineshwar Singh <asingh16 at stevens.edu> wrote:
>> Why would you do anything to *~/.aws/credentials* ?
>> If it has something to do with changing your region (as a pre-created
>> volume's zone should match with our instance's zone; here, volume's zone is
>> a constraint), probably it is achievable by suppressing the output of *aws
>> configure *and changing the value of region to the region where our
>> volume is present, since there should be no user interaction once the tool
>> is running.
>> However, since this script is to help the user, user has to be
>> cooperative (like following specific formats of saving environment variable
>> which we will consume, et cetera). This information should be reflected in
>> our script's help because the user will anyway have to refer to help part
>> when he will trying to use it for the first time and just for the sake of
>> running this tool, there will not be a requirement to change the
>> environment variables permanently rather it will be ephemeral, like: even
>> if he assigns a variable to something that we want him to put for the tool
>> to work, it will only be there for that particular shell window (another
>> shell window will reflect his permanent value, not this one). So, we can
>> use his variables by, optionally, making him choose to save those
>> environment variable in a specific format. This is not the only way.
>> Standardization of this tool is going to take some more effort.
>> The best thing to do is make the user to cooperate with the tool,
>> however, we have to keep in mind that we don't break the rules we need to
>> follow while creating this tool (no user interaction, no useless outputs,
>> no setting or modification of environment variables, no temporary files).
>> On 6 April 2016 at 18:11, Roy Vaccaro Jr. <rvaccaro at stevens.edu> wrote:
>>> In working on the HW assignment I found if you use one of the AWS SDK's
>>> the location for credentials is different from the command line "aws ec2"
>>> For example using boto in python the library will look for the
>>> credentials in either a .boto file or ~/.aws/credentials (You can also use
>>> environment variables)
>>> Should the tool require the user to have one of these files or the env
>>> variables in place?
>>> cs615asa mailing list
>>> cs615asa at lists.stevens.edu
>> Avineshwar Pratap Singh,
>> MS (in CyberSecurity),
>> Stevens Institute of Technology
>> [+] Add me to your address book
> Avineshwar Pratap Singh,
> MS (in CyberSecurity),
> Stevens Institute of Technology
> [+] Add me to your address book
> cs615asa mailing list
> cs615asa at lists.stevens.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cs615asa