- Newest
- Most votes
- Most comments
Hello.
There is a high possibility that t2.micro has too little memory.
Airflow's prerequisites state that the memory is 4GB.
It is possible that the error "[My IP address] took too long to respond." may have occurred because EC2 memory was low and processing took a long time.
https://airflow.apache.org/docs/apache-airflow/stable/installation/prerequisites.html
The minimum memory required we recommend Airflow to run with is 4GB, but the actual requirements depend wildly on the deployment options you have
Do you have an internet gateway configured on your VPC and is your EC2 in the public subnet where the internet gateway resides?
Yes I checked, and is attached and linked correctly.
Yes both of them are correctly linked
Just to confirm your security group rules you have 433 instead of 443
Hi Gary, was a typo the port is 443
Ok np. Thanks
Addicional info:
I created 2 EC2 instances: First one runs on AMI Amazon Linux 2023 with 64bits (x86) on t2.micro Free tier Second one runs on Ubuntu Server 22.04 LTS (HVM), SSD Volume type with 64bits (x86) on t2.micro Free tier (my airflow app runs on this model)
Same Security group, kes-value and simple code
#!/bin/bash
Use this for your user data (script from top to bottom)
install httpd (Linux 2 version)
yum update -y yum install -y httpd systemctl start httpd systemctl enable httpd echo "<h1>Hello World from $(hostname -f)</h1>" > /var/www/html/index.html
The first one works perfectly on Brave,Chrome and Firefox. The second one fails miserably on every browser with the same error than my airflow model.
What can be happening?
Relevant content
- asked 2 months ago
- asked 9 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Hi Riku,
I also tried with bigger EC2 instances and still persist the error