I think the issue was by ths following , I managed to resolve this issue by setting "ClockSkew" to the difference between my UTC time and server's UTC time by taking Managing-Device-Time-with-the-AWS-Mobile-SDKs in refference.
it fixes the issue It looks like the code is not handling the fractional difference between days. For example, if the start date is yesterday at 11:59 PM and the end date is today at 12:01 AM, the code will report the difference as 0 days. If you consider that to be a 1 day difference, then the code needs to handle that case. If you are selecting self.date with a date picker, self.date contains the date plus the current local time. At 6 or 7 PM your local time, it's midnight GMT (i.e., tomorrow WRT your local time), which causes the unexpected -1 in your difference calculation.
How to deal with the timezone issue when storing dates in utc using mongod?
hope this fix your issue Behind the scenes, DatePipe uses locale to display date in user's timezone. Try with client's timezone data: 1931-05-31T00:00:00.000-0300 instead of 1931-05-31T00:00:00.000+0000.
I wish this help you The timezone cannot be modified once you select it while creating new RDS for sql server instance. If you want to then you have to create a new instance. Use the 'Select your Time Zone' dropdown in the AWS Management Console to do so while creating a new instance.