This message was deleted.

Hi @steep-lamp-20408, at the bottom of the page you can find the "output" graph where the available outputs are listed for each of the resources. In your case, if you want to use them as a reference for another resource you have to use the following syntax:

name_of_your_resource.id

Also note that if you want to make a reference to another resource it have to be created already!

Hi @boundless-tomato-68419. Yes, that’s what I did :

vpc.id

However it outputs

None

. Hence my question

Its known only after initialization of the resource. Did you create it already?

Yes the creation is this line :

vpc = ec2.Vpc(resource_name="my-vpc")

But i mean you did pulumi Up and you created the resources right?

well... yeah 🙂

I think that you have to actually export the specific outputs in order to be able to print them on the console. JS:

exports.bucketName = siteBucket.id;

Did you tried it?

I’m just using the print to debug, but I need to use the id of the VPC in another resources. I don’t need it in the console, this is just an example for the debug.

vpc.id

seems to be null whether it’s printed or not.

vpc = ec2.Vpc(resource_name="my-vpc")

But why is it ec2.vpc?

Because it’s the

ec2

from the

pulumi_awsx

package (

from pulumi_awsx import ec2

). Anyway the creation of the VPC is totally working, my point is about getting its

id

afterwards

It should work. You can try using

vpc.vpc.id

if you like: the awsx VPC wraps the aws VPC. They should have the same ID (they do in TS/JS.. maybe not in Python?).

It seems

vpc_id

outputs a promise/output. Maybe I should use that.

The power of awsx is in the extra resources it creates for free: some subnets, an IGW, one NAT per private subnet, and all the route tables and routes you need. I prefer aws myself, but if you don't know all the extra bits you need for general purpose networking, then awsx is great.

I see! Thanks. Not very familiar with AWS devops so didn’t realize all this was necessary 😮

Build the awsx VPC in a test project with the correct public, private and isolated subnets, then look at the graph of resources it produces. Then convert that to your own code, using aws. This is the best option, at least until aws-native is fully featured.