security group will not delete
security-group-delete-dependency-planSend the network interfaces that carry a security group and the groups whose rules reference it. Identifies the owner of every dependent object (Bedrock AgentCore, Lambda, VPC endpoints, load balancers, EKS, ECS, RDS, EFS and more), which ones you can delete now, which need the owning service to release them, and which AWS holds for hours. Returns the ordered commands and how to keep Terraform or CloudFormation from failing meanwhile. Use when the error reads: DependencyViolation: resource sg- has a dependent object | aws_security_group: Still destroying... for many minutes | Security group deletion fails in a stack delete. Covers: Works from supplied describe-network-interfaces and describe-security-groups output for one group in one Region. Does not call AWS and does not inspect peered VPCs in other accounts. Price: 4.00 USDC on Base via x402, charged only when the case is solved.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"security_group_id": "<security_group_id>",
"network_interfaces": "<network_interfaces>"
},
"name": "security-group-delete-dependency-plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | ||
| group_name | No | ||
| security_group_id | Yes | ||
| network_interfaces | Yes | NetworkInterfaces from: aws ec2 describe-network-interfaces --filters Name=group-id,Values=SG_ID | |
| referencing_groups | No | SecurityGroups from both: aws ec2 describe-security-groups --filters Name=ip-permission.group-id,Values=SG_ID and the same with Name=egress.ip-permission.group-id |