Created a MWAA service in a VPC and our db is in a different VPC. The peering does not seem to work

0

I have updated the default routes in both the VPC to include the intenet gaetway. I have also updated the security group to allpw traffic from the other VPC. Despite all this I cannot establish a connection from my MWAA cluster to the redshift database

1 個回答
0

You mention "peering" - do you mean you've got a VPC Peering connection in place between those VPCs? If so then the routing rules need to route traffic for the other VPC via the peering connection. If on the other hand you're connecting over public internet, is your redshift cluster set to "Public"?

專家
已回答 1 年前
  • Yes, VPC peering. I have updated the routing rules and also updates the security group for both the vpcs. It still doesnt seem to work. (being within Amazon, we are not allowed to open anything to the internet)

  • OK I'm a bit confused because you said in your question "I have updated the default routes in both the VPC to include the intenet gaetway". To route between peered VPCs you need routes defined to go via the peering connections. For example if VPC1 has a peering connection pcx-11111111 to VPC2 whose CIDR block is 10.0.0.0/20, then VPC1's route tables need a route with Destination=10.0.0.0/20, Target=pcx-11111111.

  • Yes, I have done just that. Would you be open to a live chat, where I can show you all the setups that I did.? I am flexible with any time since I wfh mostly.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南

相關內容