aws-nuke
aws-nuke copied to clipboard
rebuy-de
Resource deletion says failed with Adminstrator permission when performing aws-nuke
all resources say "failed" when performing aws-nuke. Please see attached and Please advise.
Hello @Leectan. The actual error messages are located at the end of the aws-nuke output. Those failed resource also might recover. Please show us the end of the output.
Hello @Leectan. Sorry for the late response. It looks like you provided invalid access keys.
@svenwltr double checked access keys without any issue. 2nd time performed with all the failed message.
@Leectan
Are you able to use the credentials you are providing directly in the aws-cli? Are you using MFA? Do you use assumed roles?
This could potentially help you resolve the problem: https://stackoverflow.com/questions/34582318/how-can-i-resolve-the-error-the-security-token-included-in-the-request-is-inval
@bjoernhaeuser yes, I'm using --access-keys and --secret-key perimeters and inject them directly in the CLI. The account doesn't have MFA. Not using assumed roles.
@bjoernhaeuser yes, I'm using --access-keys and --secret-key perimeters and inject them directly in the CLI. The account doesn't have MFA. Not using assumed roles.
Still getting error with Admin permission, no MFA. No assumed roles. Any other suggestion is appreciated.
Well, as already said this is highly likely a problem in your configuration. Can you check that the account ids match when you execute aws sts get-caller-identity with the same access/secret key please?
also, IAM user and IAM profile that are specified in the config file for filter is also removed when execute the cmd.
@Leectan Can you please check if this command works for your?
AWS_ACCESS_KEY_ID=YOUR_ID AWS_SECRET_ACCESS_KEY=YOUR_SECRET aws iam list-roles
Please replace access key id and secret access key with the same credentials you used for aws-nuke
I am having a similar issue. When I ran the dry-run with the IAM account with admin privilege it listed everything as expected. When I ran the actual nuke I got the failed message many times even though I'm using the same credentials.
Maybe AWS is rate limiting?
@Leectan @rbeede are you able to run aws-nuke? I am having the same issue.
