RDS postgresql as the destination for Amazon AppFlow

0

I am trying to create an AppFlow with S3 as the source and RDS postgresql(Not accessible to public) as the destination. But i am getting the following error : "ValidateCredentials with CustomConnector" with connector failure The request failed because the service Source Amazon RDS returned the following error: Details: Unable to connect to the database., ErrorCode: InvalidArgument. (Service: null; Status Code: 400; Error Code: Client; Request ID: null; Proxy: null)" Is it even possible to use postgresql as the destination if RDS is made private i.e. the field accessible to public is set as No.

2 Answers
1

Hello Supriya,

With Public Accessibility set to No in RDS, only resources within your VPC can access the database. I hope your SG and network ACLs are configured correctly to access the RDS.

Also, see if the following links will help you - https://docs.aws.amazon.com/appflow/latest/userguide/connectors-amazon-rds-postgres-sql.html https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/postgresql-s3-export.html

Thanks

answered 2 months ago
  • So the RDS which I have created wont be accessible from the Amazon AppFlow which i am trying to create as the AppFlow is a fully managed service and hence will be in a different VPC than mine. Also the AppFLow VPC info wont be with me either

0

Hey there!,

Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. Ensure that the security group associated with your RDS instance allows inbound connections from the AWS AppFlow service. You'll need to add an inbound rule that allows traffic from the IP addresses or security groups associated with the AWS AppFlow service. If the RDS instance is in a private subnet, ensure that the inbound rules allow traffic from the subnet where your AppFlow service is running.
  2. If your RDS instance is in a VPC, ensure that the VPC has a route to the S3 endpoint. If the S3 bucket is in a different VPC, you'll need to set up VPC peering or VPC endpoints to allow communication between the two.

Consider using AWS PrivateLink or VPC endpoints for Amazon S3 and Amazon RDS to enable private connectivity between the services within your VPC without exposing them to the public internet.

  1. Ensure that the IAM role used by the AppFlow service has the necessary permissions to access both S3 and RDS. This includes permissions to read from S3 and write to the RDS instance.
  2. Verify that the database endpoint, port, username, and password provided in the AppFlow configuration are correct. Also, ensure that the database instance is up and running.

If you encounter any hurdles during the configuration process, feel free to tag me for assistance.

profile picture
EXPERT
answered 2 months ago

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