# Local SDK and Rapid Development Environments

> **Verified:** 2026-09 against https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/rapid-development-environments

Open this for the RDE command surface, its limits, or how to run the AEM and dispatcher SDKs locally.

## Local AEM SDK

```bash
# author on 4502, publish on 4503 — the port is taken from the file name
java -jar aem-author-p4502.jar
java -jar aem-publish-p4503.jar

mvn clean install -PautoInstallSinglePackage         # deploy the all package to author
mvn clean install -PautoInstallSinglePackagePublish  # …to publish
```

- Keep `aem-sdk-api` in the parent POM aligned with the SDK jar, and the SDK close to the cloud release. A local build that passes against a year-old SDK proves nothing.
- The SDK is not a replica: no CDN, no asset microservices, no Adobe IMS, different Tika configuration for full-text indexing. Anything that depends on those is verified on dev or an RDE.

## Dispatcher SDK

```bash
./bin/validate.sh ./dispatcher/src
./bin/docker_run.sh ./dispatcher/src host.docker.internal:4503 8080
```

`validate.sh` is the same check the web-tier pipeline runs — a failure here is a pipeline failure you found early. See `aem-dispatcher` for the configuration itself.

## Rapid Development Environments

An RDE deploys in seconds to minutes instead of the tens of minutes a full-stack pipeline takes. It has a dedicated `rde` run mode that **inherits `dev`**, so `config.dev` applies unless a `config.rde` folder overrides it.

```bash
aio plugins:install @adobe/aio-cli-plugin-aem-rde
aio aem:rde:setup                                        # pick program and environment

aio aem:rde:install all/target/acme.all-1.0.0-SNAPSHOT.zip
aio aem:rde:install core/target/acme.core-1.0.0-SNAPSHOT.jar
aio aem:rde:install -t dispatcher-config dispatcher/target/dispatcher.zip
aio aem:rde:install -t frontend  ui.frontend/dist.zip
aio aem:rde:install -t env-config config.zip

aio aem:rde:status           # what is deployed right now
aio aem:rde:history          # previous deployments
aio aem:rde:logs             # tail logs
aio aem:rde:snapshot         # capture / restore repository state
aio aem:rde:delete           # remove a previously installed artifact
aio aem:rde:reset            # back to a clean environment
```

`-t` accepts `content-package`, `osgi-config`, `osgi-bundle`, `content-file`, `dispatcher-config`, `env-config` and `frontend`. Limits worth knowing: a single artifact may be up to **1 GB**, and an environment keeps up to **7 snapshots**.

### What an RDE is and is not for

| Good fit | Not a fit |
|---|---|
| Iterating on a bundle, OSGi config or dispatcher rule | Performance testing — the sizing is not production-like |
| Demoing a feature branch before the PR merges | Integration sign-off with third parties |
| Reproducing a cloud-only bug that the SDK cannot show | Anything that must be reproducible — RDE state is not in Git |

Every change still goes through Git and a pipeline. An RDE that "works" proves the artifact installs, not that the release is good.

## Environment hibernation

Sandbox program environments hibernate after a period of inactivity and are de-hibernated on demand from Cloud Manager or by visiting the environment; the first request after de-hibernation is slow. Production program environments do not hibernate. Do not point a monitoring check or a scheduled integration at a sandbox environment and expect it to stay up.

## Cloud Manager from the command line

```bash
aio plugins:install @adobe/aio-cli-plugin-cloudmanager
aio cloudmanager:list-programs
aio cloudmanager:list-pipelines
aio cloudmanager:start-execution <pipelineId>
aio cloudmanager:environment:tail-log <envId> author aemerror
```

The same operations are available through the Cloud Manager API, which is how you wire pipeline starts into your own CI, publish deployment events to a chat channel, or manage Advanced Networking (dedicated egress IP, VPN) — that last one has a lead time measured in weeks, so raise it early in a project, not during go-live week.
