{section: Running Jobs}
+To run on your new resources, a job's submit file must contain the following line:
+
+{verbatim}
++MayUseAWS = TRUE
+{endverbatim}
+
+The new resources do _not_ share a file system with the head node, so you'll need to use file transfer:
+
+{verbatim}
+should_transfer_files = TRUE
+{endverbatim}
+
{section: Cleaning Up}
+
+{subsection: The Cloud Resources}
+
+One of the benefits of using =condor_annex= is that it will automatically terminate instances after a certain amount of time (24 hours in the example above). This happens even if the instance is running a job at the time, to make sure that misbehaving jobs don't cause you to spend more than you intended. Additionally, if at any time it's been too long (15 minutes by default) since an instance ran a job, it will shut itself down to save you money. However, if you'd like to shut down the instances early, you can do so using the =condor_off= command, replacing =MyFirstAnnex= with the name of the annex you'd like to shut down:
+
+{term}
+$ condor_off -annex MyFirstAnnex
+{endterm}
+
+{subsection: The Head Node}
+
+As noted above, you'll need to clean the head node up yourself. If you don't want to keep any of your changes, then you should "terminate" the head node to avoid paying for storage. If you just want to save money and pick up where you left off a bit later, you should instead "stop" the head node; you'll pay to keep its disk around until you start it again later. Both options are under "Instance State" if you right-click on the instance in the EC2 console.
