But many other tools don’t yet support the new format config file or multi-profiles. But they do support shell environment variables. So I wrote a simple ruby script that

• Allows you to specify the profile name as an argument
• Reads in the config file ~/.aws/config
• Outputs the export statements for publishing the environment variables
  • You can eval the output to set the environment of your current shell session

So if you had a config file ~/.aws/config that looked like this:

[default]
aws_access_key_id=AKI***********2A
aws_secret_access_key=jt41************************************p
region=us-east-1

[profile foo]
aws_access_key_id=0K***************K82
aws_secret_access_key=2b+***********************************1g
region=us-east-1

[profile bar]
aws_access_key_id=AKI**************GA
aws_secret_access_key=MG************************************/d
region=us-east-1

If you don’t specify any argument to the command it will output the default profile:
 $ aws_switch
export AWS_ACCESS_KEY_ID=AKI***********2A
export AWS_SECRET_ACCESS_KEY=jt41************************************p
export AMAZON_ACCESS_KEY_ID=AKI***********2A
export AMAZON_SECRET_ACCESS_KEY=jt41************************************p
export AWS_ACCESS_KEY=AKI***********2A
export AWS_SECRET_KEY=jt41************************************p

If you specified a profile (in this case foo):
$ aws_switch foo
export AWS_ACCESS_KEY_ID=0K***************K82
export AWS_SECRET_ACCESS_KEY=2b+***********************************1g
export AMAZON_ACCESS_KEY_ID=0K***************K82
export AMAZON_SECRET_ACCESS_KEY=2b+***********************************1g
export AWS_ACCESS_KEY=0K***************K82
export AWS_SECRET_KEY=2b+***********************************1g

You would actually use it by eval’ing the output of aws_switch so it sets the variables in the environment of yhour current shell:
eval `aws_switch foo`

Here’s the code for aws_switch. Put it in someplace in your $PATH and make sure to chmod 0755 the file so its executable:
#!/usr/bin/env ruby
require 'inifile'

configs = IniFile.load(File.join(File.expand_path('~'), '.aws', 'config'))

profile_name_input = ARGV[0]
case profile_name_input
when 'default'
  profile_name = 'default'
when nil
  profile_name = 'default'
when ""
  profile_name = 'default'
else
  profile_name = "profile #{profile_name_input}"
end

id = configs[profile_name]['aws_access_key_id']
key = configs[profile_name]['aws_secret_access_key']

puts "export AWS_ACCESS_KEY_ID=#{id}"
puts "export AWS_SECRET_ACCESS_KEY=#{key}"
puts "export AMAZON_ACCESS_KEY_ID=#{id}"
puts "export AMAZON_SECRET_ACCESS_KEY=#{key}"
puts "export AWS_ACCESS_KEY=#{id}"
puts "export AWS_SECRET_KEY=#{key}"
The post CLI to Switch Amazon AWS Shell Environment Credentials first appeared on Cognizant Transmutation.
]]>
					
		
		
		1616	
		
		
		https://www.ibd.com/macintosh/install-pgrep-and-pkill-for-mac-os-x-with-brew/
		
		
		Fri, 29 Jul 2011 05:43:31 +0000
				
		
		
		http://blog2.ibd.com/?p=801

					My fingers still tend to do ps ax | grep some_program_name_I_want_to_kill and then do a kill 2012 to kill that process. Then I remember that I could use pgrep and/or pkill to do the same kind of thing. But then I remember I’m on a Mac which doesn’t have those commands built in, though most other *nix platforms do. So…

The post Install Pgrep and PKill for Mac OS X with Brew first appeared on Cognizant Transmutation.
]]>
										My fingers still tend to do ps ax | grep some_program_name_I_want_to_kill and then do a kill 2012 to kill that process. Then I remember that I could use pgrep and/or pkill to do the same kind of thing. But then I remember I’m on a Mac which doesn’t have those commands built in, though most other *nix platforms do.

So I usually would try to use Homebrew to install it: brew install pgrep
only to get: Error: No available formula for pgrep
After a bit of googling I find again that its: brew install proctools
 
The post Install Pgrep and PKill for Mac OS X with Brew first appeared on Cognizant Transmutation.
]]>
					
		
		
		801