- Newest
- Most votes
- Most comments
Hello, thank you for reaching out!
At this time, there is no API to query information about the underlying instances. If you run the describe-sessions
API, it will only return the information from sessions that have been created. This would mean that IP's from instances that are just waiting for an incoming session would not be listed.
The closest query you can perform to answer your question is to list the Elastic Network Interfaces (ENIs) that currently exist in your account associated to your fleet. To that effect, you can run aws ec2 describe-network-interfaces --filters "Name=description,Values='AppStream 2.0 - fleet:<fleetname>'"
[1]
This API will return the AttachTime
timestamp in UTC format. You can then compare this time with the time when you called the UpdateFleet
API and that will tell you which ENIs are using the new image. If you would rather get the list of the instances that are using the previous image, then you would do the query when the ENI creation date is older than the UpdateFleet
API call date.
Another workaround is to schedule image replacements in the off hours, so you can stop a fleet entirely, replace the image and start them back. Using this approach (if possible) would effectively mean that all instances always use the latest image.
For your other question, Appstream originally only supported the Application view, which meant that you would need to add at least one app to the catalog to create an image. You can continue to add the Calculator or any other built in app like Notepad.
Relevant content
- Accepted Answerasked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
This is a help but reveals some basic features that appstream is missing. Don't get me started on trying to white-list the appstream portal IP ranges for a given region. I don't mean the URL ones, I mean the ones that need UDP QUIC 8443. Corporations are willing to allow wide QUIC access because packets can't be inspected.