Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error after 'vagrant up' #11504

Closed
prsly opened this issue Apr 9, 2020 · 2 comments
Closed

Error after 'vagrant up' #11504

prsly opened this issue Apr 9, 2020 · 2 comments

Comments

@prsly
Copy link

prsly commented Apr 9, 2020

Vagrant version

Vagrant 2.2.7

Host operating system

Mac OS Catalina 10.15.4

Guest operating system

Ubuntu on AWS

Vagrantfile

require 'vagrant-aws'
Vagrant.configure('2') do |config|
    config.vm.box = 'dummy'
    config.vm.provider 'aws' do |aws, override|
    aws.access_key_id = "xyz"
    aws.secret_access_key = "zyx"
    aws.keypair_name = 'devops-key-pair-euwest2'
    aws.instance_type = "t2.micro"
    aws.region = 'eu-west-2'
    aws.ami = 'ami-0175365'
    aws.security_groups = ['default']
    override.ssh.username = 'ubuntu'
    override.ssh.private_key_path = '~/.ssh/devops-key-pair-euwest2.pem'
  end
end

Debug output

https://gist.github.com/prsly/f79a65372b8279011390c7bc64f9eb66

Expected behavior

Connect to AWS

Actual behavior

Nothing

Steps to reproduce

  1. vagrant up --provide=aws
@soapy1
Copy link
Contributor

soapy1 commented Apr 9, 2020

Hey there, this seems to be an issue with the vagrant-aws plugin. The issue is already reported there mitchellh/vagrant-aws#566 including some workarounds

@soapy1 soapy1 closed this as completed Apr 9, 2020
@ghost
Copy link

ghost commented May 10, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants