Amazon Linux 2 yum core repository @ Ohio

Question

Since a couple of weeks ago, a fresh T3.micro instance with Amazon Linux 2 gives error on yum update/install. I've checked that the mirror list only includes one site, S3 based, that gives a permission error on access. Oregon works though. Am I missing something ? What would be the correct channel to report this if I have no support contract ?

TIA, -Carlos

TIA,
-Carlos

A-Shevchenko · Answer

It works fine for me in us-east-2., tried to update and install httpd.
```
$ cat /etc/yum.repos.d/amzn2-core.repo 
[amzn2-core]
name=Amazon Linux 2 core repository
mirrorlist=$awsproto://$amazonlinux.$awsregion.$awsdomain/$releasever/$product/$target/$basearch/mirror.list
priority=10
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-amazon-linux-2
enabled=1
metadata_expire=300
mirrorlist_expire=300
report_instanceid=yes

[amzn2-core-source]
name=Amazon Linux 2 core repository - source packages
mirrorlist=$awsproto://$amazonlinux.$awsregion.$awsdomain/$releasever/$product/$target/SRPMS/mirror.list
priority=10
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-amazon-linux-2
enabled=0
metadata_expire=300
mirrorlist_expire=300
report_instanceid=yes

[amzn2-core-debuginfo]
name=Amazon Linux 2 core repository - debuginfo packages
mirrorlist=$awsproto://$amazonlinux.$awsregion.$awsdomain/$releasever/$product/$target/debuginfo/$basearch/mirror.list
priority=10
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-amazon-linux-2
enabled=0
metadata_expire=300
mirrorlist_expire=300
report_instanceid=yes
```

tron · Answer

This is embarrasing. I had an S3 gateway endpoint at the subnet, and a restrictive policy, most surely from a test demo. 
This compounded with a set of unrelated issues and my failure to "link" a repo access to S3 service created enough confusion in my mind.
Sorry for the noise.

Amazon Linux 2 yum core repository @ Ohio

yum update

Relevant content