I can only get the value (Azure subscription Id) by sending output to Output. It also instruments the DOM to record the HTML and CSS on the page, recreating pixel-perfect videos of even the most complex single-page and mobile apps. In this case, were just interested in the name of the bucket. Setting up complex infrastructure manually is definitely more prone to errors. Simple deform modifier is deforming my object. This is right. Adding this for anyone that comes looking. Earlier, I mentioned that your resources need to be shared across stacks. Thanks. Pulumi will use the latter property to establish how to run our program. I would recommend using the same name you're providing to your API Gateway resource as the name for your Log Group. Say you're writing an sqs queue and a dlq for it, you may initially write something like this: The issue we see here is that the json lib errors out stating type Output cannot be parsed. Furthermore, if the infrastructure is not managed carefully, we might have drifts. It shows the ID for each resource and tells us whether the resource will be created, updated, or deleted. In my experience, Infrastructure as Code is worth a try. Lastly, it displays a list of outputs and a final recap of how many resources are to be created, deleted, or updated. Pulumi C# Unable to convert Output