Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support CUR 2.0 #750

Open
iakov-aws opened this issue Mar 7, 2024 · 5 comments
Open

Support CUR 2.0 #750

iakov-aws opened this issue Mar 7, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@iakov-aws
Copy link
Collaborator

Please upvote
@iakov-aws iakov-aws added the enhancement New feature or request label Mar 7, 2024
@jinman
Copy link

jinman commented Mar 26, 2024

+100 We need this. How can we implement this? or let us know what we need to do to make this work?

@gasmick
Copy link

gasmick commented Apr 15, 2024

if I understood correctly, legacy CURs are going to be deprecated by June 1

@c-a-m-a-c
Copy link

if I understood correctly, legacy CURs are going to be deprecated by June 1

Can you disclose the source?

@iakov-aws
Copy link
Collaborator Author

iakov-aws commented Apr 19, 2024 •
edited

From AWS side we do not have any news for the timeline or any plan of deprecation of Legacy CUR. And if there will be any date, it will be communicated way in advance.

@c-a-m-a-c
Copy link

Please upvote

The power of AWS Data Exports is - besides the fixed schema - the customization capability of its SQL query. This way one could e.g. properly exclude SPP credits from an export by not adding them in the first place. Desperately needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jinman @c-a-m-a-c @gasmick @iakov-aws