1 Answer
- Newest
- Most votes
- Most comments
1
I believe the root cause is a typo in ZoneId. According to utility documentation formats is based on DateTimeFormatter which uses TZDB IDs for TimeZones. According to this it should be either Asia/Calcutta
or Asia/Kolkata
. You can find a helpful list of time zones here
answered 2 years ago
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 16 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thanks for the answer, but I get following error.
can't serialize value (/createpayInfo/date) : Unable to serialize
2022-03-28 12:34:59+0530
as a valid DateTime Object.Changing the type from AWSDateTime to String fixed the issue. Seems other time zone value is not accepted when value is inserted in dynamodb.