> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-iac/test-your-iac-files/serverless-files.md).

# Serverless files

How to test serverless files with Snyk IaC using the CLI

With Snyk Infrastructure as Code, you can test your configuration files using the CLI.

Snyk Infrastructure as Code for Serverless framework supports scanning the packaged output of Serverless files in Cloudformation JSON format files.

You can **test for an issue on specified Serverless files** as explained on this page.

Be sure you have the [Serverless CLI installed](https://www.serverless.com/framework/docs/getting-started).

After installing the Serverless CLI, **navigate** to the directory that contains your Serverless files and **generate** the Serverless artifacts by entering the following:

```
serverless package --package serverless-artifacts
```

Then you can enter the following Snyk CLI command to test for vulnerabilities:

```
snyk iac test
```

You can also upload the results into the Snyk UI with the command:

```
snyk iac test --report
```


---

# 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://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-iac/test-your-iac-files/serverless-files.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.