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

You tried not specifiying ids where? In which json?
When you import the resources, all their normal outputs become available in Pulumi. This includes the id. You can use `endpoint.id` in the normal way.

I tried not specifying ids in the `resource.json` file that I fed into `pulumi import -f resource.json` E.g:
```{
  "resources": [
    {
      "type": "aws:sagemaker/endpoint:Endpoint",
      "name": "fake-model"
    },
    {
      "type": "aws:sagemaker/endpointConfiguration:EndpointConfiguration",
      "name": "fake-model"
    },
    {
      "type": "aws:sagemaker/model:Model",
      "name": "fake-model"
    }
  ]
}```
Running that caused the tool to panic: `panic: fatal: An assertion has failed`

Untitled

I also tried using ARNs of those resources as `id` values. The tool didn’t panic but said it couldn’t find those resources.

Yea, thanks for clarifying! Do you know what ids should I use?

Ah, I see, you're using `pulumi import`. In this case, the _name_ field is the name you want to use in Pulumi: it becomes the first parameter to the constructor of the resource. It is not necessarily the same as the name tag or field.

The _id_ field is whatever you use to import the resource, as described near the bottom of each resource's page in the documentation. For endpoints, that's simply the endpoint name.

So the ID isn't the AWS ID or the Pulumi ID, it's the Terraform resource import ID. Pretty confusing...

Aha, I get it now! I updated the json file to use the AWS names for those resources as _ids_, and it stops panicking now.

Thank you so much!