C2W3 - CloudWatch Dashboard Fails with DNS Error in Lab - Networking Blocked?

Course Q&A Data Engineering Source Systems, Data Ingestion, and Pipelines
1

Hi all,

I’m working on the AWS Monitoring lab and I keep running into a networking error when Terraform tries to create a CloudWatch Dashboard. Everything else (EC2, RDS, key pairs, subnet groups) creates fine after following some troubleshooting steps.

Here’s the error:

Error: putting CloudWatch Dashboard (de-c2w3lab2-rds-dashboard): operation error CloudWatch: PutDashboard, exceeded maximum number of attempts, 25, https response error StatusCode: 0, RequestID: , request send failed, Post "https://monitoring.us-east-1.amazonaws.com/": dial tcp: lookup monitoring.us-east-1.amazonaws.com on 127.0.0.11:53: server misbehaving

It hangs for a long time before failing.
I suspect the lab environment is blocking outbound DNS or internet access to AWS CloudWatch endpoints, since all other resources work except the dashboard.

Has anyone solved this, or can a staff member confirm if network access is intentionally restricted for CloudWatch?
Any workaround to test dashboard creation in this lab environment?

Thanks!

2

Hello @maxhare
I checked, and you are right. There is an issue with this lab. I will report it, and hopefully the team will fix it soon. However, since this is a practice lab, you can simply ignore it, and it won’t affect your course progress.

3

@hawraa.salami can you please look into this?
In my case, the command terraform apply in step 2 took more than 6 minutes and failed eventually, showing this error.

image
image1465×401 24.6 KB

4

Hi—just checking in to see if there’s been any progress on this.

I understand this is a practice lab and doesn’t affect course credit, but for those of us trying to learn the material, it’s still a meaningful blocker. I ended up spending around 4 hours trying to debug the issue before realizing it wasn’t on my end.

If a fix isn’t coming soon, could you at least mark the lab as broken or add a note so others don’t waste time hitting the same issue?

Thanks!

1 Like
5

@Amir_Zare , just following up. What was the resolution of this issue?