Your AWS DREAM Course coming Live SOON.... 🚀🥳 "Mastering AWS Cloud for Beginner - Learn AWS cloud by Building & Deploying scalable web application using 3 different aws architectures" Now you can: Pre-Register to the course and get 90% DISCOUNT or Get notification once the course is LIVE (Full Price) Here is everything you need to know: scaleupsaas.dev/aws-master-course-for-beginners/
Wow Wow Wow. Brilliant guide, I will be following this later on and I will feedback my thoughts. Thank you very much for taking the time to upload this.
Hello there I'm facing a problem in the deploy stage. It runs for 15 minutes to 30 minutes in progress and it fails but however my source and build stage is successfull. also I cross checked my ECS Service with ALB DNS link and the website works perfectly fine in that. what should I do?
I'm using the Ubuntu OS. I guess I have figured out the issue. when I have created my ECS server with ALB, I cloned the git repo in the nodejs-docker-aws-ecs branch but in the Source stage of my CodePipeline, I forked your nodejs-ci-cd-pipeline branch. as the dockerfile in both of these branches are different, it wouldn't have got deployed. now I'm planning to start again from the scratch. which branch should I choose for both my AWS ECR + ECS and AWS CodePipeline? note - I'm not able to use the AWS CodeCommit due to the latest update. I will be authenticating my github account and the repo for my CodeBuild and CodePipeline.
Thanks for sharing. We had the same issue with another person. It’s related to the way you installed Docker. You need to add docker to your Sudo group. When you do Sudo docker … Sudo don’t have access to the IAM user you set on the server or on your local
Well. my outcome was kinda strange. the pipeline worked. if i pushed smth ( from version 1->2) it worked and the changed got live . The strange thing is now, that the deploy stage on my pipeline still stucked on "Is being processed" . Source & build stage were still green but deploy blue :I. but worked idk why deploy stuck blue if it works... strange That was my warning: Cluster: nodejs-server-demo-ecs service: nodejs-server-demo-ecs/nodejs-server-ecs-service status: IN_PROGRESS maybe somehow faced the same "bug" ^^
Hey Tim. If you follow the same steps we did in the tutorial it supposed to work for you. We try that many times before we uploaded the Tutorial. One of our suggestions can be that try to use Ubuntu server like we did in the tutorial as your “local computer” Let us know if you need any assistance
@@ScaleUpSaaS Followed the same steps and it worked like in the Video. only the Deploy stage was just blue instead of green. Maybe a frontend bug... but thx
Your AWS DREAM Course coming Live SOON.... 🚀🥳
"Mastering AWS Cloud for Beginner - Learn AWS cloud by Building & Deploying scalable web application using 3 different aws architectures"
Now you can:
Pre-Register to the course and get 90% DISCOUNT
or
Get notification once the course is LIVE (Full Price)
Here is everything you need to know:
scaleupsaas.dev/aws-master-course-for-beginners/
Wow Wow Wow.
Brilliant guide, I will be following this later on and I will feedback my thoughts.
Thank you very much for taking the time to upload this.
Glad it was helpful! ❤️🔥
Feel Free to share it with your friends.
And Follow for more amazing tutorials.
Thanks that information helped a lot!
Thanks for sharing. Appreciated 🙌
Grate tutorial! Thank you
Thanks for sharing. Appreciated
Thank you! That was very helpful ❤
Thanks for sharing. Appreciated
Hello there
I'm facing a problem in the deploy stage. It runs for 15 minutes to 30 minutes in progress and it fails but however my source and build stage is successfull.
also I cross checked my ECS Service with ALB DNS link and the website works perfectly fine in that. what should I do?
Start from scratch.
It’s need to work.
Also, in which operation system you created the image?
I'm using the Ubuntu OS.
I guess I have figured out the issue. when I have created my ECS server with ALB, I cloned the git repo in the nodejs-docker-aws-ecs branch but in the Source stage of my CodePipeline, I forked your nodejs-ci-cd-pipeline branch. as the dockerfile in both of these branches are different, it wouldn't have got deployed. now I'm planning to start again from the scratch. which branch should I choose for both my AWS ECR + ECS and AWS CodePipeline?
note - I'm not able to use the AWS CodeCommit due to the latest update. I will be authenticating my github account and the repo for my CodeBuild and CodePipeline.
@ try to use the original branch. Or clone the branch and then upload to your git. Don’t change anything
Thanks!😁
Thanks for sharing. Appreciated
great very helpful to me
Thanks for sharing. Appreciate 🙏
sir im gettin no basic auth credentials even though i put the right credentials what to do
Thanks for sharing. We had the same issue with another person. It’s related to the way you installed Docker. You need to add docker to your Sudo group.
When you do Sudo docker … Sudo don’t have access to the IAM user you set on the server or on your local
How much charge you spend? For aws account
Thank for sharing. It’s depend on what we are using.
@@ScaleUpSaaS for this project sir
@@madhu-sv9kg again. It’s depends how many hours it will run and how many requests. Because I did it for short little time it’s took only few dollars
Beginners can never understand you.
Thanks for sharing!
What was not clear enough for you?
Well. my outcome was kinda strange. the pipeline worked. if i pushed smth ( from version 1->2) it worked and the changed got live . The strange thing is now, that the deploy stage on my pipeline still stucked on "Is being processed" . Source & build stage were still green but deploy blue :I. but worked idk why deploy stuck blue if it works... strange
That was my warning:
Cluster: nodejs-server-demo-ecs service: nodejs-server-demo-ecs/nodejs-server-ecs-service status: IN_PROGRESS
maybe somehow faced the same "bug" ^^
Hey Tim. If you follow the same steps we did in the tutorial it supposed to work for you. We try that many times before we uploaded the Tutorial.
One of our suggestions can be that try to use Ubuntu server like we did in the tutorial as your “local computer”
Let us know if you need any assistance
@@ScaleUpSaaS Followed the same steps and it worked like in the Video. only the Deploy stage was just blue instead of green. Maybe a frontend bug... but thx
@@Tim28259 thanks for sharing. Appreciated. Happy to hear that it’s works for you too 😎