[Bug]: Failures in C2S regions when creating Step Functions due to UnsupportedOperation calling ListStateMachineVersions

[thefirstofthe300]

Terraform Core Version

1.5.7

AWS Provider Version

5.61.0

Affected Resource(s)

• aws_sfn_state_machine

Expected Behavior

Step Function should have successfully been created in C2S region

Actual Behavior

Provider fails due to unhandled UnsupportedOperation error

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

Any minimal step function declaration using a provider configured to use the us-iso-east-1 region.

Steps to Reproduce

terraform apply

Debug Output

UnsupportedOperationThe functionality you requested is not available in this region.3bdcfe2bca424df6850515e5df83ba06

Panic Output

No response

Important Factoids

We are using an emulation layer on top of a public AWS region to determine what works in C2S regions: https://www.applied-insight.com/

References

No response

Would you like to implement a fix?

No

[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.

[thefirstofthe300]

Would be part of here: #18593

[justinretzolk]

Hey @thefirstofthe300 👋 Thank you for taking the time to raise this! I left a comment on your other issue, but wanted to link it here given that the question I asked there is relevant here as well. This comment is intended mainly to make the link for anyone else who may stumble across this 🙂.

[thefirstofthe300]

Regarding your question as to whether the error occurs in the actual C2S region, my response regarding validation in an actual C2S region stands.

I do not have any documentation that suggests that this particular API endpoint doesn't exist in the C2S region so I have no idea if the issue here is poor documentation or an actual issue. We do pay a significant sum for the emulation product so I would not be surprised if they have the ability to validate whether certain endpoints exist or not, either through documentation my team doesn't have access to or through access to an actual C2S region.

[thefirstofthe300]

Looks like this was caused by an actual bug in our emulation provider.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.