Table of Contents
Serverless architecture is an integral benefit of cloud computing which allows developers to build and run services without having to manage the underlying infrastructure. Amazon Web Services' (AWS) Lambda is the dominant service in the serverless market and is relied upon by the world's largest companies due to its cost-effective, event-driven service that runs code in response to events and automatically manages the computing resources required by that code.
One drawback to using AWS's services is that navigating the AWS console can be quite challenging. Additionally, lack of descriptive documentation pertaining to AWS's Lambda service makes it difficult to visualize key function metrics at a glance. To solve this, we built Lumos, a free and open-source AWS lambda monitoring tool that allows users to connect their AWS account to track and visualize their key lambda metrics on a visually appealing UI.
- React
- Material-UI
- Chart.js
- AWS Lambda
- AWS SDK
- AWS STS
- AWS CloudWatch
- Node
- Express
- PostgreSQL
- Webpack
- Bcrypt
- JSON Web Token
Lumos requires access keys to sign programmatic requests to the AWS SDK. It is best practice to create an IAM user with permanent long-term credentials to interact with AWS services directly.
- In your AWS console, create an new IAM user. Make sure to check off "Access key - Programmatic access" when selecting an AWS credential type. Save these keys in a secure location. They cannot be retrieved after you've completed your IAM setup! If you lose your key, you will have to delete the access key and create a new one.
- Attach two existing policies directly to your IAM user's security policy:
-
From your terminal, access the AWS CLI by typing in
aws configure. Follow the steps on your screen and input your access key ID and secret access key.
The key lambda metrics we found to be of most interest to users were invocations, durations, and errors. One can visualize their lambda functions metrics across three different time periods: 24 hours, 1 week, or 1 month. Users can visualize their insights through two charts: donut and line. A donut chart will give an overview of all active invocations relating to the functions. The line chart will give a visualization of the number of times each lambda function has been invoked across selected time periods. Lumos also approximates the total cost of a user's lambda functions based on the function's duration and memory usage.
At Lumos, we open-sourced the project with the intention of having amazing people iterate on our project.
If you have any suggestions on how to improve Lumos, please follow the steps below:
- Fork Lumos
- Create your Feature Branch (
git checkout -b feature/YourFeature) - Add your changes using (
git add .) - Commit your Changes (
git commit -m 'Add Your Feature') - Push to the Branch (
git push origin feature/YourFeature) - Open a Pull Request
- Hit the star button!!
Thank you and we truly appreciate all your contributions!
Distributed under the MIT License.