Reduce number of regions where the image can be shared

[mjasion]

Unfortunately we hit the quota limit, while images are not used.

Build 'amazon-ebs.source' errored after 14 minutes 35 seconds: Error modify AMI attributes: ResourceLimitExceeded: You have reached your quota of 5 for the number of public images allowed in this Region. Deregister unused public images or make them private, or request an increase in your public AMIs quota.
	status code: 400, request id: 9dbc1f11-c4e4-41bc-b395-c545b84fa21b

==> Wait completed after 14 minutes 35 seconds

==> Some builds didn't complete successfully and had errors:
--> amazon-ebs.source: Error modify AMI attributes: ResourceLimitExceeded: You have reached your quota of 5 for the number of public images allowed in this Region. Deregister unused public images or make them private, or request an increase in your public AMIs quota.
	status code: 400, request id: 9dbc1f11-c4e4-41bc-b395-c545b84fa21b

[0x2b3bfa0]

That error you're getting is about the number of images per region, not about the number of regions.

It's because we're creating a new image for every release, and image names are always different (contain the release date).

Either ask AWS to increase the limit for us, or delete old images, or don't name them with the version/date?

[mjasion]

@0x2b3bfa0

Hmm, we might start naming them same (studio-selfhosted). In the Description there is a date as I see on the screen:

The reason to add unique name to ami image was, that the unregistered AMI was hard to find on calls with Customer. And this is how EKS provide images.

Now my proposed solution involves removing the force_delete_snapshot and deregistering the AMI. This could potentially resolve the issue ¹.

Footnotes

1. I cannot find in the documentation how to fix the issue ↩

[mjasion]

Either ask AWS to increase the limit for us,

Limits are per region, and for each there was a new ticket needed :/