General
Q: What are the fees for using opswitch?
A: There is no fee to use opswitch.
Q: How do I cancel my membership?
A: Please see this page.
If there is an organization to which only the user to be deleted belongs, the following information will also be deleted together.
- Organization
- Jobs
- Tasks
-
Linked AWS accounts
- Job Execution History
- Operation History
Also, delete the CloudFormation stack in which you created the IAM role. If you created the stack with the default name, the name will start with "insightwatch-job" or "opswitch".
Q: Which browsers are supported?
A: Supported browsers are the latest versions of Google Chrome and Microsoft Edge.
Q: What is the difference between opswitch's Create EBS snapshot task and Amazon DLM's Create Snapshot Lifecycle Policy?
A: The differences at this time (as of April 2024) are as follows
Only opswitch's Create EBS snapshot task should be able to do this.：
- You can skip execution on Japanese holidays or skip execution on specified dates from the job settings.
- You can set any description for the snapshots you create.
- Multiple AWS accounts can be targeted.
- Receive notification when snapshot creation fails.
Only Amazon DLM can do this.：
-
The number of generation management can be set up to 1,000. (opswitch can be set to a maximum of 90.)
-
Retention type can be selected as "Age" and can be set to automatically delete after a certain number of days.
Q: Why didn't my job run at the specified time?
A: In the event of a server outage due to maintenance or failure, jobs that were scheduled to run during the outage period will be executed when the server is restored. Information on maintenance and outages is displayed at the top of the screen when logging into opswitch as shown below.
Otherwise, there may be a delay of a few minutes from the set time depending on load conditions. Currently, there are many jobs running from 22:00 to around 8:00, and many of them are set to 0 minutes, so you may be able to reduce the delay by changing the number to the halfway point where there is less overlap.
Q: What are the permissions of the IAM Role used by opswitch?
A: The permissions of the IAM Role created by opswitch when linking AWS accounts are summarized below.
Regarding the permissions of the IAM Role created by opswitch
Q: Where are EC2 backups, EBS snapshots, DB snapshots, and DB cluster snapshots stored?
A: The various backups created by opswitch are not based on our own specifications, but on the AWS backup mechanism. Therefore, backups created by opswitch are stored in the AWS cloud in the same way as backups created using the Management Console or AWS CLI. If you would like to check if a backup has been created, please log in to the Management Console.
- EBS snapshots can be found in the EC2 console under the section called Snapshots.
- EC2 backups can be found in the AMI section of the EC2 console.
- DB snapshots and DB cluster snapshots can be found in the RDS console under the section called Snapshots.
Q: What procedures are used to restore EC2 backups, EBS snapshots, DB snapshots, and DB cluster snapshots?
A: The various backups created by opswitch are not based on our own specifications, but rather on the AWS backup mechanism. Therefore, backups created by opswitch can be restored using the Management Consolde or AWS CLI in the same way as backups created using the Management Console or AWS CLI. Please refer to the documentation on the official website below for the restoration procedure for each resource.
Q: I have linked my AWS account and the status is invalid and unavailable.
A: This state will occur if you have moved to another screen or closed your browser while creating an AWS account linkage. If this happens, try deleting the disabled AWS Account Linkage and CloudFormation stack and start over. Deleting the stack will not affect your system.
Once an AWS account linkage is created, deleting the CloudFormation stack will invalidate the status. In that case, please refer to this page to re-link.
Q: A job containing an EC2 backup task running daily suddenly failed. The following log is output.
An error occurred (InvalidParameterValue) when calling the CreateImage operation:
Invalid value 'i-xxxxxxxxxx' for instanceId. Instance is not in state 'running' or 'stopping' or 'stopped'
A: The above error occurs when the status of the EC2 instance to be backed up is other than running, stopping, or stopped. If this error occurs even though the status is running, stopping, or stopped, it may be due to a failure of the AWS infrastructure and can be avoided by stopping and starting the target instance.
Q: The job to start EC2 failed to execute. The log contained the string "InsufficientInstanceCapacity". What is the cause?
- Early the start time of the job.
- Taking a longer "acceptable delay" time, say 30 minutes, may cause the job to start on retry.
- Change the EC2 instance type.
The EC2 instance startup/stop task has the ability to change to another instance type and start it up when "InsufficientInstanceCapacity" occurs. For details, see this page.
Q. Job execution failed. The log contained the string "RequestLimitExceeded". What is the cause?
A. This may occur when too many processes are executed at the same time. For example, if 50 EC2s are targeted with the same tag in one EC2 backup task. If this happens frequently, stagger the time by dividing it into multiple tasks, for example.
Q. Job execution failed. The log contained the string "InvalidSnapshot.InUse". What is the cause?
A. This may occur when deleting an older generation snapshot when creating an EC2 backup. When deleting an older generation snapshot, it indicates that the corresponding snapshot is in use and cannot be deleted. Even if this error occurs, if the created AMI is available, the backup was successfully created. If the old snapshot is not deleted and remains, please delete the old snapshot manually from the AWS Management Console.
Q: I did not receive an email with a confirmation code when signing up.
A: opswitch will send a confirmation code email to the email address you entered when signing up. The subject line of the confirmation code email will be "You're Invited: opswitch" and the source address of the email will be "sys@opswitch.io".
- Check that the email address you entered is correct.
- Check to see if the confirmation code email has not been sorted into your junk mail.
Q: After logging in with opswitch, I got an error screen.
A: Please make sure that the connection to the opswitch API is not blocked by a proxy server in your network, otherwise you will be redirected to an error screen after logging in.
Q: RDS automatically starts up 7 days after it is stopped. How can I keep it stopped as long as possible?
A: We recommend that you execute the stop task after executing the start task of the DB instance.
- First, create a "Stop DB instance" task with reference to this page. Next, create a "Start DB Instance" task targeting the same account and target as the "Stop DB Instance" task. Be sure to select "To Check" for "Check status".
- Next, please refer to this page and set the order of execution on the job edit screen to "Start Task" -> "Stop Task" as shown in the following screenshot. opswitch will execute the tasks from the top in the order they are displayed on the job edit screen. The order can be changed using the arrow buttons. Select "Weekly" for the job schedule and set it to be executed once on any day of the week and time.
※Please note that this method incurs a short startup time, and RDS charges a 10-minute usage fee even if the startup time is less than 10 minutes. If you wish to minimize the usage fee, please consider deleting the DB instance once after taking a DB snapshot.