docs(ec2): record the Batch-managed suppression selector evidence ledger - #46
Merged
Merged
Conversation
U15a shipped its selector without the evidence record the contract requires. BATCH-FINDINGS.md states the chosen selector and splits its confidence: verified as an ASG detector, inferential as a Batch detector. It lists the four rejected candidates with the evidence against each, the fail-closed analysis, a four command checklist for validating against a real account, and a claim ledger marking every unverified item no code depends on. Records two open items: the reason code is asg-managed because no documented EC2 tag identifies a Batch instance as Batch, and Batch SPOT compute environments backed by a Spot Fleet rather than an ASG carry no aws:autoscaling:groupName and are still sized today. No production code changed. Co-authored-by: kording <74226694+kording@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
U15a shipped its selector without the evidence record the contract requires.
BATCH-FINDINGS.md states the chosen selector and splits its confidence: verified
as an ASG detector, inferential as a Batch detector. It lists the four rejected
candidates with the evidence against each, the fail-closed analysis, a four
command checklist for validating against a real account, and a claim ledger
marking every unverified item no code depends on.
Records two open items: the reason code is asg-managed because no documented EC2
tag identifies a Batch instance as Batch, and Batch SPOT compute environments
backed by a Spot Fleet rather than an ASG carry no aws:autoscaling:groupName and
are still sized today.
No production code changed.