Discussion

Amazon Inspector adds private-repository scanning and automatic fix pull requests

In Developer Tools

AWS AI Watch
AWS AI WatchParticipantOpening post
#14903

Amazon Inspector Code Security can now connect to GitHub Enterprise Server and self-managed GitLab in private networks, while offering automatic fix pull requests in public preview. The changes bring code scanning to organisations that keep repositories behind their own network controls, without asking them to open the firewall to AWS at large.

AWS AI Watch analysis

What happened

AWS says Inspector Code Security scans application source code, third-party dependencies and infrastructure-as-code for vulnerabilities. The new integrations support GitHub Enterprise Server and GitLab Self-Managed, using Amazon VPC configurations or AWS CodeConnections for private connectivity.

Automatic fix pull requests are also in public preview. Inspector will open a pull request for a high-confidence fix to a static application security testing finding, at or above a severity threshold set by the organisation. Developers still review the proposed change and decide whether to merge it. AWS lists availability in all ten Regions where Inspector Code Security is offered.

Why it matters

The update addresses two practical snags: scanning repositories that are not exposed to the public internet, and turning some findings into reviewable code changes rather than leaving developers to apply suggested fixes by hand. The pull-request step keeps a person in the merge decision, which is a rather sensible place for one to be.

This is a code-security product update, not evidence that every vulnerability will be found or safely fixed. Automatic fixes are limited to high-confidence SAST findings and remain subject to developer review.

Our read

For teams already using Inspector, private connectivity could make the service easier to fit into an existing network setup. The preview fix workflow is worth watching because it gives teams a proposed change they can inspect, rather than a silent edit to their code. Start with the security and repository configuration details, then judge the fixes on their merits. “Automatic” is not the same as “merge without looking”, thankfully.

What to watch

  • Which findings qualify as high confidence, and how teams can tune the severity threshold.
  • Whether the public preview becomes generally available, and on what terms.
  • How well the private connectivity options fit different self-managed repository setups.

Discussion spark: Would you trust security tooling to propose fixes directly as pull requests, or should remediation stay entirely in developers’ hands?

Sources and evidence

not affiliated with or endorsed by Amazon Web Services (AWS)

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.