Updates test schedule to start at 7:30AM ET, because that's when fred often starts

Also adds script to update existing accounts

bin/aws_scheduler_configure.everywhere.sh

@@ -0,0 +1,21 @@
+#!/bin/bash
+
+echo
+echo Updating GovCloud Accounts\' Schedules
+echo
+for profile in mdr-test-c2-gov mdr-test-malware-gov mdr-test-modelclient-gov
+do
+  echo
+  echo Setting/Updating Schedule for $profile
+  aws_scheduler_configure.sh $profile us-gov-east-1
+done
+
+echo
+echo Updating Commercial Accounts\' Schedules
+echo
+for profile in mdr-test-modelclient mdr-test-c2
+do
+  echo
+  echo Setting/Updating Schedule for $profile
+  aws_scheduler_configure.sh $profile us-east-1
+done

bin/aws_scheduler_configure.sh

@@ -3,12 +3,24 @@ STACK=aws-scheduler
 PROFILE=$1
 REGION=$2
 
+echo
+echo \*\*\* Step 1 of 2: Creating periods and schedules in case they don\'t already exist. Ignore errors.
 scheduler-cli create-period --name "weekdays" --begintime 08:00 --endtime 18:00 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
-scheduler-cli create-period --name "business-hours" --begintime 09:30 --endtime 20:00 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
+scheduler-cli create-period --name "business-hours" --begintime 07:30 --endtime 20:00 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
 scheduler-cli create-period --name "extended" --begintime 08:00 --endtime 23:59 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
 scheduler-cli create-period --name "saturday" --begintime 12:00 --endtime 18:00 --weekdays sat  --stack $STACK --region $REGION --profile-name $PROFILE
 scheduler-cli create-schedule --enforced --name MSOC --periods business-hours --timezone "US/Eastern" --stack $STACK --region $REGION --profile-name $PROFILE
 #scheduler-cli create-schedule --enforced=true --name non-prod --periods weekdays --timezone "US/Eastern" --stack $STACK --region $REGION --profile-name $PROFILE
 #scheduler-cli create-schedule --enforced=true --name non-prod-extended --periods extended --timezone "US/Eastern" --stack $STACK --region $REGION --profile-name $PROFILE
 
+echo
+echo \*\*\* Step 2 of 2:  Updating periods and schedules to our standards
+scheduler-cli update-period --name "weekdays" --begintime 08:00 --endtime 18:00 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
+scheduler-cli update-period --name "business-hours" --begintime 07:30 --endtime 20:00 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
+scheduler-cli update-period --name "extended" --begintime 08:00 --endtime 23:59 --weekdays mon-fri --stack $STACK --region $REGION --profile-name $PROFILE
+scheduler-cli update-period --name "saturday" --begintime 12:00 --endtime 18:00 --weekdays sat  --stack $STACK --region $REGION --profile-name $PROFILE
+scheduler-cli update-schedule --enforced --name MSOC --periods business-hours --timezone "US/Eastern" --stack $STACK --region $REGION --profile-name $PROFILE
+#scheduler-cli update-schedule --enforced=true --name non-prod --periods weekdays --timezone "US/Eastern" --stack $STACK --region $REGION --profile-name $PROFILE
+#scheduler-cli update-schedule --enforced=true --name non-prod-extended --periods extended --timezone "US/Eastern" --stack $STACK --region $REGION --profile-name $PROFILE
+