1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
We're having the same issue in us-east-2. I am able to list the services via AWS CLI, however.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
I'm actually in us-east-2 also. I don't know why it tries to connect to fusion.gamma in us-east-1. We see in the list of accepted servers the fusion.gamma.us-east-2. Maybe it is down and it fallbacks to us-east-1 but then it refuses connection.
I'm also able to list the sevices view AWS CLI.
At least the services run fine. And the one with automatic deployments are also deploying.
I contacted support and they fixed the issue.
Yes it is thanks!