EC2 copy_image default description in copied snapshot description has timestamp redendered as human readable number

[mrgum]

Describe the bug

when using EC2.copy_image I get a snapshot with the description

Copied for DestinationAmi ami-123123123123123 from SourceAmi ami-321321321321 for SourceSnapshot snap-0123456789. Task created on 1,736,863,352,510.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Copied for DestinationAmi ami-123123123123123 from SourceAmi ami-321321321321 for SourceSnapshot snap-0123456789. Task created on 2025-01-14T14:02:32Z

Current Behavior

time is printed as human readable int rather than converted from thousandths of seconds

Reproduction Steps

ec2target.copy_image(
Name=image.name,
SourceRegion=account['region'],
SourceImageId=image.id
)

Possible Solution

No response

Additional Information/Context

No response

SDK version used

1.35.82

Environment details (OS name and version, etc.)

macos 15.2

[RyanFitzSimmonsAK]

Hi @mrgum, thanks for reaching out. I was able to reproduce this behavior, but I think this behavior is intended. In my testing, making a copy of an AMI using the console produces the same snapshot description format.

Copied for DestinationAmi ami-0379e87527e5cb7e2 from SourceAmi ami-001523bb054963747 for SourceSnapshot snap-0632a49390d7c976a. Task created on 1,738,179,414,651.

Given that Boto3 matches the console behavior, I'm not sure this is a bug. Could you elaborate on your use case and why you think this is a bug?

[mrgum]

Hi @RyanFitzSimmonsAK

Perhaps this is not a bug with boto3 but rather a bug somewhere else that both boto3 and the console use. would that be the sdk or should I file a aws support ticket?

Its a bug as rendering a epoch based timestamp in that format is not machine or human readable and not how timestamps are rendered elsewhere in resource descriptions