InitiateAuth and RespondToAuthChallenge to confirm user password and authenticate in AWS Cognito using plain HTTP calls
How to configure a new user password in AWS Cognito using plain HTTP calls?
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?
Notes to my future-self about how to configure React.js frontend guarded by AWS Cognito to securely communicate with backend based on Serverless Framework (AWS Lambda behind Api Gateway).
Issues I bumped into during restoration of a PostgreSQL backup.
Root cause of a weird ’linux/arm/v7 not supported error'.
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.
If you’re planning to use Python moto library (to mock AWS resources) for unit tests and at the same time use integration tests - watch out as it can bite you!