platformchangelog.dev
44 tools
feedpost

Enforcing zero-trust dependency policies in AWS CodeBuild with JFrog Curation

The AWS DevOps Blog describes a CodeBuild pipeline in which pip installs resolve through a JFrog Artifactory virtual PyPI repository with JFrog Curation enabled. Packages that violate a Block Critical CVEs policy (CVSS 9.0 or above) receive an HTTP 403, which fails the Docker build before any image is pushed to Amazon ECR. The post says a post-build script queries the Curation audit API to report the blocked package and suggested fix versions. The source text was truncated before the post-build section was complete.

What changes for platform teams

Platform teams running CodeBuild can enforce package policy at download time by routing pip through a curated repository, with the redirect handled in configuration rather than application code. The approach depends on a JFrog Enterprise X or Enterprise+ Curation subscription and has only been described in this source text, not independently verified.

Read the original at AWS DevOps Blog ↗

written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules

Report a mistake

context

How this was written

The summary was written from the original by the model named above, checked by fixed publishing rules, and read by an editor after publication. See the methodology.

Back to the feed

Enforcing zero-trust dependency policies in AWS CodeBuild with JFrog Curation | Platform Changelog