search

AndrewGuenther / fck-nat

Feasible cost konfigurable NAT: An AWS NAT Instance AMI
https://fck-nat.dev
MIT License
1.02k stars 40 forks source link

Change snapshot on AMI to public? #82

Open eric-freewill opened 1 month ago

eric-freewill commented 1 month ago

What are your thoughts on changing the snapshot on the AMI to be public? Being cautious, I like the idea of having a copy of your AMI just in case I need to fall back on it to spin up a new NAT instance due to some issue with your AWS account and it becomes temporarily unavailable. I'm unable to copy it since the snapshot isn't public and I understand if you want to prevent simple copies of the AMI.

"You do not have permission to access the storage of this ami"

AndrewGuenther commented 1 month ago

This is super reasonable. I'm traveling at the moment but I'll get this done ASAP.

AndrewGuenther commented 3 weeks ago

@eric-freewill Now that I've had some time to think about this more, is there any issues with copying the AMI into your own account instead? Is there a reason sharing the snapshot is preferable?

The only reason I hesitate is that discoverability on snapshots compared to AMIs is pretty poor, it's hard to make clear what snapshot goes with what AMI, and as far as I know copying there's no particular advantage to copying the snapshot vs copying the AMI?

eric-freewill commented 2 weeks ago

I tried copying the AMI into my own account just for disaster recovery purposes and get an error saying I don't have permission to the volume on the AMI.

Screenshot 2024-06-10 at 7 54 02 AM Screenshot 2024-06-10 at 7 52 16 AM

AndrewGuenther commented 2 weeks ago

Ah, I see. I didn't realize the snapshot had to be public in order for the AMI to copy. That solves my discoverability concerns then. I'll get this done some time this week hopefully.