I'd check Route 53 first. Then I'd make sure your AWX credentials have the proper access.
For OpenShift IPI on AWS, the **base domain must already exist as a valid Route 53 hosted zone**, and the installer will create the cluster subdomain records under:
cluster-name.base-domain
Example: maximodemo.dummydomain.com
So that part is expected. IBM's AWS install docs note that MAS/OpenShift uses a public hosted zone for cluster access/DNS routing.
I'd suggest checking:
aws route53 list-hosted-zones | grep dummydomain.com
Then confirm the zone is in the same AWS account being used by mas provision-aws.
The multiple VPCs are likely from repeated installer retries/failures where cleanup did not complete. I'd clean up any failed cluster resources before re-running, or use a fresh unique cluster name.
I would also verify that dummydomain.com is not just used by other resources, but is actually delegated correctly in Route 53 and can support a new child cluster domain.
Most likely issue:
DNS/base domain hosted zone mismatch
stale failed install resources, or
the AWS credentials don't have full permissions to manage DNS resources.
------------------------------
Shauna Gilbert
Naviam
------------------------------
Original Message:
Sent: 06-12-2025 20:34
From: Aakash Saxena
Subject: MAS SNO installation on AWS
Hi All, I am using below tech note to install MAS using AWS single node approach.
Save Costs with Single Node OpenShift Deployments of IBM Maximo on AWS | Amazon Web Services
I followed all the prerequisites per this note. However, I am encountering the following errors when creating the OpenShift cluster on using mas provision-aws command.
FAILED - RETRYING: [localhost]: ipi : Create cluster (4 retries left).
FAILED - RETRYING: [localhost]: ipi : Create cluster (3 retries left).
Upon checking my AWS console, it is creating multiple VPCs may be due to retrying.
Here is my AWS Cluster Configuration
Cluster Name - maximodemo
AWS Region - XXXX
AWS Base Domain - dummydomain.com
This dummydomain.com is already existing in AWS which is used for other resources. Once mas provision command fails it creates another DNS by combining cluster name and AWS Base domain ie maximodemo.dummydomain.com.
Any thoughts on what should I be checking? Thanks
| Amazon Web Services | remove preview |
| | Save Costs with Single Node OpenShift Deployments of IBM Maximo on AWS | Amazon Web Services | | IBM Maximo Application Suite (MAS), when paired with Red Hat Single Node OpenShift (SNO) on AWS offers an agile, cost-effective solution for asset management within SME (Small and Medium scale) settings. This simplified OpenShift configuration converges control and worker functionalities into a single Amazon Elastic Compute Cloud (Amazon EC2) node, fostering a lightweight, streamlined Kubernetes [...] | | View this on Amazon Web Services > |
|
|
#MaximoApplicationSuite
------------------------------
SA
Accenture
------------------------------