saw
LocalStack
saw | LocalStack | |
---|---|---|
4 | 154 | |
1,387 | 52,502 | |
- | 1.4% | |
0.0 | 9.9 | |
about 1 year ago | 1 day ago | |
Go | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
saw
-
Lambda recursive loop detection - but not (yet) for S3
We use saw to tail lambda log:
-
Ask HN: Is there an alternative CloudWatch UI?
It's not a GUI, but saw[0] was my go to for grepping, streaming, and searching CloudWatch logs.
[0] https://github.com/TylerBrock/saw
- Ask HN: How do you read AWS Cloudwatch logs
-
This cloudwatch UI sucks
Also, for something closer to tail, check out: https://github.com/TylerBrock/saw
LocalStack
- LocalStack – a functional local AWS cloud stack
-
Let's build a screenshot API
Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:
-
LocalStack e AWS CLI: Como desenvolver localmente com a AWS
Acesse o site da LocalStack e faça login.
-
Cutting down AWS cost by $150k per year simply by shutting things off
To give this a slightly different spin:
--> "The best optimization is simply not spinning things up."
At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.
We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".
What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.
-
Getting Amazonka S3 to work with localstack
(For others who hadn't heard of it: localstack is
- LocalStack v3.0.0
- Localstack, a "AWS" local para desenvolvimento em cloud
-
Integration tests with AWS S3 buckets using Localstack and Testcontainers
LocalStack Website
- LocalStack: A functional local AWS cloud stack
-
Simulando a AWS no seu ambiente Local
O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.
What are some alternatives?
kail - kubernetes log viewer
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
stern - ⎈ Multi pod and container log tailing for Kubernetes -- Friendly fork of https://github.com/wercker/stern
sst - Build modern full-stack applications on AWS
viddy - 👀 A modern watch command. Time machine and pager etc.
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
cw - The best way to tail AWS CloudWatch Logs from your terminal
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
colorstyle - colorStyle is a library of styles for command-line text.
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
jzon - A golang json library inspired by jsoniter
Appwrite - Your backend, minus the hassle.