com.xerox.amazonws.ec2.EC2Exception

Client error : AWS was not able to validate the provided access credentials

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web24

  • via Atlassian JIRA by Zed Yap [Atlassian], 10 months ago
    Client error : AWS was not able to validate the provided access credentials
  • via Atlassian JIRA by Zed Yap [Atlassian], 1 year ago
    Client error : AWS was not able to validate the provided access credentials
  • via Jenkins JIRA by David Kavanagh, 1 year ago
    Client error : The instance ID 'i-cca241af' does not exist
  • Stack trace

    • com.xerox.amazonws.ec2.EC2Exception: Client error : AWS was not able to validate the provided access credentials at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2006) at com.xerox.amazonws.ec2.Jec2.describeVolumes(Jec2.java:1511) at com.atlassian.aws.ec2.EBSVolumeManagerImpl.run(EBSVolumeManagerImpl.java:67) at com.atlassian.aws.ec2.UpdateSchedulerImpl.run(UpdateSchedulerImpl.java:45) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.