Control: 2 Amazon Elasticsearch Service domains should be in a VPC
This control checks whether Amazon Elasticsearch Service domains are in a VPC.
It does not evaluate the VPC subnet routing configuration to determine public reachability.
This AWS control also does not check whether the Amazon ES resource-based policy permits public access by other accounts or external entities. You should ensure that Amazon ES domains are not attached to public subnets. See Resource-based policies in the Amazon Elasticsearch Service Developer Guide.
If you create a domain with a public endpoint, you cannot later place it within a VPC. Instead, you must create a new domain and migrate your data.
The reverse is also true. If you create a domain within a VPC, it cannot have a public endpoint. Instead, you must either create another domain or disable this control.
See the information on migrating from public access to VPC access in the Amazon Elasticsearch Service Developer Guide.
steampipe check aws_compliance.control.foundational_security_es_2
This control uses a named query:es_domain_in_vpc