Account A must put events onto an EventBridge event bus in Account B for a multi-account city services mesh. What must be true?
Select an answer to reveal the explanation.
Short Explanation
Cross-account EventBridge is a two-sided handshake: the producer needs permission, and Account B’s bus policy has to welcome that principal. Matching detail-type text does not erase account walls. Public writable buses are not the pattern.
Full Explanation
Cross-account event delivery requires authorization on both sides: the caller needs permission to PutEvents to the target bus, and the destination account’s event bus resource policy must allow the external principal. Detail-type matching is filtering, not authorization. Public anonymous writable buses are not an appropriate microservice auth pattern.