After running AWS Nuke multiple times, it's still not removing any of my EC2 instances S3 buckets and CFn Stacks

[amith1108]

./aws-nuke-v2.15.0-linux-amd64 -c config.yml --access-key-id xxxxxxxxxxxxxxxxxx --secret-access-key xxxxxxxxxxxl --no-dry-run

I'm using the above command to nuke my entire AWS account, but all i see is failed in front of the above services.

Below is my Config.yml file:

`regions:

• global
• us-east-1
• us-east-2
• us-west-1
• ap-south-1
• ap-southeast-1
• ap-southeast-2

account-blocklist:

• "999999999999" # production

accounts: "665977444369": # aws-nuke-example filters: IAMUser: - "aws-nuke" IAMUserPolicyAttachment: - "aws-nuke -> AdministratorAccess" IAMUserAccessKey: - "aws-nuke -> xxxxxxxx"`

What am i missing here?

After running the nuke i can still all the resources intact, The first time i ran this tool it deleted a couple of Users

Some of my Ec2 instances in us-east-1 got deleted after i specified the regions explicitly at the top.

But even after mentioning ap-south-1 I can still see Ec2 instances running there.

[jrdufresne]

can you provide the output after running the command?

[oll-gregtasonis]

This is a known issue with regard to EC2 and VPC's and they'll need to be cleaned up manually/scripting AFAIK. Dependencies aren't always deleted in the right order.

[svenwltr]

This issue is not known to us, but we cannot tell more without having any output.

[neolace]

I have run into the same issue, I think it's because of auto-scaling that's set up.