Is the AMI ID retained after the copy from account A to account B ?

[nitrocode]

Hi @martinbaillie . Thank you so much for creating this post processor. I found this while looking for post processors that could copy AMIs to a list of accounts and copy the tags of those AMIs to the accounts. And an extra benefit is encryption!

• When the AMIs are copied to the other accounts, are the AMI IDs different from the original account or are the same AMI IDs retained?
  • I'm guessing yes because it's a copy of an AMI.
• Are there additional packer IAM permissions to get this to work ? Does the user/role that runs the packer job require certain IAM permissions or role assumption for the other accounts ?
  • Edit: Nevermind, I see this other issue that mentions it Which AWS permissions do I need to give to make the copy and tagging work. #6 (comment)

[vishalbasra]

In my experience the AMI ID changes in that you have two ami's in the destination account

==> amazon-ebs.windows-base-image (ami-copy): [us-east-1] Copying ami-<id-generated-by-packer> to account <accountid> (encrypted: false)
==> amazon-ebs.windows-base-image (ami-copy): Going to wait for image to be in available state
==> amazon-ebs.windows-base-image (ami-copy): Waiting one minute (1/30) for AMI to become available, current state: pending for image ami-0b8cc040176c68a2b on account 504055967630
==> amazon-ebs.windows-base-image (ami-copy): Waiting one minute (2/30) for AMI to become available, current state: pending for image ami-0b8cc040176c68a2b on account 504055967630
==> amazon-ebs.windows-base-image (ami-copy): Waiting one minute (3/30) for AMI to become available, current state: pending for image ami-0b8cc040176c68a2b on account 504055967630
==> amazon-ebs.windows-base-image (ami-copy): Waiting one minute (4/30) for AMI to become available, current state: pending for image ami-0b8cc040176c68a2b on account 504055967630
==> amazon-ebs.windows-base-image (ami-copy): Waiting one minute (5/30) for AMI to become available, current state: pending for image ami-0b8cc040176c68a2b on account 504055967630
==> amazon-ebs.windows-base-image (ami-copy): [us-east-1] Finished copying ami-<id-generated-by-packer> to <accountid> (copied id: ami-<new-id>)

In that the original AMI generated is copied over to the destination account with the same id but without tags, this image has the source account listed as the owner. This happens in packer now when you use https://www.packer.io/docs/builders/amazon/ebs#ami_users and the snapshot modification attribute.
Then there is the image the plugin creates with the tags denoted by ami-<new-id> which has the source as the destination account itself.
So you essentially get two AMIs in the destination accounts specified by target account id