- Newest
- Most votes
- Most comments
Using the IMPORT FROM S3 function, RDS PostgreSQL can directly read a file from an S3 bucket and import the data. This approach works well if your RDS PostgreSQL instance has a network path to access the S3 bucket. However, if your instance is private and the subnet route table lacks a NAT gateway or NAT server, then direct access to the S3 bucket won't be possible. An alternative solution is to leverage AWS PrivateLink S3 Gateway, which allows data to flow internally through a VPC endpoint.
Hello.
Since it was a timeout error, I thought there was a problem with the network settings for accessing S3 from RDS.
So, I thought that if I created a gateway VPC endpoint for S3 and set a route to the VPC endpoint in the route table of the subnet used by RDS, I would be able to communicate.
https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html#create-gateway-endpoint-s3
Relevant content
- asked a year ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago