> 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/compute/appsec-aws-117.md).

# AWS Lambda Function is not assigned to access within VPC misconfiguration detected in code

## Rule Details

|                        |                                           |
| ---------------------- | ----------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_117                          |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type   |
| Provider               | AWS                                       |
| Severity               | LOW                                       |
| Framework              | CloudFormation, Terraform, Terraform Plan |

## Impact

By default, Lambda runs functions in a secure VPC with access to AWS services and the internet. Lambda owns this VPC, which isn't connected to the account's default VPC. Internet access from a private subnet requires Network Address Translation (NAT). To give your function access to the internet, route outbound traffic to a NAT gateway in a public subnet.

## How to Fix

To fix this issue, you should ensure that your AWS Lambda function configuration includes the `VpcConfig` property. Below is an example of how to set this property in a CloudFormation configuration:

## Example: \[source,go]

{ "Resources": { "ExampleLambdaFunction": { "Type": "AWS::Lambda::Function", "Properties": { "Handler": "index.handler", "Role": "arn:aws:iam::123456789012:role/lambda-role", "Code": { "S3Bucket": "my-bucket", "S3Key": "my-function.zip" }, "VpcConfig": { "SubnetIds": \[ "subnet-0bb1c79de3EXAMPLE" ], "SecurityGroupIds": \[ "sg-085912345678492fb" ] } } } } Resources: ExampleLambdaFunction: Type: AWS::Lambda::Function Properties: Handler: "index.handler" Role: "arn:aws:iam::123456789012:role/lambda-role" Code: S3Bucket: "my-bucket" S3Key: "my-function.zip" VpcConfig: SubnetIds:

* "subnet-0bb1c79de3EXAMPLE" SecurityGroupIds:
* "sg-085912345678492fb"

***


---

# 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/compute/appsec-aws-117.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.