Getting an "Asset does not exist or user does not have access" error using Tagging API even though the asset is visible in CloudHealth
search cancel

Getting an "Asset does not exist or user does not have access" error using Tagging API even though the asset is visible in CloudHealth

book

Article ID: 282708

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

When using the tagging API you must use the CloudHealth internal ID and not the AWS ID.

Resolution

The value of this id is returned as the ID parameter of the asset from the asset API.  If you try to use the AWS ID you will get the "Asset does not exist or user does not have access" error.

 

 

Powered by Wolken Software