title: MySQL Timestamps transferred using AWS-DMS seem to be a mixture of GMT and BST
body: <p>I'm using AWS-DMS to copy a local MySQL database into an AWS-RDS MySQL database.
  I am finding the fields that are TIMESTAMP will differ from source to destination, but only for date/times that are in BST (British Summer Time - Daylight Saving Time).
  The source is GMT and the destination is UTC (Checked using <code>select @@system_time_zone , @@time_zone ;</code>)</p>
  <p>So, for example, 2021-11-30 09:47:00 is correctly migrated to 2021-11-30 09:47:00 but
  2021-07-08 <strong>12</strong>:27:15 is migrated to 2021-07-08 <strong>11</strong>:27:15</p>
  <p>I have found details of the DMS setting ServerTimezone that will define what the time zone is for the endpoint. I have added &quot;ServerTimezone&quot;: &quot;GMT&quot; to the source endpoint. I understand that GMT and UTC are the same, but I tried it (no difference).</p>
  <p>My question is, how do I get the timestamp to be copied exactly as stored in the source?
  Is there a ServerTimezone value I can use in the DMS endpoint?</p>
  <p>I can understand that the timestamp stored in the source is actually in GMT + 1 hour (in the summer) and it's migrated as GMT. That would explain the hour difference for the BST timestamps only, BUT doesn't a timestamp get saved in the current timezone, which in this case should be GMT?</p>