Review Pending Changes on OpsMan shows error "AWS was not able to validate the provided access credentials"

Products

• Operations Manager

Issue/Introduction

The Review Pending Changes / Apply Changes process cannot be started due to AWS credentials validation errors.
When the customer accesses Ops Manager and attempts to execute an Apply Changes, the UI shows errors when trying to validate AWS credentials. This can be caused by the OpsManager VM time being out of sync.

Environment

Product Version: 2.10

Resolution

To identify if the issue is caused by time synchronization issues, you can validate by SSH into the OpsManager VM and executing the command below. Compare the output to the command to the official UTC time. (https://www.timeanddate.com/worldclock/timezone/utc) The slightest time drift can be the root cause for the validation errors.

Solution 1: Restart the OpsMan VM from the IaaS console. (AWS)
Note: You need to make sure to have the OpsMan Decryption Passphrase available before you start this process.

• Access the IaaS console and find the OpsMan VM.
• Restart the VM. There are two options to do this:
  • Select the Stop Instance and then the Start Instance options.
  • Use the Reboot Instance option

• Access the OpsManager UI. The first time accessing it after restart it will request the Decryption Passphrase before loading the login page.
• Login to OpsMan and retry the Apply Changes process, the time should be back in sync and the credentials validated without issues.

Solution 2: Restart the OpsManager VM ntp service.

• SSH into the OpsMan VM.
• Restart the ntp process.

sudo systemctl restart ntp

• In the OpsManager UI try to run the Apply Changes again.

Solution 3: Manually adjust the OpsManager VM time.

• SSH into the OpsMan VM.
• Disable the NTP synchronization setting.

sudo timedatectl set-ntp false

• Set the time manually using the official UTC time.

sudo timedatectl set-time UTC_time_from_website

• Re-enable the NTP synchronization setting.

sudo timedatectl set-ntp true

• In the OpsManager UI try to run the Apply Changes again.