AWS CodeArtifact doesn’t support RPM. Have your TAM +1 the PFR for RPM support. Then all those AWS customers running AL2 or RHEL 8 can use a secure, local-to-the-VPC mirror.
So, let's say you set up an EL7 system with stock everything, and then enable epel with dnf install epel-release or equivalent.
You now get the stock epel mirror listing, not a custom package Amazon rewrote, and they'd need to add a custom mirror that provides an override for that package to make it work that way.
So I would _guess_ one or more large companies migrated a bunch of things onto cloud hosted EL7-based system after EOL meant god help you finding new hardware support.
(I would also guess either EPEL doesn't have a mirror on Amazon or it should have auto-picked it, or the auto-picker is bad, and either way, Amazon will probably go "oh our bad", since I believe they host local mirrors of things anyway...)
Comments
I wonder why Amazon did not create their own mirror. They would sync with Fedora mirrors once. All aws traffic can then go to their own mirrors.
Isn't that sensible thing to do?
AWS CodeArtifact doesn’t support RPM. Have your TAM +1 the PFR for RPM support. Then all those AWS customers running AL2 or RHEL 8 can use a secure, local-to-the-VPC mirror.
So, let's say you set up an EL7 system with stock everything, and then enable epel with dnf install epel-release or equivalent.
You now get the stock epel mirror listing, not a custom package Amazon rewrote, and they'd need to add a custom mirror that provides an override for that package to make it work that way.
So I would _guess_ one or more large companies migrated a bunch of things onto cloud hosted EL7-based system after EOL meant god help you finding new hardware support.
(I would also guess either EPEL doesn't have a mirror on Amazon or it should have auto-picked it, or the auto-picker is bad, and either way, Amazon will probably go "oh our bad", since I believe they host local mirrors of things anyway...)