SSE-S3 bucket encryption enabled but "Encryption is not enabled" message still appears

[thesuavehog]

Describe the bug
When the state bucket in S3 has SSE-S3 encryption enabled, the "Encryption is not enabled on the S3 remote state bucket ..." warning message still appears. If the intention is to recommend SSE-KMS (or another type on encryption) then the message should state that. As it is now, it is an inaccurate warning message as my S3 bucket is encrypted.

time=2024-04-22T11:48:02-04:00 level=warning msg=Encryption is not enabled on the S3 remote state bucket ####################. Terraform state files may contain secrets, so we STRONGLY recommend enabling encryption! prefix=[C:\####################]

Note: AWS has set all S3 buckets to have SSE-S3 encryption enabled by default on all new S3 Buckets and you cannot select "no encryption".

To Reproduce
Create an S3 bucket in AWS and use it as the terraform state location.
Run terragrunt (configured to use that bucket for TF state).

Expected behavior
No warning message should be displayed.

Versions

• Terragrunt version: 0.57.5
• Terraform version: v1.6.2
• Environment details (Ubuntu 20.04, Windows 10, etc.): Windows 11, Powershell 7.4.1