Add permissions to EC2 to describe running Fargates #532
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.
🗣 Description
Add permissions to describe Fargate asks to the EC2 instance.
💭 Motivation and context
The EC2 is the control center that launches the SQS and Fargate scan process. With scans that require limited API access (limited number of running containers), we need to make sure there aren't any existing containers for each scan so we don't go past the limit of concurrent containers per scan.
With these permissions we can check before launching.
🧪 Testing
Passes terraform plan nad formatting.
✅ Pre-approval checklist
in code comments.
to reflect the changes in this PR.
✅ Pre-merge checklist
✅ Post-merge checklist