aws-nuke | Nuke a whole AWS account and delete all its resources | AWS library

I was able to look at the source of the error, which is shown the error on aws-nuke code line 100.

From there I would look at the calls to ValidateAccount(). The relevant call is on line 43.

Once narrowing down the issue and error message, I would figure out why the Account.Aliases() is empty. It looks like "Account" is a resource type in AWS. So I would reproduce the call to fetch the account resource, e.g. using boto3 or the AWS CLI. Then I'd confirm that it's also empty there. Then I'd figure out how to set the alias

I have used aws-nuke to manage my AWS organization accounts. You can definitely use cross-account roles for the task assuming that you already can run aws-nuke on your resources in your AWS account. What you can do inside your AWS account, you can do with cross-account roles except for a handful of AWS actions. The only issue will be the AWS cross-organization role will have to be too much permission and that is risky. AWS-nuke documentation says, such tool for AWS-nuke is very risky and destructive!

Linking AWS accounts via AWS Organization allows you to consolidate billing, use Service Control Policies, etc. It doesn't actually give any more capability than what you can do with Cross-Account Roles. You still would need to use those as SCP actually doesn't give you permission that IAM doesn't give you. So to answer your question, would you be able to do it with AWS Organizations?

Yes, if you use cross-account AWS role.

Would you be able to do it with other non-members too?

Yes, with cross-account roles. I am emphasizing cross-account roles here and reiterating, whatever you can do inside your AWS account, you can do with cross-account roles except for a handful of actions. That's my 2 cents would be just to use cross-account roles.

To fix the first issue try moving zsh-syntax-highlighting to the very end of plugins. From zsh-syntax-highlighting FAQ:

Why must zsh-syntax-highlighting.zsh be sourced at the end of the .zshrc file?

zsh-syntax-highlighting.zsh wraps ZLE widgets. It must be sourced after all custom widgets have been created (i.e., after all zle -N calls and after running compinit). Widgets created later will work, but will not update the syntax highlighting.

To fix the second issue add the following at the end of ~/.zshrc: