I’m having issues opening Airflow in both of the labs in this module. I followed the instructions of going to the console, going to CloudFormation, going to Outputs and getting AirflowDNS, but trying to visit the site is unsuccessful. Getting error that:
“This site can’t be reached. (The Instance Name) took too long to respond.”
I tried running the restart script and still get the same results. I see that others have had this same issue in the past based on previous posts. Could someone help please?
I’m facing the error like you in the afternoon, but in the late night, when I tried to open the lab again, it was already fixed. I had the same issue with my previous lab. I think the problem is related to the AWS resources allocated for this course, maybe a throttling issue or something else.
Interesting, how late are you talking? I just tried now in the morning and got the same error.
I think we should just re-try it on the same day with the open lab, so CloudFormation will redeploy it. For the root cause, let’s just wait and let the team fix it 
Hi, sorry for jumping to conclusions earlier. After troubleshooting for several hours, I realized the problem comes from the network we are using. Since the EC2 Public DNS uses unsecured HTTP, some networks (like our office network) block access to specific ports like 8080. I found two ways to fix this:
-
Use ngrok for port forwarding: Run ngrok http <dns airflow ui> and access it via the link ngrok provides.
-
Use AWS SSM on your terminal:
-
Get credentials by running cat ../.aws/credentials (remember to use region us-east-1).
-
Run this CLI command: aws ssm start-session --target <your-instance-id> --document-name AWS-StartPortForwardingSession --parameters '{"portNumber":["8080"],"localPortNumber":["8080"]}'
-
Access via localhost:8080 in your browser."