We were using (and weโre still it using for some services) Docker Cloud. Main problem with DC is that they canโt handle private subnets. EC2 instance must be in the public subnet and thatโs not what we want. Hooray (irony), we have to switch to the EC2 Container Service. Try to explain this to our business department. Additional time for infrastructure. Can handle it, but itโs tough sometimes.
Docker images repository Cloud Formation Template This step is optional, but weโre trying to leverage as many as possible AWS services. Read More...
As a small start up, weโre playing with lot of technologies and we try to choose the best ones. Okay, sometimes not because of money constraints, but weโre trying. One day, canโt remember when it was, we decided to go with AWS. Not just EC2 instances for Docker Cloud, but full stack. I mean API Gateway, Lambda, EC2, ECS, DynamoDB, etc. Counted them, AWS provides 51 services. Some of them are perfect, some of them still needs polishing, but theyโre pretty good generally speaking. Read More...
Itโs fragile and kind of terrible. Letโs look at it. We have a function named lambda. It has one argument named action (enum with allowed values data, exception or timeout). First thing we would like to do is to validate input via schema. Then we would like to return custom error message (and status code) if itโs invalid or do other things based on the action argument value.
Hereโs the code, just to demonstrate how it works. Read More...