AWS EventBridge作为Lambda目标

如何解决AWS EventBridge作为Lambda目标

我有两个Lambda函数，一个EventProducer和一个EventConsumer。所需的场景如下：EventProducer在自定义AWS EventBridge总线中添加事件，并且EventConsumer读取事件。

我想使用Lambda目标实现此目标，但EventBridge似乎无法正常工作。 我已经通过显式调用AmazonEventBridge :: putEvent推送事件来使事件对消费者可用，但是我没有通过返回输出并发送输出来做到这一点。

如果我使用Lambda或SQS作为目的地而不是EventBridge，则该代码有效。当我使用AWS CLI发送消息时，消费者也会读取消息。

有人有使用Lambda目标从Lambda函数在EventBridge中推送事件的可行示例吗？

我的代码如下：

Handler code:

@Override
public void handleRequest(InputStream input,OutputStream output,Context context) throws IOException {
        DataciteDoiRequest sentDirectly = newDataciteDoiRequest();
        logger.info(lOG_HANDLER_HAS_RUN);
        putEventDirectlyToEventBridge(sentDirectly); 

        DataciteDoiRequest sentThroughLambdaDestination =
            sentDirectly.copy().withPublicationId(URI.create("https://localhost/fromOutputStream")).build();
        writeOutput(sentThroughLambdaDestination,output);
    }

    private <I> void writeOutput(I event,OutputStream outputStream)
        throws IOException {
        try (BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(outputStream))) {
            String responseJson = Optional.ofNullable(objectMapper.writeValueAsString(event))
                .map(StringUtils::replaceWhiteSpacesWithSpace)
                .map(StringUtils::removeMultipleWhiteSpaces)
                .orElseThrow();
            logger.info(responseJson);
            writer.write(responseJson);
        }
    }

    private void putEventDirectlyToEventBridge(DataciteDoiRequest dataciteDoiRequest) {
        PutEventsRequestEntry putEventsRequestEntry = new PutEventsRequestEntry()
            .withDetail(dataciteDoiRequest.toString())
            .withEventBusName(environment.readEnv(EVENT_BUS_ENV_VAR))
            .withSource(SOURCE)
            .withDetailType(dataciteDoiRequest.getType());

        PutEventsRequest putEventsRequest = new PutEventsRequest().withEntries(putEventsRequestEntry);
        eventBridgeClient.putEvents(putEventsRequest);
    }


CloudFormation template:

 EventConsumer:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: dynamo-event-to-datacite-request
      Handler: handlers.EventConsumer::handleRequest
      Runtime: java11
      MemorySize: 1400
      Role: !GetAtt LambdaRole.Arn
      Environment:
        Variables:
          EVENT_BUS: !GetAtt EventBus.Name
          AWC_ACCOUNT_ID: !Ref AWS::AccountId
      Events:
        EventBridgeEvent:
          Type: EventBridgeRule
          Properties:
            EventBusName: !GetAtt EventBus.Name
            Pattern: { "detail": { "type": [ "MyType" ] } }
  EventProducer:
    DependsOn:
      - EventBus
      - FailQueue
      - EventConsumer
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: dynamo-event-to-datacite-request
      Handler: handlers.EventProducer::handleRequest
      Runtime: java11
      MemorySize: 1400
      Role: !GetAtt LambdaRole.Arn
      EventInvokeConfig:
        DestinationConfig:
          OnSuccess:
            Type: EventBridge
            Destination: !GetAtt EventBus.Arn
          OnFailure:
            Type: SQS
            Destination: !GetAtt FailQueue.Arn

      Environment:
        Variables:
          EVENT_BUS: !GetAtt EventBus.Name
  EventBus:
    Type: AWS::Events::EventBus
    Properties:
      Name: orestis-event-bus
  FailQueue:
    Type: AWS::SQS::Queue
    Properties:
      MaximumMessageSize: 262144
      QueueName: orestis-failure-queue

解决方法

您的EventConsumer Events -config对我而言似乎不正确的EventBridgeRule。 模式缺少来源-属性。这应该与您的发件人使用的源名称相匹配。此外，如果您使用“详细信息” 属性来区分不同的事件类型，则该属性应为“详细信息类型” ：https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-events-rule.html

如果您这样编写事件-config（在Yaml中全部使用），该怎么办？

std::shared_ptr<S> ps = std::make_shared<S>();
auto& s = *ps; // Keep a reference to the S.
auto p = std::shared_ptr<S>(ps,nullptr); // Aliasing c'tor with null pointer.
//ps = nullptr;
assert(ps != nullptr);
assert(p == nullptr);
cout << ps.use_count() << endl; // prints 2
cout << p.use_count() << endl; // prints 2
foo(s); //< S is still alive here