RSA Authentication Manager 8.7 SP2 (AMI)
RSA Authentication Manager 8.8 (AMI)
RSA Authentication Manager 8.9 (AMI)
Customers who have already deployed AM on AWS and have not explicitly disabled Instance auto-recovery
RSA Authentication Manager (AM) deployed using AWS AMI may have the EC2 "Instance auto-recovery" setting left at the default value ("Default") at the time of instance launch. However, this configuration is not supported by RSA.
The AWS Instance auto-recovery feature may modify installed software during the automatic recovery process. Since AM is not designed or validated with the assumption that third-party (AWS) software modifications may occur, running AM with Instance auto-recovery set to "Default" or enabled is not a supported configuration.
All customers running AM on AWS AMI must set Instance auto-recovery to "Disabled".
Required Action:
Change the Instance auto-recovery setting from "Default" to "Disabled" for all EC2 instances running RSA Authentication Manager.
Procedure:
To change the Instance auto-recovery setting on an existing EC2 instance, refer to the following AWS official documentation:
Automatic instance recovery - Amazon Elastic Compute Cloud
https://docs.aws.amazon.com/en_us/AWSEC2/latest/UserGuide/instance-configuration-recovery.html
Note: The Instance auto-recovery setting can also be configured at the time of instance launch:
EC2 Console → Launch Instance → Advanced Details → Instance auto-recovery → Select "Disabled"
As AWS may update their documentation and UI at any time, please refer to the latest AWS official page for the most up-to-date instructions.
Setting Instance auto-recovery to "Disabled" does NOT cause any functional restrictions on AM itself. This is a supported and recommended configuration.
Disabling Instance auto-recovery means that AWS will not automatically recover the instance in the event of an underlying hardware failure. Customers should ensure appropriate high availability (HA) and backup configurations are in place (e.g., Operations Console backup, replica instances) to maintain service continuity.
For backup and restore procedures specific to AM on AWS, refer to the "Primary or Replica Instance Amazon Web Services Snapshots" section in the AM Administrator's Guide.
Related Articles
How to configure AM Prime / AMIS to authenticate remote application servers with MTLS (Mutual Authentication) 177Number of Views RSA Authentication Manager 8.6 Amazon Machine Image (AMI) Getting Started 21Number of Views Cannot apply RSA Authentication Manager 8.1 SP1 patch due to special characters in OS user rsaadmin password 1.18KNumber of Views Removing a drive mounted as CD-ROM on the RSA AM virtual machine via vCenter console 140Number of Views Unique constraint (AVUSER.PK_WP_USER_DATA) violated error while upgrading RSA Identity Governance & Lifecycle 282Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide