-
Notifications
You must be signed in to change notification settings - Fork 3
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Trim the child IAM role to the permissions TOPS actually uses
roadmap:nextQueued behind the current milestoneQueued behind the current milestonesecuritySecurity-relevant changeSecurity-relevant changesize/SA day or twoA day or twoStatus: Open.#111 In teemops/tops;teemops_main queue policy grants SQS:ReceiveMessage to Principal: "*"
infrastructureCI, release, deployment, toolingCI, release, deployment, toolingroadmap:nextQueued behind the current milestoneQueued behind the current milestonesecuritySecurity-relevant changeSecurity-relevant changesize/XSUnder a dayUnder a dayStatus: Open.#109 In teemops/tops;- Status: Open.#105 In teemops/tops;
N-11 phase 2 · Scope the SNS topic to this install with a filter secret
roadmap:nowSequenced path to the current milestoneSequenced path to the current milestonesecuritySecurity-relevant changeSecurity-relevant changesize/MAbout a weekAbout a weekStatus: Open.PERF-18 · ec2 makes ~12 sequential API calls per region even when the region is empty
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:nextQueued behind the current milestoneQueued behind the current milestonesize/SA day or twoA day or twoStatus: Open.#94 In teemops/tops;PERF-17 · Batch the SQS dispatch loop
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:laterReal, but waiting on a triggerReal, but waiting on a triggersize/XSUnder a dayUnder a daywaiting-on-triggerDeliberately not started until a condition firesDeliberately not started until a condition firesStatus: Open.#80 In teemops/tops;PERF-16 · Revisit region-pruning defaults
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:laterReal, but waiting on a triggerReal, but waiting on a triggersize/SA day or twoA day or twowaiting-on-triggerDeliberately not started until a condition firesDeliberately not started until a condition firesStatus: Open.#79 In teemops/tops;PERF-15 · Remove dead $scan->region read in RulesEngine::getScanner()
good first issueGood for newcomersGood for newcomersperformanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:laterReal, but waiting on a triggerReal, but waiting on a triggersize/XSUnder a dayUnder a dayStatus: Open.#78 In teemops/tops;PERF-14 · Remove debug logging from the param-evaluation hot path
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:laterReal, but waiting on a triggerReal, but waiting on a triggersize/XSUnder a dayUnder a dayStatus: Open.#77 In teemops/tops;PERF-13 · Memoize AWS client construction
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:laterReal, but waiting on a triggerReal, but waiting on a triggersize/XSUnder a dayUnder a dayStatus: Open.#76 In teemops/tops;PERF-12 · Bulk-insert scan details
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:laterReal, but waiting on a triggerReal, but waiting on a triggersize/XSUnder a dayUnder a dayStatus: Open.#75 In teemops/tops;PERF-11 · Index scan_details (scan_id, service, region)
performanceScan speed, throughput, resource useScan speed, throughput, resource useroadmap:nextQueued behind the current milestoneQueued behind the current milestonesize/XSUnder a dayUnder a dayStatus: Open.#74 In teemops/tops;