StackServicesBedrock

Bedrock

Last updated: Oct 30, 2026

Rationale

Amazon Bedrock is the primary point of contact of Fluid Attacks with LLMs.

These are the primary reasons why Fluid Attacks selected it and not other alternatives:

  • It gives a wide range of foundational models.
  • It gives open-source and proprietary foundational models.
  • It does not send information to third parties.
  • It complies with GDPR and SOC 2.
  • Its infrastructure is in the US.
  • You can easily configure it with Terraform.
  • It gives guardrails and other protection mechanisms.

Alternatives

Fluid Attacks examined these alternatives, but it did not select them for these reasons:

Anthropic

  • Its models are available through Amazon Bedrock.
  • It has a smaller range of foundational models.

Self-hosted open-source models

  • This alternative has high maintenance costs.
  • It does not give access to some proprietary models.

Usage

Fluid Attacks uses Amazon Bedrock to interact with foundational models.

Batch

Learn about Batch, an AWS service employed by Fluid Attacks to execute batch processing tasks in the cloud.

BigCodeBench

Fluid Attacks uses BigCodeBench to define the best model to use in the features that suggest vulnerability fixes within the platform and VS Code extension.

On this page

RationaleAlternativesAnthropicSelf-hosted open-source modelsUsage