ECS is a good option for hosting Node.js applications with less billing because it allows you to pay only for the resources that you use. For example, if you use Fargate, you will only pay for the vCPU and memory that your containers consume. If you use EC2, you will only pay for the EC2 instances that your containers are running on. Serverless computing services such as AWS Lambda allows you to run Node.js code without having to manage any infrastructure. You are charged only for the time that your code is running.
This is really a great question. There are many good things you can do to maintain a live application: 1. Automate Deployments with GitHub Actions: Create a workflow that triggers on code changes (e.g., pushes to the main branch). 2. Blue-Green Deployments (Recommended) 3. Rolling Updates: Update a few container instances at a time, gradually rolling out the new version. 4. Health Checks: Ensure ECS has health checks configured to monitor container health and automatically replace unhealthy instances. 5. Monitoring and Logging: Monitor application and infrastructure metrics to track deployment success and identify potential issues. 6. Security: Enforce security best practices throughout the deployment pipeline.
error parsing HTTP 404 response body: invalid character 'p' after top-level value: "404 page not found " 146Error: Process completed with exit code 1. I m getting the above error.
My app is running but unable to reach through public ip It is running in PORT 5000 also added container port mapping But still unable to reach the app Can you please help me?
Please check security group settings if you can access the content through public ip and that port. Also check firewall settings, and applications logs in cloud watch.
Thanks for the question! Adding SSL is an important step for securing your application. You can follow below mentioned points: 1. Generate SSL Certificates: You can either generate a self-signed certificate for testing purposes or obtain a trusted certificate from a Certificate Authority (CA). 2. Store Certificates in Secrets Manager: AWS Secrets Manager is a secure way to store your SSL certificates and private keys within your AWS environment. You can integrate this step into your GitHub Actions workflow. 3. Configure Your Application: Update your Node.js application to use the stored SSL certificates and keys. This might involve environment variables or configuration files within your Docker image. 4. Configure AWS Load Balancer: Modify your AWS Load Balancer configuration (e.g., Application Load Balancer) to terminate SSL connections at the load balancer level. This offloads processing from your Node.js instances. Try out mentioned steps, in future I will also create tutorial with SSL soon.
Best of the best AWS tutorials I have watched so far. Thanks, Helped a lot.
Glad it helped!
Insightful, thanks for sharing this 👍
Glad you enjoyed it!
it's very helpful for me,keep it upbro
Thanks.
Thanks! It helps a lot!
Glad to hear that!
Thanks for your help
No Problem. Keep Learning 😀
Hi, I stuck in ecsTaskExecution creation while task definition, will you able to help with proper document ?
Try to create ecsTaskExecution role from IAM console.
what service case /use case should be added in IAM role
What are best option for hosting nodejs with less billing ec2, ecs Or any other option, like to handle around 50k traffic?
ECS is a good option for hosting Node.js applications with less billing because it allows you to pay only for the resources that you use. For example, if you use Fargate, you will only pay for the vCPU and memory that your containers consume. If you use EC2, you will only pay for the EC2 instances that your containers are running on.
Serverless computing services such as AWS Lambda allows you to run Node.js code without having to manage any infrastructure. You are charged only for the time that your code is running.
Hi while creating task definitions im not getting ecsTaskExecution role in dropdown
You can create a task execution role from IAM console.
how to deploy full stack mern , nextjs
Will upload a video soon on deployment process for MERN stack application.
how will we deploy if we have mysql database to node backend
Need to configure docker-compose.yml file with db configuration and MySQL setup on AWS. I will try to create that tutorial soon.
Hi After Deploy on Ecs Node Js application Suppose Developer Update on Node js application Github How to manage Live application
This is really a great question. There are many good things you can do to maintain a live application:
1. Automate Deployments with GitHub Actions: Create a workflow that triggers on code changes (e.g., pushes to the main branch).
2. Blue-Green Deployments (Recommended)
3. Rolling Updates: Update a few container instances at a time, gradually rolling out the new version.
4. Health Checks: Ensure ECS has health checks configured to monitor container health and automatically replace unhealthy instances.
5. Monitoring and Logging: Monitor application and infrastructure metrics to track deployment success and identify potential issues.
6. Security: Enforce security best practices throughout the deployment pipeline.
Can you provide Real Time Example video So better understanding
error parsing HTTP 404 response body: invalid character 'p' after top-level value: "404 page not found
"
146Error: Process completed with exit code 1.
I m getting the above error.
Will it cost in future if yes then how can we stop them
I am a freshman and that's why I have these kinds of questions so please answer me brooo
My app is running but unable to reach through public ip
It is running in PORT 5000 also added container port mapping
But still unable to reach the app
Can you please help me?
Please check security group settings if you can access the content through public ip and that port. Also check firewall settings, and applications logs in cloud watch.
@@IntegrationNinjas Thanks
I think my issue was VPC
how do you add ssl
Thanks for the question! Adding SSL is an important step for securing your application. You can follow below mentioned points:
1. Generate SSL Certificates: You can either generate a self-signed certificate for testing purposes or obtain a trusted certificate from a Certificate Authority (CA).
2. Store Certificates in Secrets Manager: AWS Secrets Manager is a secure way to store your SSL certificates and private keys within your AWS environment. You can integrate this step into your GitHub Actions workflow.
3. Configure Your Application: Update your Node.js application to use the stored SSL certificates and keys. This might involve environment variables or configuration files within your Docker image.
4. Configure AWS Load Balancer: Modify your AWS Load Balancer configuration (e.g., Application Load Balancer) to terminate SSL connections at the load balancer level. This offloads processing from your Node.js instances.
Try out mentioned steps, in future I will also create tutorial with SSL soon.
Can you share aws eks ?
I will create on that soon
bruhh IAM rolle coment karo for ec2ContainerService...?
You can create a role and assign below policies:
AmazonEC2ContainerServiceforEC2Role
AmazonECSTaskExecutionRolePolicy
bruhh i am a dev struggled quit a lot knowing aws plz do recreate this video verry janky
Please go through this tutorial and follow step by step.
why do you every time jump from one tab to another ?
why do you nervouse moving a mouse a lot ?
dislike for this
I am just following the process I want to show. I appreciate the feedback and I will try to improve myself. Thanks.
why do you every time jump from one tab to another ?
why do you nervouse moving a mouse a lot ?
dislike for this
I am just following the process I want to show. I appreciate the feedback and I will try to improve myself. Thanks.