amazing. how is it such a terrible experience? spent hours/days on this and gave up and moved to GCP, got it done almost immediately. i only came back to this because the video caught my eye and i thought why not just finish what i started. thank you for a great walkthrough.
Thanks so much for your comment! I totally get the frustration-Elastic Beanstalk can be tricky at times, especially when things don’t go as expected. I’m glad the video helped you out, and kudos to you for coming back to finish it! GCP definitely has its strengths too, but once you get the hang of AWS, it can be really powerful. Feel free to reach out if you hit any more roadblocks!
Life saver video, really thanks. Struggling with - Error "The instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist" After watching successfully launch beanstalk. Liked & subscribed!!
best video for modern aws beanstalk interface ,cause previous version was more simple and environment created automatically without any additional steps, thank you for you work
@@thecloudinvestor777 i stuck with a problem if i want to create application load balanced beanstalk environment instead of ec2 single instance i got an error `The EC2 instances failed to communicate with AWS Elastic Beanstalk, either because of configuration problems with the VPC or a failed EC2 instance. Check your VPC configuration and try launching the environment again.` I really tried everything , but nothing helped,maybe you encountered with such error
That's fantastic to hear! I'm thrilled that you found the solution you were looking for after three months. Persistence pays off! If you have any more questions or need further assistance, feel free to reach out. Cheers!
That's fantastic to hear! I'm really glad the video was helpful for you. If you have any more questions or need further assistance, feel free to ask. Keep up the great work!
Thank you so much for your kind words! I'm thrilled to hear that you found my content helpful. If you have any more questions or need further assistance, feel free to reach out anytime. Keep being awesome!
Thanks a lot; not sure why there is an option for it to generate a default; I spent hours trying to get elastic Beanstalk to work while doing a training course. Has changed since the training vid
Beautiful presentation 😊 (At the point in the configuration where I chose my default VPC, they were no availability zones appearing and so couldn't pass that stage ). What do you suggest I do?
You can first create a new VPC and then configure the elastic beanstalk environment. I have created a video where I explained the VPC creation process. If you still need help on this feel free to let me know and thank you for all your positive comments 😊
Hey Mant thatnks for the help, but I am currently facing an issue where by the web application is producing the 403 forbidden error. Would you mind giving me advice I'm still very new to cloud and aws
This is one possible solution: When compressing your project and uploading to elastic beanstalk you need to set your folder as the root folder. 1.Click on your app 2.Go to Configuration 3.Click Software Configuration 4.Go to Document root and type the name of your folder with a slash before and after e.g. /nameOfFolder/ 5.Apply and you're done I hope this helps. If still the error remains, please send me more details about the 403 error. What exact error messages its showing?
Savior! But why do we need basically 2 of the same roles? I mean, the one (IAM role) it auto creates if you leave blank,it has the same policys attached with the one we just created for the instance profile, am i missing something?
great question! The dual roles in AWS Elastic Beanstalk might seem a bit redundant. The IAM role created by Elastic Beanstalk is for service-level permissions, while the one you set up is more specific for instances within your environment. They might share policies initially, but separating them allows for more granular control in the future. It's a good practice for security and management, especially as your AWS usage evolves. Feel free to dig deeper or hit me up if you want to chat more about it!
Thanks for the answer, but still, I think it should allow me to attach the same role as an instance profile in case I wanted the same permissions. Basically I stuck there for a good amount of time before seeing your video. I wouldn't imagine the need to manually create a new role from IAM 😂
Thanks , but i'm facing issue while deploying next js app with docker on elastic bean stalk. below is the error in log events: During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version. can you please help?
Listing down all possible fixes which can resolve this issue: Reason: some bug with elasticbeanstalk, which is making the multi-stage builder step to fail. AWS logs would show you a message like docker pull requires exactly one argument Solution: Use unnamed builder. By default, the stages are not named, and you refer to them by their integer number, starting with 0 for the first FROM instruction. Reason: Incase using t2.micro as instance type. npm install command sometimes times out on the t2.micro instance. Solution: Change the instance type that Elastic Beanstalk is using something other than t2.micro(say t2.small) If none of the above two fixes work, try changing the COPY line of your Dockerfile as below: COPY package*.json ./ As AWS sometimes prefer ./ over '.'
You're welcome! I'm glad the video helped you out. Persistence pays off! If you have any more questions or run into any other issues, feel free to ask. Thanks for watching!
Hi, Mr. After creating Elastic Beanstalk, when I open the Domain link, it shows" 502 Bad Gateway nginx". Could you please tell me how to fix it? Thank you so much
Hi there! A "502 Bad Gateway" error in Elastic Beanstalk usually indicates that your application server isn't responding correctly to requests. Here are a few steps you can take to troubleshoot and fix the issue: - Check Logs: Go to the Elastic Beanstalk dashboard and check the logs for any errors. Look for anything in the eb-activity.log or web.stdout.log that might indicate a problem with your application. - Environment Health: Make sure your environment is healthy. If you see any red flags in the environment dashboard, it could point to issues with your instances. - Instance Status: Check the status of the instances in your environment. If any are in a pending or terminating state for a long time, there could be a problem with them. - Application Code: Ensure that your application is running properly and that the necessary ports are open (like port 80 for HTTP or port 443 for HTTPS). - Re-deploy: Sometimes, simply redeploying your application can resolve the issue. If you're still having trouble, feel free to share more details, and I'll do my best to help you out. Good luck!
Sure thing! Here are a few top picks for AWS Certified Developer Associate courses: 1. Udemy's "AWS Certified Developer - Associate 2022" by Stephane Maarek. 2. Coursera's "AWS Certified Developer Associate" by Andrew Brown. 3. Pluralsight's "AWS Certified Developer - Associate Level" by Fernando Medina Corey. These courses offer comprehensive coverage of the exam material. Best of luck with your certification!
I am getting below error after successful creation of environment and pipeline. it runs for few mins and then goes to Degraded status. "Environment health has transitioned from Ok to Degraded. Application update completed 64 seconds ago and took 54 seconds. Impaired services on all instances." Could you please help.
Hello! It seems you're encountering a 'Degraded' status issue in your AWS Elastic Beanstalk environment. This error often arises due to various reasons, such as errors in your application code, resource constraints, or service dependencies. Start by checking your logs for specific error messages and verifying the health of services your application relies on. If you recently updated your environment and the problem emerged, consider rolling back to a known working version. Providing detailed information about your setup will help pinpoint the problem more effectively. Good luck in resolving it!
I followed everything and the generated url is working fine on PC. But when I try to access the deployed website using the link from mobile,I get a timeout error. Can you tell me what could be causing it?
Hey there! It's awesome that the website works on your PC! For the timeout on mobile, first, confirm your mobile's internet connection is stable. Next, consider checking if any firewall or strict security settings on the mobile device might be causing the issue. Also, test the website on various mobile browsers to ensure compatibility. If the problem persists, review your Elastic Beanstalk settings-sometimes, adjustments there can resolve mobile access issues. Wishing you success in getting it sorted!
Beautifully present sir but i have doubt i tried load balancing , elastic Bean stack. Both these services are working on laptop but when we try to open it on android it doesn't work. Can you please guide us with that ?
Thank you for your positive feedback! Regarding the issue on Android, here are quick steps to troubleshoot: Network: Ensure both devices are on the same network. Security: Check AWS security groups and firewalls for Android access. Subnet: Confirm Elastic Beanstalk is using public subnets. Code: Ensure the application is compatible with Android. Browser: Use an updated browser on Android. Logs: Check Elastic Beanstalk logs for errors. CORS: Verify Cross-Origin Resource Sharing settings. SSL/TLS: Confirm correct HTTPS configuration. Responsiveness: Ensure the app is designed for mobile screens. These steps should help identify and resolve the issue. If needed, share more details for further assistance!
Yes sir, I tried this same setting. The problem I face in load balancing is when I try to access my html page through public IP from httpd or apache2 service on laptop and Android it works but when I configure load balancer with same security group and everything same setting then from created dns it will work only in laptop not on mobile but if I enter public IP of ec2 in both of them it works. Sir please make proper video on this thing for our help or I will record my screen please tell me the mistakes I am doing. This is really helpful 🙂🙏
Environment health has transitioned to Pending. Initialization in progress (running for 7 seconds). There are no instances. I am getting the above message and health is pending. What should I do?
Hello! Seeing the "Environment health has transitioned to Pending" message indicates that your AWS Elastic Beanstalk environment is currently in the initialization process. To address this, first, double-check your environment's configuration settings to ensure they are accurate. Review the logs for any potential errors, as they can provide valuable insights into the issue. If you're using Auto Scaling, be patient as it may take some time for instances to launch. It's also a good idea to check the AWS Service Status page to rule out any ongoing outages in your region. If the problem persists, consider recreating the environment with the same or slightly adjusted configurations. Best of luck with your Elastic Beanstalk deployment!
If your package file isn't being uploaded to the environment, there are a few things you can check: - File Size: Ensure your package file doesn't exceed the size limit. AWS Elastic Beanstalk has a maximum file size of 512 MB for ZIP files. - File Format: Make sure your package is in the correct format (usually a ZIP file). - Permissions: Verify that you have the necessary permissions to upload and deploy the application. You might need to check your IAM roles and policies. - Configuration File: Check your configuration files (like ebextensions and Dockerfile if applicable) to ensure there are no errors that might cause the deployment to fail. - Network Issues: Sometimes, network issues can cause uploads to fail. Ensure you have a stable internet connection. - Elastic Beanstalk Logs: Look at the logs provided by Elastic Beanstalk to see if there are any specific error messages. You can find the logs in the Elastic Beanstalk dashboard under the "Logs" section. Try these steps, and let me know if you still face issues!
Sure, here's a guide: AWS Certificate: Get a free SSL certificate from AWS Certificate Manager (ACM). Elastic Beanstalk Settings: Go to your environment's configuration, modify the Load Balancer settings to enable HTTPS on port 443, and select the ACM certificate. Test: After applying changes, test your site using HTTPS for a secure connection. Hope this helps!
I'm facing an issue while my own PHP code deploying in the elastic Beanstalk environment. but it is working as a sample application, health is going to a degraded state I'm unable to resolve this can you help me, sir
Absolutely! - Look for PHP error logs in your Elastic Beanstalk environment to identify any issues with your code or configuration. - Double-check your Elastic Beanstalk setup to ensure PHP is properly configured, including the correct PHP version and environment variables. - Make sure all required dependencies for your PHP application are included in your deployment package and properly installed within Elastic Beanstalk. - Ensure your Elastic Beanstalk environment has adequate resources allocated to handle your PHP application's workload. You may need to adjust instance types or scaling settings. - Review the health check configuration in Elastic Beanstalk to ensure it's accurately assessing the health of your PHP application endpoints. These steps should help pinpoint the issue causing the health degradation. Let me know if you need further guidance!
Hey! Glad to hear the application was created successfully, but sorry to hear about the EC2 instance issue. This can happen if there are configuration issues in the Elastic Beanstalk environment. I’d recommend checking a few things: - Make sure there are no security group or IAM role restrictions blocking instance creation. - Check your EC2 instance limits in the region where you’re deploying - sometimes hitting the limit can prevent new instances from launching. - Take a look at the Elastic Beanstalk logs and event logs to see if there are any errors during the environment creation. Let me know if this helps, or feel free to ask for more troubleshooting tips!
Hey there! It seems like you're encountering an issue with creating an Elastic Beanstalk Environment. The error message suggests that there might be a resource not found after multiple retries. To troubleshoot this, consider the following steps: - Double-check your Elastic Beanstalk Environment configuration. - Verify that all the required resources, such as IAM roles or security groups, are properly set up. - Check if there are any issues with your AWS credentials or permissions.
Thank you so much! I really appreciate your kind words. If there's anything specific you enjoyed or if you have any questions, feel free to let me know. Your support means a lot!
@@thecloudinvestor777 I wasn’t even able to get the sample app to run until I came across your tutorial. Do you have any videos with typescript code on aws? Either way you earned yourself a like and subscribe!
For the "AWSEBAutoScallingGroup does not exist" error, review the Auto Scaling Group setup within Elastic Beanstalk. Confirm that the naming and configurations are accurate as per Elastic Beanstalk guidelines. As for the "created failed reason the following resources failed to create" issue, check the error logs for specific details. This error often relates to permission settings, misconfigurations, or dependencies among resources. Refer to AWS Elastic Beanstalk documentation for troubleshooting steps. You're making progress; keep troubleshooting, and if you need further assistance, feel free to share more details!
Please follow the instructions: 1.Goto Configurations on the left pane 2.Select software edit 3.under root document write /public 4.if you got 404 again change Nginx to apache
It sounds like you're facing some issues with your AWS Elastic Beanstalk environment. The health status can turn red due to several reasons: - Resource Overload: Check if your application is using too much CPU or memory. - Deployment Issues: Ensure recent deployments didn’t introduce any errors. - Configuration Changes: Review any recent changes in environment settings. - Application Errors: Look for errors in your application logs. - Dependency Failures: Verify that all external services your app depends on are working correctly. Check the Elastic Beanstalk logs and health dashboard for more details. If you need more help, feel free to share specific error messages!
everything work fine but when I use this deploy url to fetch my API its says, mixed content error, I look into it and got to know our deploy url is http only not a https so nothing is working, how to make http to https, I seen some video where you need to add ssl certificate but I could not see any option in my configuration, no such thing like load balancer and listener, where you can add your ssl certificate one humble request, if you create one video where you show how to create SSL certificate and add that into project environment to make http to https
Thank you for your comment! It sounds like you're experiencing a common issue with mixed content errors due to the absence of HTTPS. Let me break down the steps to resolve this issue: 1. Create an SSL Certificate: You can create an SSL certificate using AWS Certificate Manager (ACM). Here’s a quick overview: - Go to the AWS Management Console. - Navigate to ACM. - Request a public certificate. - Follow the steps to validate your domain. 2. Configure Elastic Beanstalk to Use HTTPS: - Since you mentioned that you don't see options for a load balancer and listener, it’s possible that your environment is a single-instance environment. Here’s what you can do: - If you’re using a single-instance environment, you’ll need to manually install the SSL certificate on your instance. This usually involves configuring the web server (like Nginx or Apache) to use the certificate. - Alternatively, you can convert your environment to a load-balanced one, where you can easily add the SSL certificate to the load balancer. 3. Update Security Groups: - Ensure that your security groups allow traffic on port 443 (HTTPS). 4. Force Redirect from HTTP to HTTPS: - You can configure your web server to redirect all HTTP traffic to HTTPS. Since you've requested a video tutorial, I'll create one showing the entire process from creating an SSL certificate to configuring your Elastic Beanstalk environment to use HTTPS. I'll cover both single-instance and load-balanced environments. Stay tuned to my channel, and I’ll update you once the video is live. Thanks for the suggestion!
@@devabakare357 I totally understand your situation. For a college project, managing costs is crucial. Since converting to a load-balanced environment can be expensive, manually installing the SSL certificate on a single-instance environment is a practical solution. Here's a quick guide to help you: Connect to Your Instance: Use SSH to connect to your EC2 instance. Install Web Server: If you haven't already, install a web server like Nginx or Apache. Obtain SSL Certificate: You can use free services like Let's Encrypt to get an SSL certificate. Configure the Web Server: Update your Nginx or Apache configuration to use the SSL certificate. This way, you can secure your application without incurring additional costs. Feel free to ask if you need more detailed steps or run into any issues. Good luck with your projec
@@thecloudinvestor777 Okay will try this and get back to you, I would like to say a deep hearted thank you for taking time in your busy schedule and replying me, I appreciate your reply and I just want to tell you it mean alot for me, thank you, thank you
I followed the steps. when i use the domain URL i get error: The connection has timed out. The environment is healthy. The Ec2 instance is stable and running.
It sounds like the issue might be related to your Elastic Load Balancer (ELB) or your security group settings. Here are a few things you can check: - Load Balancer Configuration: Ensure that the ELB is correctly forwarding requests to the EC2 instance. Check the listener rules in the ELB and confirm that the target group has healthy instances. - Security Group Settings: Verify that the security group attached to your EC2 instance and/or the ELB allows inbound traffic on the required ports (e.g., port 80 for HTTP or port 443 for HTTPS). - Route 53 or DNS Settings: If you're using a custom domain, make sure the domain is correctly mapped to the Elastic Beanstalk environment. - Network ACLs and Subnet Configuration: Double-check your VPC network configurations to ensure there are no restrictions on incoming or outgoing traffic. - EC2 Logs: Check the EC2 instance logs (e.g., /var/log/httpd/access_log or /var/log/nginx/access.log) to see if requests are reaching the instance and whether there are any errors. If you've already checked these and the issue persists, let me know with more details about your setup, and I’ll do my best to assist further!
I'm sorry to hear you're experiencing issues with your Elastic Beanstalk environment. A degraded health status can be caused by several factors. Here are a few common issues to check: - Instance Health: Make sure your EC2 instances are healthy. You can check their status in the EC2 console. - Logs: Review the logs in your Elastic Beanstalk environment for any errors or warnings. These logs can provide clues about what might be going wrong. - Resource Limits: Ensure that your environment is not running out of resources like CPU, memory, or disk space. You can monitor these metrics in the CloudWatch console. - Application Errors: Check if your application is generating errors that could affect the health of your environment. - Ensure that your application code is handling requests properly. - Configuration Issues: Verify that your environment configuration is correct and that all necessary dependencies are installed and configured properly. I hope this helps! Let me know if you have any other questions.
Thanks for trying out the steps! It sounds like there might be an issue with your auto-scaling configuration in Elastic Beanstalk. Could you share more details about the error you're seeing? In the meantime, here are a few things you can check: - Make sure your auto-scaling settings (min/max instance count) are properly configured in the Elastic Beanstalk environment. - Verify that your instance type supports auto-scaling. - Check if your security groups and permissions allow scaling. Feel free to drop the exact error message here, and I'll help you troubleshoot it further!
Absolutely! To deploy your GitHub code on AWS Elastic Beanstalk: Prepare Your Code: Ensure your GitHub repository is ready with the code you want to deploy. AWS Credentials: Set up your AWS credentials on your local machine. Install AWS CLI: Install the AWS Command Line Interface (CLI) if you haven't already. Initialize Elastic Beanstalk: Use the eb init command to initialize your Elastic Beanstalk environment. Create Environment: Run eb create to create your Elastic Beanstalk environment. Deploy Code: Use eb deploy to deploy your GitHub code to AWS Elastic Beanstalk. Remember to check AWS Elastic Beanstalk documentation for detailed steps and troubleshooting. Happy deploying!
No worries at all! Windows creation on AWS Elastic Beanstalk can indeed differ from Linux. If you're interested, I could create a video focusing on Linux setup too. Let me know if that would be helpful for you!
The 403 Forbidden error usually indicates a permissions issue. Here are some steps you can take to resolve it: - File Permissions: Ensure that your sample_code.php file has the correct permissions. The file should typically have 644 permissions (readable by the server). You can set this using: chmod 644 sample_code.php - Directory Permissions: Check the permissions of the directory containing the sample_code.php file. The directory should have 755 permissions: chmod 755 /path/to/directory - Ownership: Make sure the file and directory are owned by the correct user. The web server user (e.g., www-data for Apache on Ubuntu) should have ownership. You can change ownership using chown www-data:www-data sample_code.php - .htaccess File: If you have an .htaccess file, ensure it doesn't have any rules blocking access to your PHP file. - Server Configuration: Check your server configuration files (like httpd.conf for Apache) to ensure there are no restrictions that might be causing the 403 error. - Web Server Logs: Look at the web server logs for more detailed error messages. They can provide insights into why the server is denying access. Try these steps and see if they resolve the issue. If the problem persists, feel free to provide more details so I can help further!
amazing. how is it such a terrible experience? spent hours/days on this and gave up and moved to GCP, got it done almost immediately. i only came back to this because the video caught my eye and i thought why not just finish what i started. thank you for a great walkthrough.
Thanks so much for your comment! I totally get the frustration-Elastic Beanstalk can be tricky at times, especially when things don’t go as expected. I’m glad the video helped you out, and kudos to you for coming back to finish it! GCP definitely has its strengths too, but once you get the hang of AWS, it can be really powerful. Feel free to reach out if you hit any more roadblocks!
Life saver video, really thanks. Struggling with - Error "The instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist" After watching successfully launch beanstalk.
Liked & subscribed!!
Glad to know that. Thank you for your comment. It means a lot 🙂
Thanks, someone who actually knew what's the problem and addressed it !!
You're welcome! I'm glad the video helped address the issue. If you have any more questions or need further assistance, feel free to ask!
Blessings upon you! Searched for hours!
So glad you found what you were looking for! Blessings to you as well!
best video for modern aws beanstalk interface ,cause previous version was more simple and environment created automatically without any additional steps, thank you for you work
You are welcome! Please stay connected 🙂
@@thecloudinvestor777 i stuck with a problem if i want to create application load balanced beanstalk environment instead of ec2 single instance i got an error `The EC2 instances failed to communicate with AWS Elastic Beanstalk, either because of configuration problems with the VPC or a failed EC2 instance. Check your VPC configuration and try launching the environment again.`
I really tried everything , but nothing helped,maybe you encountered with such error
Seriously thanks to provide this relevant information it’s helps us a lot
Its my pleasure! Please stay connected 🙂
seriously i got the solution after 3 month thanks a lot brother
That's fantastic to hear! I'm thrilled that you found the solution you were looking for after three months. Persistence pays off! If you have any more questions or need further assistance, feel free to reach out. Cheers!
Thank you so much brother!
You saved me hours and hours.
Glad I could help 🙂
Fantastic, the Configure Service Access part helped me solve my problem. Thank you!
Glad it helped!
Thank you so much! This is the information I was missing from my lesson.
Glad it was helpful!
exactly what I was looking for. many thanks
Glad I could help!
This man is a real life hero
Thank you so much! Your kind words mean a lot to me. I'm glad you find my content helpful.
Thanks a lot, I was stuck in my project for the past 3-2 days now its totaly working awesome !!
Glad to hear that! Please subscribe to my channel to stay connected 🙂
You just made my dayt! Thank you very much!
My pleasure! Please stay connected 🙂
Thank you so much for this tutorial.
Glad it was helpful!
Thank you for your such a awesome presentation.
Glad you enjoyed it!
God damn. I'm gonna cry.
Thank you so much!!!!
I am glad to help you out. Please stay connected 🙂
nice explanation thank you so much 🙏🏼🙏🏼🙏🏼
You're most welcome
Really helpful video easy to understand elastic beanstalk😊
Glad it was helpful! Please stay connected 😊
Thank you soooo much. I was struggling with this. You saved lot of time for me. Thanks a lot !!
That's fantastic to hear! I'm really glad the video was helpful for you. If you have any more questions or need further assistance, feel free to ask. Keep up the great work!
Dude... You're the best. Thank you.
Thank you so much for your kind words! I'm thrilled to hear that you found my content helpful. If you have any more questions or need further assistance, feel free to reach out anytime. Keep being awesome!
Thanks for this clear cut content.😊
Glad it was helpful!
Thanks a lot; not sure why there is an option for it to generate a default; I spent hours trying to get elastic Beanstalk to work while doing a training course. Has changed since the training vid
You are welcome!
This is was just a perfect answer to my problem😀. Thank you
Happy to help!
You re the real life saver
I am glad to help. Please stay connected 🙂
you are my savior !!!!!
Glad I could help! Hope everything is running smoothly now. Let me know if you have any other questions!
just wanna say thanks in billion bro! wondrous!!! An An!
You are welcome. I am glad this video helped you 🙂
super sir very nice video it is very usefull to me thank u
Thanks and welcome 🙂
Thank you man! That solved the issue in my case. Fantastic!
Glad it helped!
Beautiful presentation 😊 (At the point in the configuration where I chose my default VPC, they were no availability zones appearing and so couldn't pass that stage ). What do you suggest I do?
You can first create a new VPC and then configure the elastic beanstalk environment. I have created a video where I explained the VPC creation process. If you still need help on this feel free to let me know and thank you for all your positive comments 😊
Thank you, it was awsome, just what i was looking for :)
Glad I could help!
Thank you, God bless you sir!
You are very welcome!
Sir You are Awesome, thank you so much for this Video...
You are most welcome! Please stay connected 🙂
Can you please help me to resolve this issue
Works for me. Thanks!!!
You're welcome! Glad to hear it worked for you! If you have any other questions or need further assistance, feel free to ask. Happy to help!
THANK YOU SO MUCH, YOU'RE THE MAN!!!!!
You're welcome!
thanks, it resolved my problem
You are welcome. I am glad to hear that. Please stay connected 🙂
This video helps!!!! Thank so much
Glad it helped!
Hey Mant thatnks for the help, but I am currently facing an issue where by the web application is producing the 403 forbidden error. Would you mind giving me advice I'm still very new to cloud and aws
This is one possible solution: When compressing your project and uploading to elastic beanstalk you need to set your folder as the root folder.
1.Click on your app
2.Go to Configuration
3.Click Software Configuration
4.Go to Document root and type the name of your folder with a slash before and after e.g. /nameOfFolder/
5.Apply and you're done
I hope this helps.
If still the error remains, please send me more details about the 403 error. What exact error messages its showing?
Savior! But why do we need basically 2 of the same roles? I mean, the one (IAM role) it auto creates if you leave blank,it has the same policys attached with the one we just created for the instance profile, am i missing something?
great question! The dual roles in AWS Elastic Beanstalk might seem a bit redundant. The IAM role created by Elastic Beanstalk is for service-level permissions, while the one you set up is more specific for instances within your environment. They might share policies initially, but separating them allows for more granular control in the future. It's a good practice for security and management, especially as your AWS usage evolves. Feel free to dig deeper or hit me up if you want to chat more about it!
Thanks for the answer, but still, I think it should allow me to attach the same role as an instance profile in case I wanted the same permissions.
Basically I stuck there for a good amount of time before seeing your video. I wouldn't imagine the need to manually create a new role from IAM 😂
Thanks , but i'm facing issue while deploying next js app with docker on elastic bean stalk. below is the error in log events:
During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
can you please help?
Listing down all possible fixes which can resolve this issue:
Reason: some bug with elasticbeanstalk, which is making the multi-stage builder step to fail. AWS logs would show you a message like docker pull requires exactly one argument
Solution: Use unnamed builder. By default, the stages are not named, and you refer to them by their integer number, starting with 0 for the first FROM instruction.
Reason: Incase using t2.micro as instance type. npm install command sometimes times out on the t2.micro instance.
Solution: Change the instance type that Elastic Beanstalk is using something other than t2.micro(say t2.small)
If none of the above two fixes work, try changing the COPY line of your Dockerfile as below:
COPY package*.json ./
As AWS sometimes prefer ./ over '.'
Thank you, that worked great!
Glad it helped! Please stay connected 🙂
Thanks man, you helped me a lot 🥺🥺.
I have subscribed
Glad I could help. Please stay connected 🙂
thanks a lots tried more times without creating the instance profile name. thank u.
You're welcome! I'm glad the video helped you out. Persistence pays off! If you have any more questions or run into any other issues, feel free to ask. Thanks for watching!
Thank you so much !!! , it help me a lot.. Do you have class sessions available in udemy?
It’s my pleasure 🙂 Sorry don’t have any classes available in Udemy but I am continuously uploading videos in this channel. Please stay connected 🙏
Hi, Mr. After creating Elastic Beanstalk, when I open the Domain link, it shows" 502 Bad Gateway
nginx". Could you please tell me how to fix it? Thank you so much
Hi there! A "502 Bad Gateway" error in Elastic Beanstalk usually indicates that your application server isn't responding correctly to requests. Here are a few steps you can take to troubleshoot and fix the issue:
- Check Logs: Go to the Elastic Beanstalk dashboard and check the logs for any errors. Look for anything in the eb-activity.log or web.stdout.log that might indicate a problem with your application.
- Environment Health: Make sure your environment is healthy. If you see any red flags in the environment dashboard, it could point to issues with your instances.
- Instance Status: Check the status of the instances in your environment. If any are in a pending or terminating state for a long time, there could be a problem with them.
- Application Code: Ensure that your application is running properly and that the necessary ports are open (like port 80 for HTTP or port 443 for HTTPS).
- Re-deploy: Sometimes, simply redeploying your application can resolve the issue.
If you're still having trouble, feel free to share more details, and I'll do my best to help you out. Good luck!
thanks a lot, these really helped me
Glad it helped!
Can you please upload the vpc creation in Linux video brooo
Good! This help me a lot
Glad it helped!
can you suggest any course for aws certified developer associate?
Sure thing! Here are a few top picks for AWS Certified Developer Associate courses:
1. Udemy's "AWS Certified Developer - Associate 2022" by Stephane Maarek.
2. Coursera's "AWS Certified Developer Associate" by Andrew Brown.
3. Pluralsight's "AWS Certified Developer - Associate Level" by Fernando Medina Corey.
These courses offer comprehensive coverage of the exam material. Best of luck with your certification!
Great I was literally searching for this tut from past 1 week.
I am glad it helped you. Please stay connected 🙂
Thank you so much. This helps me a lot
Glad it helped!
I am getting below error after successful creation of environment and pipeline. it runs for few mins and then goes to Degraded status.
"Environment health has transitioned from Ok to Degraded. Application update completed 64 seconds ago and took 54 seconds. Impaired services on all instances."
Could you please help.
Hello! It seems you're encountering a 'Degraded' status issue in your AWS Elastic Beanstalk environment. This error often arises due to various reasons, such as errors in your application code, resource constraints, or service dependencies. Start by checking your logs for specific error messages and verifying the health of services your application relies on. If you recently updated your environment and the problem emerged, consider rolling back to a known working version. Providing detailed information about your setup will help pinpoint the problem more effectively. Good luck in resolving it!
I followed everything and the generated url is working fine on PC. But when I try to access the deployed website using the link from mobile,I get a timeout error. Can you tell me what could be causing it?
Hey there! It's awesome that the website works on your PC! For the timeout on mobile, first, confirm your mobile's internet connection is stable. Next, consider checking if any firewall or strict security settings on the mobile device might be causing the issue. Also, test the website on various mobile browsers to ensure compatibility. If the problem persists, review your Elastic Beanstalk settings-sometimes, adjustments there can resolve mobile access issues. Wishing you success in getting it sorted!
Beautifully present sir but i have doubt i tried load balancing , elastic Bean stack. Both these services are working on laptop but when we try to open it on android it doesn't work. Can you please guide us with that ?
Thank you for your positive feedback! Regarding the issue on Android, here are quick steps to troubleshoot:
Network: Ensure both devices are on the same network.
Security: Check AWS security groups and firewalls for Android access.
Subnet: Confirm Elastic Beanstalk is using public subnets.
Code: Ensure the application is compatible with Android.
Browser: Use an updated browser on Android.
Logs: Check Elastic Beanstalk logs for errors.
CORS: Verify Cross-Origin Resource Sharing settings.
SSL/TLS: Confirm correct HTTPS configuration.
Responsiveness: Ensure the app is designed for mobile screens.
These steps should help identify and resolve the issue. If needed, share more details for further assistance!
Yes sir, I tried this same setting.
The problem I face in load balancing is when I try to access my html page through public IP from httpd or apache2 service on laptop and Android it works but when I configure load balancer with same security group and everything same setting then from created dns it will work only in laptop not on mobile but if I enter public IP of ec2 in both of them it works.
Sir please make proper video on this thing for our help or I will record my screen please tell me the mistakes I am doing.
This is really helpful 🙂🙏
Environment health has transitioned to Pending. Initialization in progress (running for 7 seconds). There are no instances.
I am getting the above message and health is pending. What should I do?
Hello! Seeing the "Environment health has transitioned to Pending" message indicates that your AWS Elastic Beanstalk environment is currently in the initialization process. To address this, first, double-check your environment's configuration settings to ensure they are accurate. Review the logs for any potential errors, as they can provide valuable insights into the issue. If you're using Auto Scaling, be patient as it may take some time for instances to launch. It's also a good idea to check the AWS Service Status page to rule out any ongoing outages in your region. If the problem persists, consider recreating the environment with the same or slightly adjusted configurations. Best of luck with your Elastic Beanstalk deployment!
how can i resolve the issue of my package file not being uploaded on the environment
If your package file isn't being uploaded to the environment, there are a few things you can check:
- File Size: Ensure your package file doesn't exceed the size limit. AWS Elastic Beanstalk has a maximum file size of 512 MB for ZIP files.
- File Format: Make sure your package is in the correct format (usually a ZIP file).
- Permissions: Verify that you have the necessary permissions to upload and deploy the application. You might need to check your IAM roles and policies.
- Configuration File: Check your configuration files (like ebextensions and Dockerfile if applicable) to ensure there are no errors that might cause the deployment to fail.
- Network Issues: Sometimes, network issues can cause uploads to fail. Ensure you have a stable internet connection.
- Elastic Beanstalk Logs: Look at the logs provided by Elastic Beanstalk to see if there are any specific error messages. You can find the logs in the Elastic Beanstalk dashboard under the "Logs" section.
Try these steps, and let me know if you still face issues!
It indeed works!
Awesome! Glad to hear it worked for you! Let me know if you need any more help.
Great Video
Can we please have https enabled for my elastic beanStalk ?
Sure, here's a guide:
AWS Certificate: Get a free SSL certificate from AWS Certificate Manager (ACM).
Elastic Beanstalk Settings: Go to your environment's configuration, modify the Load Balancer settings to enable HTTPS on port 443, and select the ACM certificate.
Test: After applying changes, test your site using HTTPS for a secure connection.
Hope this helps!
thanks! .. your video helped !
Glad it helped!
You saved me , thanks man!
Glad I could help! Please stay connected 🙂
Thank you so much!
You're welcome!
Thank you bro it helped
Glad it helped. Please stay connected.
I'm facing an issue while my own PHP code deploying in the elastic Beanstalk environment. but it is working as a sample application, health is going to a degraded state I'm unable to resolve this can you help me, sir
Absolutely!
- Look for PHP error logs in your Elastic Beanstalk environment to identify any issues with your code or configuration.
- Double-check your Elastic Beanstalk setup to ensure PHP is properly configured, including the correct PHP version and environment variables.
- Make sure all required dependencies for your PHP application are included in your deployment package and properly installed within Elastic Beanstalk.
- Ensure your Elastic Beanstalk environment has adequate resources allocated to handle your PHP application's workload. You may need to adjust instance types or scaling settings.
- Review the health check configuration in Elastic Beanstalk to ensure it's accurately assessing the health of your PHP application endpoints.
These steps should help pinpoint the issue causing the health degradation. Let me know if you need further guidance!
Elastic Beanstalk application was created successfully, but the EC2 instance that should be associated with it hasn't launched
Hey! Glad to hear the application was created successfully, but sorry to hear about the EC2 instance issue. This can happen if there are configuration issues in the Elastic Beanstalk environment. I’d recommend checking a few things:
- Make sure there are no security group or IAM role restrictions blocking instance creation.
- Check your EC2 instance limits in the region where you’re deploying - sometimes hitting the limit can prevent new instances from launching.
- Take a look at the Elastic Beanstalk logs and event logs to see if there are any errors during the environment creation.
Let me know if this helps, or feel free to ask for more troubleshooting tips!
thank you brother
You're welcome!
Thank you Thank you.
You are very welcome
Please explain the error mentioned in the title brother!
Bro, How can i fix this Error: waiting for Elastic Beanstalk Environment (e-vdbvvkftqq) create: couldn't find resource (21 retries)
Hey there! It seems like you're encountering an issue with creating an Elastic Beanstalk Environment. The error message suggests that there might be a resource not found after multiple retries.
To troubleshoot this, consider the following steps:
- Double-check your Elastic Beanstalk Environment configuration.
- Verify that all the required resources, such as IAM roles or security groups, are properly set up.
- Check if there are any issues with your AWS credentials or permissions.
Thank you man
You're welcome!
Thanks you helped me there !
Glad I could help!
Thank you bro.
You're welcome!
Thank you!!
You're welcome!
you're the man.
Thank you so much! I really appreciate your kind words. If there's anything specific you enjoyed or if you have any questions, feel free to let me know. Your support means a lot!
@@thecloudinvestor777 I wasn’t even able to get the sample app to run until I came across your tutorial. Do you have any videos with typescript code on aws?
Either way you earned yourself a like and subscribe!
Sir 2 errors is came
1 is AWSEBAutoScallingGroup does not exist
2 is created failed reason the following resources failed to create
For the "AWSEBAutoScallingGroup does not exist" error, review the Auto Scaling Group setup within Elastic Beanstalk. Confirm that the naming and configurations are accurate as per Elastic Beanstalk guidelines.
As for the "created failed reason the following resources failed to create" issue, check the error logs for specific details. This error often relates to permission settings, misconfigurations, or dependencies among resources. Refer to AWS Elastic Beanstalk documentation for troubleshooting steps. You're making progress; keep troubleshooting, and if you need further assistance, feel free to share more details!
Thanks, you da man
Glad to help 🙂
Thanks.
You're welcome 🙂
Hello Sir, I am getting 404 error while hitting elasticbeanstalk url
Please follow the instructions:
1.Goto Configurations on the left pane
2.Select software edit
3.under root document write /public
4.if you got 404 again change Nginx to apache
My health was in green status later on it became red. Any idea why??
It sounds like you're facing some issues with your AWS Elastic Beanstalk environment. The health status can turn red due to several reasons:
- Resource Overload: Check if your application is using too much CPU or memory.
- Deployment Issues: Ensure recent deployments didn’t introduce any errors.
- Configuration Changes: Review any recent changes in environment settings.
- Application Errors: Look for errors in your application logs.
- Dependency Failures: Verify that all external services your app depends on are working correctly.
Check the Elastic Beanstalk logs and health dashboard for more details. If you need more help, feel free to share specific error messages!
everything work fine but when I use this deploy url to fetch my API its says, mixed content error, I look into it and got to know our deploy url is http only not a https so nothing is working, how to make http to https, I seen some video where you need to add ssl certificate but I could not see any option in my configuration, no such thing like load balancer and listener, where you can add your ssl certificate
one humble request, if you create one video where you show how to create SSL certificate and add that into project environment to make http to https
Thank you for your comment! It sounds like you're experiencing a common issue with mixed content errors due to the absence of HTTPS. Let me break down the steps to resolve this issue:
1. Create an SSL Certificate:
You can create an SSL certificate using AWS Certificate Manager (ACM). Here’s a quick overview:
- Go to the AWS Management Console.
- Navigate to ACM.
- Request a public certificate.
- Follow the steps to validate your domain.
2. Configure Elastic Beanstalk to Use HTTPS:
- Since you mentioned that you don't see options for a load balancer and listener, it’s possible that your environment is a single-instance environment. Here’s what you can do:
- If you’re using a single-instance environment, you’ll need to manually install the SSL certificate on your instance. This usually involves configuring the web server (like Nginx or Apache) to use the certificate.
- Alternatively, you can convert your environment to a load-balanced one, where you can easily add the SSL certificate to the load balancer.
3. Update Security Groups:
- Ensure that your security groups allow traffic on port 443 (HTTPS).
4. Force Redirect from HTTP to HTTPS:
- You can configure your web server to redirect all HTTP traffic to HTTPS.
Since you've requested a video tutorial, I'll create one showing the entire process from creating an SSL certificate to configuring your Elastic Beanstalk environment to use HTTPS. I'll cover both single-instance and load-balanced environments.
Stay tuned to my channel, and I’ll update you once the video is live. Thanks for the suggestion!
@@devabakare357 I totally understand your situation. For a college project, managing costs is crucial. Since converting to a load-balanced environment can be expensive, manually installing the SSL certificate on a single-instance environment is a practical solution. Here's a quick guide to help you:
Connect to Your Instance: Use SSH to connect to your EC2 instance.
Install Web Server: If you haven't already, install a web server like Nginx or Apache.
Obtain SSL Certificate: You can use free services like Let's Encrypt to get an SSL certificate.
Configure the Web Server: Update your Nginx or Apache configuration to use the SSL certificate.
This way, you can secure your application without incurring additional costs. Feel free to ask if you need more detailed steps or run into any issues. Good luck with your projec
@@thecloudinvestor777 Okay will try this and get back to you, I would like to say a deep hearted thank you for taking time in your busy schedule and replying me, I appreciate your reply and I just want to tell you it mean alot for me, thank you, thank you
Thanks bro
You are welcome bro
thank you so much
You're welcome!
I followed the steps. when i use the domain URL i get error: The connection has timed out.
The environment is healthy. The Ec2 instance is stable and running.
It sounds like the issue might be related to your Elastic Load Balancer (ELB) or your security group settings. Here are a few things you can check:
- Load Balancer Configuration: Ensure that the ELB is correctly forwarding requests to the EC2 instance. Check the listener rules in the ELB and confirm that the target group has healthy instances.
- Security Group Settings: Verify that the security group attached to your EC2 instance and/or the ELB allows inbound traffic on the required ports (e.g., port 80 for HTTP or port 443 for HTTPS).
- Route 53 or DNS Settings: If you're using a custom domain, make sure the domain is correctly mapped to the Elastic Beanstalk environment.
- Network ACLs and Subnet Configuration: Double-check your VPC network configurations to ensure there are no restrictions on incoming or outgoing traffic.
- EC2 Logs: Check the EC2 instance logs (e.g., /var/log/httpd/access_log or /var/log/nginx/access.log) to see if requests are reaching the instance and whether there are any errors.
If you've already checked these and the issue persists, let me know with more details about your setup, and I’ll do my best to assist further!
My Health still keeps showing degraded and I'm still confused on whats happening
I'm sorry to hear you're experiencing issues with your Elastic Beanstalk environment. A degraded health status can be caused by several factors. Here are a few common issues to check:
- Instance Health: Make sure your EC2 instances are healthy. You can check their status in the EC2 console.
- Logs: Review the logs in your Elastic Beanstalk environment for any errors or warnings. These logs can provide clues about what might be going wrong.
- Resource Limits: Ensure that your environment is not running out of resources like CPU, memory, or disk space. You can monitor these metrics in the CloudWatch console.
- Application Errors: Check if your application is generating errors that could affect the health of your environment. - Ensure that your application code is handling requests properly.
- Configuration Issues: Verify that your environment configuration is correct and that all necessary dependencies are installed and configured properly.
I hope this helps! Let me know if you have any other questions.
Thanks man❤
You're welcome 😊
i did your steps and got error about autoscaling
Thanks for trying out the steps! It sounds like there might be an issue with your auto-scaling configuration in Elastic Beanstalk. Could you share more details about the error you're seeing?
In the meantime, here are a few things you can check:
- Make sure your auto-scaling settings (min/max instance count) are properly configured in the Elastic Beanstalk environment.
- Verify that your instance type supports auto-scaling.
- Check if your security groups and permissions allow scaling.
Feel free to drop the exact error message here, and I'll help you troubleshoot it further!
thanks G
Welcome
THANK YOUUUUUUU
My pleasure!
Its is showing still error 😊
nice
Thanks 🙏
Still it is showing error like there are no instances
Please send me the complete error 🙂
Okay I will
Saying there are no instance
Thank you so much
Please Create video hiw to deploy my githhub code
Absolutely! To deploy your GitHub code on AWS Elastic Beanstalk:
Prepare Your Code:
Ensure your GitHub repository is ready with the code you want to deploy.
AWS Credentials:
Set up your AWS credentials on your local machine.
Install AWS CLI:
Install the AWS Command Line Interface (CLI) if you haven't already.
Initialize Elastic Beanstalk:
Use the eb init command to initialize your Elastic Beanstalk environment.
Create Environment:
Run eb create to create your Elastic Beanstalk environment.
Deploy Code:
Use eb deploy to deploy your GitHub code to AWS Elastic Beanstalk.
Remember to check AWS Elastic Beanstalk documentation for detailed steps and troubleshooting. Happy deploying!
@@thecloudinvestor777 please bro can u create one video for that ? 💖💖
Can u share me your instagram id or anything to connect with you easily
I knew the windows creation I don't know Linux creation
No worries at all! Windows creation on AWS Elastic Beanstalk can indeed differ from Linux. If you're interested, I could create a video focusing on Linux setup too. Let me know if that would be helpful for you!
king
Thank you 🙏
Thanks
You are welcome. I am glad to help.
403 FORBIDDEN ERROR WHEN I USE MY SAMPLE CODE.PHP
The 403 Forbidden error usually indicates a permissions issue. Here are some steps you can take to resolve it:
- File Permissions: Ensure that your sample_code.php file has the correct permissions. The file should typically have 644 permissions (readable by the server). You can set this using:
chmod 644 sample_code.php
- Directory Permissions: Check the permissions of the directory containing the sample_code.php file. The directory should have 755 permissions:
chmod 755 /path/to/directory
- Ownership: Make sure the file and directory are owned by the correct user. The web server user (e.g., www-data for Apache on Ubuntu) should have ownership. You can change ownership using
chown www-data:www-data sample_code.php
- .htaccess File: If you have an .htaccess file, ensure it doesn't have any rules blocking access to your PHP file.
- Server Configuration: Check your server configuration files (like httpd.conf for Apache) to ensure there are no restrictions that might be causing the 403 error.
- Web Server Logs: Look at the web server logs for more detailed error messages. They can provide insights into why the server is denying access.
Try these steps and see if they resolve the issue. If the problem persists, feel free to provide more details so I can help further!
@@thecloudinvestor777 thanks sir I will try .
Thankyou so much!
You're welcome!
Thanks brother 🙏
My pleasure