panther_analysis_tool
test to ensure your unit tests are passing, followed by panther_analysis_tool upload
to upload new detections to your Panther instance. Setting environment variables AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY_ID
and AWS_DEFAULT_REGION
(obtained from support if an IAM user is created, yours if a Panther role was created) is necessary for these commands to execute successfully.AWS_ACCESS_KEY_ID
, AWS_SECRET_ACCESS_KEY_ID
and AWS_DEFAULT_REGION
are passed into the job to allow for correct authentication. These will be provided by support in the case they created an IAM user and can be stored encrypted as repository secrets. The process of adding repository secrets is covered more in-depth in the next section.panther-analysis
. The CircleCI documentation for environment variables can be found here. The environment variables that need to be created are are $INTERNAL_ACCESS_KEY_ID
(AWS Access Key), $INTERNAL_SECRET_ACCESS_KEY
(AWS Secret Access Key), and$INTERNAL_DEFAULT_REGION
(AWS Default Region). These are obtained from support if an IAM user is created, yours if a Panther role was created.panther-analysis
repo..circleci/aws_config
within your forked version of panther-analysis
. In the below example, you will need to update the role_arn
which will be provided to you by Panther and region
where your Panther instance has been deployed.