Confirmation before using
When using Coati, it is necessary to confirm the support requirements in advance. In particular, since it is necessary to install SSM, please make sure that SSM is installed and available to each instance you want to monitor before using (AmazonEC2RoleforSSM is required).
Sign up for Coati
Please register your account by entering your email address from a "sign up(Free”) link at https://coati.sios.com. An email for authentication will be sent to the address you provided.
Subject: SIOS Coati:アカウント作成のご連絡
SIOS Coati team
Move to the link of "Sign up URL", enter the registered email address and the verification code (the number following the Code:), and press the send button. Once authentication and registration is completed, you will be able to sign in to Coati.
If the confirmation code is expired, or you cannot receive the code, open the resending code page from registration page, please resend confirmation code.
Creating an IAM Role
You need to configure an IAM Role with your AWS environment to enable Coati’s monitoring of your Amazon EC2 (EC2) instances. Coati can automatically create a necessary IAM Role for the service with CloudFormation. If the CloudFormation is not available, please see the section Creating an IAM Role Manually.
Creating an IAM Role with CloudFormation
Using AWS Management Console
Login to AWS Management Console.
Select Service → CloudFormation → Create Stack.
Enter any name in the Stack name, IAMRoleName and PolicyName field and click Next.
On the Capabilities screen, tick the check box and click Create stack.
Make sure that the stack status is “CREATE_COMPLETE”.
Now the IAM Role is created.
Go on to
When you sign in to Coati for the first time, the user's "AWS account ID" and "IAM Role name" are checked first. Please enter your AWS account ID and IAM Role name you created, and click “Register” button.
AWS Account ID Initial Setting Screen
Obtaining monitoring target list
To start monitoring, Coati needs to obtain a list of the resources (EC2 instance) owned by the user. Resources can be detected at this timing. You can also do this manually later.
At this point, the user's EC2 instances have not been monitored yet.
Advanced settings for monitoring target
Before starting Coati’s monitoring, you can select monitored instances and specify services to monitor. Coati will automatically monitor and restore all the active services. If you have any services you do not want to monitor, please exclude them before the monitoring is started.
This setting can also be changed after the monitoring is started. Please refer to the technical guide for detailed setting steps.
Selection Policy for the Monitored Target
Users can select any service to monitor with SIOS Coati. However, are not suitable for SIOS Coati monitoring. Services that are not suitable for monitoring by SIOS Coati that we have identified cannot be selected, but not all services that are not suitable for monitoring are excluded.
SIOS Coati is supposed to monitor services that are always running. Because of this nature of Coati, if you include services such as Windows TrustedInstaller and wuauserv are services that are not always running in Coati's monitoring targets, Coati may behave differently than expected, such as frequent failure detection.
SIOS Coati does not recommend to include services that are not always running as Coati’s monitoring targets. Please exclude services that are not suitable for SIOS Coati monitoring. Services that are currently not recommended by SIOS Coati are as follows:
After obtaining the list of monitored instances, you can finally start monitoring with Coati. Click the "Start/Stop Monitoring" button on the left pane of the GUI screen, then click "Start monitoring" on the confirmation screen. If "Monitoring status" becomes “Monitoring”, Coati has started monitoring.