Public IP of AWS MWAA

Question

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.

Answer

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.

- Verify security group rules. 
- If your MWAA subnets are using NAT -Gateway, you can add an EIP to the NAT gateway. And similar EIP can be allowed on Redshift Security Group.
-  Work with NAT gateways - https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html#nat-gateway-working-with ( Step - 7)

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

Public IP of AWS MWAA

Conteúdo relevante