To drive down operational costs even more replace the NLB with an elastic IP, associate it to the EC2 instance hosting the task.
Also, if you are ok with having 1 instance of the task at any given moment (no auto-scaling, blue/green deployments) replace the EFS with an EBS volume. EFS is a very expensive storage option.
Otherwise, nice article. Look forward to seeing more of your writings.
I completely agree with you 😊 I've used EFS because I have the same FS for both vanilla and modded Minecraft but different access points. I will try and create a new branch with even lower costs but at the end of they day there will always be cheaper options 😅
I have corrected some mistakes in the post, i.e. 200$ was way too expensive :P
I have also created a budget version, around 25$ if you want to flex and host Minecraft on ECS.
Github: https://github.com/siakon89/minecraft-server/tree/budget-server
To drive down operational costs even more replace the NLB with an elastic IP, associate it to the EC2 instance hosting the task.
Also, if you are ok with having 1 instance of the task at any given moment (no auto-scaling, blue/green deployments) replace the EFS with an EBS volume. EFS is a very expensive storage option.
Otherwise, nice article. Look forward to seeing more of your writings.
I completely agree with you 😊 I've used EFS because I have the same FS for both vanilla and modded Minecraft but different access points. I will try and create a new branch with even lower costs but at the end of they day there will always be cheaper options 😅
Nice article! NLB over ALB because we are on L4, which offers lower latency?
Went with L4 (NLB) due to Minecraft server, it is just a TCP port. If you have a web application ALB it is 😊
I have update the budget-server branch with just an EIP and no NLB as David said.