Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
AWS Relational Database discovery throws an Errors - Failed Exploring CI Pattern. Check Pattern Amazon AWS Relational Database Service - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • AWS Relational Database discovery throws an Errors - Failed Exploring CI Pattern. Check Pattern Amazon AWS Relational Database Service
KB0726322

AWS Relational Database discovery throws an Errors - Failed Exploring CI Pattern. Check Pattern Amazon AWS Relational Database Service


841 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


Amazon AWS Relational Database Service pattern failures when there are no RDS instances in the LDC with an error - Failed Exploring CI Pattern. Check Pattern Amazon AWS Relational Database Service

Release


Jakarta release. Same is fixed in Kingston.

Cause


When there are no RDS instances available in data center, Step 3 of Identification section of "Amazon AWS Relational Database Service" pattern fails with error.

Resolution


  1. Open "Amazon AWS Relational Database Service" pattern
  2. Open "Identification of Amazon AWS RDS" of Identification Section
  3. Open step 3 and change this step as below.
    • Change Termination Type to "Expected"
    • Update Information Message to "No RDS is found in the LDC (region)".
    • Save and Publish.
    • Attached screenshot have the updated step.
  4. Restart the MID Server to Sync the pattern changes
  5. Further discoveries should show this Information message in the patterns logs.

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • Amazon AWS Relational Database Service.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.