It looks like juju-dist.s3.amazonaws.com translates to several IPs, and it's hard to find a list of all. In fact, such a list doesn't exist. The firewall has to play catch up and filter new ones as we find them.
In this particular case, we believe that the IP juju-dist.s3.amazonaws.com resolved too wasn't allowed in the egress filtering rules of our firewall. We will add it, but this will happen again.
My suggestions are:
- log which IP was used to try the connection
- if attempting a retry, make sure to do a DNS resolution one more time before
It looks like juju-dist. s3.amazonaws. com translates to several IPs, and it's hard to find a list of all. In fact, such a list doesn't exist. The firewall has to play catch up and filter new ones as we find them.
In this particular case, we believe that the IP juju-dist. s3.amazonaws. com resolved too wasn't allowed in the egress filtering rules of our firewall. We will add it, but this will happen again.
My suggestions are:
- log which IP was used to try the connection
- if attempting a retry, make sure to do a DNS resolution one more time before