AndrewGuenther/fck-nat

AMI unavailable from ap-east-1

Opened this issue · 5 comments

dantetwc commented

Hi, Thanks for the great work!
I found the AMI is not available in some regions, i.e. ap-east-1.
Do you have any plans on making it to more regions?

Thanks.

AndrewGuenther commented

ap-east-1 is actually the only region fck-nat is not in because I have API calls to copy the AMI there consistently fail and I've been unable to track down why.

I've been waiting to see if anyone noticed so I guess I have a reason to track it down now. 😅

  • 👍2
RaJiska commented

Tried deploying directly in ap-east-1 region and worked for me. The only thing was that I needed to enable the region which was disabled by default.

AndrewGuenther commented

I have ap-east-1 enabled. Packer replicates AMIs via a copy call which consistently times out for me. So I guess if I did a separate dedicated Packer build directly in ap-east-1 it might fix this?

RaJiska commented

Ah right. Indeed, just directly building in ap-east-1 worked on my end ye.

AndrewGuenther commented

@dantetwc I've copied fck-nat 1.3 to ap-east-1. I'm leaving this open since I had to do it manually and would like to get it automated starting with 1.4, but 1.3 is available now.

  • 👍1