By using AWS re:Post, you agree to the Terms of Use

Can't install any packages on Amazon Linux 2 instance


I have launched an ec2(Amazon Linux 2) but I am not able to install any packages. Below errors and instructions, I am getting every time. The image is attached.Enter image description here

One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=<repoid> ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>
        subscription-manager repos --disable=<repoid>

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
asked 11 days ago29 views
1 Answers

Hi rePost-User-5598008, could you update your post with more network information?

From the first couple lines we can see your server received a time out in port 443.

Is your instance connected to the internet? If not, do you mind trying AWS Knowledge Center - EC2 Update YUM without internet ?

Have you checked the Security Groups rules for this specific instance?

Can you reach any other endpoint?

  • telnet 443 (should show Connected)
  • telnet 443( should show Connected)
answered 11 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions