You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
/Users/rpkad744~/scripts -> aws-nuke -c nuke-config.yaml --profile aws-nuke-example
Error: failed get caller identity: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
The text was updated successfully, but these errors were encountered:
It couldn't find valid authentication credentials. You've specified a profile, you need to make sure the profile exists and the aws configuration on your systems is set properly.
Should this issue persist, please open an issue here.
Please see a copy of the notice from the README about the deprecation of this project. Sven was kind enough to grant me access to help triage and close issues and pull requests that have already been addressed in the actively maintained fork. Some additional information is located in the welcome issue for more information.
Caution
This repository for aws-nuke is no longer being actively maintained. We recommend users to switch to the actively maintained fork of this project at ekristen/aws-nuke.
We appreciate all the support and contributions we've received throughout the life of this project. We believe that the fork will continue to provide the functionality and support that you have come to expect from aws-nuke.
Please note that this deprecation means we will not be addressing issues, accepting pull requests, or making future releases from this repository.
Thank you for your understanding and support.
Failed to run on the Mac OS. Below is the error.
/Users/rpkad744~/scripts -> aws-nuke -c nuke-config.yaml --profile aws-nuke-example
Error: failed get caller identity: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
The text was updated successfully, but these errors were encountered: