AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-07-10 · Documentation low

File: prescriptive-guidance/latest/eks-gitops-tools/jenkins-x.md

Summary

Reformatted Jenkins X capabilities from a table to a bulleted list and updated an image path

Security assessment

The change restructures existing content without modifying security-related statements. The 'Secrets management' bullet point remains unchanged and describes existing functionality without introducing new security documentation or addressing vulnerabilities.

Diff

diff --git a/prescriptive-guidance/latest/eks-gitops-tools/jenkins-x.md b/prescriptive-guidance/latest/eks-gitops-tools/jenkins-x.md
index e8ceddc55..8e6891f5f 100644
--- a//prescriptive-guidance/latest/eks-gitops-tools/jenkins-x.md
+++ b//prescriptive-guidance/latest/eks-gitops-tools/jenkins-x.md
@@ -15,22 +15,42 @@ Jenkins X is a cloud-native, open-source CI/CD platform that implements GitOps p
-Area | Tool capabilities  
----|---  
-Git-centric workflow | Jenkins X uses Git repositories as the primary source of truth for both application code and configuration. All changes to applications and infrastructure are made through Git.  
-Environment as code (EaC) | Environments (such as staging and production) are defined as code in Git repositories. This allows for version control and review of environment configurations.  
-Automated CI/CD pipelines | Jenkins X automatically sets up CI/CD pipelines for projects. These pipelines are defined as code (pipeline as code) and stored in Git.  
-Kubernetes-native | Jenkins X is built specifically for Kubernetes environments. It uses Kubernetes resources and custom resource definitions (CRDs).  
-Preview environments | Jenkins X automatically creates temporary environments for pull requests. It enables easy review and testing of changes before merges.  
-Promotion between environments | Jenkins X uses a GitOps approach to promote applications between environments (for example, from staging to production). Promotions are handled by using pull requests to ensure proper review and approval processes.  
-Helm chart management | Jenkins X uses Helm charts to package and deploy applications. Charts are version-controlled in Git repositories.  
-Automated versioning | Jenkins X automatically manages versioning of applications and releases. It uses semantic versioning and generates release notes.  
-ChatOps integration | Jenkins X supports ChatOps for common operations. This aligns with the GitOps principles of automation and collaboration.  
-Extensibility | This tool provides a plugin system for extending functionality. It allows integration with various cloud-native tools.  
-Infrastructure as code (IaC) | Jenkins X supports Terraform, CloudFormation, AWS Cloud Development Kit (AWS CDK), and other IaC tools to define and manage infrastructure. Infrastructure definitions are version-controlled alongside application code.  
-Automated rollbacks | Jenkins X supports automated rollbacks if issues are detected after deployment.  
-Secrets management | The tool integrates with external secrets management solutions to handle sensitive information securely.  
-Observability | Jenkins X provides integration with monitoring and logging tools for observability.  
-Multi-cloud support | Jenkins X is designed to work across different cloud providers and on-premises environments.  
-Team collaboration | This tool encourages collaboration through Git-based workflows and pull requests.  
-Continuous feedback | The tool provides quick feedback on changes through automated testing and preview environments.  
-DevOps best practices | Jenkins X implements DevOps best practices by default, including GitOps principles.  
-Declarative configuration | The tool uses declarative configurations for defining applications and environments.  
-Automated upgrades | Jenkins X provides tools for automating upgrades of the Jenkins X platform itself.  
+  * **Git-centric workflow** : Jenkins X uses Git repositories as the primary source of truth for both application code and configuration. All changes to applications and infrastructure are made through Git.
+
+  * **Environment as code (EaC)** : Environments (such as staging and production) are defined as code in Git repositories. This allows for version control and review of environment configurations.
+
+  * **Automated CI/CD pipelines** : Jenkins X automatically sets up CI/CD pipelines for projects. These pipelines are defined as code (pipeline as code) and stored in Git.
+
+  * **Kubernetes-native** : Jenkins X is built specifically for Kubernetes environments. It uses Kubernetes resources and custom resource definitions (CRDs).
+
+  * **Preview environments** : Jenkins X automatically creates temporary environments for pull requests. It enables easy review and testing of changes before merges.
+
+  * **Promotion between environments** : Jenkins X uses a GitOps approach to promote applications between environments (for example, from staging to production). Promotions are handled by using pull requests to ensure proper review and approval processes.
+
+  * **Helm chart management** : Jenkins X uses Helm charts to package and deploy applications. Charts are version-controlled in Git repositories.
+
+  * **Automated versioning** : Jenkins X automatically manages versioning of applications and releases. It uses semantic versioning and generates release notes.
+
+  * **ChatOps integration** : Jenkins X supports ChatOps for common operations. This aligns with the GitOps principles of automation and collaboration.
+
+  * **Extensibility** : This tool provides a plugin system for extending functionality. It allows integration with various cloud-native tools.
+
+  * **Infrastructure as code (IaC)** : Jenkins X supports Terraform, CloudFormation, AWS Cloud Development Kit (AWS CDK), and other IaC tools to define and manage infrastructure. Infrastructure definitions are version-controlled alongside application code.
+
+  * **Automated rollbacks** : Jenkins X supports automated rollbacks if issues are detected after deployment.
+
+  * **Secrets management** : The tool integrates with external secrets management solutions to handle sensitive information securely.
+
+  * **Observability** : Jenkins X provides integration with monitoring and logging tools for observability.
+
+  * **Multi-cloud support** : Jenkins X is designed to work across different cloud providers and on-premises environments.
+
+  * **Team collaboration** : This tool encourages collaboration through Git-based workflows and pull requests.
+
+  * **Continuous feedback** : The tool provides quick feedback on changes through automated testing and preview environments.
+
+  * **DevOps best practices** : Jenkins X implements DevOps best practices by default, including GitOps principles.
+
+  * **Declarative configuration** : The tool uses declarative configurations for defining applications and environments.
+
+  * **Automated upgrades** : Jenkins X provides tools for automating upgrades of the Jenkins X platform itself.
+
+
+
@@ -48 +68 @@ The following diagram illustrates a GitOps-driven CD workflow that uses Jenkins
-![Jenkins X architecture and workflow on AWS.](/images/prescriptive-guidance/latest/eks-gitops-tools/images/jenkins-x-on-aws.png)
+![Jenkins X architecture and workflow on AWS.](/images/prescriptive-guidance/latest/eks-gitops-tools/images/guide-img/b6f49161-b2c5-42aa-b1d8-b0781836edb7/images/0038b3b0-9652-4e04-b03b-bb67d53d3e9b.png)