This message was deleted.

So you have a few options here (I’m working on a plan for “proper” adoption at the moment, also): 1.

get

resources to populate their attributes. This can be done by ID:

const vpc = aws.ec2.Vpc.get("my-vpc", id, {})

2. Use a data source - all of the Terraform data sources are mapped as functions with a

get

prefix:

const publicHostedZoneId = (await aws.route53.getZone({           name: baseDomain,
})).id;

that first example is exactly what i was looking for

If you are just getting something by ID, 1 is better.

i just could not find it in the docs - likely passed it over

Did you say you need to look things up by Tag value though?

ideally, ya - that would make it dynamic

Yeah - so for those you can use the data source method:

const amiId = (await aws.getAmi({
        owners: ["self"],
        mostRecent: true,
        filters: [{
            name: "name",
            values: ["some-ami-*"],
        }],
    })).id;

so can I just replace

Ami

with any other resource type?

So AMI is a weird case, and I think it might be mapped poorly (cc @white-balloon-205) - it really should be

aws.ec2.getAmi

) - most get functions are in the module for their namespace

ah ok, i scrolled past the modules section

No worries - let me know if you’re still stuck following this