Amazon Bedrock

Amazon Bedrock integration setup for Arnica

Arnica uses Amazon Bedrock to provide code fix suggestions for SAST and IaC findings. Unlike the direct OpenAI or Anthropic integrations, Bedrock runs in your own AWS account.

  1. In Arnica, navigate to the Integrations pagearrow-up-right and click Connect next to Amazon Bedrock.

  1. Select the AWS Region where your Bedrock models are available.

We strongly recommend using an IAM Role instead of access keys. It is more secure (no long‑lived keys) and easier to manage.

  • If you have AWS access:

    1. In the integration dialog, keep the IAM Role tab selected.

    2. Click Deploy CloudFormation Template.

    3. In the AWS Console, click Create Stack to deploy the template. Any region works because IAM roles are global.

    4. After the stack finishes, open the Outputs tab.

    5. Copy the RoleArn value. You do not need to copy the ExternalId if you left it unchanged in Arnica.

    6. Back in Arnica, paste the RoleArn into the Role ARN field (if you changed the External ID earlier, enter the updated value here).

    7. (Optional) Enter an alias to help you recognize the integration.

    8. Click Validate, then OK.

  • If you do not have AWS access:

    1. Copy the Direct template link and your External ID from the integration dialog:

      • Template URL: https://arnica-integration-templates.s3.amazonaws.com/bedrock-integration-role.yaml

      • External ID: use the value shown in Arnica. Keep this External ID so you can complete the integration later.

    2. Ask your AWS administrator to deploy the template using that External ID (any region is fine) and to send you the RoleArn from the stack's Outputs.

    3. When you receive the RoleArn, paste it into the Role ARN field in Arnica. If your admin used a different External ID, update the External ID field to match.

    4. (Optional) Enter an alias, click Validate, then OK.

chevron-rightWhat permissions does the CloudFormation template grant?hashtag

The template creates an IAM role (ArnicaBedrockIntegrationRole) with the following permissions:

Permission
Purpose

bedrock:ListFoundationModels

List models so Arnica can populate the model picker

bedrock:GetFoundationModel

Read model metadata

bedrock:ListInferenceProfiles

List inference profiles (cross-region)

bedrock:GetInferenceProfile

Read inference profile metadata

bedrock:InvokeModel

Call the selected model

bedrock:InvokeModelWithResponseStream

Call the selected model (streaming)

The role can only be assumed by Arnica's AWS account, and the External ID is required to prevent confused deputy attacksarrow-up-right.

Only use this method if you cannot use the IAM Role approach above.

  1. Create an IAM user with the following permissions:

  2. In Arnica, switch to the Access Key tab, enter the Access Key ID and Secret Access Key, click Validate, then OK.

Model selection

After connecting, Arnica pulls the list of models available in your account and selects a default model. To switch models, go to the AI Model Configuration pagearrow-up-right in the Admin menu.

circle-info

Most Bedrock models are accessible out of the box — you don't need to enable them one by one. If a model doesn't show up, see the Amazon Bedrock model access docsarrow-up-right for any provider-specific or regional requirements.

Usage

Recommendations are generated on demand rather than automatically for every finding, so you only pay for what you use.

To request a recommendation, go to the Code Risksarrow-up-right page and select a SAST or IaC finding. Click the AI icon in the top-right corner of the details pane. The icon spins while Arnica generates and validates the recommendation.

circle-info

To generate an alternative recommendation, click the AI icon again.

Each recommendation includes a code example followed by an explanation, so the fix is clear for both developers and Arnica operators.

Last updated

Was this helpful?