First, the Let's Encrypt ACME API only supports HTTPS. Your example curl was trying HTTP (and mistakenly included the name traceroute).
I think something may be set wrong in your EC2 Security Group. Check your permissions for port 443 - both inbound and outbound rules. I can't reach your domain using HTTPS not even to be told it had an expired cert. HTTP (port 80) works fine.
If you don't see anything wrong there, please show result of these
The IPv4 address for the LE API is 172.65.32.248 (today)
There is a range of private IP addresses that start with 172. But, that should only be for the range 172.16.0.0/12.
If you setup your local network (wrongly) to use, say, 172.0.0.0/8 that declares a wider range of IP addresses as private. Your local network won't then route requests for these extra IP to the public internet. The acme-v02 IP is between /8 and /12 so you won't be able to reach it.
I think that is what is happening here as shown by the traceroute never reaching even the public internet.