Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/setup/bootstrap-awscli.sh

34 lines
983 B
Bash
Raw Normal View History

bootstrap-awscli: Remove executable bit. Even though this looks like an independently runnable script, it should not be run independently: a SHA-256 mismatch will fail to stop the script, unless it was sourced from another script that has ‘set -e’. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-06-25 03:24:21 +02:00
# shellcheck shell=bash
provisioning: Use AWS CLI to automate provisioning The previous steps for standing up a new host were somewhat manual. This further scripts the process, by using the AWS CLI to start the instance, and pass it a "user data" script to provision itself upon boot. This results in a hands-off provisioning process which completes in 5min. Additional settings are required for `~/.zulip-install-server.conf`. It is not suited for all roles, as it assumes one instance type and security group value. Additionally, not all of the post-provision process is currently automated -- Nagios SSH key verification, for instance, is still a manual step. There are also additional steps for database or frontend servers. Regardless, this is a move toward automated provisioning.
2020-07-15 20:54:57 +02:00
bootstrap-awscli: Set -eu, for if this is run standalone. The existing callsites of this are via `source` or being inline'd into the startup of a new host; in both of these cases, the surrounding script is already `set -eu`. However, if run as a standalone tool, it should also configure itself to catch checksum failures and other problems.
2021-12-31 00:53:47 +01:00
set -eu
bootstrap-aws: Support aarch64.
2021-12-29 03:24:01 +01:00
ARCH=$(uname -m)
bootstrap-awscli: Upgrade awscli version.
2022-03-16 02:06:12 +01:00
AWS_CLI_VERSION="2.4.26"
bootstrap-aws: Support aarch64.
2021-12-29 03:24:01 +01:00
if [ "$ARCH" == "x86_64" ]; then
bootstrap-awscli: Upgrade awscli version.
2022-03-16 02:06:12 +01:00
AWS_CLI_SHA="20d0f048b32782c67fcb1495928deec5aa4e4e93cb67778a0f5a4f14de0c4b8d"
bootstrap-aws: Support aarch64.
2021-12-29 03:24:01 +01:00
elif [ "$ARCH" == "aarch64" ]; then
bootstrap-awscli: Upgrade awscli version.
2022-03-16 02:06:12 +01:00
AWS_CLI_SHA="c7e5b9a4893aa51a51af7ff95db0a41d695f90509b13787935d6ff9a5b60e2a5"
bootstrap-aws: Support aarch64.
2021-12-29 03:24:01 +01:00
else
echo "Unsupported architecture: $ARCH"
exit 1
fi
provisioning: Use AWS CLI to automate provisioning The previous steps for standing up a new host were somewhat manual. This further scripts the process, by using the AWS CLI to start the instance, and pass it a "user data" script to provision itself upon boot. This results in a hands-off provisioning process which completes in 5min. Additional settings are required for `~/.zulip-install-server.conf`. It is not suited for all roles, as it assumes one instance type and security group value. Additionally, not all of the post-provision process is currently automated -- Nagios SSH key verification, for instance, is still a manual step. There are also additional steps for database or frontend servers. Regardless, this is a move toward automated provisioning.
2020-07-15 20:54:57 +02:00
if [ ! -d "/srv/zulip-aws-tools/v2/$AWS_CLI_VERSION" ]; then
mkdir -p /srv/zulip-aws-tools
bootstrap-awscli: Set -eu, for if this is run standalone. The existing callsites of this are via `source` or being inline'd into the startup of a new host; in both of these cases, the surrounding script is already `set -eu`. However, if run as a standalone tool, it should also configure itself to catch checksum failures and other problems.
2021-12-31 00:53:47 +01:00
cd /srv/zulip-aws-tools
provisioning: Use AWS CLI to automate provisioning The previous steps for standing up a new host were somewhat manual. This further scripts the process, by using the AWS CLI to start the instance, and pass it a "user data" script to provision itself upon boot. This results in a hands-off provisioning process which completes in 5min. Additional settings are required for `~/.zulip-install-server.conf`. It is not suited for all roles, as it assumes one instance type and security group value. Additionally, not all of the post-provision process is currently automated -- Nagios SSH key verification, for instance, is still a manual step. There are also additional steps for database or frontend servers. Regardless, this is a move toward automated provisioning.
2020-07-15 20:54:57 +02:00
rm -rf awscli.zip awscli.zip.sha256 aws/
bootstrap-aws: Support aarch64.
2021-12-29 03:24:01 +01:00
curl -fL "https://awscli.amazonaws.com/awscli-exe-linux-$ARCH-$AWS_CLI_VERSION.zip" -o awscli.zip
shfmt: Reformat shell scripts with shfmt. https://github.com/mvdan/sh Signed-off-by: Anders Kaseorg <anders@zulip.com>
2020-10-15 04:55:57 +02:00
echo "$AWS_CLI_SHA awscli.zip" >awscli.zip.sha256
provisioning: Use AWS CLI to automate provisioning The previous steps for standing up a new host were somewhat manual. This further scripts the process, by using the AWS CLI to start the instance, and pass it a "user data" script to provision itself upon boot. This results in a hands-off provisioning process which completes in 5min. Additional settings are required for `~/.zulip-install-server.conf`. It is not suited for all roles, as it assumes one instance type and security group value. Additionally, not all of the post-provision process is currently automated -- Nagios SSH key verification, for instance, is still a manual step. There are also additional steps for database or frontend servers. Regardless, this is a move toward automated provisioning.
2020-07-15 20:54:57 +02:00
sha256sum -c awscli.zip.sha256
unzip -q awscli.zip
(
cd ./aws || exit 1
./install -i /srv/zulip-aws-tools -b /srv/zulip-aws-tools/bin -u
)
rm -rf awscli.zip awscli.zip.sha256 aws/
fi
# shellcheck disable=SC2034
AWS="/srv/zulip-aws-tools/bin/aws"