Notifications
Clear all
Topic starter
07/10/2022 4:28 am
A media company is using Amazon RDS for PostgreSQL to store user data. The RDS DB instance currently has a publicly accessible setting enabled and is hosted in a public subnet. Following a recent AWS Well-Architected Framework review, a Database Specialist was given new security requirements.
Only certain on-premises corporate network IPs should connect to the DB instance. Connectivity is allowed from the corporate network only.
Which combination of steps does the Database Specialist need to take to meet these new requirements? (Choose three.)
- A . Modify the pg_hba.conf file. Add the required corporate network IPs and remove the unwanted IPs.
- B . Modify the associated security group. Add the required corporate network IPs and remove the unwanted IPs.
- C . Move the DB instance to a private subnet using AWS DM
- E . Enable VPC peering between the application host running on the corporate network and the VPC associated with the DB instance.
- F . Disable the publicly accessible setting.
- G . Connect to the DB instance using private IPs and a VP
Suggested Answer: BEF
Explanation:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding
Explanation:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding