Change time zone display of run time logs from local time to UTC for ETL pipeline jobs so that they are consistent between Event Bridge, Step Functions, Glue, and Redshift

Is there some kind of way to tell AWS services like Step Functions, Glue, and Redshift to use UTC exclusively, and simply not display local time anywhere? Time zone display in AWS is an indecipherable mess. For example, the run time of Step Functions are displayed in local time, while the Event bridge rules that launch the Step Functions are defined by cron expressions in UTC. Glue schedules are expressed in UTC, but are displayed in local time. Redshift maintenance windows are defined in local time, and displayed in UTC. There seems to be no rhyme or reason to it. This makes scheduling pipeline events maddeningly complex, especially when different services are being coordinated and they require different time zones for setup and display not only between services but within services. It would be so much easier and less error-prone if the user could settle upon one time zone when coordinating events on AWS.