Contents

---
page_title: "Providers - Getting Started"
sidebar_current: "gettingstarted-providers"
---

# Providers

In this getting started guide, your project was always backed with
[VirtualBox](http://www.virtualbox.org). But Vagrant can work with
a wide variety of backend providers, such as [VMware Fusion](/v2/vmware-fusion/index.html),
[AWS](http://github.com/mitchellh/vagrant-aws), and more. Read the page
of each provider for more information on how to set them up.

Once you have a provider installed, you don't need to make any modifications
to your Vagrantfile, just `vagrant up` with the proper provider and
Vagrant will do the rest:

```
$ vagrant up --provider=vmware_fusion
...
```

Ready to move that to the cloud? Take it to AWS:

```
$ vagrant up --provider=aws
...
```

Once you run `vagrant up` with another provider, every other Vagrant
command doesn't need to be told what provider to use. Vagrant can automatically
figure it out. So when you're ready to SSH or destroy or anything else,
just run the commands like normal, such as `vagrant destroy`. No extra
flags necessary.

For more information on providers, read the full documentation on
[providers](/v2/providers/index.html).

Version data entries

5 entries across 5 versions & 2 rubygems

Version	Path
tamtam-vagrant-reload-1.1.3	vendor/cache/vagrant-0ac2a8738841/website/docs/source/v2/getting-started/providers.html.md
tamtam-vagrant-reload-1.1.2	vendor/cache/vagrant-0ac2a8738841/website/docs/source/v2/getting-started/providers.html.md
tamtam-vagrant-reload-1.1.1	vendor/cache/vagrant-0ac2a8738841/website/docs/source/v2/getting-started/providers.html.md
tamtam-vagrant-reload-1.1	vendor/cache/vagrant-0ac2a8738841/website/docs/source/v2/getting-started/providers.html.md
tnargav-1.3.3	website/docs/source/v2/getting-started/providers.html.md