Alright, this has diverged, since I last created this story back in October.
I'm thinking the best plan of action is to use Cloudfront/S3 for the client. Then Cloudfront/ApiGatewayv2HTTP/lambda/dynamodb for doing actions on the game. And finally ApiGatewayv2Websocket/lambda/dynamodb for controlling the websocket and live updates for the game.
The reason that I chose this over Cloudfront/ALB/ECS, is because ALB/ECS is pretty expensive (or really just ALB), and I'm going with the little over-engineered route so that it can always be up, and barely cost me anything (since it won't be used that much).
kirbyjs
commented
4 years ago
Description
Alright, this has diverged, since I last created this story back in October.
I'm thinking the best plan of action is to use Cloudfront/S3 for the client. Then Cloudfront/ApiGatewayv2HTTP/lambda/dynamodb for doing actions on the game. And finally ApiGatewayv2Websocket/lambda/dynamodb for controlling the websocket and live updates for the game.
The reason that I chose this over Cloudfront/ALB/ECS, is because
ALB/ECSis pretty expensive (or really just ALB), and I'm going with the little over-engineered route so that it can always be up, and barely cost me anything (since it won't be used that much).