- 新しい順
- 投票が多い順
- コメントが多い順
I think I've figured it out.
It appears to be an aws-generated Endpoint for my RDS serverless instance. I was able to determine this from 2 things: 1) the network monitoring of the endpoint correlated to my RDS network traffic, and 2) the security groups attached to the network interfaces attached to the endpoint both had rules that were associated with my RDS instance. Another hint was that RDS requires a minimum of 2 availability zones (for Multi-AZ), which is why there were exactly 2 subnets in this Endpoint.
I was able to confirm this by logging onto an EC2 instance in the VPC, and running nslookup against my RDS instance's private DNS name. It had a CNAME of the Endpoint, and the A record IPs associated with the CNAME were the same IPs listed in the Endpoint's subnet listing. Mystery solved, and good thing I didn't delete this.
Head into the VPC console and click on "Endpoints". In there you'll see the endpoints that have been deployed in your VPC. The name you've given isn't too helpful - it's the last part which determines which service the endpoint has been created for.
関連するコンテンツ
AWS公式更新しました 1年前
Hi, thanks for the quick response. The full service name is (redacted, not sure if necessary): "com.amazonaws.vpce.us-west-2.vpce-svc-*************", with the asterisks appearing to be a random hash.
FWIW, the network traffic on the "Monitoring" tab of the endpoint seems directly tied to the network traffic of a serverless RDS instance. Does this give a clue as to what the endpoint is for?