received some great feedback here in regards to updates for ossim in AWS, but now coming across some different issues. current situation is that we took the ossim instance that is available for AWS, took a snapshot, created a VPC, and used the snapshot to create another instance using the c1.xlarge vm configuration. now while it is up and running, it seems to be stuck in time. connection is fine, its updated to 4.2.3, and receiving new events, however the web interface reflects the system status of when the snapshot was taken. it still has the hardware configuration of the original instance and not the specs of the c1.xlarge and shows that updates are required.
was just wondering if anyone has tried anything similar with AWS or knows where its pulling this information from or if this is something that just is not going to resolve.