> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec-aws-102.md).

# Neptune cluster instance is publicly available misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_102                     |
| Category - Subcategory | Public Exposure - Database Endpoints |
| Provider               | AWS                                  |
| Severity               | HIGH                                 |
| Framework              | Terraform, Terraform Plan            |

## Impact

Amazon Neptune is a graph database service that for high-performance graph database engine. Neptune supports the popular graph query languages Apache TinkerPop Gremlin and W3C's SPARQL. Neptune also gives you the ability to create snapshots of your databases, which you can use later to restore a database. You can share a snapshot with a different Amazon Web Services account, and the owner of the recipient account can use your snapshot to restore a DB that contains your data. You can even choose to make your snapshots public -- that is, anybody can restore a DB containing your data. This is a check to make sure that your database resource is not Publicly available. This is the resources' default behaviour. <https://docs.aws.amazon.com/neptune/latest/userguide/security-vpc.html>.

## How to Fix

*Resource:* aws\_neptune\_cluster\_instance

* *Arguments:* publicly\_accessible this default to false, so the check is to ensure it's missing or false. \[source,go]

***

## resource "aws\_neptune\_cluster\_instance" "example" { count = 2 cluster\_identifier = aws\_neptune\_cluster.default.id engine = "neptune" instance\_class = "db.r4.large" apply\_immediately = true }


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec-aws-102.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.