[bsfp-cryptocurrency style=”widget-18″ align=”marquee” columns=”6″ coins=”selected” coins-count=”6″ coins-selected=”BTC,ETH,XRP,LTC,EOS,ADA,XLM,NEO,LTC,EOS,XEM,DASH,USDT,BNB,QTUM,XVG,ONT,ZEC,STEEM” currency=”USD” title=”Cryptocurrency Widget” show_title=”0″ icon=”” scheme=”light” bs-show-desktop=”1″ bs-show-tablet=”1″ bs-show-phone=”1″ custom-css-class=”” custom-id=”” css=”.vc_custom_1523079266073{margin-bottom: 0px !important;padding-top: 0px !important;padding-bottom: 0px !important;}”]

GitLab Collaborates with AWS to Bring Agentic DevSecOps to Enterprise Teams Using Their Existing Amazon Bedrock Accounts and Spend

GitLab Inc. Logo

  • Customers can route GitLab Duo Agent Platform inference through Amazon Bedrock models already running in their AWS accounts without new vendor onboarding or model endpoints.

  • GitLab Credits purchased through AWS Marketplace count toward existing AWS spending commitments.

  • GitLab’s Bring Your Own Model (BYOM) capability for Self-Managed customers lets teams connect their self-hosted AI Gateway directly to Amazon Bedrock, keeping inference traffic and source code within their own AWS environment.

Related Posts
1 of 43,009

GitLab Inc., the intelligent orchestration platform for DevSecOps, announced a deepened integration with Amazon Web Services (AWS). Joint customers can now route GitLab Duo Agent Platform inference through Amazon Bedrock, powering agentic DevSecOps with the Amazon Bedrock models, IAM policies, and AWS spending commitments they already have in place.

Also Read: AiThority Interview with Glenn Jocher, Founder & CEO, Ultralytics

As AI agents generate more code, merge requests, and pipeline activity, enterprises need the governance and auditability to keep pace without building a parallel infrastructure stack. For organizations that have already standardized on AWS, this integration brings GitLab Duo Agent Platform into their existing environment, from approved models in Amazon Bedrock, to access controls in IAM, and usage that counts toward existing AWS spend. There’s no new vendor risk assessment, no separate model endpoint to provision, and no additional billing relationship to manage.

GitLab’s orchestration layer adds workflow-level governance on top of what Amazon Bedrock already enforces at the model level. GitLab is already the system of record for merge requests, pipelines, and security findings, which means admin-defined policies control which models agents can call, audit logs capture every agent action alongside the code it produced, and teams can establish approved configurations so agents operate consistently across projects and regions.

This integration builds on GitLab’s recent Bring Your Own Model (BYOM) capability for Self-Managed customers. With BYOM, teams route inference from a self-hosted AI Gateway directly to Amazon Bedrock in their own AWS environment, so source code and inference traffic never leave the customer’s network boundary. Teams that have fine-tuned models on Amazon Bedrock can use those directly. Teams that prefer GitLab-managed models, now including the latest Anthropic Claude models available on Amazon Bedrock, can use those instead. GitLab handles the orchestration and governance regardless of which path a team chooses.

GitLab Duo Agent Platform is billed per request from a shared organizational pool of GitLab Credits, with no per-seat pricing. For customers purchasing GitLab through AWS Marketplace, those credits draw down existing AWS spend commitments, which makes scaling agentic AI a capacity decision within an existing contract.

Also Read: ​​The Infrastructure War Behind the AI Boom

[To share your insights with us, please write to psen@itechseries.com]

Comments are closed.