Why are new cached accounts displaying as "inaccessible" if they were created in v2.15.4 or older?

For customers that create (or previously created) new accounts using Kion version 2.15.4 or older, those cached accounts may display as Inaccessible, as shown below.

 

 

This is related to the availability of the CloudFormation service within AWS on the newly-created account. Starting with version 2.15.5, we added a feature to continuously attempt to install the "cloudtamer-service-role" until the CloudFormation service becomes available, but this feature was not available in earlier versions. If you created an account while running version 2.15.4 or earlier and you encounter this issue (or if you are currently running 2.15.4), you will have to perform the following workaround. 

 

1. Browse to the project.
2. Click on the Accounts tab.
3. Find the affected account and choose Delete from the ellipsis menu to remove the account from the project.
4. In the pop-up modal, choose Yes to place the account in the cache. 

1. Click on the Account Name and view the URL bar: https://YOURCLOUDTAMERURL/portal/account-cache/ACCT_CACHE_ID. Grab the ACCT_CACHE_ID from the URL.
2. Create an App API Key by clicking on your username within Kion in the top right corner, choosing App API Key, and creating a new one. For more information on App API keys, see our Public API Guide.
3. Run the cURL command below from a UNIX host that has access to the Kion application, updating the fields in red to reflect the appropriate values (replace “APITOKENHERE” with your App API Key):

curl --location --request POST 'https://YOURCLOUDTAMERURL/api/v1/account-cache/organization-complete' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer APITOKENHERE' \
--data-raw '{
	"AccountCacheID": ACCT_CACHE_ID, 
	"AccountNumber": "ACCOUNT_NUMBER",
	"RequesterID": 2
}'