Geek Answers Handbook

The tramp continues to try to use the AWS plugin. How to stop?

I'm just trying to create a vagrant up standard Ubuntu image for the first time. My company has already installed Vagrant on my laptop and installed some plugins for AWS. When I try to run vagrant up on my personal Ubuntu image with a separate Vagrantfile, I get the following error:

 There are errors in the configuration of this machine. Please fix the following errors and try again: AWS Provider: * An access key ID must be specified via "access_key_id" * A secret access key is required via "secret_access_key" * An AMI must be configured via "ami" (region: #{region})

I am not trying to connect to AWS. I'm just trying to set up my first personal image on my laptop.

+6
source share
2 answers
  • Make sure VirtualBox is actually installed. I witnessed this error message today, and it happened because I have the vagrant-aws plugin installed, but not VirtualBox. Installing VirtualBox was all that was needed to fix the problem.

  • If for some reason this still fails, and then for the OP comment above , try using the vagrant up --provider :

     vagrant up --provider virtualbox
+2
source

By default, Vagrant will go through all config.vm.provider and select the first service provider, so you must add virtualbox before aws :

  config.vm.provider "virtualbox" do |v| v.customize ['modifyvm', :id, '--natdnshostresolver1', 'on'] v.memory = 4096 v.cpus = 2 end

or select another provider manually, either using --provider , as already mentioned, or the VAGRANT_DEFAULT_PROVIDER variable:

 VAGRANT_DEFAULT_PROVIDER=virtualbox vagrant up

or use config.vm.provider without configuration to set the order in your Vagrantfile, for example:

 Vagrant.configure("2") do |config| # ... other config up here # Prefer VirtualBox Fusion before VirtualBox config.vm.provider "virtualbox" config.vm.provider "aws" end

See: Provider’s primary use on vagrantup.com

If you need to use the AWS provider, these errors mean that you need to configure the correct credentials using the aws configure command, so ~/.aws/credentials can be created with your aws_access_key_id and aws_secret_access_key . To configure AMI, check the README plugin file (basically you need to add aws.ami to your stray file).

0
source

More articles:


All Articles