メインコンテンツまでスキップ

AWS node

An AWS node lets you interact with AWS services directly from your flow. Use it to retrieve data, create or modify resources, and perform actions across AWS services. The output of one node becomes the input for the next, allowing you to define a sequence of actions and operations.

Find an action​

When adding an AWS node to a flow, select AWS as the provider and then find an action by searching or browsing within AWS services. In addition, a template node allows you to add a pre-built group of actions to the current flow.

Search all a provider's services for an action

Configure an action​

Selecting an action node will open a side panel with three tabs for configuration:

Action configuration

  • Parameters: This tab shows the service and action you've chosen and the option to change. You also configure approval settings on this tab. The parameters available vary with service and action.

  • Permissions: This tab helps you verify whether you have the required permissions to perform the action and provides instructions if you don't. See also APIs in CloudFlow.

  • Test: Use Test to validate your configuration. It is important to test the configuration of each node in a flow to ensure that every node functions as expected and that data is processed correctly throughout.

    注意

    This action performs a full execution of the step which can initiate real actions, such as deletion.

Require approval​

If an action should be approved before its execution, select Require approval for this action on the Permissions tab.

Require approval for action

  • Notification provider: Specifies whether to notify the approver via Slack or email. For the former, you should have created a shared Slack channel with DoiT.

  • Message (optional): A message for the approver. You can add fields from previous nodes to your message. When the message is created, the data from the field is displayed in the message. This is useful because it provides recipients with the details they need to make a decision without having to navigate to the system and manually search for the relevant information. An array of fields are displayed as a comma-separated list. For example, Instance ID: i-123,i-466.

  • Reject approval after certain time (optional): Limits for how long the action will wait for an approval. Possible time units are Hours, Days, Weeks, and Months. For example, you can set that an approver must approve/reject the action within 24 hours. If the approver takes no action before the specified time period expires, the action is automatically rejected.

Add a waiter​

A waiter ensures that an AWS action in a flow is complete before the flow proceeds to the next step. This enables you to configure a pause in your flow for time-dependent factors, asynchronous operations, or external dependencies. For example, when launching an EC2 instance, you might want to wait for the operating system to start before continuing to the next step in the flow.

To configure a waiter, select Enable waiter.

Waiter for action

  • Wait until: Defines the waiter to take for the action. As each service works differently, the available waiters are unique to each AWS action you are using.

  • (optional) Override waiter configuration: Enables you to provide overrides for waiter behavior. For example, if you are waiting for a critical, fast operation, you might reduce a waiter's default delay from 5 seconds to 1 second to get a quicker result. See also WaiterConfiguration.

  • (optional) Parameters: Specifies the parameters you need to define for the waiter. For example, if you want to wait for an S3 bucket to exist before proceeding, then specify the name of the bucket.

に最終更新