Oracle GoldenGate 26ai on AWS User Guide
Overview
This guide covers launching and using the Oracle GoldenGate 26ai (23.26.1.0.0) Microservices on Oracle Linux 9 AMI from cloudimg on Amazon EC2.
Oracle GoldenGate replicates data between databases in real time: Extract processes capture committed changes from a source database, trail files carry them, and Replicat processes apply them to a target, with the Distribution and Receiver services moving trails between hosts. The Microservices Architecture runs this as a set of web services (Service Manager, Administration, Distribution, Receiver and Performance Metrics) that you drive from a browser, the Admin Client command line or a REST API. Oracle GoldenGate 26ai is release 23.26 of the 23ai line, and Oracle's release notes, the sign-in page, the credentials file and the paths ogg26ai all use the 26ai name; this image is the build for Oracle Database, which works with Oracle Database 19c, 21c, 23ai and 26ai sources and targets through the Oracle client libraries in the GoldenGate home.
The cloudimg image adds:
- A Service Manager and deployment made on your instance, not on ours. The image contains the GoldenGate software only. On the first boot of every instance, a one-time service runs Oracle's configuration assistant (
oggca.sh) to create the Service Manager and a deployment namedogg26ai, with a Service Manager administrator (smadmin) and a separate deployment administrator (oggadmin), each with a strong password generated on that instance. Their credential wallets are therefore unique to your instance and no two instances share a password. The passwords never appear on a command line or in a log; they are written to/root/goldengate-credentials.txt(readable by root only). - Fail closed. GoldenGate and the HTTPS front end refuse to start until first boot has finished. If first boot ever fails, the partial deployment is removed and nothing listens.
- HTTPS from the first boot. Every GoldenGate service listens on
127.0.0.1only (ports 7809 to 7813). nginx 1.26 publishes them on port 443 with Oracle's own reverse-proxy routes and a certificate generated on your instance; port 80 redirects to HTTPS. Requests for a host name the instance does not serve get no answer. - Locked-down defaults. SSH by key only (no passwords, no root login, no X11 forwarding);
rootandoraclehave no password at all. GoldenGate and nginx are blocked from the instance metadata service and the AMI requires IMDSv2. SELinux stays enforcing and the Service Manager runs asoracleunder a locked down systemd unit. - Base media only. GoldenGate is installed from Oracle's 23.26.1.0.0 release media (checked against its SHA-256 checksum) with no patch applied: you apply Oracle's patches with your own Oracle support (see Step 11).
- Fully patched Oracle Linux 9 at build time, with
dnf-automaticapplying Oracle Linux security updates every day.
What is on the image: Oracle GoldenGate 23.26.1.0.0 Microservices for Oracle in /u01/app/oracle/product/ogg26ai (with the Java runtime Oracle's installer places in the GoldenGate home for Oracle's own tools), nginx, Oracle Linux 9.8 with the Unbreakable Enterprise Kernel, cloud-init and the AWS Systems Manager agent.
Default user: ec2-user · Architecture: x86_64 · Recommended instance type: m5.large (t3.large for tests and light use)
Pricing: $0.04 per vCPU per hour for the cloudimg software (an m5.large has 2 vCPUs, so $0.08 per hour), plus AWS infrastructure charges. The charge is for what cloudimg adds to Oracle's base media: the Service Manager and deployment created on each instance at first boot with their own administrator passwords and wallets, HTTPS through nginx with a certificate generated on the instance, the GoldenGate services on localhost only, SSH by key pair only, and GoldenGate and nginx blocked from the instance metadata service; it does not include an Oracle licence.
Licence: Oracle GoldenGate is a commercial Oracle product. Bring your own licence: using Oracle GoldenGate requires your own Oracle GoldenGate licence covering the instance under Oracle's licensing policy for cloud computing environments. Your source and target databases need their own licences too. See Licensing and price at the end of this guide; the notices are in /usr/share/doc/cloudimg/licenses/README-ORACLE.txt.
Prerequisites
- An AWS account subscribed to the listing, an EC2 key pair and a VPC subnet with a route to the internet (or a private route you use for management).
- A security group that allows TCP 443 (HTTPS: the GoldenGate web UI, the REST API and Distribution paths from other GoldenGate deployments) and TCP 80 (redirects to HTTPS) from the people and systems that use GoldenGate, and TCP 22 (SSH) from your own networks only. Ports 7809 to 7813 are never needed in the security group.
- Network access from the instance to your databases (for example TCP 1521 to an Oracle listener).
Step 1: Launch the instance
In the AWS Marketplace listing choose Continue to Subscribe, then Continue to Configuration, pick Oracle GoldenGate 26ai (23.26.1) on Oracle Linux 9 as the software version (the version name ends with the date and time it was added) and your Region, then Launch through EC2. If the version list also shows older Oracle DB 26ai Enterprise versions, that is the product this listing sold before and is not this image. Choose m5.large (or larger for production replication), your key pair and a security group as above. The root volume holds the GoldenGate software, your deployment and its trail files; size it for the change volume you replicate (for example 50 GiB). The root file system grows to fill the volume on first boot.
With the AWS CLI (replace the values in angle brackets):
aws ec2 run-instances --region <region> --image-id <ami-id-from-the-listing> \
--instance-type m5.large --key-name <your-key-pair> \
--security-group-ids <your-security-group> --subnet-id <your-subnet> \
--metadata-options HttpTokens=required,HttpEndpoint=enabled \
--block-device-mappings 'DeviceName=/dev/sda1,Ebs={VolumeSize=50,VolumeType=gp3}' \
--tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=goldengate}]'
Step 2: Connect to your instance
| Version | SSH user |
|---|---|
| Oracle GoldenGate 26ai (23.26.1) on Oracle Linux 9 | ec2-user |
ssh -i <your-key.pem> ec2-user@<public-ip>
Confirm the operating system release:
cat /etc/oracle-release
Oracle Linux Server release 9.8
Step 3: Check the services
On a newly launched instance, first boot creates the Service Manager and deployment in about a minute and a half, then starts GoldenGate and nginx; until then port 443 refuses connections. Check the three units:
sudo systemctl is-active goldengate-firstboot.service goldengate.service nginx.service
active
active
active
goldengate-firstboot.service reports active because it is a one-time unit that has finished; on later boots it sees its marker and does nothing. The first boot log shows the host name the instance was configured for and how long it took (this example comes from a newly launched instance):
sudo cat /var/log/goldengate-firstboot.log
[2026-11-15T01:58:58Z] goldengate-firstboot: configured host: ec2-52-91-245-99.compute-1.amazonaws.com
[2026-11-15T01:58:58Z] goldengate-firstboot: creating the Service Manager and deployment 'ogg26ai' (oggca silent, services on 127.0.0.1)
[2026-11-15T02:00:05Z] goldengate-firstboot: nginx routes from Oracle's ReverseProxySettings (Service Manager password on stdin)
[2026-11-15T02:00:23Z] goldengate-firstboot: TLS certificate + nginx names for ec2-52-91-245-99.compute-1.amazonaws.com
[2026-11-15T02:00:24Z] goldengate-firstboot: done in 86s; starting GoldenGate and nginx
The Service Manager runs the deployment's four services as its children, all on the loopback address:
ss -tln
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 511 0.0.0.0:80 0.0.0.0:*
LISTEN 0 511 0.0.0.0:443 0.0.0.0:*
LISTEN 0 128 127.0.0.1:7809 0.0.0.0:*
LISTEN 0 128 127.0.0.1:7811 0.0.0.0:*
LISTEN 0 128 127.0.0.1:7810 0.0.0.0:*
LISTEN 0 128 127.0.0.1:7813 0.0.0.0:*
LISTEN 0 128 127.0.0.1:7812 0.0.0.0:*
LISTEN 0 128 [::]:22 [::]:*
LISTEN 0 511 [::]:80 [::]:*
LISTEN 0 511 [::]:443 [::]:*
| Port | Service |
|---|---|
| 7809 | Service Manager |
| 7810 | Administration Service (deployment ogg26ai) |
| 7811 | Distribution Service |
| 7812 | Receiver Service |
| 7813 | Performance Metrics Service |
Step 4: Get your URL and passwords
The values generated for this instance are in a root-only file. This shows the file with the passwords hidden:
sudo sed -E 's/^(SERVICE_MANAGER_PASSWORD=|DEPLOYMENT_ADMIN_PASSWORD=).*/\1<hidden>/' /root/goldengate-credentials.txt
# Oracle GoldenGate 26ai (23.26.1.0.0) Microservices - this instance's own credentials (generated on its first boot)
# Generated: 2026-11-15T02:00:24Z
GOLDENGATE_URL=https://ec2-52-91-245-99.compute-1.amazonaws.com/
SERVICE_MANAGER_USER=smadmin
SERVICE_MANAGER_PASSWORD=<hidden>
DEPLOYMENT_NAME=ogg26ai
DEPLOYMENT_ADMIN_USER=oggadmin
DEPLOYMENT_ADMIN_PASSWORD=<hidden>
TLS_CERT_SHA256_FINGERPRINT=A0:C7:93:48:6B:8B:5E:D9:7C:4E:50:86:B1:DF:D4:74:69:1D:7B:B1:4D:4D:7C:7F:BD:0D:4C:83:A6:EB:BB:97
There are two administrator accounts, each with its own password:
| Account | Signs in to | Use it for |
|---|---|---|
smadmin |
the Service Manager | deployments, their services, users and certificates of the Service Manager |
oggadmin |
deployment ogg26ai |
database connections, Extracts, Replicats, paths, trails |
Print the passwords when you need them (and store them in your secret manager):
sudo grep -E '^(SERVICE_MANAGER|DEPLOYMENT_ADMIN)_PASSWORD=' /root/goldengate-credentials.txt
The host name is the instance's public DNS name (or its public or private address when it has no public name). To serve GoldenGate on your own DNS name, see Step 9.
Step 5: Sign in to the Service Manager
The certificate is self-signed and generated on your instance. Check it, and compare its SHA-256 fingerprint with TLS_CERT_SHA256_FINGERPRINT above before you trust it in your browser:
sudo openssl x509 -in /etc/nginx/ssl/goldengate.crt -noout -subject -ext subjectAltName -fingerprint -sha256
subject=CN=ec2-52-91-245-99.compute-1.amazonaws.com
X509v3 Subject Alternative Name:
DNS:ec2-52-91-245-99.compute-1.amazonaws.com, IP Address:52.91.245.99, DNS:ip-172-31-91-38.ec2.internal, IP Address:172.31.91.38, DNS:localhost, IP Address:127.0.0.1
sha256 Fingerprint=A0:C7:93:48:6B:8B:5E:D9:7C:4E:50:86:B1:DF:D4:74:69:1D:7B:B1:4D:4D:7C:7F:BD:0D:4C:83:A6:EB:BB:97
Open GOLDENGATE_URL (for example https://ec2-52-91-245-99.compute-1.amazonaws.com/) in your browser and accept the certificate. The Oracle GoldenGate 26ai sign-in page appears:

Sign in as smadmin with SERVICE_MANAGER_PASSWORD. The Service Manager home lists the Service Manager itself and deployment ogg26ai, both Running:

Choose Deployments, then ogg26ai, to see its Administration, Distribution, Performance Metrics and Receiver services:

Step 6: Sign in to the deployment
Click Administration Service in the deployment's service list (it opens https://<your-host>/services/ogg26ai/adminsrvr/v2/content/ in a new tab) and sign in as oggadmin with DEPLOYMENT_ADMIN_PASSWORD. This is where you work with GoldenGate: database connections, Extracts, Replicats, Distribution and Receiver paths, trails and parameter files.

The Service Manager account (smadmin) does not sign in to the deployment and the deployment account (oggadmin) does not sign in to the Service Manager: each has its own user store. Add more users for your team under User Administration in each place.
Step 7: Use the Admin Client
The Admin Client is GoldenGate's command line. It runs on the instance as oracle, whose profile sets OGG_HOME, PATH and the library path:
sudo -iu oracle adminclient --version
Oracle GoldenGate Administration Client for Oracle
Version 23.26.1.0.0 OGGCORE_23.26.1.0.0OGGRU_LINUX.X64_260117.1830_FBO
Linux, x64, 64bit (optimized) on Jan 18 2026 01:06:11
Start it with sudo -iu oracle adminclient and connect to the deployment's Administration Service on the loopback address as oggadmin, or to the Service Manager as smadmin (type the password from Step 4 where the example shows it in angle brackets):
OGG (not connected) 1> CONNECT http://127.0.0.1:7810 DEPLOYMENT ogg26ai AS oggadmin PASSWORD <DEPLOYMENT_ADMIN_PASSWORD>
OGG (http://127.0.0.1:7810 ogg26ai) 2> INFO ALL
No processes found.
OGG (not connected) 1> CONNECT http://127.0.0.1:7809 DEPLOYMENT ServiceManager AS smadmin PASSWORD <SERVICE_MANAGER_PASSWORD>
OGG (http://127.0.0.1:7809 ServiceManager) 2> INFO ALL
Deployment Name Service Name Service Status
ogg26ai ADMINSRVR RUNNING
ogg26ai DISTSRVR RUNNING
ogg26ai PMSRVR RUNNING
ogg26ai RECVSRVR RUNNING
The plain http://127.0.0.1 addresses never leave the instance; from anywhere else use the web UI or the REST API over HTTPS.
Step 8: Use the REST API
Every action in the web UI is a REST call, available over HTTPS at the same host. This lists the deployments as the Service Manager administrator, then checks the deployment's Administration Service as the deployment administrator (the passwords are read from the root-only file and handed to curl in a config file, never on its command line):
HOST=$(sudo sed -n 's|^GOLDENGATE_URL=https://\([^/]*\)/$|\1|p' /root/goldengate-credentials.txt)
CA=$(mktemp); sudo cat /etc/nginx/ssl/goldengate.crt > "$CA"
curl -s --cacert "$CA" --resolve "$HOST:443:127.0.0.1" \
-K <(printf 'user = "smadmin:%s"\n' "$(sudo sed -n 's/^SERVICE_MANAGER_PASSWORD=//p' /root/goldengate-credentials.txt)") \
"https://$HOST/services/v2/deployments" | python3 -c 'import json,sys; print([i["name"] for i in json.load(sys.stdin)["response"]["items"]])'
curl -s --cacert "$CA" --resolve "$HOST:443:127.0.0.1" \
-K <(printf 'user = "oggadmin:%s"\n' "$(sudo sed -n 's/^DEPLOYMENT_ADMIN_PASSWORD=//p' /root/goldengate-credentials.txt)") \
"https://$HOST/services/ogg26ai/adminsrvr/v2/config/health" | python3 -c 'import json,sys; r=json.load(sys.stdin)["response"]; print(r["deploymentName"], r["serviceName"], "healthy" if r["healthy"] else "NOT healthy")'
rm -f "$CA"
['ServiceManager', 'ogg26ai']
ogg26ai adminsrvr healthy
The routes follow Oracle's reverse-proxy layout: the Service Manager answers at https://<your-host>/services/v2/... and each service of the deployment at https://<your-host>/services/ogg26ai/<service>/v2/... (adminsrvr, distsrvr, recvsrvr, pmsrvr). Requests without valid credentials are refused (HTTP 401, or 403 for a wrong password). The image also checks all of this for you:
sudo /usr/local/sbin/goldengate-selftest
Service Manager (smadmin) lists ogg26ai and deployment administrator (oggadmin) reaches adminsrvr, distsrvr, recvsrvr, pmsrvr over https://ec2-52-91-245-99.compute-1.amazonaws.com/ (instance certificate verified); refused: anonymous 401/401, wrong password 403/403, deployment user on the Service Manager 401
GG_ROUNDTRIP_OK
Step 9: Your own DNS name and certificate
To serve GoldenGate on your own DNS name, point the name at the instance (for example an Elastic IP and a DNS A record), then run:
sudo /usr/local/sbin/goldengate-set-host goldengate.your-domain.com
This makes a new self-signed certificate for the name and updates the nginx server names and the URL in /root/goldengate-credentials.txt; GoldenGate itself keeps running. To use a certificate from your own certificate authority instead, replace /etc/nginx/ssl/goldengate.crt and /etc/nginx/ssl/goldengate.key (keep the key root:nginx, mode 0640) and run sudo systemctl reload nginx.
When another GoldenGate deployment sends you trail data through a Distribution path, point the path at this host on port 443: nginx publishes this deployment's Receiver Service under /services/ogg26ai/recvsrvr/ (Oracle's documentation on Distribution paths through a reverse proxy gives the exact target syntax), and the sending deployment must trust this certificate (or your CA).
Step 10: Connect your database
GoldenGate for Oracle connects to your databases with Oracle Net. Put your tnsnames.ora in the deployment's TNS_ADMIN directory, /u01/app/oracle/network/admin, as oracle:
sudo -iu oracle tee /u01/app/oracle/network/admin/tnsnames.ora <<'EOF'
SOURCEDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = <your-database-host>)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = <your-service-name>)))
EOF
Prepare the database as Oracle describes for GoldenGate (supplemental logging, ENABLE_GOLDENGATE_REPLICATION, and a GoldenGate user, conventionally ggadmin, with the privileges Oracle lists). Then, in the deployment's Administration Service, open DB Connections, add a credential for the alias (for example SOURCEDB with your ggadmin user and password) and connect. From there you create Extracts, Replicats and paths. Oracle's documentation covers each step: Oracle GoldenGate 26ai documentation.
Step 11: Apply Oracle patches
The image ships Oracle's 23.26.1.0.0 base release with no patch applied:
sudo -iu oracle /u01/app/oracle/product/ogg26ai/OPatch/opatch lspatches -oh /u01/app/oracle/product/ogg26ai
There are no Interim patches installed in this Oracle Home "/u01/app/oracle/product/ogg26ai".
OPatch succeeded.
Download GoldenGate release updates and patches from My Oracle Support with your own Oracle support entitlement and apply them as Oracle describes for Microservices (stop GoldenGate with sudo systemctl stop goldengate.service, apply with OPatch as oracle, then sudo systemctl start goldengate.service). Oracle Linux packages, nginx included, are updated by dnf-automatic every day; GoldenGate itself is not an RPM and is never changed by dnf.
Step 12: Change the administrator passwords
Change a password in the web UI: as smadmin in the Service Manager, or as oggadmin in the deployment's Administration Service, open User Administration and edit the user. The values in /root/goldengate-credentials.txt are the first-boot passwords; after you change a password, update or delete that file (sudo shred -u /root/goldengate-credentials.txt), keep the new password in your secret manager, and note that goldengate-selftest reads the file.
Step 13: Check the security model
The GoldenGate and nginx services cannot reach the instance metadata service (169.254.169.254) even as root, because systemd filters their network access:
systemctl show -p IPAddressDeny goldengate.service nginx.service
IPAddressDeny=169.254.169.254/32 168.63.129.16/32 fd00:ec2::254/128
IPAddressDeny=169.254.169.254/32 168.63.129.16/32 fd00:ec2::254/128
SSH accepts keys only, and SELinux is enforcing:
sudo sshd -T | grep -E '^(passwordauthentication|permitrootlogin|x11forwarding) '
getenforce
permitrootlogin no
passwordauthentication no
x11forwarding no
Enforcing
The firewall opens only SSH, HTTP and HTTPS. GoldenGate's Receiver Service also listens for its UDP trail transport on port 7812; the firewall and your security group keep it closed from outside unless you open it on purpose:
sudo firewall-cmd --zone=public --list-services
dhcpv6-client http https ssh
Managing the GoldenGate services
| Task | Command |
|---|---|
| Status | sudo systemctl status goldengate.service nginx.service |
| Stop / start / restart GoldenGate | sudo systemctl stop goldengate.service (start, restart) |
| Service Manager and deployment logs | /u01/app/oracle/deployments/ServiceManager/var/log/, /u01/app/oracle/deployments/ogg26ai/var/log/ |
| GoldenGate output in the journal | sudo journalctl -u goldengate.service |
| nginx logs | /var/log/nginx/ |
goldengate.service runs the Service Manager as oracle; the Service Manager starts and watches the deployment's services. Stopping the unit stops the Service Manager first, then its services (any that do not stop within 30 seconds are ended; GoldenGate restarts processes from their checkpoints). If you add another deployment with oggca.sh, run Oracle's ReverseProxySettings again so nginx publishes it (Oracle's documentation, "Configure Reverse Proxy Servers for Oracle GoldenGate Microservices").
Filesystem layout
| Path | Contents |
|---|---|
/u01/app/oracle/product/ogg26ai |
GoldenGate 23.26.1.0.0 software home (OGG_HOME) |
/u01/app/oracle/deployments/ServiceManager |
the Service Manager (configuration, wallet, logs) |
/u01/app/oracle/deployments/ogg26ai |
deployment ogg26ai (configuration, wallet, trails under var/lib/data, logs) |
/u01/app/oracle/network/admin |
TNS_ADMIN for the deployment (tnsnames.ora, sqlnet.ora) |
/root/goldengate-credentials.txt |
this instance's first-boot URL, users and passwords (root only) |
/etc/nginx/conf.d/goldengate-ogg.conf |
Oracle's reverse-proxy routes, generated on first boot |
/etc/nginx/ssl/ |
this instance's TLS certificate and key |
/var/log/goldengate-firstboot.log |
the first boot log |
Troubleshooting
- Port 443 refuses connections right after launch. First boot is still creating the deployment; check
sudo systemctl is-active goldengate-firstboot.serviceand/var/log/goldengate-firstboot.log, and wait fordone. - The browser shows no page for the host you typed. nginx answers only the names in the certificate (the instance's DNS names and addresses). Use
GOLDENGATE_URL, or run/usr/local/sbin/goldengate-set-hostfor your own name (Step 9). - "Invalid Username or Password!" on sign-in. Sign in to the Service Manager as
smadminand to the deployment (its Administration Service) asoggadmin; each account works only in its own place. - A Distribution path cannot reach this host. Allow TCP 443 from the sending host in the security group and trust this instance's certificate in the sending deployment.
Support
For help with this image, contact cloudimg support:
- Support: www.cloudimg.co.uk/support or support@cloudimg.co.uk, on hand 24 hours a day by email, with a guaranteed response within 24 hours: first sign in, connecting the deployment to your databases, Extracts, Replicats, Distribution paths, the reverse proxy and your own host name and certificate
- Website: www.cloudimg.co.uk
- User Guides: www.cloudimg.co.uk/guides
Oracle product defects, GoldenGate patches and licensing questions are handled by Oracle under your own Oracle agreement. For administration, see the Oracle GoldenGate documentation at https://docs.oracle.com/en/database/goldengate/core/.
Licensing and price
Bring your own licence: using Oracle GoldenGate requires your own Oracle GoldenGate licence for the instance, under Oracle's licensing policy for cloud computing environments, and your source and target databases need their own licences. GoldenGate release updates come with your own Oracle entitlement, as Step 11 describes. The cloudimg software charge of $0.04 per vCPU per hour (plus AWS infrastructure charges) is for what cloudimg adds to the image: the Service Manager and deployment created on each instance at first boot with their own administrator passwords and wallets, HTTPS through nginx with a certificate generated on the instance, the GoldenGate services on localhost only, SSH by key pair only, and GoldenGate and nginx blocked from the instance metadata service. Your Oracle licence is not part of this charge; you obtain it from Oracle.
Oracle, Java and GoldenGate are registered trademarks of Oracle and/or its affiliates; cloudimg is not affiliated with or endorsed by Oracle.