Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

AWS requires an external endpoint, with https. The default installation of Kloudfuse enables an ingress service with external IP enabled, but no https support. To get the external IP, run: kubectl get svc | grep kfuse-ingress-nginx-controller.

Contact us at info@kloudfuse.com, if help is needed for setting up https on the external endpoint.

Create EventBridge Connection

  • Go to the EventBridge console

    • In the navigation pane, choose API destinations.

    • Choose the Connections tab, and then choose Create connection.

    • For Destination type, choose Other

    • For Authorization type, choose API key.

    • For API key name, enter KFUSE-API-KEY.

    • For Value, enter KFUSE-API-VALUE.

    • Choose Create.

Create EventBridge API Destination

  • Go to the EventBridge console

    • In the navigation pane, choose API destinations.

    • Choose Create API destination.

    • Enter a name and description for the API destination.

    • For API destination endpoint, enter https://<external facing endpoint of Kfuse cluster>/ingester/eventbridge.

    • For HTTP method, choose POST.

    • For Connection, choose Use an existing connection and choose the connection you created in step 1.

    • Choose Create.

Create EventBridge Rule

  • Go to the EventBridge console

    • In the navigation pane, choose Rules.

    • Choose Create rule.

    • Enter a name and description for the rule.

    • For Event bus, choose default.

    • For Rule type, choose Rule with an event pattern.

    • Choose Next.

    • For Event source, choose Other.

    • For Event pattern, enter the following to send everything (Note the pattern can be changed to match specific events):

      {
        "source": [{
          "exists": true
        }]
      }

    • Choose Next.

    • For Target types, choose EventBridge API destination.

    • For API destination, choose Use an existing API destination, and then choose the destination you created in step 2.

    • For Execution role, choose Create a new for role for this specific resource.

    • Choose Next.

    • Choose Next.

    • Review the details of the rule and choose Create rule.

  • No labels