What you have described to me is an aspatial table in a database, not a geodatabase, that has attributes and spatial properties in the form of two double fields, one for Lat and one for Long. This needs to be consumed in the GIS. In a pure desktop world, we would have introduced this to the Table of Contents as a X/Y Event layer, and then to get some form of performance, you would right click on the layer and 'Export As'.
In logical steps this is what you need to do here. Two doubles cannot be indexed spatially, literally they're just numbers and not shapes or geometries. There are many ways of doing all of this.
If you have someone skilled in SQL then you could create a table that has the same schema as AWS, but has a geography/geometry column. Inserts/Updates would then update the 'shape' with the attributes of your Lat/Long. It's just SQL. You can then use a Query Layer.
If you've got a developer, you could look to use Python to do the same thing. Theoreticlly, you can do it with model builder as well, but I haven't touched it in years... Sorry.
Otherwise, and the way I always recommend is to use Data Interop or FME.
My skillset these days is architecture and IaaS/Cloud and deploying Esri into that, rather than writing scripts etc. 😞 As much as I miss that. I'm probably not the best person to help you here, but X/Y Event layers do not perform well in ArcGIS Server and I cannot recommend them. They create bottlenecks and performance issues.
Scott Tansley
https://www.linkedin.com/in/scotttansley/