How nukunga/pipe-workshop works
Main Components
A. Development Pipeline Components:
• Source Control (CodeCommit)
• Build System (CodeBuild)
• Deployment System (CodeDeploy)
• Pipeline Orchestration (CodePipeline)
B. Security Testing Layers:
• SCA (Dependency-CHECK)
• SAST (SonarQube)
• DAST (OWASP ZAP)
C. Monitoring & Security Components:
• AWS WAF
• CloudTrail
• GuardDuty
• OpenSearch (for log aggregation and alerting)
┌─────────────────────────────────────────────────────────────┐
• Development Layer │
• ┤
• Security Testing Layer │
• ┤
• Deployment Layer │
• ┤
• Monitoring Layer │
• ┘
Specific Implementation Details
A. Development Flow:
CodeCommit → CodeBuild → CodeDeploy → Production
B. Security Testing Integration:
CodeBuild → [SCA → SAST → DAST] → Security Validation
C. Monitoring Flow:
WAF ─┐
CloudTrail ─┼→ OpenSearch → Alerts
GuardDuty ─┘
Additional Elements
Specific components from the project:
• IAM roles and permissions (from iac/deploy-test/modules/iam-role)
• S3 buckets for artifacts (from iac/deploy-test/modules/s3)
• KMS for encryption (from iac/deploy-test/modules/kms)
• Lambda functions for security hub integration (from yaml&script/lambda)
Implementation Notes
• Version/environment indicators
• Security group boundaries
• Alert trigger points