If you prefer to set up the GitHub repository manually or the automated scripts don't work, follow these steps:
- Go to GitHub.com
- Click the "+" icon in the top right → "New repository"
- Repository name:
sysops.aws.securitygroup - Description:
🔒 AWS Security Groups Traffic Analysis Tool - Comprehensive multi-account security group analysis and visualization dashboard for identifying vulnerabilities and mapping traffic patterns - Make it Public (or Private if preferred)
- Do NOT initialize with README, .gitignore, or license (we already have these)
- Click "Create repository"
gh repo create Tranzact/sysops.aws.securitygroup \
--description "🔒 AWS Security Groups Traffic Analysis Tool - Comprehensive multi-account security group analysis and visualization dashboard for identifying vulnerabilities and mapping traffic patterns" \
--public \
--push \
--source .# Initialize Git (if not already done)
git init
git branch -M main
# Add all files
git add .
# Commit with descriptive message
git commit -m "Initial commit: AWS Security Groups Analysis Tool v1.0.0
- Multi-account security group analysis
- Interactive Streamlit dashboard
- Risk assessment and compliance reporting
- Cross-account IAM role support
- Comprehensive CSV export functionality
- Network visualization and traffic mapping"# Add remote origin for Tranzact organization
git remote add origin https://github.com/Tranzact/sysops.aws.securitygroup.git
# Push to GitHub
git push -u origin mainGo to your repository → Settings → General → Topics, and add:
awssecurity-groupssecurity-analysisaws-securitysecurity-auditmulti-accounttraffic-analysisdashboardpythonstreamlitsecurity-toolsaws-clidevopssysopsnetwork-security
Go to Settings → Security & analysis:
- ✅ Enable "Secret scanning"
- ✅ Enable "Secret scanning push protection"
- ✅ Enable "Dependabot alerts"
- ✅ Enable "Dependabot security updates"
Go to Settings → Branches → Add rule for main:
- ✅ Require pull request reviews before merging
- ✅ Require status checks to pass before merging
- ✅ Dismiss stale pull request approvals when new commits are pushed
- Go to your repository → Releases → "Create a new release"
- Tag version:
v1.0.0 - Release title:
AWS Security Groups Analysis Tool v1.0.0 - Description: Copy from the release notes in the automated script
- Click "Publish release"
gh release create v1.0.0 \
--title "AWS Security Groups Analysis Tool v1.0.0" \
--notes "Initial release with multi-account security group analysis, interactive dashboard, and comprehensive reporting capabilities."Your repository should now have:
- ✅ All project files committed
- ✅ README.md with comprehensive documentation
- ✅ LICENSE file (MIT)
- ✅ CONTRIBUTING.md guidelines
- ✅ SECURITY.md policy
- ✅ CODE_OF_CONDUCT.md
- ✅ GitHub Actions workflow (
.github/workflows/ci.yml) - ✅ Repository topics for discoverability
- ✅ Security features enabled
- ✅ Initial v1.0.0 release
- Clone and test: Clone the repository and test the installation
- Add collaborators: Invite team members if this is a shared project
- Set up CI/CD: Configure any additional automation
- Documentation: Add any organization-specific setup instructions
- Share: Share the repository URL with your team
After setup, your repository will be available at:
- HTTPS:
https://github.com/Tranzact/sysops.aws.securitygroup.git - SSH:
git@github.com:Tranzact/sysops.aws.securitygroup.git - Web:
https://github.com/Tranzact/sysops.aws.securitygroup
This repository will be created under the Tranzact organization.
# Check GitHub CLI authentication
gh auth status
# Login if needed
gh auth login# Set up Git user (if not already done)
git config --global user.name "Your Name"
git config --global user.email "your.email@example.com"If you get an error that the repository already exists, either:
- Choose a different name, or
- Delete the existing repository and try again
Note: Remember to keep your AWS credentials secure and never commit them to the repository!