The Access/License server has been running fine for several years but it has become apparent that the system is vulnerable to some “single point of failure” conditions.

There are many potential problems with the current Access server architecture. In a rough order of severity they are:

• RDS or EC-2 instance failure (has happened in 2011 and 2012, about once per year)
• AWS fabric failure (at least once per year), e.g. S3, network, virtual host failure
• Storage and retrieval failures, mostly experienced by the Agtek Access Java Client
• Client failures (losing keys)

Virtual Machine failure recovery strategies

• Quick reboot - Available via the AWS management console.
• Quick instance recreation - Either:
  • scripted in command lines tools on dev.agtek.com or
  • built into the AccessSupport tool (NOT keyforge)
  • Scripting is easy, but not easy to transfer the skills to another person
  • Building into the support tool makes them easy to use, but not as easy to adapt for future changes.

The following areas are routine maintenance items and/or feature requests that need to be done.

• Upgrade the server infrastructure to the latest Java 7
• Add wildcard search to admin api for users
• Routine update of AMI Linux server upgrades (security)
• Possible update of entire Linux AMI (2013-03 variant released).