AAS is what I've got and I'm working in the field.
The biggest difference between an AAS and a BS is probably the material covered to get your degree. I know I personally didn't formally learn much in the way of coding when going for my AAS, though I did learn quite a bit about Cisco devices and Windows Server management. There are some things that you just must learn on the job, though, no matter whether you get an AAS or a BS. Most schools don't teach a proficiency in using or managing a digital phone system, yet that will often be given to IT/IS as a main responsibility.
If you make connections while going for your AAS, you'll have no problems getting into the field, no matter how friendly or unfriendly your area job market is toward entry level IT.
I am a part of a team of 3 that manages about 160 client PCs at 4 sites , with 14 physical servers that are solely our responsibility (which probably have a total of about 20 Hyper-V guests running between them, though I'm not sure on the exact number) and another 7 physical servers that we assist with managing (4 of which run a total of 14 Hyper-V guests on top of them) that act as automation controllers and are fortunately not solely our responsibility. We are also responsible for maintaining around 60 printers, managing and supporting the digital phone systems at each site (notice that these are not VOIP phones - those would be their own mess), and supporting the 60 or so smart phones on the company plan. That's the major stuff. There's some other stuff, too, but listing all of that would make the list too long.