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 ssh: file must exist when I do Vagrant up mastercore --provider=aws #7

Closed
jmoraleses opened this issue Feb 23, 2018 · 3 comments

Comments

@jmoraleses
Copy link

jmoraleses commented Feb 23, 2018

error private_key_path file must exist:
when operating the following command line:
vagrant up mastercore --provider=aws

private_key_path file must exist:

I have installed aws tools and rds tools, I have also created my .pem file in amazon and download it. But I do not know where I should put it, I wrote in LocalVagrantConfig.rb the path (/home/user/key.pem) but the console indicates that file does not exist.

Any suggestions? Something must be wrong.
Thank you

@jmoraleses
Copy link
Author

jmoraleses commented Feb 23, 2018

I have written the EXPORT of setup-omni-private in the console and now I get the following error:

.........

Bringing machine 'mastercore' up with 'aws' provider...
==> mastercore: Warning! The AWS provider doesn't support any of the Vagrant
==> mastercore: high-level network configurations (config.vm.network). They
==> mastercore: will be silently ignored.
==> mastercore: Launching an instance with the following settings...
==> mastercore: -- Type: t2.small
==> mastercore: -- AMI: ami-39501209
==> mastercore: -- Region: us-east-1
==> mastercore: -- Keypair: ***
==> mastercore: -- Security Groups: ["web"]
==> mastercore: -- Block Device Mapping: [{"DeviceName"=>"/dev/sda1", "Ebs.VolumeSize"=>60, "Ebs.DeleteOnTermination"=>false}]
==> mastercore: -- Terminate On Shutdown: false
==> mastercore: -- Monitoring: false
==> mastercore: -- EBS optimized: false
==> mastercore: -- Source Destination check:
==> mastercore: -- Assigning a public IP address in a VPC: false
==> mastercore: -- VPC tenancy specification: default
==> mastercore: Warning! Vagrant might not be able to SSH into the instance.
==> mastercore: Please check your security groups settings.
There was an error talking to AWS. The error message is shown
below:

InvalidParameterValue => Value () for parameter groupId is invalid. The value cannot be empty

..................

Thanks you.

@jmoraleses
Copy link
Author

Vagrant does not connect through ssh to the mastercore.
I have tried everything, but it is not possible for me. I do not understand why.

@msgilligan
Copy link
Member

I'm closing this as an effective duplicate of Issue #10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants