In order to build & applications in , you need to assume that everything will fail. Therefore, you always design and deploy your application in multiple & . So you end up with many unused AWS resources (Snapshots, ELB, EC2, Elastic IP, etc) that could cost you a fortune. HA Resilient AWS AZ regions One pillar of is . That’s why you need to have a global overview of your . Fortunately, AWS offers many fully-managed services like , , & to help you achieve that. But, they require a deep understanding of AWS Platform and they are not straighforward. AWS Well-Architected Framework Cost optimization AWS Infrastructure CloudWatch CloudTrail Trusted Advisor AWS Config That’s why I came up with a tool that simplifies the process by querying the to fetch information about almost all critical services of AWS like , , , , … in real-time in a single . Komiser AWS API EC2 RDS ELB S3 Lambda Dashboard Note: To prevent excedding AWS API rate limit for requests, the response is cached in by default for . in-memory cache 30 minutes supported : Komiser AWS Services Compute: Running/Stopped/Terminated EC2 instances Current EC2 instances per region EC2 instances per family type Lambda Functions per runtime environment Disassociated Elastic IP addresses Total number of Key Pairs Total number of Auto Scaling Groups Network & Content Delivery: Total number of VPCs Total number of Network Access Control Lists Total number of Security Groups Total number of Route Tables Total number of Internet Gateways Total number of Nat Gateways Elastic Load Balancers per family type (ELB, ALB, NLB) Management Tools: CloudWatch Alarms State Billing Report (Up to 6 months) Database: DynamoDB Tables DynamoDB Provisionned Throughput RDS DB instances Messaging: SQS Queues SNS Topics Storage: S3 Buckets EBS Volumes EBS Snapshots Security Identity & Compliance: IAM Roles IAM Policies IAM Groups IAM Users 1 — Configuring Credentials needs your AWS credentials to authenticate with AWS services. The supports multiple methods of supporting these credentials. By default the CLI will source credentials automatically from its . The common items in the credentials chain are the following: Komiser CLI default credential chain Environment Credentials: AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION ( ) Shared Credentials file ~/.aws/credentials EC2 Instance Role Credentials To get started, create a new , and assign to it this following : IAM user IAM policy Next, generate a new & , then update file as below: AWS Access Key Secret Key ~/.aws/credentials 2 — Installation 2.1 — CLI Find the for your system and download it. For linux: appropriate package wget https://s3.us-east-1.amazonaws.com/komiser/1.0.0/linux/komiser chmod +x komiser Note: The is updated frequently with support for new AWS services. To see if you have the latest version, see the . Komiser CLI project Github repository After you install the , you may need to add the path to the executable file to your variable. Komiser CLI PATH 2.2 — Docker Image Use the official : Komiser Docker Image docker run -d -p 3000:3000 -e AWS_ACCESS_KEY_ID=”” -e AWS_SECRET_ACCESS_KEY=”” -e AWS_DEFAULT_REGION=”” — name komiser mlabouardy/komiser 3 — Overview Once installed, start the : Komiser server komiser start — port 3000 — duration 30 If you point your favorite browser to , you should see : http://localhost:3000 Komiser Dashboard Hope it helps ! The CLI is still in its early stages, so you are welcome to contribute to the project on . Github
