Troubleshooting for AWS ACM

Overview

This section helps you troubleshoot the common problems that you might encounter when using AWS cloud functionalities for ACM & IAM service like server addition using AppViewX, fetch, certificate discovery & certificate push.

Supported Web Browsers

Browser Version Notes
Firefox Till latest (Version 84.0.4147.135) NA
Chrome Till latest (Version 80.0) NA
IE Limited support in 9, Full support from 10+ No support for IE9 post-AppViewX Version 11.0
Safari

Till latest (Windows - Version 5.1.7,

macOS - Version 13.1.2)

 From AppViewX Version 11.1
Opera Till latest (Version 70) From AppViewX Version 11.1

Supported Devices

Device OS Resolution
Desktop Windows 1024 X 768 onwards, 1366x768, 1920x1080, Higher
Desktop Linux 1024 X 768 onwards, 1366x768, 1920x1080, Higher
Desktop Mac 1024 X 768 onwards, 1366x768, 1920x1080, Higher
iPad iOS 1024 X 768

Issues in Server Addition using AppViewX GUI

Table 1. Error messages and resolutions
Error Message Possible Cause Possible Solution
Please provide valid credentials Provided credential is invalid.

  1. Provide valid Access Key.

  2. Provide valid Secret Key.
Provide valid account name Account name can be duplicate or not as per standard.

  1. Provide unique name for account name.

  2. Account name can be alphanumeric and can also have period (.) in it.
Details Incorrect Provide mandatory fields.

Enter mandatory fields like

  1. Account Number

  2. Access Key

  3. Secret Key

  4. Data Center

  5. Services

  6. Regions

Issues in Fetch Regions

Table 2. Error messages and resolutions
Error Message Possible Cause Possible Solution
Please provide valid credentials The provided credential is invalid.

  1. Provide valid Access Key.

  2. Provide a valid Secret key.

Issues in Discovery in ACM

Table 3. Error messages and resolutions
Error Message Possible Cause Possible Solution
Please provide information as required

  1. Discovery name is not given or the length is less than 2 characters.

  2. Interval between batches info. is missing when execution type is sequential.

  1. Enter a valid name with a minimum of 2 characters.

  2. Provide a time interval between batches in minutes.
Please select a device No device is selected in the Discover By section. Select at least one device from which to discover certificates.

Issues in Push and Rollback

Table 4. Error messages and resolutions
Error Message Possible Cause Possible Solution
Unable to initiate request.
  1. Pushing to device when certificate is unavailable, such as in a new state.
  2. Previous work order is in progress and not completed.
  3. AppConnector might not be in sync.
  1. Push to device after certificate has been retrieved from CA.
  2. Initiate push after previous work order is finished.
  3. Synchronize the AppConnector and retry.
Unable to initiate request, template is in disabled state Given workflow is not in enabled state Enable the push/rollback workflow from the Workflow section.
User is not authorized Userdoes not have required permissions to push to the device. Retry after getting the access for required action.
Private key content is unavailable. Private key content is not available for the certificate. Private key is mandatory for the certificate to be pushed.
Application connector(s) not found Application connector info was not found. Provide the correct connectorId if not pushing using AppViewX UI.
Request associated with the application connector is in progress Previous work order is in progress and not completed. Initiate this request after the previous work order is finished.
Push not triggered or succeeded or No existing data available for backup process. Rollback couldn’t proceed because push was not successful. Only successfully pushed certificates can be rolled back.
Certificate not found. Pushing to device when certificate is unavailable, i.e, in a new state. Push to device after certificate has been retrieved from CA.
Provided certificate is not a valid self signed. Please provide either a valid self-signed certificate or certificate chain Provided certificate is not a valid certificate. Push a valid certificate.
Push failed as there exists another certificate with commonName Certificate with same common name is present in certificate manager Check whether it is a duplicate certificate and remove the invalid one.