Just a little addition, you can also update Beanstalk by using Codepipeline. You can connect your GitHub repository to Codepipeline and then set up the workflow to update your Beanstalk once the code is done building.
Although I would recommend ECS/Fargate over Beanstalk, if you need to do some HTTPS termination and don't want to purchase a custom domain, you can add Cloudfront in front of your Beanstalk application.
That being said, Apprunner is IMO the best way to host lightweight Node JS backend apps since the CPU is throttled when no inbound requests are detected. Be mindful however as this does not support the running of worker type of processes.
But all the same, very enlightening post Airah! Looking forward to your next one.
Thank you so much for reading and offering these suggestions Tomisin🙏🏾
I have not explored much of AWS services for CI/CD but I can definitely see CodePipeline being a way to automate the uploads for Beanstalk.
Taiwo Oluwatomisin
Amazing post Airah! Keep it up.
Just a little addition, you can also update Beanstalk by using Codepipeline. You can connect your GitHub repository to Codepipeline and then set up the workflow to update your Beanstalk once the code is done building.
Although I would recommend ECS/Fargate over Beanstalk, if you need to do some HTTPS termination and don't want to purchase a custom domain, you can add Cloudfront in front of your Beanstalk application.
That being said, Apprunner is IMO the best way to host lightweight Node JS backend apps since the CPU is throttled when no inbound requests are detected. Be mindful however as this does not support the running of worker type of processes.
But all the same, very enlightening post Airah! Looking forward to your next one.