Hi,
I have been trying to set up new Connect peer through Transit Gateway Connect attachment, several times delete/create Transit Gateway and all attachments. I have the new Connect Attachment created without issue every time. But each time I try to create Connect in it, always got the same response "Transit Gateway Attachment null was deleted or does not exist". As following is the CLI output.
[cloudshell-user@ip-10-2-60-215 ~]$ aws ec2 create-transit-gateway-connect-peer \
--transit-gateway-attachment-id tgw-attach-0bc4c456d11251d1e \
--peer-address 172.30.0.1 \
--bgp-options PeerAsn=400178 \
--inside-cidr-blocks 169.254.248.0/29
An error occurred (InvalidTransitGatewayAttachmentID.NotFound) when calling the CreateTransitGatewayConnectPeer operation: Transit Gateway Attachment null was deleted or does not exist.
[cloudshell-user@ip-10-2-60-215 ~]$
I assume this is a bug on AWS API call. Is anyone else experiencing the same problem now? If anyone had similar issue and got a fix somehow, I would be deeply appreciated if you could share with me here.
Best Regards,
Y.K.L.
AWS 공식업데이트됨 2년 전
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