diff --git a/tests/destroy-aws.sh b/tests/destroy-aws.sh
index baf4dc2..93ae457 100755
--- a/tests/destroy-aws.sh
+++ b/tests/destroy-aws.sh
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
-
+AWS_NUKE_VERSION=v3.29.5
 # reference: https://github.com/GlueOps/scripts-teardown-aws-amazon-web-services
 echo "Preform an AWS Cleanup with AWS Nuke"
-wget https://github.com/rebuy-de/aws-nuke/releases/download/v2.25.0/aws-nuke-v2.25.0-linux-amd64.tar.gz && tar -xvf aws-nuke-v2.25.0-linux-amd64.tar.gz && rm aws-nuke-v2.25.0-linux-amd64.tar.gz && mv aws-nuke-v2.25.0-linux-amd64 aws-nuke
-./aws-nuke -c aws-nuke.yaml --no-dry-run --force
+wget https://github.com/ekristen/aws-nuke/releases/download/$AWS_NUKE_VERSION/aws-nuke-$AWS_NUKE_VERSION-linux-amd64.tar.gz && tar -xvf aws-nuke-$AWS_NUKE_VERSION-linux-amd64.tar.gz && rm aws-nuke-$AWS_NUKE_VERSION-linux-amd64.tar.gz
+./aws-nuke nuke -c nuke.yaml --max-wait-retries 200 --no-dry-run --force --log-full-timestamp true
diff --git a/tests/aws-nuke.yaml b/tests/nuke.yaml
similarity index 98%
rename from tests/aws-nuke.yaml
rename to tests/nuke.yaml
index 39ae750..0bbfaf0 100644
--- a/tests/aws-nuke.yaml
+++ b/tests/nuke.yaml
@@ -1,4 +1,4 @@
-account-blocklist:
+blocklist:
 - "0123456789" # Keep listing any accounts you want to ensure do NOT get touched. If you did this properly and are using IAM credentials that only have access to your sub account then this is less important and could be left with this default/invalid value
 
 accounts: