A VPC endpoint is a service provided by Amazon Web Services (AWS) that allows a secure connection between resources in your Virtual Private Cloud (VPC) and other AWS services. By default, VPC endpoints are only accessible from within your VPC, meaning they are not publicly accessible. However, it is possible to create a VPC endpoint that is publicly accessible by configuring it to have a route to an Internet Gateway. This allows the endpoint to be accessible from the internet, which may be necessary in certain scenarios, such as when hosting a public-facing web application. It is important to note that creating a publicly accessible VPC endpoint increases the risk of unauthorized access and should be done with caution. It is recommended to implement appropriate security measures, such as configuring access controls and monitoring the endpoint for unusual activity.‍


If you have determined that a VPC endpoint in your Amazon Web Services (AWS) environment is publicly accessible, it is important to take immediate remediation steps to reduce the risk of unauthorized access. Here are some steps you can take:

  1. Disable public accessibility: The first step is to disable the public accessibility of the VPC endpoint. You can do this by removing the route to the internet gateway from the VPC route table that is associated with the endpoint. This will prevent the endpoint from being accessible from the internet.
  2. Implement access controls: You should implement appropriate access controls to restrict access to the VPC endpoint. This can be done by creating security groups and network ACLs that limit inbound and outbound traffic to only the necessary ports and protocols. You can also use AWS Identity and Access Management (IAM) to control who can access the endpoint.
  3. Monitor for unusual activity: You should monitor the VPC endpoint for unusual activity that may indicate unauthorized access. This can be done by enabling AWS CloudTrail to capture API calls made to the endpoint and setting up CloudWatch alarms to alert you of any unusual activity.
  4. Review other VPC configurations: It is also a good idea to review other VPC configurations in your environment to ensure that they are not publicly accessible. This includes checking the route tables, security groups, and network ACLs associated with each VPC.
  5. Perform periodic audits: Finally, it is important to perform periodic audits of your AWS environment to ensure that all VPC endpoints are configured securely and are not publicly accessible. This can help you identify and remediate any vulnerabilities before they are exploited by attackers.

By following these remediation steps, you can help reduce the risk of unauthorized access to your VPC endpoints and ensure that your AWS environment is secure.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.