aws_acm_certificate with subject_alternative_names not maintaining order

[giridharmp]

I am creating an AWS ACM certificate with the below terraform code:

resource "aws_acm_certificate" "alb_certificate" {
domain_name = "${var.subdomain}"
validation_method = "DNS"

subject_alternative_names = ["api.example.com","kib.example.com","gra.example.com","pro.example.com","proapp.example.com","prom.example.com","promfro.example.com","dash.example.com","pgad.example.com"]
}

When we used to look into the issued certificate, in the additional names section, the above order in subject_alternative_names used to be maintained. But suddenly when we tried recently, the order is not being maintained and the names are getting used randomly. Because of this, when we refresh or want to update any other resource, a new certificate is always getting issued.

But the terraform plan is showing as below:
aws_acm_certificate.alb_certificate: Creating...
arn: "" => ""
domain_name: "" => "np"
domain_validation_options.#: "" => ""
subject_alternative_names.#: "" => "9"
subject_alternative_names.0: "" => "api.example.com"
subject_alternative_names.1: "" => "kib.example.com"
subject_alternative_names.2: "" => "gra.example.com"
subject_alternative_names.3: "" => "pro.example.com"
subject_alternative_names.4: "" => "proapp.example.com"
subject_alternative_names.5: "" => "prom.example.com"
subject_alternative_names.6: "" => "promfro.example.com"
subject_alternative_names.7: "" => "dash.example.com"
subject_alternative_names.8: "" => "pgad.example.com"
validation_emails.#: "" => ""
validation_method: "" => "DNS"

but the order in "Additional names" in the certificate is as follows:
promfro.example.com,
api.example.com,
prom.example.com,
proapp.example.com,
pro.example.com,
kib.example.com,
dash.example.com,
gra.example.com,
pgad.example.com

The order in which the subject alternative names are mentioned need to be maintained.

[tdmalone]

Duplicates #8531 & #8570

[nywilken]

@giridharmp thanks for opening this issue, and sorry you are running into trouble here. This is a duplicate of #8531 so I am going to close this issue and ask that any new comments be tracked on the existing thread. If you haven't already done so please upvote #8531

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!