Skip to content

Commit 87a4c89

Browse files
committed
micro-osd.sh: Clarify the suspicion around S3 credentials
It's unusual to put any kind of credentials out in open. The set of credentials defined with `S3_ACCESS_KEY` and `S3_SECRET_KEY` variables in the script are questionable in its nature. But these are not real/valid credential values in any form for AWS rather used for testing the S3 compatible API from Ceph RGW. Therefore clarify the intention and replace with sample values from official AWS documentation. Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
1 parent bd40739 commit 87a4c89

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

micro-osd.sh

+8-3
Original file line numberDiff line numberDiff line change
@@ -39,10 +39,15 @@ MON_NAME="a"
3939
MGR_NAME="x"
4040
MIRROR_ID="m"
4141
RGW_ID="r"
42-
S3_ACCESS_KEY=2262XNX11FZRR44XWIRD
43-
S3_SECRET_KEY=rmtuS1Uj1bIC08QFYGW18GfSHAbkPqdsuYynNudw
44-
HOST_IP=$(getent ahostsv4 "${HOSTNAME}" | grep STREAM | head -n 1 | awk '{print $1}')
4542

43+
# Following are examples for S3 credentials taken from official AWS docs:
44+
# https://docs.aws.amazon.com/IAM/latest/UserGuide/security-creds.html#access-keys-and-secret-access-keys
45+
# These does not represent real/valid credentials for AWS in any form.
46+
# They are exclusively used for testing S3 compatible API from Ceph RGW.
47+
S3_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE
48+
S3_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
49+
50+
HOST_IP=$(getent ahostsv4 "${HOSTNAME}" | grep STREAM | head -n 1 | awk '{print $1}')
4651
FSID="$(uuidgen)"
4752
export CEPH_CONF=${DIR}/ceph.conf
4853

0 commit comments

Comments
 (0)