Is it a bad idea to create a large amount of AWS EC2 instances for automated integration tests with Vagrant?

I've created an automated integration test that uses Vagrant to create an environment with MySQL database, runs my application under test, asserts the database, and finally destroys the Vagrant box. I want to have it run automatically when somebody commits code so I want to create a Jenkins job. The problem is we don't have a dedicated machine for running Vagrant. One of the options that I was suggested is to use AWS. So I finally got "vagrant up --provider=aws" to work. It created an instance but I started to think that we'll have large amount of integration tests constantly creating and destroying EC2 instances. Question: is it a bad idea to create and destroy constantly new instances of EC2?