AWS Workspaces: Problem that uploaded package doesn't appear on validation instance

0

Hello,

I created a new packaging instance to build a new version of my application that I want to deploy (as I always did). I used the Amazon WorkSpaces Application Manager Studio, chose my application and clicked "Update". After my changes I used "Upload". After uploading the status of my application version on "Dashboard" becomes "Upload complete". Then I started my EC2 validation instance and connected to it. In the Amazon WorkSpaces Application Manager I went to "Pending Apps" and clicked "Refresh" but my new version didn't appear. I waited now for more than 1,5 hours and it's still not visible.

In my packaging instance I checked the log files but the last steps seemed to be successful:

2022-05-30  07.06.51.944  Info:    Writing final package data...
2022-05-30  07.06.51.944  Info:    Packaging application...
2022-05-30  07.06.52.382  Info:    Writing project file "C:\Users\ADMINI~1\AppData\Local\Temp\2\EBC567BD-A637-4603-AF2C-31D1D7837E4A_15.stw"
2022-05-30  07.06.52.382  Info:    Done writing project file "C:\Users\ADMINI~1\AppData\Local\Temp\2\EBC567BD-A637-4603-AF2C-31D1D7837E4A_15.stw"
2022-05-30  07.06.55.415  Info:    Done patching in 4.2s
2022-05-30  07.06.55.462  Info:    Successfully created package.
2022-05-30  07.06.55.462  Info:    Successfully created package.

For testing I created another new packaging instance, chose my application in the Amazon WorkSpaces Application Manager Studio and create "Update". I got the following error message:

Failed to extract application from the specified appset. Appset file might be invalid.

So what went wrong and what can I do to continue? Do you need further information to help me?

Thanks a lot in advance, Michaela

已提問 2 年前檢視次數 213 次
1 個回答
0

Hello Michaela! Looking at your question I believe you have done everything correctly. In WAM Studio Dashboard, the app should have been shown as "Upload Complete" and then as "Pending Testing".

Please confirm that the validation instance was launched from the WAM Player AMI, in the same VPC and Public Subnet as the WAM Studio packaging instance and that it has the same role attached to it (AmazonWamAppPackaging that has the managed policy AmazonWorkSpacesApplicationManagerAdminAccess attached to it)

If you still have issues I suggest to open a new support case with us and to provide the logs from WAM Studio (C:\Program Files\Amazon\WAM Studio\wamstudio.log) and WAM Player (File and Options - Log tab - choose View Log, along with the instance ID's for each instance.

References: https://docs.aws.amazon.com/wam/latest/adminguide/application_packaging.html#cant_get_apps https://docs.aws.amazon.com/wam/latest/adminguide/iam.html#app_package_role https://docs.aws.amazon.com/wam/latest/adminguide/application_log_files.html

AWS
支援工程師
已回答 2 年前
  • Hello, I can confirm that the validation instance was launched from the WAM Player AMI, in the same VPC and Public Subnet as the WAM Studio packing instance and that it has the same role AmazonWamAppPacking attached to it .

    But the app never change to "Pending Testing". As a workaround I created a new application (instead of creating a new version of the existing application) and this works fine.

    I will then open a support case.

    Thanks a lot for your answer!

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南