1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
Are the access key and secret access key you are using activated?
If it is not activated, I believe an error will occur.
You must make sure you are using the correct access key and secret access key.
In some cases, it may be easier to reissue and set up access keys.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- Comment gérer les adresses IP statiques sur mes instances Lightsail à l'aide des commandes AWS CLI ?AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 5 ans
As I mentioned, I was able to run the CLI commands on the Jenkins server. Why would it work if it wasn't activated?
Is it possible that someone has accidentally disabled it?
Is it possible to share all the commands you are running? Am I correct in my understanding that it was originally running on the pipeline? Also, have you set up the credentials correctly for the OS user running the jenkins pipeline? Also, will it work if I embed the access key and secret access key in the pipeline configuration without setting them in "~/.aws"? https://plugins.jenkins.io/aws-credentials/
@Riku_Kobayashi They are iam related list commands. Yes, it was running and stopped working. I will try and let you know. Thanks.
I tried adding AWS credentials via Manage Credentials. It throws, AWS was not able to validate the provided access credentials.
Another point to check is to see if the server's time synchronization is out of sync. https://stackoverflow.com/questions/27685288/aws-was-not-able-to-validate-the-provided-access-credentials https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html
It is also possible that a server restart may correct the problem.