BWong
New Contributor III

Thanks guys. It's indeed a network issue on the AWS side. It's resolved now

View solution in original post