ran into a situation when parsing timestamps for events that the year gets appended to timestamps if they were created in the previous year i.e. if the timestamp has 2023 but the current year is 2024 then 2024 gets appended and then the parse fails. you can also end up adding a year to a timestamp that was created last year which ends up throwing off calculated events times considerably. it would probably make sense to pull the year when the ec2 instance was requested / created early in the process and use this value to check / add the year value.
ran into a situation when parsing timestamps for events that the year gets appended to timestamps if they were created in the previous year i.e. if the timestamp has 2023 but the current year is 2024 then 2024 gets appended and then the parse fails. you can also end up adding a year to a timestamp that was created last year which ends up throwing off calculated events times considerably. it would probably make sense to pull the year when the ec2 instance was requested / created early in the process and use this value to check / add the year value.