Your options are 1) to fix AWS first; that will stop refresh from noticing the difference; 2) to not fix AWS at all, run refresh then up, so that Pulumi fixes AWS for you.

The refresh+up option is great when it works, but I find that it often changes values that aren't in your code (that is, puts AWS defaults into state), so now code and state are different. When you run up, changes will happen that effectively do nothing (essentially removing defaults from state). Usually this is fine, but sometimes this causes unwanted updates or delete-replaces. Which can be very bad if it's in RDS, Aurora, Directory Services, etc. So be attentive to the preview before running up!

refresh

maps something-in-AWS-with-ID-X to something-in-state-with-ID-X.

But you've got something-in-state-with-ID-X and something-in-AWS-with-ID-Y

You need to use the

import

opt to tell Pulumi that AWS ID Y is the same as Pulumi ID X.

(Whoops, typo back a few lines, fixed it, would have mislead you if you read it before)

ok since i had the resource IDs defined as options in the code, this is how i fixed it: 1.

pulumi refresh

(and allow the resources to be removed from the state) 2.

pulumi up

which caused the imports to succeed They do indeed have new IDs now.