// Add steps as necessary for accessing the software, post-configuration, and testing. Don’t include full usage instructions for your software, but add links to your product documentation for that information.
//Should any sections not be applicable, remove them

== Test the deployment

To test the deployment, check that the full stack has been created successfully and
that the `lcdstatus` command reports that failover is allowed for all resources.

. Open the https://console.aws.amazon.com/cloudformation[AWS CloudFormation console^].
. Select the correct Region from the top toolbar.
. On the *Stacks* page, look for a status of `CREATE_FAILED`. 
. Choose the stack name.
. On the *Stack details* page, choose the *Events* tab. Find the explanation for the failed status in the *Status reason* column.
. Fix errors with the stack. For help, see https://docs.us.sios.com/Linux/9.2.2/LK4L/AllTechDocs/index.htm#troubleshooting.htm#kanchor187[Troubleshooting^] or see https://support.us.sios.com/aspx/SupportHome[SIOS Support^]. Contact mailto:evalsupport@us.sios.com[SIOS pre-sales support^] during an evaluation period.
. After all stacks have a status of `CREATE COMPLETE`, open the https://console.aws.amazon.com/ec2/v2/home?region=us-east-1[Amazon EC2 console^].
. Log in to either the bastion host or the optional Windows jump server. Follow the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html#ec2-connect-to-instance-linux[AWS guidelines^] for connecting to your instances.
. From the jump server node, use SSH (Secure Shell) to connect to the instance in the first Availability Zone.
. Run `sudo /opt/LifeKeeper/bin/lcdstatus`.
. The output should contain two resources: `/opt/sample_mirror` and `datarep-sample`. Both resources should report `FAILOVER ALLOWED`. Two known machines should be listed and reported as `ALIVE`.

[#test]
.Output of lcdstatus
image::../images/lcdstatus-output.png[Test]

For more information, see http://docs.us.sios.com/Linux/9.2.2/LK4L/AllTechDocs/index.htm[SIOS Technical Documentation^].

== Best Practices

Refer to the following AWS best practices for creating and using IAM roles and policies, IAM user credentials and roles, and access key rotation.

* https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_forservice.html[What is IAM?^]
* https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html[Creating IAM policies^]
* https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_sign-in.html[How IAM users sign in to AWS^]
* https://aws.amazon.com/blogs/security/how-to-rotate-access-keys-for-iam-users[How to Rotate Access Keys for IAM Users^]

For SIOS best practices, see https://docs.us.sios.com/dkce/8.8.0/en/topic/best-practices[Best Practices^].