You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
CreationDate in the console is the same value you would get if you did aws s3 ls --region us-east-1 while the CreationDate you get in any other region is the last modified date.
Expected Behavior
Return a consistent Creation Date
Steps to Reproduce
aws s3 ls --region us-east-1 aws s3 ls --region us-east-2
Possible Solution
No response
Provider and CloudQuery version
all
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
CreationDate in the console is the same value you would get if you did
aws s3 ls --region us-east-1
while the CreationDate you get in any other region is the last modified date.Expected Behavior
Return a consistent Creation Date
Steps to Reproduce
aws s3 ls --region us-east-1
aws s3 ls --region us-east-2
Possible Solution
No response
Provider and CloudQuery version
all
Additional Context
No response
The text was updated successfully, but these errors were encountered: