2 Answers
- Newest
- Most votes
- Most comments
0
Ok - I got to the bottom of this and it was my error. The DX connection was to a region that we hadn't yet enabled (as the region didn't exist when we set up the rest of our VPCs). As soon as the region was enabled within the account, the pending connection popped up.
Thanks, ANdrew
answered 2 months ago
0
Hello.
Is the connection created in a different AWS account?
If the hosted connection was created with the correct AWS account, you should be able to see it from the management console.
https://docs.aws.amazon.com/directconnect/latest/UserGuide/hosted_connection.html#accept-hosted-connection
Relevant content
- asked a year ago
- Accepted Answerasked 3 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago
Thanks for your comment, Riku. Yes, I've confirmed with the network provider that the AWS account ID they used for setting up the connection (via the Megaport wholesaler) is the same account I'm viewing the Direct Connect information in.