AWS lightsail documentation change
Summary
Updated command syntax and filenames for certificate management in GitLab CE instance setup. Changed multi-command steps to single-line chained commands using &&, updated certificate filenames from server.* to tls.*, and adjusted permissions/ownership commands.
Security assessment
The changes streamline certificate management steps (e.g., using tls.crt/tls.key instead of server.crt/server.key) and improve command reliability by chaining with &&. While certificate management is security-related, there is no explicit evidence these changes address a specific vulnerability. The modifications appear to be procedural improvements rather than responses to security incidents.
Diff
diff --git a/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-gitlab.md b/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-gitlab.md index 35765b5ba..c1363e484 100644 --- a//lightsail/latest/userguide/amazon-lightsail-quick-start-guide-gitlab.md +++ b//lightsail/latest/userguide/amazon-lightsail-quick-start-guide-gitlab.md @@ -141 +141 @@ You should see a response similar to the following example. Your GitLab CE insta -If that command fails, you might be using an older version of the GitLab CE instance. Try running the following commands instead. Replace `<DomainName>` with the domain name that is routing traffic to your instance. +If that command fails, you might be using an older version of the GitLab CE instance. Try running the following command instead. Replace `<DomainName>` with the domain name that is routing traffic to your instance. @@ -143 +143 @@ If that command fails, you might be using an older version of the GitLab CE inst - cd /opt/bitnami/apps/gitlab + cd /opt/bitnami/apps/gitlab && \ @@ -146 +146 @@ If that command fails, you might be using an older version of the GitLab CE inst -After running those commands, enter the following command to keep the bnconfig tool from automatically running every time the server restarts. +After running the above command, enter the following command to keep the bnconfig tool from automatically running every time the server restarts. @@ -193 +193 @@ On the Lightsail console home page, under the **Domains & DNS** tab, choose **Cr - 7. Enter the following commands one by one to stop the application services that are running on your instance. + 7. Enter the following command to stop the application services that are running on your instance. @@ -195 +195 @@ On the Lightsail console home page, under the **Domains & DNS** tab, choose **Cr - sudo service bitnami stop + sudo service bitnami stop && \ @@ -224 +224 @@ If successful, a set of certificates are saved to the `/opt/bitnami/letsencrypt/ - 10. Enter the following commands one by one to rename the existing certificates on your instance. Later, you will replace these existing certificates with your new Let's Encrypt certificates. + 10. Enter the following command to rename the existing certificates on your instance. Later, you will replace these existing certificates with your new Let's Encrypt certificates. @@ -226,3 +226,2 @@ If successful, a set of certificates are saved to the `/opt/bitnami/letsencrypt/ - sudo mv /etc/gitlab/ssl/server.crt /etc/gitlab/ssl/server.crt.old - sudo mv /etc/gitlab/ssl/server.key /etc/gitlab/ssl/server.key.old - sudo mv /etc/gitlab/ssl/server.csr /etc/gitlab/ssl/server.csr.old + sudo mv /etc/gitlab/ssl/tls.crt /etc/gitlab/ssl/tls.crt.old && \ + sudo mv /etc/gitlab/ssl/tls.key /etc/gitlab/ssl/tls.key.old @@ -230 +229 @@ If successful, a set of certificates are saved to the `/opt/bitnami/letsencrypt/ - 11. Enter the following commands one by one to create symbolic links for your new Let's Encript certificates in the `/etc/gitlab/ssl` directory, which is the default certificates directory on your GitLab CE instance. + 11. Enter the following command to create symbolic links for your new Let's Encript certificates in the `/etc/gitlab/ssl` directory, which is the default certificates directory on your GitLab CE instance. @@ -232,2 +231,2 @@ If successful, a set of certificates are saved to the `/opt/bitnami/letsencrypt/ - sudo ln -sf /opt/bitnami/letsencrypt/certificates/Domain.key /etc/gitlab/ssl/server.key - sudo ln -sf /opt/bitnami/letsencrypt/certificates/Domain.crt /etc/gitlab/ssl/server.crt + sudo ln -sf /opt/bitnami/letsencrypt/certificates/Domain.key /etc/gitlab/ssl/tls.key && \ + sudo ln -sf /opt/bitnami/letsencrypt/certificates/Domain.crt /etc/gitlab/ssl/tls.crt @@ -239,2 +238,2 @@ In the command, replace `Domain` with the primary root domain that you specified - sudo ln -sf /opt/bitnami/letsencrypt/certificates/example.com.key /etc/gitlab/ssl/server.key - sudo ln -sf /opt/bitnami/letsencrypt/certificates/example.com.crt /etc/gitlab/ssl/server.crt + sudo ln -sf /opt/bitnami/letsencrypt/certificates/example.com.key /etc/gitlab/ssl/tls.key && \ + sudo ln -sf /opt/bitnami/letsencrypt/certificates/example.com.crt /etc/gitlab/ssl/tls.crt @@ -242 +241 @@ In the command, replace `Domain` with the primary root domain that you specified - 12. Enter the following commands one by one to change the permissions of your new Let's Encrypt certificates in the directory you moved them into. + 12. Enter the following command to change the permissions of your new Let's Encrypt certificates in the directory you moved them into. @@ -244,2 +243,2 @@ In the command, replace `Domain` with the primary root domain that you specified - sudo chown root:root /etc/gitlab/ssl/server* - sudo chmod 600 /etc/gitlab/ssl/server* + sudo chown root:root /etc/gitlab/ssl/tls* && \ + sudo chmod 600 /etc/gitlab/ssl/tls* @@ -247 +246 @@ In the command, replace `Domain` with the primary root domain that you specified - 13. Enter the following commands one by one to restart the application services on your GitLab CE instance. + 13. Enter the following command to restart the application services on your GitLab CE instance. @@ -249 +248 @@ In the command, replace `Domain` with the primary root domain that you specified - sudo service bitnami start + sudo service bitnami start && \