- Newest
- Most votes
- Most comments
You did not really explain how/where you are running postgREST
i am guessing on EC2? in that case, make sure you are adding the rule to the SG of the EC2 instance, and not the RDS instance
Howdy Ruslan! Thanks for taking the time to look at my question.
My test unit of postgREST associated with this RDS instance is running on a local machine; sorry for the lack of clarity.
I've got another instance running great on DigitalOcean (postgres _ postgREST running on same VM), but clearly I'm doing something wrong with this RDS _ remote postgREST config.
Edited by: MisterOctober on Jul 23, 2019 2:39 PM
You are running postgrest locally so aws has nothing to do with it.
You need to open the port 3000 on your local machine, not in rds.
How are you testing, what is your exact curl line?
It should be like curl http://localhost:3000/ ....
Thanks for your help, Ruslan! I ended up moving postgREST to an EC2 instance, but was having the same problem {plus some!}-- the fix ended up being :
** to set the RDS instance port 5432 ingress rule source ID to _the security group, rather than the CIDR IP block, of the EC2 instance.**
postgREST API calls are now working properly in all respects. Bellissimo!
p.s. special thanks also to Pooja @ AWS Support for the analysis and additional tips
Edited by: MisterOctober on Jul 30, 2019 3:10 PM
edited for clarity
Edited by: MisterOctober on Jul 30, 2019 4:06 PM
Relevant content
- asked 5 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago