software at the end of the universe

Main menu

Monthly Archives: May 2011

Using AWS Identity and Access Management you can create separate users and permissions to use any AWS service, for instance EC2, and avoid giving other people your Amazon username, password or private key. 

You can set very granular permissions, on users, groups, specific resources, and a combination of them.  It will become really complex soon!  But there are several very common use cases, that IAM is useful for.  For instance having a AWS account for a team of developers. 

The first line is your Access Key ID; the second line is your Secret Access Key.  You need to save these IDs. 

Save your Access Key ID and your Secret Access Key to a file called for instance ~/YOUR_NAME_cred.txt.  You can use those credentials from now on instead of the global AWS credentials for the whole account. 

export AWS_CREDENTIAL_FILE=~/YOUR_NAME_cred.txt

Creating a dev group

Let’s create an example dev group where the users will have only read access to EC2 operations. 

iam-groupcreate -g dev

Now we need to set the group policy to allow all EC2 Describe* actions, which are the ones that allow users to see data, but not to change it.  Create a file MyPolicy.txt with these contents

About Policies

AWS policy files can be really complex.  The AWS Policy Generator will help as a start point and see what actions can be used, but it won’t help you making them easier to read (using wildcards) or applying them to specific resources.  Amazon could have provided a better generator tool allowing you to choose your own resources (users, groups, S3 buckets,…) from a easy to use interface and not having to lookup all sorts of crazy AWS identifiers.  Hopefully they will be provide a comprehensive tool as part of the AWS Console.