AWS devopsagent documentation change
Summary
Updated GitLab connection documentation with restructured steps, UI navigation changes (Capabilities tab to Capability Providers page), and removed section about associating AWS resources with project deployments.
Security assessment
The changes are procedural updates to the user interface and workflow for connecting GitLab. There is no evidence of addressing security vulnerabilities or weaknesses. The removal of the section about associating AWS resources with project deployments is a documentation reorganization, not a security fix. No security features are added.
Diff
diff --git a/devopsagent/latest/userguide/connecting-to-cicd-pipelines-connecting-gitlab.md b/devopsagent/latest/userguide/connecting-to-cicd-pipelines-connecting-gitlab.md index 1c35abd17..55d499036 100644 --- a//devopsagent/latest/userguide/connecting-to-cicd-pipelines-connecting-gitlab.md +++ b//devopsagent/latest/userguide/connecting-to-cicd-pipelines-connecting-gitlab.md @@ -21 +21 @@ GitLab is registered at the AWS account level and shared among all Agent Spaces - 3. Go to the **Capabilities** tab + 3. Go to the **Capability Providers** page (accessible from the side navigation) @@ -23 +23 @@ GitLab is registered at the AWS account level and shared among all Agent Spaces - 4. In the **Pipeline** section, click **Add** + 4. Find **GitLab** in the **Available** providers section under **Pipeline** and click **Register** @@ -25 +24,0 @@ GitLab is registered at the AWS account level and shared among all Agent Spaces - 5. Select **GitLab** from the list of available providers @@ -28,0 +28 @@ GitLab is registered at the AWS account level and shared among all Agent Spaces +### Step 2: Configure GitLab connection @@ -30 +30 @@ GitLab is registered at the AWS account level and shared among all Agent Spaces -If GitLab hasn't been registered yet, you'll be prompted to register it first. +On the GitLab registration page, configure the following: @@ -32 +32 @@ If GitLab hasn't been registered yet, you'll be prompted to register it first. -### Step 2: Choose connection type +**Connection type** – Select whether you're connecting as a person or a group: @@ -34,3 +34 @@ If GitLab hasn't been registered yet, you'll be prompted to register it first. -On the "Register GitLab Account / Group" screen, select whether you're connecting as a person or a group: - - * **Personal** – Your individual GitLab user account with a username and profile + * **Personal** (default) – Your individual GitLab user account with a username and profile @@ -43,7 +41 @@ On the "Register GitLab Account / Group" screen, select whether you're connectin -### Step 3: Select GitLab instance type - -Choose which type of GitLab instance you're connecting to: - - * **[GitLab.com](http://GitLab.com)** (default) – The public GitLab service - - * **Publicly accessible Managed GitLab instance** – A managed GitLab deployment accessible from the public internet +**GitLab instance type** – Choose which type of GitLab instance you're connecting to: @@ -51 +43 @@ Choose which type of GitLab instance you're connecting to: - * **Publicly accessible self-hosted GitLab** – Your own GitLab deployment accessible from the public internet + * **GitLab.com** (default) – The public GitLab service @@ -52,0 +45 @@ Choose which type of GitLab instance you're connecting to: + * **Publicly accessible self-hosted GitLab** – Check the **Use GitLab self hosted endpoint** box and provide the URL to your GitLab instance @@ -56 +48,0 @@ Choose which type of GitLab instance you're connecting to: -If you're using a self-hosted or managed GitLab instance, check the box "Use GitLab self hosted endpoint" and provide the URL to your GitLab instance. @@ -62 +54 @@ If you're using a self-hosted or managed GitLab instance, check the box "Use Git -### Step 4: Create and provide an access token +**Access token** – Provide a GitLab personal access token: @@ -91 +83 @@ If you're using a self-hosted or managed GitLab instance, check the box "Use Git -### Step 5: Complete registration +### Step 3: Complete registration @@ -93 +85,3 @@ If you're using a self-hosted or managed GitLab instance, check the box "Use Git -Click **Submit** to complete the GitLab registration process. The system will validate your access token and establish the connection. +**(Optional) Tags** – Add AWS tags to the GitLab registration for organizational purposes. + +Click **Next** to review your configuration, then click **Submit** to complete the GitLab registration process. The system will validate your access token and establish the connection. @@ -116,4 +109,0 @@ AWS DevOps Agent will monitor these projects for deployments from GitLab Pipelin -### Associating AWS resources with project deployments - -See [Associating AWS resources with project deployments](./connecting-to-cicd-pipelines-associating-aws-resources-with-project-deployments.html) to associate deployments with AWS resources. This helps incident investigations correlate recent deployments with possible root causes. - @@ -139 +129 @@ Connecting GitHub -Associating AWS resources with project deployments +Connecting MCP Servers