# Page Not Found

The URL `files/g6XPI32eCIxCPCGaccke` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Configure Jenkins on EC2 instance](https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/configure-jenkins-on-ec2-instance.md)
- [Configure EC2 instance to setup the CI pipeline](https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/configure-ec2-instance-to-setup-the-ci-pipeline.md)
- [Configure EC2 instance to setup the CD pipeline](https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/configure-ec2-instance-to-setup-the-cd-pipeline.md)
- [Create Jenkins CI pipeline](https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/create-jenkins-ci-pipeline.md)
- [Install ArgoCD](https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/install-argocd.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/configure-jenkins-on-ec2-instance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://devops-maestro.gitbook.io/cicd-pipeline-using-jenkins-and-argocd/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/cicd-pipeline-using-jenkins-and-argocd/configure-jenkins-on-ec2-instance.md`).

You may also use `Accept: text/markdown` header for content negotiation.