Mapping File

Mon, 01 Jan 0001 00:00:00 +0000

Overview

S3 Protector uses a mapping.json file to determine how columns in the source file are mapped to Protegrity data elements for protection. The Lambda resolves the mapping file location using the following precedence order (highest to lowest):

Priority	Source	Description
1 — S3 Object Tag	AWS S3 object tag `MAPPING_LOCATION` on the source file	If the source S3 object has a tag with the key `MAPPING_LOCATION`, its value is used to locate the mapping file. The value can be a full S3 URI (`s3://bucket/path/to/mapping.json`) pointing to an exact file, or a bucket name for a hierarchical folder walk. This takes precedence over all other methods. Requires `s3:GetObjectTagging` permission on the source bucket.
2 — `MAPPING_CONFIG_BUCKET` (mirror bucket)	`MAPPING_CONFIG_BUCKET` environment variable	When set, S3 Protector looks for the mapping file in this dedicated bucket, using the same folder path as the source file (mirroring the source bucket’s folder structure). Use this to centralise mapping files without tagging every individual object or using source bucket.
3 — Source bucket	Source S3 bucket (used by default)	If neither a tag nor `MAPPING_CONFIG_BUCKET` resolves a mapping file, S3 Protector falls back to loading `mapping.json` from the same bucket and folder as the source file.

Using S3 Object Tags for Mapping File Resolution

Add a tag to the source S3 object to point to a specific mapping file. The tag key is always MAPPING_LOCATION. The tag value supports two formats:

Column Mapping Rules

Mon, 01 Jan 0001 00:00:00 +0000

Common Error Conditions

The table below summaries common error conditions that may occur when creating a ‘mapping.json’ file:

Mapping	Error Message
A column name appears in ‘mapping.json’ but does not exist in the source file.	Columns [‘column name’] in the mapping file have no matches in the input data columns
Source file column name appears neither in ‘columns’ nor ‘ignored-columns’ sections.	Input file contains data columns which are not defined in the mapping file.
Source file column name appears in both ‘columns’ and ‘ignored-columns’ sections.	Ignored column [‘column-name’] is present in ‘columns’ list. Column must be defined in either ‘columns’ or ‘ignored-columns’, but not both.
Source file column name appears more than once in either ‘columns’ or ‘ignored-columns’ section.	Duplicate column [“column-name”] found in ‘ignored-columns’.

Note