No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

What would be the equivalent of this in Pulumi?

```aws lambda add-permission   --function-name "arn:aws:lambda:&lt;region&gt;:&lt;account&gt;:function:graphql:${stageVariables.GRAPHQL_ALIAS}"   --source-arn "arn:aws:execute-api:&lt;region&gt;:&lt;account&gt;:&lt;resource&gt;/*/POST/graphql"   --principal <http://apigateway.amazonaws.com|apigateway.amazonaws.com>   --statement-id &lt;statement_id&gt;   --action lambda:InvokeFunction```
Got this from the AWS console (Api Gateway) for adding the lambda with the `${stageVariables}` in it.

I wonder if the “\” is escaping the “$” and so the variable is not being evaluated

Yeah, but is intentional, so to get the `stageVariables` out of the stage.

Like from here: <https://docs.aws.amazon.com/apigateway/latest/developerguide/amazon-api-gateway-using-stage-variables.html>

I tried a couple of quick things and both of these appear to work - they keep the “${stageVariables.GRAPHQL_ALIAS}” in tact in the output.
(Not tested by actually passing to lambda.)
```export const goo = pulumi.concat("arn:aws:lambda:",aws.config.region,"blah blah ${stageVariables.GRAPHQL_ALIAS}:",bucket.id)
export const foo = pulumi.interpolate `arn:aws:lambda:${aws.config.region} blah blah \$\{stageVariables.GRAPHQL_ALIAS\}:${bucket.id}````
`

So with interpolate I added a couple more escapes

Ok, so instead of

`:\${stageVariables.GRAPHQL_ALIAS}`
Do it like this?
`:\$\{stageVariables.GRAPHQL_ALIAS\}`

I think I might have express myself badly.

The error is not from escaping, but when trying to deploy `Permission` for the lambda with the alias as the `stageVariables`, it fails due to
`"function_name" doesn't comply with restrictions`.

Maybe I’m using the wrong resource to do it..

<@U01BSQWRZFA> thanks for responding. I figured it out. Error on my end. Mixed permissions (per alias) with the actual lambda call definition.