diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-01-14 00:14:07 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-01-14 00:14:07 +0300 |
| commit | 3e64e1af8dfcad514151335813daa31601332676 (patch) | |
| tree | 4cb9faef9035c8df6d702982047b2b8ad7da58f4 /doc/install/aws/index.md | |
| parent | aa072fd68cfe366c0d5968c65e9b42aecb2a75b5 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/install/aws/index.md')
| -rw-r--r-- | doc/install/aws/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/install/aws/index.md b/doc/install/aws/index.md index cf5ee2fa643..8dbda7420b0 100644 --- a/doc/install/aws/index.md +++ b/doc/install/aws/index.md @@ -63,7 +63,7 @@ When deploying a GitLab instance using the official AMI, the root password to th Instances running on Community Edition (CE) require a migration to Enterprise Edition (EE) in order to subscribe to the GitLab Premium or Ultimate plan. If you want to pursue a subscription, using the Free-forever plan of Enterprise Edition is the least disruptive method. NOTE: -Since any given GitLab upgrade might involve data disk updates or database schema upgrades, simply swapping out the AMI is not sufficent for taking upgrades. +Since any given GitLab upgrade might involve data disk updates or database schema upgrades, simply swapping out the AMI is not sufficent for taking upgrades. 1. Log in to the AWS Web Console, so that clicking the links in the following step take you directly to the AMI list. 1. Pick the edition you want: |