Here's the link to troubleshoot the error "Could not reach AWS" -- 
As mentioned, This error occurs because of a failed attempt by the Discovery Connector to establish an HTTPS connection to an AWS domain that the connector needs to communicate with during the setup process. The Discovery Connector configuration fails if a connection can't be established.
To fix the connection to AWS
- Check with your IT admin to see if your company firewall is blocking egress traffic on port 443 to any of the AWS domains that need outbound access. OR Check if port 443 is allowed for the below domains to double check.
The following AWS domains need outbound access:
awsconnector.Migration Hub home Region.amazonaws.com
sns.Migration Hub home Region.amazonaws.com
arsenal-discovery.Migration Hub home Region.amazonaws.com
- If your firewall is blocking egress traffic, unblock it. After you update the firewall, reconfigure the connector.
If updating the firewall does not resolve the connection issue, check to make sure that the connector virtual machine has outbound network connectivity to the listed domains. If the virtual machine has outbound connectivity, test the connection to listed domains by running telnet on ports 443 as shown in the following example.
telnet ec2.amazonaws.com 443 -- run this command and see what is the output. If this works fine, please open up a case with AWS Support and they will be able to help you. Please note that they might ask for the logs.
Log back in to the AWS Agentless Discovery Connector console (as you did during configuration) and choose Download log bundle.
Once the log bundle has finished downloading, send it as instructed by AWS Support.
Please click Accept answer if this solution helped you !!
Hi, i test the conectiviy with ping command to iam.amazonaws.com aws.amazon.com ec2.amazonaws.com and is ok, and this command telnet ec2.amazonaws.com 443 is ok too.
Now i have this errors I sent to aws support.
aws discovery connectorasked 2 months ago
Cloudwatch Connector V2 Upgrade Deployment FailsAccepted Answerasked 3 years ago
AD Connector inoperable state - Unable to deleteasked 10 months ago
ECS service discovery: Can I use short for inter-service communication?asked 4 months ago
ECS Fargate - CloudMap Service Discovery not working.asked 3 months ago
AWS SSO ERROR 403 with AD connectorasked 5 months ago
AD Connector MFA Setup Completed but AD Connector not sending RADIUSasked 2 years ago
I am not able to delete AD connector and need assistanceasked a month ago
MSK connect connector deploymentasked 5 months ago
API Gateway jwt authorizer OIDC discovery endpointasked a year ago