Aws

Why AWS has announced supporting rust for the lambda, but does not provide an official runtime for it. You have to provide your own, and the official way is through building a target where you can statically link a libc implementation: musl. While it appears you could statically link the glibc, it is not advised. (see here and here) So for AWS: What While searching for alternative solutions to this (Because reasons), I found that since late 2020, they added a container image support to AWS lambda. ...

Moving from Docker Hub to ECR Pubstack, my current client decided to migrate all its docker images to ECR. With the recent announcement about rate limiting on Docker Hub, maybe we will not be the only ones moving away. For our CI/CD pipelines we use both CircleCI and GitHub Actions. Using an ECR image is a really simple task in CircleCI, it consists of adding the aws_auth to the image configuration. docker: - image: ACCOUNT.dkr.ecr.REGION.amazonaws.com/IMAGE:VERSION aws_auth: aws_access_key_id: $AWS_ACCESS_KEY_ID aws_secret_access_key: $AWS_SECRET_ACCESS_KEY On the other hand, using ECR images in GitHub Actions was a bit more tricky. ...

First try without systemd During my previous mission, we used AWS ECR to manage the docker images. Amazon EC2 Container Registry (ECR) is a fully-managed Docker container registry that makes it easy for developers to store, manage, and deploy Docker container images. To be able to store/retrieve docker images, you have to be authenticated. AWS CLI provides a command which takes your credentials and generate a token, authenticating the user for 12 hours. ...