- Newest
- Most votes
- Most comments
Hi Samson,
-
For hosting as mentioned above you can use CloudFront and s3 for React. To seamlessly hook it into a CI/CD pipeline you can also look into Amplify, some references here (https://workshops.aws/categories/Front%20End) and here (https://aws.amazon.com/blogs/mobile/complete-guide-to-full-stack-ci-cd-workflows-with-aws-amplify/).
-
For Node you can use EC2,Elastic Beanstalk, ECS Fargate, AppRunner or even Lambda function
CloudFront and S3 could be used to host the front end, and EC2 or ECS could be used for the back end.
If you have members who are good with containers, using ECS on Fargate, for example, will make management a little easier because it will eliminate the need for OS maintenance.
In addition, if only static content is used, it is possible to function as a website with only CloudFront and S3 configuration.
https://repost.aws/knowledge-center/cloudfront-serve-static-website
Also, the following document may be helpful for CI/CD to S3.
https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-S3Deploy.html
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
Thank you alatech. I will review the link you mentioned. But, how can one use multiple services at the same time? You mentioned CloudFront and S3 for React, Amplify for CICD, and then Elastic Beanstalk for Node. That's four services right there......I AWS supposed computing easy.......