Overview
The problem with existing DevOps AMIs Every Jenkins/SonarQube AMI on the market gives you tools - but leaves you alone with 800 lines of build logs, cryptic SonarQube warnings, and Trivy CVE IDs you have to look up manually.
What AI DevSecOps Workbench does differently This AMI ships a complete DevSecOps stack with an embedded AI assistant that actually understands your pipeline. It reads your build logs, explains your code quality issues, and analyses your container vulnerabilities - all from a single dashboard, without you leaving the browser.
Three core tools, one AI layer:
- Jenkins: CI/CD automation with auto-fetching build log analysis
- SonarQube: Code quality scanning with AI-powered issue explanation
- Trivy: Container and filesystem CVE scanning with prioritised fix recommendations
What makes it different from a Jenkins plugin: Jenkins AI plugins only work inside Jenkins. This assistant works across all three tools simultaneously - one chat interface for your entire DevSecOps pipeline.
Proactive health monitoring: The dashboard automatically polls Jenkins and SonarQube every 60 seconds and surfaces failed builds and critical issues as alerts. One click on any alert triggers an AI analysis - no manual searching required.
Bring your own AI provider: Configure your preferred AI backend in a single config file:
- AWS Bedrock (default - uses your EC2 IAM role, no API key needed)
- Anthropic Claude (direct API)
- OpenAI GPT-4
- Ollama (offline, no internet required) Switch providers by changing one line. No AMI rebuild needed.
Zero-friction first boot: SSH in and your credentials are waiting in the terminal. Jenkins and SonarQube are pre-configured with unique random passwords. The AI assistant is ready to use as soon as you add your API tokens.
Highlights
- AI-powered Jenkins build log analyser - paste a log or enter a job name, get root cause and fix in seconds
- SonarQube code quality explainer - groups issues by severity, explains each one in plain English
- Trivy CVE scanner - scans Docker images and filesystems, AI prioritises which vulnerabilities to fix first
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/hour |
|---|---|
t3.large Recommended | $0.07 |
t3.medium | $0.05 |
t3.xlarge | $0.10 |
Vendor refund policy
We offer a full refund within 48 hours of purchase if the product does not function as described. To request a refund, contact vishnu.sharma@3sdatacloud.com with your AWS account ID and a description of the issue. Refund requests are reviewed within 2 business days. No refunds after 48 hours of usage.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Initial release of AI DevSecOps Workbench.
- Jenkins LTS with CI/CD pipeline support
- SonarQube Community for code quality analysis
- Trivy for container and filesystem CVE scanning
- AI assistant powered by AWS Bedrock (pluggable to Claude, OpenAI, or Ollama)
- Proactive health dashboard with zero-token monitoring
- Auto-generated unique credentials on first boot
- Configurable data retention via config.yaml
- All traffic routed through Nginx reverse proxy
Additional details
Usage instructions
-
Launch the instance with ports 22 (SSH) and 80 (HTTP) open in your security group.
-
Attach an IAM role with bedrock:InvokeModel permission to use the default AI provider (AWS Bedrock).
-
SSH into the instance: ssh -i your-key.pem ubuntu@YOUR_INSTANCE_IP
-
Your Jenkins and SonarQube credentials are displayed automatically in the terminal on login. To view them again: sudo cat /etc/devops-agent/credentials.txt
-
Open http://YOUR_INSTANCE_IP in your browser to access the AI DevSecOps dashboard.
-
Log into Jenkins at /jenkins/ and SonarQube at /sonar/ using the credentials from step 4.
-
Generate API tokens in both tools and add them to the config file: sudo nano /etc/devops-agent/config.yaml
- jenkins_token: Jenkins > your username > Configure > API Token
- sonarqube_token: SonarQube > avatar > My Account > Security > Generate Token
-
Enable Bedrock model access in AWS Console: Bedrock > Model access > Enable Claude Sonnet Then update bedrock_model in config.yaml with your inference profile ID.
-
Restart the AI agent after config changes: sudo systemctl restart devops-agent
Support: vishnu.sharma@3sdatacloud.com
Support
Vendor support
Support Email: vishnu.sharma@3sdatacloud.com Community support via email. We aim to respond to queries within 2-3 business days.
This product includes detailed setup documentation within the AMI at /etc/devops-agent/config.yaml and a first-boot credentials file at /etc/devops-agent/credentials.txt.
For common issues:
- Check service status: sudo systemctl status devops-workbench devops-agent nginx
- View agent logs: sudo journalctl -u devops-agent -n 50
- AI provider setup: ensure your EC2 IAM role has bedrock:InvokeModel permission and Bedrock model access is enabled in your AWS account
Provided by 3S Data Cloud
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.