kxseven / axe Goto Github PK

An axe command for logging into your AWS account.

As a user I start axe and run the 'axe-login' command. This will look the same as running the .login command but will show up in axe command completion.

Option 1:

• After loading initial credentials it should be possible to list and then assume available configured roles

Option 2:

• Initial load of credentials is also combined with assuming an IAM role after credentials are loaded

If I run the command 'axe list ec2' rather than getting a message to say this is a bad command I get the error message "no filter".

The following would be more user friendly
"No such command 'list ec2', here are the available options for the list command."

• ideally a simple wrapper for

cd $AXE_ROOT
git pull
cd -
axe --version

Would it be possible to get OS type and tags from the inventory report?

I know its possible to get OS type with describe-images and the AMI id.

As an axe user I'd like to be able to pipe a subset of the output fields to another command.

For example, I'd like to be able to run the following command to list all my instances and their IP addresses.

'axe list ec2-instance-detailed -o InstanceId,PrivateIpAddress'

As an axe user I run the axe-region command. I am prompted with a list of regions, I choose the region and my environment is changed such that the commands I run are run in the region I have just chosen.

AWS' recent accouncement of support for extended token expiry for IDP/SAML based authentication (
https://aws.amazon.com/blogs/security/enable-federated-api-access-to-your-aws-resources-for-up-to-12-hours-using-iam-roles/)

Requires

• Requires the 'latest' version of the awscli and boto

aws iam get-role --role-name AWS-Cloud-Admin

{
    "Role": {
        "AssumeRolePolicyDocument": {
            "Version": "2012-10-17", 
            "Statement": [
                {
                    "Action": "sts:AssumeRoleWithSAML", 
                    "Principal": {
                        "Federated": "arn:aws:iam::1234567890:saml-provider/IDP"
                    }, 
                    "Effect": "Allow", 
                    "Condition": {
                        "StringEquals": {
                            "SAML:aud": "https://signin.aws.amazon.com/saml"
                        }
                    }, 
                    "Sid": ""
                }
            ]
        }, 
        "MaxSessionDuration": 14400, 
        "RoleId": "ABCDEFGHIJKLMONPQRSTUVWXYZ", 
        "CreateDate": "2015-08-03T12:24:07Z", 
        "RoleName": "AWS-Cloud-Admin", 
        "Path": "/", 
        "Arn": "arn:aws:iam::1234567890:role/AWS-Cloud-Admin"
    }
}

The ec2-instances* JQF filters are causing duplicate entries in the results when the Description Tag is blank

As an axe user I'd like to be able to pipe my output to another command. The header information can sometimes be hard for another command to accept.

Could you have an option on the axe command such that headers do not get displayed.

As an initial axe user I run a command to import my AWS credentials and settings like region into an axe identity.

Should we default to including any and all Tags found on the resources being listed?

Pros:

• More useful information by default
• Lessens the need for secondary '-detailed' filters as the number of resource types grows

Cons:

• Long-ass tag names and values (eg. CloudFormation, 'Description' fields)

As an axe user I'd like the ability to run axe commands on all regions. This could link in with the axe-region command such that you can choose 'ALL' as a region and then your commands will them be run on all regions.

Add support for other commonly used resources;

• Load Balancers (ELBs, ALBs)
• RDS instances

Add support for SSL certs in detailed ELB listing

Not everyone has patched fonts available. Default to using unpatched font compatible PS1

Add support for transposing the rows/cols of the tabular output of the 'list' sub-command

This is an issue to collect and collate feedback on possible changes and improvements to making the AXE tools more accessible to users;

Suggestions to-date:

• Docker image
• Vagrantfile that provides a complete workspace
• An AWS AMI
• Something similar to Google's Cloud Shell (https://cloud.google.com/shell/docs/)