主页 / unix / 问题

问题[aws](unix)

Martin Hope
jayvardhan
Asked: 2024-01-30 19:16:28 +0800 CST
  • 5

我正在尝试将 aws cli 的输出保存到日志文件中。它在某种程度上正在发挥作用。问题是，从下面共享的第一个命令执行它将输出保存到文件中，但是当第二个命令运行时，它删除第一个命令的输出并仅附加第二个命令的新输出。

请帮助我将两个命令的输出保存在同一个日志文件中。

#!/bin/sh
#
#set -vx
timestamp=$(date +"%Y-%m-%d-%H-%M-%S")
LOGFILE=/home/ec2-user/POC/restore/my_setup_log_file.$timestamp.log
aws rds restore-db-cluster-from-snapshot --db-cluster-identifier $credit_iden_t --snapshot-identifier $credit_snap_name --engine aurora-mysql --engine-version 5.7.mysql_aurora.2.11.4 --engine-mode serverless --db-subnet-group-name vpc-dbsubnetgroup-1 --vpc-security-group-ids sg-03214e 2> "${LOGFILE}"
aws rds restore-db-cluster-from-snapshot --db-cluster-identifier $task_iden_t --snapshot-identifier $task_snap_name --engine aurora-mysql --engine-version 5.7.mysql_aurora.2.11.4 --engine-mode serverless --db-subnet-group-name vpc-dbsubnetgroup-1 --vpc-security-group-ids sg-03214e 2> "${LOGFILE}"
exit;
aws
Martin Hope
e456ryftcgv
Asked: 2022-04-11 06:46:17 +0800 CST
  • 0

我正在连接到 AWS EC2 实例并启动我的 API。我希望 API 继续运行并接受请求。

那么，tmux 是一个很好的方法吗？或者，还有更好的方法？我的印象是 tmux 和 screen 更适合非常长的任务。不确定它们是否适合无限期地运行 API。

ssh aws
Martin Hope
srijal
Asked: 2022-02-01 23:44:54 +0800 CST
  • 0

/etc/skel 目录包含从 useradd 命令创建时自动复制到新用户的文件和目录。但是，当检查旧的现有用户时，它不包含 /etc/skel 中应该包含的所有文件和目录（在我的情况下为 .ssh 目录）。

  1. 我在 /etc/default/useradd 中取消了 SKEL=/etc/skel 的注释。
  2. 将 .ssh 目录放置在 /etc/skel 但是从现有用户登录时 .ssh 目录没有显示，它适用于新创建的用户。
ssh aws
Martin Hope
Tom Crawford
Asked: 2021-10-29 07:07:18 +0800 CST
  • 0

我尝试按照以下说明进行操作： Can't resize a partition using resize2fs

但似乎没有任何效果。

的输出lsblk是：

[AWS root@archive ~]$ lsblk
NAME                          MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
xvda                          202:0    0   300G  0 disk
├─xvda1                       202:1    0   500M  0 part /boot
├─xvda2                       202:2    0  29.5G  0 part
│ ├─vg_archive-lv_root (dm-0) 253:0    0 147.6G  0 lvm  /
│ └─vg_archive-lv_swap (dm-1) 253:1    0     2G  0 lvm  [SWAP]
├─xvda3                       202:3    0    10G  0 part
│ └─vg_archive-lv_root (dm-0) 253:0    0 147.6G  0 lvm  /
└─xvda4                       202:4    0   110G  0 part
  └─vg_archive-lv_root (dm-0) 253:0    0 147.6G  0 lvm  /

您可以看到 300Gb 可用，但我无法从 150Gb 扩展根卷。非常感谢任何帮助，谢谢。

更新：以为我会添加 linux 发行版，它很旧，可能是问题的一部分...

Linux version 2.6.32-358.18.1.el6.x86_64 ([email protected]) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Wed Aug 28 17:19:38 UTC 2013

根据评论中的要求，这是来自上面链接的建议命令的输出：

