You could also set the group that contains the image element that you want to display to be of type text — this way you eliminate the customs state — and you can do a workflow to pass data to the group being the URL text

So each static image is contained by a group with type text and the datasource is the copied AWS URL — then when you set the workflow event to display data in the main group to show the larger image and that group is also of type text and the image element has the datasource for dynamic images set the the container groups text

I do have a question though…why do you have a list of static images? All those images are once you upload them as a static image in your file manager

Which means that they are taking up space in your apps storage and will count against your capacity usage…also using the static image upload feature doesn’t provide you with any ability to set a maximum file size of an image uploaded, which will also negatively impact your capacity and usage.

There are other ways out there as well to achieve the goal of having a list of images displayed without showing a scroll bar in a repeating group. You could set the repeating group to a full list which removes the scroll bar and if you are searching a large list of images stored in the database you could always set items from items until to get a specific number of images displayed.

What was your use case for the set up you put together?