AWSのEC2にnode.jsがインストールできない

https://qiita.com/naoki_mochizuki/items/814e0979217b1a25aa3e

こちらの記事を見ながら、デプロイ作業中です。
その途中のNode.jsのインストールをする所で、エラーが発生しています。
エラー文は下記の通りです。

Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main                                                                                        | 2.1 kB  00:00:00
amzn-updates                                                                                     | 2.5 kB  00:00:00


 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. Disable the repository, 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>

     4. 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
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again