2 個答案
- 最新
- 最多得票
- 最多評論
1
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
已回答 2 個月前
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
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
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.