Even though the EC2 instance has been granted sufficient privileges, a warning indicating insufficient privileges is displayed when attempting to create an EC2 resource (the route table scenario), resulting in the failure of resource creation.

This event occurs due to the following:
1. During the creation of an EC2 resource (the route table scenario), the role check may determine that the permission has not been granted. This is due to LifeKeeper performing role checks on a route table for which privileges have not been granted.
2. v9.6.0 added a process to disable a source/destination check. The default behavior of this feature results in a failure to create an EC2 resource (in the route table scenario) if permissions are insufficient.

By setting EC2_NO_SRC_DEST_CHECK=0 in /etc/default/LifeKeeper, you can modify the behavior so that resource creation succeeds even if a warning of insufficient privileges is displayed. (This will result in the same behavior as in versions v9.5.1 or earlier.)
Set the UTC time of the instance to the AWS UTC time.

If the time of the instance does not match the AWS time, restoring of the EC2 resources will fail.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment