aws-codebuild-docker-images
awslogs
Our great sponsors
aws-codebuild-docker-images | awslogs | |
---|---|---|
9 | 8 | |
1,091 | 4,750 | |
1.5% | - | |
6.1 | 0.0 | |
3 days ago | 26 days ago | |
Dockerfile | Python | |
GNU General Public License v3.0 or later | 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.
aws-codebuild-docker-images
-
DevSecOps with AWS- IaC at scale - Building your own platform - Part 1
Based on public repository for Codebuild Image, the image base will be the Ubuntu standard 7.0.
-
Firecracker internals: deep dive inside the technology powering AWS Lambda(2021)
This is basically what CodeBuild does.
The default Docker containers that CodeBuild uses (you can create your own) and the shell script it uses to parse the yaml configuration file (mostly a list of shell scripts) are all open source and the entire process can be run locally.
https://github.com/aws/aws-codebuild-docker-images
https://docs.aws.amazon.com/codebuild/latest/userguide/use-c...
Disclaimer: I work for AWS. But nowhere near the team that developed Firecracker
-
CircleCI says hackers stole encryption keys and customers’ source code
Disclaimer: I work for AWS in Professional Services. All opinions are my own.
The beauty about CodeBuild is that there is no “lock-in”. All it is fundamentally is a Linux or Windows Docker container with popular language runtimes and a shell script that processes a yaml file or you can supply your own Docker container.
You just put a bunch of bash commands or PowerShell commands in the yaml file and it runs anything.
The Docker container and the shell scripts are all open source and you can quite easily run them locally.
I could see outside of AWS keeping your Docker containers for your specific build environments in a local repository and doing all of your builds inside them using Jenkins.
https://github.com/aws/aws-codebuild-docker-images
https://docs.aws.amazon.com/codebuild/latest/userguide/use-c...
For a “batteries included” approach though, I really like Azure DevOps Pipelines.
I’ve even done a couple of integrations between Azure DevOps and AWS when we had clients that are Microsoft shops.
https://aws.amazon.com/vsts/
For AWS, if you use CodeCommit (AWS git service), all access is via IAM and granular permissions. If you integrate with Azure DevOps, the AWS credentials do have to be stored in a separate MS hosted credential storage.
CodeBuild also supports at least Github natively.
I’m not shilling for AWS. I have an MS development background (.Net) and only have “DevOps” experience using AWS and Microsoft tooling.
-
Continuous Integration and Deployment on AWS - and a wishlist for CI/CD Tools on AWS
Docker Images provided by the CodeBuild team should be updated regularly and should support all "modern" toolkits. The open source project has some activity, but an issue for supporting newer Android versions is now open for some time...
-
Building a Flutter application for Web, iOS and Android using a CI/CD pipeline on CodeBuild – #cdk4j
The runtimes available and exposed by CodePipeline support Android runtime 29 – and the Docker images are provisioned using Java 8. Unfortunately, as of July 2021, the Android gradle tools (used by Flutter) require Java 11. I have created an issue in the corresponding Github (see here) but needed to find a workaround to move on – I think I’ve found one, but I hope that anyone reading this might have a better way or idea?
- Is there a way to request a new runtime for codebuild?
-
Run local Graviton2 builds with AWS CodeBuild agent
$ git clone https://github.com/aws/aws-codebuild-docker-images.git $ cd aws-codebuild-docker-images/al2/aarch64/standard/2.0 $ docker build -t codebuild/amazonlinux2-aarch64-standard:2.0 .
-
Build and share Docker images using AWS CodeBuild and Graviton2
This also is the place where we specify this is an AArch64 build. The managed image indicates to use a standard image provided by AWS. The source of the Graviton2 image can be found on GitHub.
-
DevOps tools you should have on your belt
🏗 AWS CodeBuild Local Builds - Simulate a CodeBuild environment locally to quickly troubleshoot the commands and settings located in the BuildSpec file.
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?
cfn-python-lint - CloudFormation Linter
Loguru - Python logging made (stupidly) simple
hello-arm
cw - The best way to tail AWS CloudWatch Logs from your terminal
saml2aws - CLI tool which enables you to login and retrieve AWS temporary credentials using a SAML IDP
GoAccess - GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through your browser.
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.
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
aws-extend-switch-roles - Extend your AWS IAM switching roles by Chrome extension, Firefox add-on, or Edge add-on
faasd - A lightweight & portable faas engine
awsume - A utility for easily assuming AWS IAM roles from the command line.
aws-lambda-runtime-interface-emulator