terraforming
awslogs
terraforming | awslogs | |
---|---|---|
9 | 8 | |
4,298 | 4,755 | |
- | - | |
1.6 | 0.0 | |
over 2 years ago | about 1 month ago | |
Ruby | 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.
terraforming
- Importing multiple modules at once from AWS
-
Tools like terraformer
Terraforming
- Copy Azure resources via terraform
- Existing AWS resource to HCL?
-
Where to start with a mess?
I would also strongly recommend an iterative triage process: don't feel that you need to solve everything all once. It's a huge amount of progress if you can get to a stage where you understand the relationships between services, have enough monitoring to identify failures, and can iteratively move services to more granular IAM policies even if it's all still running in one big account. Simply using a tool like terraformer or terraforming to move the manual configuration into an IaC workflow is an accomplishment, especially since it helps you both make changes more confidently and identify where new changes are still being made. Depending on the politics, that last part might be important: you'll be unpopular if you take away everyone's rights but you'll probably have better luck first nudging people to make them using a sensible flow rather than by hand.
-
Just starting out with terraform. Doubts wrt existing infra.
Haven't tried this but if I ever find myself in your situation I'll give it a spin https://github.com/dtan4/terraforming
-
Continuous Infrastructure Deployment with Terraform Cloud
There are a couple of tools to automate creating terraform configuration and prepopulate state from existing resources, like terraforming, terraformer or cf-terraforming. But it is still cumbersome and laborious and in my experience, it's usually way easier to just recreate everything within terraform from scratch wherever that's possible.
- Current infrastructure as code
-
DevOps tools you should have on your belt
🧪 Terraforming export existing AWS resources to Terraform style (tf, tfstate).
awslogs
-
Logging in Python Like a Pro
Using the official CLI (aws logs get-log-events) or https://github.com/jorgebastida/awslogs is pretty close to SSH-ing and grepping.
- Tail log groups with CW Logs Insights?
-
I use cw, which is OSS to tail AWS CloudWatch Logs
cw is a native executable targeting your OS, and not needed external dependencies such as pip and npm. Compared to awslogs which is famous helpful tool for CloudWatch Logs1, cw is written in golang and faster.
-
What are you using to analyze/visualize CloudFront logs?
Its a command line tool but some people I know also use awslogs
-
Ask HN: Does anyone else find the AWS Lambda developer experience poor?
Not a full solution, but when I was doing this I really got to love the awslogs utility:
https://github.com/jorgebastida/awslogs
It allows you to stream Cloudwatch logs from the command line, so you can grep them, save them to files, etc... (The web based Cloudwatch interface is terrible.)
Another suggestion is to try to modularize the core business logic in your lambda such that you separate the lambda-centric stuff from the rest of it. Obviously, though, if "the rest of it" is hitting other AWS services, you're going to hit the same testing roadblock.
Or you can try mocking, which may or may not provide much value for you. There's a python library for that, (moto), but it's not 100% up to date wrt AWS services/interfaces, last I had checked. Might be worth a try though.
https://github.com/spulec/moto
-
Datadog alternatives
Cloudwatch Logs is pretty meh visually, but awslogs can give you a pretty good `tail -f`-like experience, and Insights is pretty good. Cloudwatch Metric Filters give you a 'StatsD'-like experience, in that you can log out a certain message or code and then use its appearance as a metric.
-
Cloud watch logs from console always show tail. How to show head without having to click ‘show more’ over and over again?
Check out https://github.com/jorgebastida/awslogs , you can define a `--start`, and it also has a `--watch`, and can be piped the `grep` or whatever you want. It's a pretty flexible tool.
-
DevOps tools you should have on your belt
📖 awslogs - a simple command-line tool for querying groups, streams, and events from Amazon CloudWatch logs.
What are some alternatives?
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
Loguru - Python logging made (stupidly) simple
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
cw - The best way to tail AWS CloudWatch Logs from your terminal
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
GoAccess - GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through your browser.
cf-terraforming - A command line utility to facilitate terraforming your existing Cloudflare resources.
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
aws-toolkit-vscode - Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
aws-codebuild-docker-images - Official AWS CodeBuild repository for managed Docker images http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html
saml2aws - CLI tool which enables you to login and retrieve AWS temporary credentials using a SAML IDP
faasd - A lightweight & portable faas engine