Assume role for lambda fails at first try

[viveklak]

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

As discussed in #139 - initial apply of the specified example fails with:

operation CREATE failed with "InvalidRequest": The role defined for the function cannot be assumed by Lambda. (Service: Lambda, Status Code: 400, Request ID: 78882e88-526d-49d5-a3d6-a383ce69b074, Extended Request ID: null).

This seems like an eventual consistency issue with cloudcontrol API? Similar issue filed in TF: hashicorp/terraform-provider-awscc#221

Steps to reproduce

Run example in https://github.com/pulumi/pulumi-aws-native/tree/master/examples/aws-native-ts-stepfunctions

Expected: Success
Actual:
On first run:

operation CREATE failed with "InvalidRequest": The role defined for the function cannot be assumed by Lambda. (Service: Lambda, Status Code: 400, Request ID: 78882e88-526d-49d5-a3d6-a383ce69b074, Extended Request ID: null).

Subsequent updates succeed.