To submit AWS Cloud incident ticket in SNOW:
- Number: INC9166068
- Caller: Kian Ming Aau
- Contact Number: +12268681981
- Requested by: Kian Ming Aau
- Location: VRT59
- Category: Cloud
- Subcategory: AWS
- Business service: null
- Service offering: null
- Configuration item: ec2-cdk-sbx-us
- Caller’s asset: null
- Non-Production: checked
- Opened: 2026-06-03 11:42:32
- Contact type: Email
- State: New
- Impact: 3 - Medium
- Urgency: 3 - Medium
- Priority: 3 - Medium
- Submitter Group: BLD_TREO_NACB_SRE
- Assignment group: BLD_ENG_CLOUD_SERVERLESS
- Assigned to: null
- Lower Environments: QA
- Short description: EC2 Failed to Register in Active Directory While Deployed with BMO CDK in Sandbox Environment
Description:
We try to re-spin up our EC2 in Sandbox (520049198415) with bmo-cdk, however, the deployment failed with the "ERROR!!
Did not find computer [tcacaueslapp001] in Active Directory. Exiting" . Our code was working about 3 weeks ago.
Could we please examine is there any misconfiguration with the "HostnameApiDeployment" lambda?
Failed resources:
epre-sre-coei-cac-ec2-tcacaueslapp001-stack | 4:16:59 AM | CREATE_FAILED | AWS::CloudFormation::CustomResource |
tcacaueslapp001/HostnameApiDeployment/Default
(tcacaueslapp001HostnameApiDeployment96DA4693) Received response status [FAILED] from custom resource.
Message returned: FAILED (RequestId: cae2fa5c-19dd-4d8d-b6e0-7675a5f0a105)
❌ epre-sre-coei-cac-ec2-tcacaueslapp001-stack failed: DeploymentError: Resource updates failed:
└─ epre-sre-coei-cac-ec2-tcacaueslapp001-stack
└─ tcacaueslapp001
└─ HostnameApiDeployment
└─ Default (AWS::CloudFormation::CustomResource tcacaueslapp001HostnameApiDeployment96DA4693)
🛑 Received response status [FAILED] from custom resource. Message returned: FAILED (RequestId:
cae2fa5c-19dd-4d8d-b6e0-7675a5f0a105)
Please do not input Confidential and/or customer information into ServiceNow
To submit AWS Cloud incident ticket in SNOW:
- Number: INC9468588
- Caller: Kian Ming Aau
- Contact Number: +12268681981
- Requested by: Kian Ming Aau
- Location: VRT59
- Category: Cloud
- Subcategory: AWS
- Business service: null
- Service offering: null
- Configuration itema: ec2-cdk-sbx-us
- Caller’s asset: null
- Non-Production: cheked
- Opened: 2026-08-10 09:58:34
- Contact type: Email
- State: New
- Impact: 3 - Medium
- Urgency: 3 - Medium
- Priority: 3 - Medium
- Submitter Group: BLD_TREO_NACB_SRE
- Assignment group: BLD_ENG_CLOUD_SERVERLESS
- Assigned to: Lower Environments
- Unlock Lower Environments: QA
- Short description: EC2 Failed to Register to DNS While Deployed with BMO CDK in Sandbox Environment
Description:
We successfully spinned up EC2 with bmo-cdk/ec2 in the Sandbox (520049198415) environment. However, the deployment failed to register the hostname and IP to DNS.
We wonder if the DNS registration lambda somehow no longer working or figure out what we did wrong.
For exanmple,
Account: 520049198415
Region: us-east-1
EC2 instance: i-0ff36739432eec16b
IP address: 10.164.93.203
hostname: tcacaueslapp003.devhcloud.bmogc.net
PS C:\Users\kaau> nslookup
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 10.231.0.195
> tcacaueslapp003.devhcloud.bmogc.net
Server: UnKnown
Address: 10.231.0.195
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** UnKnown can't find tcacaueslapp003.devhcloud.bmogc.net: Non-existent domain
> exit