Creation of aws_pinpointsmsvoicev2_phone_number fails with timeout

[IMKnysh]

Terraform and AWS Provider Version

Terraform v1.12.1
on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v5.100.0
+ provider registry.terraform.io/hashicorp/null v3.2.4
+ provider registry.terraform.io/hashicorp/tls v4.1.0

Affected Resource(s) or Data Source(s)

• aws_pinpointsmsvoicev2_phone_number

Expected Behavior

The new phone number should be requested

Actual Behavior

Terraform fails when applying changes. It is waiting for the phone number status to become "ACTIVE", but it can take up to 10 DAYS. Can the logic be modified to create the resource successfully when the status is "PENDING"?

Relevant Error/Panic Output

Error: waiting for End User Messaging SMS Phone Number (phone-xxxxxxxxxxxx) create
│
│   with aws_pinpointsmsvoicev2_phone_number.appointment_reminder[0],
│   on end-user-messaging.tf line 2, in resource "aws_pinpointsmsvoicev2_phone_number" "appointment_reminder":
│    2: resource "aws_pinpointsmsvoicev2_phone_number" "appointment_reminder" {
│
│ timeout while waiting for state to become 'ACTIVE' (last state: 'PENDING', timeout: 5m0s)

Sample Terraform Configuration

Click to expand configuration

resource "aws_sns_topic" "user_updates" {
  name = "user-updates-topic"
}
resource "aws_pinpointsmsvoicev2_opt_out_list" "example" {
  name = "example-opt-out-list"
}
resource "aws_pinpointsmsvoicev2_phone_number" "messaging_service" {
  iso_country_code = "US"
  message_type     = "TRANSACTIONAL"
  number_type      = "TEN_DLC"

  number_capabilities = [
    "SMS",
    "VOICE"
  ]
  deletion_protection_enabled = true
  opt_out_list_name = aws_pinpointsmsvoicev2_opt_out_list.example.name
  registration_id = var.registration_id_appt_reminder
  self_managed_opt_outs_enabled = true
  two_way_channel_arn = data.aws_sns_topic.user_updates.arn
  two_way_channel_enabled = true
}

Steps to Reproduce

1. Apply the configuration

Debug Logging

Click to expand log output

GenAI / LLM Assisted Development

n/a

Important Facts and References

No response

Would you like to implement a fix?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue 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.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.

[sanyamk23]

Hey, it looks like the main issue is that when you create an aws_pinpointsmsvoicev2_phone_number resource, Terraform waits for the phone number status to become "ACTIVE"—but in reality, it can remain "PENDING" for days, causing Terraform to timeout and fail the apply. This is understandably frustrating since the resource creation is technically successful, but Terraform doesn’t recognize it as complete.

Possible Approach:
One potential improvement would be to adjust the provider logic so that resource creation is considered successful when the status is "PENDING", not just "ACTIVE". This would let the apply finish, and you could track the transition to "ACTIVE" separately. Alternatively, making the timeout configurable (which is supported for many Terraform resources) could help, but it doesn’t solve the root problem if "PENDING" is an acceptable intermediate state.

If you’re open to it, I’d be happy to look into a provider enhancement or open a feature request to support this more gracefully. Or, if you’re already working on a workaround, let me know and I can help test or review.

Just let me know how you’d like to proceed!

[IMKnysh]

@sanyamk23 It would be great if you could work on the provider enhancement. I don't see any other options except adjusting the provider logic so that resource creation is considered successful when the status is "PENDING", not just "ACTIVE".

Thank you.

[sanyamk23]

Hi @IMKnysh ! Thanks so much for trusting me with this. I’m currently tied up with some other priority tasks, so I won’t be able to work on this at the moment. But I appreciate you thinking of me, and I’m happy to help or support in other ways if needed. Please feel free to reach out anytime!