[AWS root@archive ~]$ sudo pvs
  PV         VG         Fmt  Attr PSize   PFree
  /dev/xvda2 vg_archive lvm2 a--   29.51g    0
  /dev/xvda3 vg_archive lvm2 a--    9.99g    0
  /dev/xvda4 vg_archive lvm2 a--  110.00g    0
[AWS root@archive ~]$ sudo pvresize /dev/xvda2
  Physical volume "/dev/xvda2" changed
  1 physical volume(s) resized / 0 physical volume(s) not resized
[AWS root@archive ~]$ sudo pvresize /dev/xvda3
  Physical volume "/dev/xvda3" changed
  1 physical volume(s) resized / 0 physical volume(s) not resized
[AWS root@archive ~]$ sudo pvresize /dev/xvda4
  Physical volume "/dev/xvda4" changed
  1 physical volume(s) resized / 0 physical volume(s) not resized
[AWS root@archive ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_archive-lv_root
                      146G  131G  8.0G  95% /
tmpfs                 938M     0  938M   0% /dev/shm
/dev/xvda1            485M   80M  380M  18% /boot
[AWS root@archive ~]$ sudo lvextend -r -l +100%FREE /dev/mapper/vg_archive-lv_root
  Extending logical volume lv_root to 147.56 GiB
  Logical volume lv_root successfully resized
resize2fs 1.41.12 (17-May-2010)
The filesystem is already 38682624 blocks long.  Nothing to do!

[AWS root@archive ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_archive-lv_root
                      146G  131G  8.0G  95% /
tmpfs                 938M     0  938M   0% /dev/shm
/dev/xvda1            485M   80M  380M  18% /boot

更新：从下面的输出看来 fs 类型是 ext4

[AWS root@archive ~]$ df -Th
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/vg_archive-lv_root
              ext4    146G  131G  8.0G  95% /
tmpfs        tmpfs    938M     0  938M   0% /dev/shm
/dev/xvda1    ext4    485M   80M  380M  18% /boot

更新：cfdisk /dev/xvda按要求输出：

                                                         cfdisk (util-linux-ng 2.17.2)

                                                             Disk Drive: /dev/xvda
                                                      Size: 322122547200 bytes, 322.1 GB
                                             Heads: 255   Sectors per Track: 63   Cylinders: 39162

       Name                 Flags                Part Type         FS Type                       [Label]                   Size (MB)
 ---------------------------------------------------------------------------------------------------------------------------------------------
                                                                   Unusable                                                     1.05          *
       xvda1                Boot                  Primary          Linux ext3                                                 524.29          *
       xvda2                                      Primary          Linux LVM                                                31686.92          *
       xvda3                                      Primary          Linux LVM                                                10731.94          *
       xvda4                                      Primary          Linux LVM                                               118115.03
                                                                   Unusable                                                161063.34          *
aws resize2fs
Martin Hope
Santosh Garole
Asked: 2021-10-09 00:09:23 +0800 CST
  • -1

我的提供程序代码init.tf如下：

provider "aws" {
 shared_credentials_file = "~/.aws/credentials"
 region                  = "us-east-1"
}

我使用的 Terraform 版本是：0.11.14

我在执行以下操作时收到如下错误terraform init：

Error installing provider "aws": openpgp: signature made by unknown entity.

Terraform analyses the configuration and state and automatically downloads
plugins for the providers used. However, when attempting to download this
plugin an unexpected error occured.

This may be caused if for some reason Terraform is unable to reach the
plugin repository. The repository may be unreachable if access is blocked
by a firewall.

If automatic installation is not possible or desirable in your environment,
you may alternatively manually install plugins by downloading a suitable
distribution package and placing the plugin's executable file in the
following directory:
    terraform.d/plugins/windows_amd64
aws openpgp
Martin Hope
Nagev
Asked: 2020-02-08 09:43:41 +0800 CST
  • 1

我想加密以破折号开头的客户端密码，但如果我执行以下操作：

aws kms encrypt --region us-east-1 --key-id xxxyyzz --output text --query CiphertextBlob --plaintext -blahblah-

结果是：

usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: argument --plaintext: expected one argument

尝试转义如下：

aws kms encrypt --region us-east-1 --key-id xxxyyzz --output text --query CiphertextBlob --plaintext \-blahblah-

但是得到了同样的错误。到目前为止，我的搜索只给出了特定于应用程序的答案（例如sed）。我错过了什么难以捉摸的把戏？

bash aws
Martin Hope
BitFreak
Asked: 2020-01-25 20:45:13 +0800 CST
  • 1

我需要能够以用户身份停止 aws EC2 服务器。我找到了https://www.cyberciti.biz/tips/howto-linux-allow-users-to-shutdown-server.html但由于我需要在 aws EC2 实例上使用此功能，所以我没有一个静态主机名，所以我尝试了：

ubuntu ALL=(ALL:ALL) ALL=/sbin/halt /sbin/reboot

但这让我：

>>> /etc/sudoers: syntax error near line 21 <<<
What now?     
Options are:
  (e)dit sudoers file again
  e(x)it without saving changes to sudoers file
  (Q)uit and save changes to sudoers file (DANGER!)

我怎样才能正确解决这个问题？

aws not-root-user
Martin Hope
alexfvolk
Asked: 2020-01-18 13:47:11 +0800 CST
  • 2

这对我来说是莫名其妙的行为。我在 aws s3 sync 命令运行时向我的脚本发送终止信号，尽管我处理了 sigterm 错误，但错误陷阱也由 aws sync 命令触发，我不明白为什么。更令人困惑的是，该命令会引发错误并继续：

脚本：

#! /bin/bash

trap 'echo GOT ERROR, exiting' ERR
trap 'echo GOT SIGTERM!' SIGTERM
while true; do
    date +%F_%T
    aws s3 cp /vagrant/audio/ s3://testarchive/tester/ --recursive
    sleep 1
done

运行脚本的命令：

timeout 5s ./tester.sh

输出：

upload: ../../vagrant/audio/2019-09-16/3/35322118-8264-406B-961B-EAF1FE7A34EF.wav to s3://testarchive/tester/2019-09-16/3/35322118-8264-406B-961B-EAF1FE7A34EF.wav
upload: ../../vagrant/audio/2019-09-16/1/165BD3D0-773A-4591-A43E-D67810716066.wav to s3://testarchive/tester/2019-09-16/1/165BD3D0-773A-4591-A43E-D67810716066.wav
upload: ../../vagrant/audio/2019-09-16/2/2A9559BB-168A-47D2-943A-A51B7885233B.wav to s3://testarchive/tester/2019-09-16/2/2A9559BB-168A-47D2-943A-A51B7885233B.wav
Terminated6.8 MiB/123.1 MiB (1.5 MiB/s) with 422 file(s) remaining
GOT ERROR, exiting
GOT SIGTERM!
2020-01-17_21:05:40
upload: ../../vagrant/audio/2019-09-16/0/07502A17-9304-4995-94E1-A1B0D439EEE7.wav to s3://testarchive/tester/2019-09-16/0/07502A17-9304-4995-94E1-A1B0D439EEE7.wav
upload: ../../vagrant/audio/2019-09-16/0/05E4C765-C2FA-4EC0-9803-8FF02C0FEDDE.wav to s3://testarchive/tester/2019-09-16/0/05E4C765-C2FA-4EC0-9803-8FF02C0FEDDE.wav
upload: ../../vagrant/audio/2019-09-

编辑＃2：

29   1   *   *   *   root   strace -e trace=kill timeout --foreground 6 /home/vagrant/tester.sh &> /home/vagrant/tester.log

#! /bin/bash

trap 'echo GOT ERROR..' ERR
trap 'echo GOT SIGTERM! && set_terminate_flag' SIGTERM

terminate_flag=false

function set_terminate_flag {
  terminate_flag=true
}

while true; do
  if [ "$terminate_flag" = true ]; then
    echo OMG IT WORKS!
    exit 0
  fi
  date +%F_%T
  aws s3 cp /vagrant/audio/ s3://testarchive/tester/ --recursive
  echo LOOP IS Done, begin sleep
done

输出：

...(skip output, 6 seconds have passed!!!)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_TIMER, si_timerid=0, si_overrun=0, si_value={int=14831664, ptr=0xe25030}} ---
kill(9432, SIGTERM)                     = 0
kill(9432, SIGCONT)                     = 0
...(skip output)
upload: ../vagrant/audio/2020-01-01/E7914F83-8A89-4679-ABBC-8DB261D13349-01.wav to s3://testarchive/tester/2020-01-01/E7914F83-8A89-4679-ABBC-8DB261D13349-01.wav
GOT SIGTERM!
LOOP IS Done, begin sleep
OMG IT WORKS!
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=9432, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
+++ exited with 124 +++
shell-script aws
Martin Hope
Mcar49
Asked: 2019-11-22 01:38:51 +0800 CST
  • 4

我有一个 json 文件，其中包含大量 AWS CloudWatch 日志（从 CLI 命令生成）。我正在尝试使用 jq仅返回没有“retentionInDays”字段的条目的值。我有以下内容，可以根据需要返回所有内容，但我似乎无法过滤掉确实具有保留时间的结果。

# Working output (unfiltered)
jq ".logGroups[] | { log_name: .logGroupName, log_arn: .arn, retention_scheme: .retentionInDays }" cwlogs.json

我已经尝试了几件事，但要么得到错误，要么完成并且什么也不输出：

# Doesn't return anything
jq '.logGroups[] | { log_name: .logGroupName, log_arn: .arn, retention_scheme: select(.retentionInDays | contains ("null")?) }' cwlogs.json

# Errors with "jq: error (at cwlogs.json:760): number (7) and string ("null") cannot have their containment checked"
jq '.logGroups[] | { log_name: .logGroupName, log_arn: .arn, retention_scheme: select(.retentionInDays | contains ("null")) }' cwlogs.json

# Hangs forever
jq '.logGroups[] | select(.retentionInDays != "null").type'

更新：我正在使用的 JSON 的可测试段

{
    "logGroups": [
        {
            "storedBytes": 0,
            "metricFilterCount": 0,
            "creationTime": 1234,
            "logGroupName": "/aws/elasticbeanstalk/docker",
            "retentionInDays": 7,
            "arn": "longarnhere"
        },
        {
            "storedBytes": 0,
            "metricFilterCount": 0,
            "creationTime": 1245,
            "logGroupName": "/aws/elasticbeanstalk/nginx",
            "arn": "longarnhere"
        }
    ]
}
linux aws
Martin Hope
MikiBelavista
Asked: 2019-06-25 06:24:43 +0800 CST
  • 1

我正在尝试 ssh（从我的 Ubuntu 18.04 桌面）到正在运行的 EC2 实例

ssh -i /home/miki/pizda/jk/keys/kur/kjam/python-kjam.pem [email protected]
ssh: connect to host ec2-18-194-207-247.eu-central-1.compute.amazonkur.com port 22: Connection timed out

同样如果我尝试IP

ssh -i /home/miki/pizda/jk/keys/kur/kjam/python-kjam.pem [email protected]
ssh: connect to host 18.194.207.247 port 22: Connection timed out

我可以ping IP

ping 18.194.207.247
PING 18.194.207.247 (18.194.207.247) 56(84) bytes of data.
^C
--- 18.194.207.247 ping statistics ---
544 packets transmitted, 0 received, 100% packet loss, time 556011ms

为什么我有 100% 的丢包率？如何设置安全组？ 在此处输入图像描述 还有什么可能导致问题？

ssh aws