Introduction

This article is part 11 of a tutorial to help you get started with FME Cloud. We will cover FME Cloud events. This tutorial needs to be followed in order. Please complete Part 1: Sign Up and Part 2: Launch Instance before continuing with this article.

Step-by-Step Instructions

1) Login to FME Cloud

Login to FME Cloud here if you have not already done so.

2) Explore events

From the FME Cloud Instances page, select an instance and open the Events tab. Events trigger when a certain situation occurs and then send a notification. By default, instances have events that notify their creator

1. when a fatal error occurred during an instance transition, or
2. when an instance failed to switch states (e.g. from running to paused).

These are visible in the Events tab:

Events tab

You can choose to notify a user or notification group.

Events can be triggered by a number of situations:

• when an instance is started;
• when an instance is paused;
• when an instance is rebooted;
• when a security patch is available;
• when a reboot is required;
• when an SSH login occurs (such as when Safe Software support accesses your instance);
• or when a security group is modified.

You can read more about these events in the FME Cloud events documentation.

Event options

Note: the “Security patch available” option is for users running instances with User initiated OS Security Updates, which is not the recommended option. The "Reboot required" option is for users running the recommended Unattended OS Security Updates option. This alert is triggered when the security patch has been applied, but the instance must be rebooted for the changes to take effect.

Conclusion

We hope you have found these Getting Started with FME Cloud tutorials useful. If you have any questions about using FME Cloud, check search the Q&A Forum, read the FME Cloud Documentation, or post your question in the comments below. Thanks!