AWS Macie Compression Ratio

[AnmolBhatt]

Description

Hi Team,

Is it possible to set a compression ratio for a macie service scheduling job via terraform script?

Awaiting for your response

Thanks & Regards,
Anmol Bhatt

References

No response

Would you like to implement a fix?

No response

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[bschaatsbergen]

Hi @AnmolBhatt,

I was trying to make sense of the issue you've raised here, please help me out.

If I understand correctly; Macie assumes a 3:1 Compression Ratio and I can't find if we can change this assumption from Macie.

Source: https://docs.aws.amazon.com/macie/latest/user/discovery-jobs-costs.html

By default, Macie assumes the following when it calculates cost estimates for a job:

All compressed and archive files use a 3:1 compression ratio.
All the extracted files use a supported file or storage format.

If you're able to set the compression ration anywhere in the UI, please let me know how exactly, I can't seem to find it in the API docs nor in the UI.

[AnmolBhatt]

Hi bschaatsbergen,
My question is is it possible to set compression ratio using terraform script?
As per documentation, no argument mentioned regarding the compression ratio using terraform script.

With UI we can set the compression ratio. But with terraform, do we have the option?

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!