# AWS CodeBuild

### Common Build Integration Documentation

This documentation is specific to AWS CodeBuild. [Common build server](https://docs.threatrix.io/integrations/build-integrations) documentation should be reviewed before proceeding further. 

### Environment Variables

Before continuing, you'll need to collect the following values from your Threatrix account. Please refer to [Common build server](https://docs.threatrix.io/integrations/build-integrations) documentation for details on where to find these values. 

Environment variable values can be found in your [user profile](https://docs.threatrix.io/threat-center-1/user-profile).

* THREATRIX\_OID - Your organization ID.
* THREATRIX\_EID - Your entityID
* THREATRIX\_API\_KEY - Service/API key.

### Install ThreatAgent into AWS CodeBuild pipeline

### Add CLI Threat Agent

Edit your existing *buildspec.yml* file to add the following two commands to download the agent and run the scan during your build.  The oid, eid and api-key may be setup as environment variables or the values may just be pas as arguments directly to the agent. Simple replace the curly brace holders with the associated values. 

```
phases:
  pre_build:
    commands:
      - curl -LJO https://github.com/threatrix/threat-matrix/releases/download/agent-release-latest/threat-agent-latest.jar
      - java -jar threat-agent-latest.jar --oid={THREATRIX_OID} --eid={THREATRIX_EID} --api-key={THREATRIX_API_KEY} .
```


---

# Agent Instructions: 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:

```
GET https://docs.threatrix.io/integrations/build-integrations/aws-codebuild.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.