AWS AMI Images for new region (Mexico Central)

Rocky Linux Help & Support
1

Hi Rocky Linux team,

Quick heads-up: in AWS region mx-central-1 (Mexico Central), the official Rocky Linux 9 AMI for aarch64 is available, but the x86_64 variant isn’t showing up in the Marketplace or public AMI list.

It feels odd to have ARM ready but not x86_64. Since mx-central-1 fully supports EC2, having the x86_64 image would really help avoid manual copying from other regions and streamline deployments for teams that rely on Intel/AMD instances.

Is it possible to publish the official x86_64 Rocky Linux 9 AMI in mx-central-1 soon? Parity between architectures there would be awesome.

Thanks!

2

That’s strange, I must have missed it!

Will take a look right away.

3

I’ve submitted the request to update the Marketplace image regions. For some reason, despite using the “Enable future regions” setting, sometimes that doesn’t always happen.

I also went and published the AMIs in EC2–there was a setting on the region to block public AMIs. I’ve filed a ticket to address this deficiency.

Thanks again for the report.

4

Thank you, Neil. Looking forward to using it in my region!

5

Huh. I’m not able to see mx regions at all. @neil is that something I need to be configure my AWS account to be able to see?

$ aws ec2 describe-regions --output json | jq -r '.Regions[].RegionName' | sort   
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-north-1
eu-west-1
eu-west-2
eu-west-3
me-central-1
me-south-1
sa-east-1
us-east-1
us-east-2
us-west-1
us-west-2
6

Hello!

Yes, you have to manually activate the region on AWS Console > Account > Regions

~ $ aws ec2 describe-regions --output json | jq -r ‘.Regions.RegionName’ | sort
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-north-1
eu-west-1
eu-west-2
eu-west-3
mx-central-1
sa-east-1
us-east-1
us-east-2
us-west-1
us-west-2

SCR-20250626-hwzz
SCR-20250626-hwzz1962×402 34 KB

7

Yep. We can probably just setup a read-only token in our AMI account for this, if you want? Throw a ticket in and I’ll make some credentials available in Bitwarden