0

我在Windows 10上,並使用vagrant-aws(https://github.com/mitchellh/vagrant-aws)來避開和亞馬遜實例,並獲得以下錯誤。我也列出了我的流浪文件。vagrant-aws:AWS無法驗證所提供的訪問憑據

此外,有人報告這可能是由時間造成的。我在Windows 10上同步了系統時間,但仍然沒有運氣!

$ vagrant up --provider=aws 
Bringing machine 'default' up with 'aws' provider... 
C:/Users/jacky/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:98: warning: duplicated key at line 100 ignored: :associate_public_ip 
==> default: Warning! The AWS provider doesn't support any of the Vagrant 
==> default: high-level network configurations (`config.vm.network`). They 
==> default: will be silently ignored. 
==> default: Launching an instance with the following settings... 
==> default: -- Type: m3.medium 
==> default: -- AMI: ami-42116522 
==> default: -- Region: us-west-1 
==> default: -- Keypair: 2016_05_14_keypair 
==> default: -- Block Device Mapping: [] 
==> default: -- Terminate On Shutdown: false 
==> default: -- Monitoring: false 
==> default: -- EBS optimized: false 
==> default: -- Source Destination check: 
==> default: -- Assigning a public IP address in a VPC: false 
==> default: -- VPC tenancy specification: default 
There was an error talking to AWS. The error message is shown 
below: 

AuthFailure => AWS was not able to validate the provided access credentials 

Vagrang文件:

Vagrant.configure("2") do |config| 
    config.vm.box = "dummy" 

    config.vm.provider :aws do |aws, override| 
    aws.access_key_id = "..." 
    aws.secret_access_key = "..." 
    aws.session_token = "..." 
    aws.keypair_name = "2016_05_14_keypair" 

    aws.ami = "ami-42116522" 
    aws.region = "us-west-1" 
    #aws.instance_type = "t2.small" 
    override.ssh.username = "ubuntu" 
    override.ssh.private_key_path = "C:/2016_05_14_keypair.pem" 
    end 
end 
+0

我已經通過憑證進行雙重檢查,並且所有這些都是正確的。 – user1187968

+0

你是如何生成session_token的? –

+0

aws sts get-session-token --duration-seconds 129600 – user1187968

回答

2

我知道這可能有點晚了你。我遇到了與您的流浪病毒文件相同的問題,我通過刪除「aws.session_token =」行來解決它。

相關問題