# Allow requests to elastic deployment only from AWS EC2 instances in VPN **URL:** \ **Category:** Elasticsearch\ **Created:** [February 19, 2024, 3:02pm UTC](https://discuss.elastic.co/t/allow-requests-to-elastic-deployment-only-from-aws-ec2-instances-in-vpn/353618 "2024-02-19T15:02:33Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![searchwithme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchwithme/32/137075_2.png) [@searchwithme](https://discuss.elastic.co/u/searchwithme)\ **Post date:** [February 19, 2024, 3:02pm UTC](https://discuss.elastic.co/t/allow-requests-to-elastic-deployment-only-from-aws-ec2-instances-in-vpn/353618/1 "2024-02-19T15:02:33Z")
Is it possible to restrict access to elastic deployment only from AWS EC2 instances that are part of a particular VPN? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [February 19, 2024, 6:02pm UTC](https://discuss.elastic.co/t/allow-requests-to-elastic-deployment-only-from-aws-ec2-instances-in-vpn/353618/2 "2024-02-19T18:02:39Z")
Of course, network security is multi-faceted... (you can implement your own FWs, VPC controls, Private link etc..etc..) Here are the built-in features for self-managed elasticsearch > **[Restricting connections with IP filtering | Elasticsearch Guide \[8.12\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/ip-filtering.html)** ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 18, 2024, 6:03pm UTC](https://discuss.elastic.co/t/allow-requests-to-elastic-deployment-only-from-aws-ec2-instances-in-vpn/353618/3 "2024-03-18T18:03:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.