-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More compute resources #6
Comments
Added SQS Queue Policies. In this case boto3 return a non default response like other resources.. maybe it's a legacy version.. |
ASGs launches EC2 instances every time that scale-out process occurs and if in "ASG Groups" a custom vpc was selected than existent check (EC2 INSTANCES) will catch that instances and alert... I know that there may be some situations where the desired capacity is zero and there may not be instances launched by ASG, but the "ASG Group" will contain the custom vpc and it would be interesting to inform. But maybe there is duplicate information, what do you think about this point? |
Added MSK cluster.. |
I think it's desirable to list the ASGs, even those with Right now I got a list of EC2 instances but majority of them are created as a part of an ASG. It would be good to have a reference to that somewhere as well. |
Added EC2 check.. |
Added ASG check. |
Everything done... Closing issue. |
It would be good to list:
The text was updated successfully, but these errors were encountered: