Thanks another question. if aws is bot traffic can the admin exclude this going forward? I do not have admin or tagging access but before I advise on this would like to inform my team on the same.
Yes.. though it depends on how the traffic registers... you can add custom Bot Rules to your report suite... but depending on that data, the indicators may not exist to use the rules available...
However, one of the tricks I use to get rid of issues when say a bad release goes out and causes double (or more) tracking (i.e. a few years ago there was a release that caused an infinite reload for anyone on an iPad - oops), but I created a virtual suite called "{suite name} (Clean Data)" and I used a segment to try and remove to the best of my ability issues where we have over-counted data.... I had to transition all my reports over to use the "Clean" suite... but IF the AWS traffic can't be removed as a bot, you can certainly create a segment to exclude it, and use a Virtual Report Suite applying that new exclusion rule.