1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I think temporary issue and resolved? I dont face any error right now.
con risposta un anno fa
I am not quite sure, but I think so. AWS reached out to me for more detail, and then I tried again by removed the Direct Connect Gateway and Virtual Interface, and so new Transit Gateway. After that, I could set up multiple new Connect Attachments and Peers without any problem. Thanks for following up!
Contenuto pertinente
- AWS UFFICIALEAggiornata 6 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
Are you creating the Connect Peer to an appliance that lives in the same VPC as the Transit Gateway attachment? The IP address doesn't seem to indicate this is so. https://docs.aws.amazon.com/vpc/latest/tgw/tgw-connect.html#tgw-connect-peer:~:text=The%20following%20example
I was testing and trying to create Connect Peer over the Connect attachment which is using Direct Connect Gateway attachment as transport. This Direct Connect Gateway is connecting to our physical Juniper MX router. In other words, I create the other end of this GRE tunnel on our Juniper MX, and hopefully it could connect to Transit Gateway through this Connect-Peer/GRE-tunnel. The Peer IP I used here is just for a internal test, not a really a public service IP at all. Sorry for the confusion. I re-configured Connect Attachment and setting and test again, still the same.
Debug output of my creating Connect peer command, looks like where got wrong. 2023-05-30 16:42:25,192 - MainThread - awscli.clidriver - DEBUG - Exception caught in main() Traceback (most recent call last): File "awscli/clidriver.py", line 460, in main File "awscli/clidriver.py", line 595, in call File "awscli/clidriver.py", line 798, in call File "awscli/clidriver.py", line 929, in invoke File "awscli/clidriver.py", line 941, in _make_client_call File "awscli/botocore/client.py", line 341, in _api_call File "awscli/botocore/client.py", line 697, in _make_api_call