Public IP of AWS MWAA

0

Hi everyone.

  1. I have Redshift (in VPC1) that is publicly accessible, but whose security group (SG1) configured to accept specific IPs.
  2. I have public MWAA (in VPC2).

I want to add MWAA's public IP to SG1, so MWAA can access Redshift too. But, apparently there is no such thing as public IP of MWAA.

P.S. I tried creating vpc peering between VPC1 and VPC2, but it didn't work. My understanding of why it didn't work is that Redshift's dns name resolves into public IP, therefore MWAA uses internet to access Redshift instead of peering.

1 Answer
0

Hello, I understand that you are unable to connect to Redshift (VPC-A) from MWAA (VPC-B).

The issue might be related to the networking configuration between the MWAA Airflow instance and the Redshift Cluster.

Since your Redshift server is publicly accessible, you need to allow the Elastic IP of the NAT gateways (Configured in MWAA) in the inbound rules of the Redshift security group.

Also, make sure to create a New NAT if previous NAT gateway does not have an EIP attached.

In order to get proper resolution for your use case we require details that are non-public information. Please open a support case with AWS using the following link. https://console.aws.amazon.com/support/home#/case/create

AWS
SUPPORT ENGINEER
Babar
answered a year ago
  • Thank you for reply. Providing additional clarification.

    MWAA's VPC has 4 subnets: 2 public and 2 private. 2 private subnets has NAT gateways with EIPs attached to them. I already added those EIPs to Redshift's security group. In turn, 2 public subnets use internet gateway which do not have EIPs.

    Since adding NAT EIPs didn't help, my guess is that request is coming from MWAA's public subnets. And IP of those public subnets is unknown.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions