linux - 用户数据未在启动时运行 aws ec2-6ren

linux - 用户数据未在启动时运行 aws ec2

转载作者：太空宇宙更新时间：2023-11-04 11:55:14

我正在尝试启动一个 ec2 linux 实例 (linux 2 ami) 并在用户数据中执行此操作时，我正在尝试安装node js，同时安装git。然后我尝试克隆我的 github 存储库，然后启动节点 js 服务器，所有这些都在用户数据中完成。

我正在尝试在 cloudlog init 文件中到处检查，以找出导致我的用户数据无法正常工作的一些错误。

这是代码。

#!/bin/bash
sudo yum update -y
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.0/install.sh | bash 
. ~/.nvm/nvm.sh
nvm install 4.4.5
sudo yum upgrade
sudo yum install git -y
git clone https://github.com/myname/one_user.git
cd one_user

dnsaddress=$(curl -s http://169.254.169.254/latest/meta-data/public-hostname)
export dns_name=${dnsaddress}
npm install -y
node server.js

以下代码来自云初始化日志文件。

Cloud-init v. 18.2-72.amzn2.0.6 running 'init-local' at Sun, 10 Feb 2019 15:49:35 +0000. Up 4.93 seconds.
Cloud-init v. 18.2-72.amzn2.0.6 running 'init' at Sun, 10 Feb 2019 15:49:38 +0000. Up 7.42 seconds.
ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++
ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+
ci-info: | Device |  Up  |           Address           |      Mask     | Scope  |     Hw-Address    |
ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+
ci-info: |  eth0  | True |          10.0.1.72          | 255.255.255.0 | global | 0e:1f:76:6a:3c:6c |
ci-info: |  eth0  | True | fe80::c1f:76ff:fe6a:3c6c/64 |       .       |  link  | 0e:1f:76:6a:3c:6c |
ci-info: |   lo   | True |          127.0.0.1          |   255.0.0.0   |  host  |         .         |
ci-info: |   lo   | True |           ::1/128           |       .       |  host  |         .         |
ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++
ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
ci-info: | Route |   Destination   | Gateway  |     Genmask     | Interface | Flags |
ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
ci-info: |   0   |     0.0.0.0     | 10.0.1.1 |     0.0.0.0     |    eth0   |   UG  |
ci-info: |   1   |     10.0.1.0    | 0.0.0.0  |  255.255.255.0  |    eth0   |   U   |
ci-info: |   2   | 169.254.169.254 | 0.0.0.0  | 255.255.255.255 |    eth0   |   UH  |
ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
ci-info: +-------+-------------+---------+-----------+-------+
ci-info: | Route | Destination | Gateway | Interface | Flags |
ci-info: +-------+-------------+---------+-----------+-------+
ci-info: |   9   |  fe80::/64  |    ::   |    eth0   |   U   |
ci-info: |   11  |    local    |    ::   |    eth0   |   U   |
ci-info: |   12  |   ff00::/8  |    ::   |    eth0   |   U   |
ci-info: +-------+-------------+---------+-----------+-------+
Cloud-init v. 18.2-72.amzn2.0.6 running 'modules:config' at Sun, 10 Feb 2019 15:49:39 +0000. Up 8.99 seconds.
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Existing lock /var/run/yum.pid: another copy is running as pid 3265.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  31 M RSS (321 MB VSZ)
    Started: Sun Feb 10 15:49:38 2019 - 00:02 ago
    State  : Sleeping, pid: 3265
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  70 M RSS (361 MB VSZ)
    Started: Sun Feb 10 15:49:38 2019 - 00:04 ago
    State  : Running, pid: 3265
 --> 1:openssl-libs-1.0.2k-16.amzn2.0.1.x86_64 from installed removed (updateinfo)
 --> 1:openssl-1.0.2k-16.amzn2.0.1.x86_64 from installed removed (updateinfo)
 --> 1:openssl-libs-1.0.2k-16.amzn2.0.2.x86_64 from amzn2-core removed (updateinfo)
 --> 1:openssl-1.0.2k-16.amzn2.0.2.x86_64 from amzn2-core removed (updateinfo)
1 package(s) needed (+0 related) for security, out of 3 available
Resolving Dependencies
--> Running transaction check
---> Package kernel-tools.x86_64 0:4.14.88-88.76.amzn2 will be updated
---> Package kernel-tools.x86_64 0:4.14.94-89.73.amzn2 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package           Arch        Version                    Repository       Size
================================================================================
Updating:
 kernel-tools      x86_64      4.14.94-89.73.amzn2        amzn2-core      111 k

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 111 k
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : kernel-tools-4.14.94-89.73.amzn2.x86_64                      1/2 
  Cleanup    : kernel-tools-4.14.88-88.76.amzn2.x86_64                      2/2 
  Verifying  : kernel-tools-4.14.94-89.73.amzn2.x86_64                      1/2 
  Verifying  : kernel-tools-4.14.88-88.76.amzn2.x86_64                      2/2 

Updated:
  kernel-tools.x86_64 0:4.14.94-89.73.amzn2                                     

Complete!
Cloud-init v. 18.2-72.amzn2.0.6 running 'modules:final' at Sun, 10 Feb 2019 15:49:47 +0000. Up 16.22 seconds.
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Existing lock /var/run/yum.pid: another copy is running as pid 3324.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  54 M RSS (270 MB VSZ)
    Started: Sun Feb 10 15:49:45 2019 - 00:03 ago
    State  : Running, pid: 3324
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:4.14.94-89.73.amzn2 will be installed
---> Package openssl.x86_64 1:1.0.2k-16.amzn2.0.1 will be updated
---> Package openssl.x86_64 1:1.0.2k-16.amzn2.0.2 will be an update
---> Package openssl-libs.x86_64 1:1.0.2k-16.amzn2.0.1 will be updated
---> Package openssl-libs.x86_64 1:1.0.2k-16.amzn2.0.2 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package           Arch        Version                    Repository       Size
================================================================================
Installing:
 kernel            x86_64      4.14.94-89.73.amzn2        amzn2-core       19 M
Updating:
 openssl           x86_64      1:1.0.2k-16.amzn2.0.2      amzn2-core      496 k
 openssl-libs      x86_64      1:1.0.2k-16.amzn2.0.2      amzn2-core      1.2 M

Transaction Summary
================================================================================
Install  1 Package
Upgrade  2 Packages

Total download size: 21 M
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
--------------------------------------------------------------------------------
Total                                               33 MB/s |  21 MB  00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : 1:openssl-libs-1.0.2k-16.amzn2.0.2.x86_64                    1/5 
  Updating   : 1:openssl-1.0.2k-16.amzn2.0.2.x86_64                         2/5 
  Installing : kernel-4.14.94-89.73.amzn2.x86_64                            3/5 
  Cleanup    : 1:openssl-1.0.2k-16.amzn2.0.1.x86_64                         4/5 
  Cleanup    : 1:openssl-libs-1.0.2k-16.amzn2.0.1.x86_64                    5/5 
  Verifying  : 1:openssl-libs-1.0.2k-16.amzn2.0.2.x86_64                    1/5 
  Verifying  : kernel-4.14.94-89.73.amzn2.x86_64                            2/5 
  Verifying  : 1:openssl-1.0.2k-16.amzn2.0.2.x86_64                         3/5 
  Verifying  : 1:openssl-libs-1.0.2k-16.amzn2.0.1.x86_64                    4/5 
  Verifying  : 1:openssl-1.0.2k-16.amzn2.0.1.x86_64                         5/5 

Installed:
  kernel.x86_64 0:4.14.94-89.73.amzn2                                           

Updated:
  openssl.x86_64 1:1.0.2k-16.amzn2.0.2                                          
  openssl-libs.x86_64 1:1.0.2k-16.amzn2.0.2                                     

Complete!
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10007  100 10007    0     0  10007      0  0:00:01 --:--:--  0:00:01 99079
=> Downloading nvm as script to '/.nvm'

=> Profile not found. Tried  (as defined in $PROFILE), ~/.bashrc, ~/.bash_profile, ~/.zshrc, and ~/.profile.
=> Create one of them and run this script again
=> Create it (touch ) and run this script again
   OR
=> Append the following lines to the correct file yourself:

export NVM_DIR="/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm
=> Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm
/var/lib/cloud/instance/scripts/part-001: line 4: /root/.nvm/nvm.sh: No such file or directory
/var/lib/cloud/instance/scripts/part-001: line 5: nvm: command not found
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Existing lock /var/run/yum.pid: another copy is running as pid 11772.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  52 M RSS (268 MB VSZ)
    Started: Sun Feb 10 15:50:08 2019 - 00:02 ago
    State  : Running, pid: 11772
No packages marked for update
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Resolving Dependencies
--> Running transaction check
---> Package git.x86_64 0:2.17.2-2.amzn2 will be installed
--> Processing Dependency: perl-Git = 2.17.2-2.amzn2 for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: git-core-doc = 2.17.2-2.amzn2 for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: git-core = 2.17.2-2.amzn2 for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: emacs-filesystem >= 25.3 for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: perl(Term::ReadKey) for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: perl(Git::I18N) for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: perl(Git) for package: git-2.17.2-2.amzn2.x86_64
--> Processing Dependency: libsecret-1.so.0()(64bit) for package: git-2.17.2-2.amzn2.x86_64
--> Running transaction check
---> Package emacs-filesystem.noarch 1:25.3-3.amzn2.0.1 will be installed
---> Package git-core.x86_64 0:2.17.2-2.amzn2 will be installed
---> Package git-core-doc.noarch 0:2.17.2-2.amzn2 will be installed
---> Package libsecret.x86_64 0:0.18.5-2.amzn2.0.2 will be installed
---> Package perl-Git.noarch 0:2.17.2-2.amzn2 will be installed
--> Processing Dependency: perl(Error) for package: perl-Git-2.17.2-2.amzn2.noarch
---> Package perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2 will be installed
--> Running transaction check
---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package              Arch       Version                   Repository      Size
================================================================================
Installing:
 git                  x86_64     2.17.2-2.amzn2            amzn2-core     217 k
Installing for dependencies:
 emacs-filesystem     noarch     1:25.3-3.amzn2.0.1        amzn2-core      64 k
 git-core             x86_64     2.17.2-2.amzn2            amzn2-core     4.0 M
 git-core-doc         noarch     2.17.2-2.amzn2            amzn2-core     2.3 M
 libsecret            x86_64     0.18.5-2.amzn2.0.2        amzn2-core     153 k
 perl-Error           noarch     1:0.17020-2.amzn2         amzn2-core      32 k
 perl-Git             noarch     2.17.2-2.amzn2            amzn2-core      70 k
 perl-TermReadKey     x86_64     2.30-20.amzn2.0.2         amzn2-core      31 k

Transaction Summary
================================================================================
Install  1 Package (+7 Dependent packages)

Total download size: 6.8 M
Installed size: 36 M
Downloading packages:
--------------------------------------------------------------------------------
Total                                               18 MB/s | 6.8 MB  00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : git-core-2.17.2-2.amzn2.x86_64                               1/8 
  Installing : git-core-doc-2.17.2-2.amzn2.noarch                           2/8 
  Installing : libsecret-0.18.5-2.amzn2.0.2.x86_64                          3/8 
  Installing : 1:perl-Error-0.17020-2.amzn2.noarch                          4/8 
  Installing : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                    5/8 
  Installing : 1:emacs-filesystem-25.3-3.amzn2.0.1.noarch                   6/8 
  Installing : perl-Git-2.17.2-2.amzn2.noarch                               7/8 
  Installing : git-2.17.2-2.amzn2.x86_64                                    8/8 
  Verifying  : 1:emacs-filesystem-25.3-3.amzn2.0.1.noarch                   1/8 
  Verifying  : perl-TermReadKey-2.30-20.amzn2.0.2.x86_64                    2/8 
  Verifying  : 1:perl-Error-0.17020-2.amzn2.noarch                          3/8 
  Verifying  : libsecret-0.18.5-2.amzn2.0.2.x86_64                          4/8 
  Verifying  : git-core-2.17.2-2.amzn2.x86_64                               5/8 
  Verifying  : git-2.17.2-2.amzn2.x86_64                                    6/8 
  Verifying  : perl-Git-2.17.2-2.amzn2.noarch                               7/8 
  Verifying  : git-core-doc-2.17.2-2.amzn2.noarch                           8/8 

Installed:
  git.x86_64 0:2.17.2-2.amzn2                                                   

Dependency Installed:
  emacs-filesystem.noarch 1:25.3-3.amzn2.0.1                                    
  git-core.x86_64 0:2.17.2-2.amzn2                                              
  git-core-doc.noarch 0:2.17.2-2.amzn2                                          
  libsecret.x86_64 0:0.18.5-2.amzn2.0.2                                         
  perl-Error.noarch 1:0.17020-2.amzn2                                           
  perl-Git.noarch 0:2.17.2-2.amzn2                                              
  perl-TermReadKey.x86_64 0:2.30-20.amzn2.0.2                                   

Complete!
Cloning into 'zero2architect'...
/var/lib/cloud/instance/scripts/part-001: line 16: npm: command not found
/var/lib/cloud/instance/scripts/part-001: line 17: node: command not found
Feb 10 15:50:16 cloud-init[3314]: util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-001 [127]
Feb 10 15:50:16 cloud-init[3314]: cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
Feb 10 15:50:16 cloud-init[3314]: util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python2.7/site-packages/cloudinit/config/cc_scripts_user.pyc'>) failed
Cloud-init v. 18.2-72.amzn2.0.6 finished at Sun, 10 Feb 2019 15:50:16 +0000. Datasource DataSourceEc2.  Up 45.55 seconds

最佳答案

您检查过您的 SG 和 NACL 配置了吗？您需要在出站 SG 规则中允许端口 80 (HTTP) 和端口 443 (HTTPS) - 目标 0.0.0.0/0。您还需要允许相同的出站 NACL 规则和入站规则的临时端口。确保您的实例位于公共(public)子网中(带有到 IGW 的路由)并且它附加了公共(public)/弹性 IPv4。

如果不满足这些条件中的任何一个，您的用户数据凭证将失败，因为它需要连接到互联网(在您的情况下)。

如果您的实例位于私有(private)子网中，请确保您正在运行 NAT 网关或 NAT 实例，并且您的路由表以及 SG 和 NACL 已正确配置。如果您正在使用 NAT 实例，还要确保在 NAT 实例上禁用源/目标检查。

更新

您的日志清楚地表明您没有安装 npm 和 node，因此您还需要将安装指令传递给脚本。

npm install -y

不是安装 npm 的正确方法。您可以按照以下步骤安装 node 和 npm。

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.0/install.sh | bash

. ~/.nvm/nvm.sh

nvm install 4.4.5

这将安装节点版本 4.4.5。如果您想安装其他版本的节点，请更改任何支持版本的编号。

关于linux - 用户数据未在启动时运行 aws ec2，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/54607205/

文章推荐： sql - 如何在 shell 脚本中验证更新或选择查询？

文章推荐： c++ - Blitz++:用随机数填充数组

文章推荐： c++ - 奇怪的未处理异常；访问违规阅读位置

文章推荐： linux - "sys_open"文件时正确的权限是什么？

amazon-ecs - AWS ECS(容器服务)虽然连接了 ECS 代理，但没有启动容器
尽管我的 EC2 实例(带有针对 ECS 优化的 AIM)正在运行 ecs 代理，但容器并未在我的 EC2 中启动。为了确认 ecs-agent 正在我的 EC2 实例上运行，我检查了: ecs 日志
amazon-ecs - ECS 任务的动态端口映射
我想在一个任务定义中使用客户端和服务器在 aws ecs 中运行套接字程序。当我使用 awsvpc 网络模式并每次连接到本地主机上的服务器时，我都可以运行它。这很好，所以我不需要知道服务器的 IP 地
amazon-ecs - 如何在没有负载均衡器的情况下访问 ECS 服务？
我有一个在 AWS ECS 上运行的 Docker 容器。我不想要负载均衡器，因为容器是用来处理 websocket 连接的。 https://aws.amazon.com/getting-start
amazon-web-services - 带有 `aws ecs run-task` 后跟 `aws ecs execute-command` 的 Amazon ECS 的 Docker 镜像中的交互式 shell
我想在我的 AWS ECS/Fargate 集群上的公共(public) Docker 镜像中启动交互式 shell，以便从集群内部运行网络/连接测试。似乎官方的方法是使用 aws ecs run-
amazon-ecs - 如何调试 ECS Fargate 服务由于弹性负载均衡器运行状况检查不正常而偶尔重启任务
我在 ECS Fargate 上托管了一个 Shiny 的应用程序。它运行得相当好，但偶尔在使用该应用程序时它会崩溃。我在事件选项卡中将其追溯到以下内容: service YYYY has start
amazon-ecs - 如何在 AWS ECS 容量提供程序中计算目标容量百分比
在 AWS ECS 中创建容量提供程序时。我们正在填充的值 Target capacity %，在超过这个值后我们的集群缩小，但我很好奇当前集群的这个值是如何计算的，如果我想检查当前的是什么集群的值(
amazon-ecs - 如何在 AWS ECS 容量提供程序中计算目标容量百分比
在 AWS ECS 中创建容量提供程序时。我们正在填充的值 Target capacity %，在超过这个值后我们的集群缩小，但我很好奇当前集群的这个值是如何计算的，如果我想检查当前的是什么集群的值(
amazon-ecs - 管道永远不会通过代码管道完成部署 AWS ECS Fargate 任务
我在 AWS 上设置了具有多个目标组和应用程序负载均衡器的 Fargate ecs 服务。它按预期运行。然后我尝试使用本教程设置管道 https://docs.aws.amazon.com/Amaz
amazon-ecs - 如何确定每个日期的 ECS 服务的 Cloudwatch 日志流
我有一个运行任务的 ECS 集群服务，可以使用 AWS 控制台查看其 Cloudwatch 日志流。如何为 awslogs-stream-prefix 设置日期，因为我想按日期识别日志流。 "c
amazon-ecs - 如何在 CodePipeline 中处理 ECS 部署以更改任务定义
我正在使用两个容器部署 ECS Fargate 任务:1 个反向代理 nginx 和 1 个 python 服务器。对于每个我有一个 ECR 存储库，我有一个 CI/CD CodePipeline 设
amazon-ecs - 在 ECS 部署中更新 Docker 镜像
我在 AWS ECS 上部署了一个 CloudFormation 堆栈，比如 teststack , 通过命令 aws cloudformation deploy --template-file ./
amazon-ecs - 使用 AWS ECS Fargate 进行水平和垂直自动扩展
我这里有一些具体的用例。我需要自动扩展在 ECS Fargate 上运行的分布式 Web 应用程序。问题是所有节点都需要在内存中保留相同的数据(因此增加节点数量无助于内存压力)。因此，只有在水平(添加
amazon-ecs - AWS ECS 任务内存和 CPU 分配
我正在寻找有关为 ECS 任务分配内存的指南。我正在为希望在服务器成本上尽可能便宜的客户运行 Rails 应用程序。我正在查看具有 2 个 CPU 和 4 GB 内存的中等服务器大小。大多数情况下，
docker - ECS Fargate 部署卡住，无法部署 ECS 服务
我是 ECS 新手，我正在尝试使用 Cloudformation 部署它。我通过查看文档以及从博客和一些文章中找到的一些示例来制作以下 cloudformation 模板。但是，由于某种原因，它在
amazon-ecs - 如何在基于 Python 的 ECS 任务中读取环境变量
也许这很愚蠢，但如果我创建一个 ECS 任务定义(例如参见 https://aws.amazon.com/blogs/compute/better-together-amazon-ecs-and-aw
amazon-ecs - memoryReservation 在带有 Fargate 的 ECS 上实际上做了什么？
ECS 的容器定义允许您指定 memoryReservation对于每个容器: The soft limit (in MiB) of memory to reserve for the contain
amazon-ecs - 无法将弹性 IP 地址关联到我的 AWS ECS 实例
我在 ca-central 区域创建了一个 AWS ECS 实例。它与每次更新服务时都会更改的动态公共(public) ip 一起使用。到目前为止一切都很好。由于需要一个公网静态IP，所以我在同一区
amazon-ecs - ECS TaskDefinition 创建失败，错误为 "Invalid containerPort'“
Invalid 'containerPort' setting for container 'prerenderContainer'.(Service: AmazonECS; Status Code:
amazon-web-services - 使用 ECS 容量提供程序和使用 ECS 集群中自动伸缩组的自动伸缩有什么区别？
如果我在 ECS 服务级别进行自动扩展，我看不到使用容量提供程序扩展 ECS 集群的意义: https://docs.aws.amazon.com/AmazonECS/latest/developer
amazon-ecs - 使用 ECS 进行 Prometheus DNS 服务发现
关闭。这个问题不符合 Stack Overflow guidelines 。它目前不接受答案。想改进这个问题？更新问题，使其成为 Stack Overflow 的 on-topic。 1年前关闭。

太空宇宙

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

linux - 用户数据未在启动时运行 aws ec2