Private AWS ECR with custom domain, credHelper and Cognito
Let’s make it all work: private AWS ECR repository + custom external domain + ECR Credentials Helper Login + control permissions to fetch your images via Cognito
Let’s make it all work: private AWS ECR repository + custom external domain + ECR Credentials Helper Login + control permissions to fetch your images via Cognito
How to be able to use your custom domain when accessing docker repository hosted in private AWS ECR.
You have a Quarkus-based AWS Lambda using logback and want to send logs to logz.io? Then this is something for you!
You have your Lambda on AWS. Now you want to view the logs in Cloudwatch and you probably know this is not the most pleasant thing to do. But wait, there are things like Logz.io - an ELK service that makes viewing logs a breeze. Let’s see how to connect logz.io log shipper that will push your Lambda logs from cloudwatch to their ELK stack.
How to configure a new user password in AWS Cognito using plain HTTP calls?
How to easily revert to previously deployed docker image in case new version of your app behaves abnormally?
How to authenticate in AWS Cognito using plain HTTP calls?
Imagine your code waits for some external system to respond. Easy to deal with non-serverless world where you have your application running 24/7, right? But how would you solve this in a serverless where you should pay for actual job and not for waiting. In serverless ‘wait’ equals ’loosing money’. In this post I’ll describe how you can use SQS for serverless job triggering.
AWS Systems Manager (formerly SSM) allows you to define secure, encrypted variables that you can read from other processes. Here, I’ll shortly discuss how to define such encrypted varible and read it from AWS CodeBuild.
With Serverless Framework application it’s not enough to add proper gitignore statements. You also need to take care of properly defining what should go and what should not go into your package or you can easily end with 100 MB packages.