The Athena source table stores the value B0FYDPFAAA
Our Lambda code contains no “SWIFT” strings at all (verified via grep)
Direct Lambda invoke returns Sample ASIN：B0FYDPFAAA
The same Lambda behind the same Gateway displays the ASIN correctly on the AmzSdoRbsArts Quick account
On amazonbi, identical inputs sometimes render correctly and sometimes get masked (non-deterministic)
Since the data is correct at every hop up to and including the Lambda response, the masking must be happening on the Quick output side. [SWIFT_CODE] matches the standard AWS Comprehend PII entity type, so we suspect amazonbi has an output-side PII masking guardrail enabled that misidentifies 10-character alphanumeric ASINs as SWIFT/BIC bank codes.
Questions:
Is PII detection/masking enabled on Flow/MCP connector outputs for the amazonbi account?
If so, can the SWIFT_CODE entity type be removed from the masking list, or can specific connector outputs be exempted?
Based on what you have stated your diagnosis makes a lot of sense. The [SWIFT_CODE] tag matches standard PII entity-type masking behavior, and ASINs like B0FYDPFAAA (10-character alphanumeric) fall within the character range that SWIFT/BIC code detectors target (8–11 alphanumeric characters). The non-deterministic behavior is also consistent with ML-based PII detection, which is context-dependent and won’t always fire on the same input.
Moreover, it is interesting that the same connector works correctly on the AmzSdoRbsArts Quick account. Due to that, something is happening behind the scenes, and I would recommend creating a support ticket and the support team will be able to further investigate into this issue. Please refer to this resource on how to create a support ticket (Case management - AWS Support).
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime. Moreover, if you submitted a support ticket and it uncovered any findings, please feel free to share them!
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
Since I haven’t received any further updates from you, I’ll treat this inquiry as complete at this time. Please feel free to create a new post if you have more questions.
