Naming constraints for files and directories
The following is a list of constraints you must account for when naming your cloud storage file or directory.
- Directory and file component names cannot exceed 255 characters.
- Directory and file names cannot end with a forward slash (
/
). If provided, it will be automatically removed. - The following reserved URL characters must be properly escaped:
! ' ( ) ; @ & = + $ , % # [ ]
- The following characters are not allowed:
" \ / : | < > * ?
. - Illegal URL path characters not allowed. Code points like
\uE000
, while valid in NTFS filenames, are not valid Unicode characters. In addition, some ASCII or Unicode characters, like control characters (0x00 to 0x1F, \u0081, etc.), are also not allowed. For rules governing Unicode strings in HTTP/1.1 see RFC 2616, Section 2.2: Basic Rules and RFC 3987. - The following file names are not allowed: LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, PRN, AUX, NUL, CON, CLOCK$, dot character (.), and two dot characters (…).
Configure permissions on Amazon S3
To ingest a single directory with S3, you must create an Identity and Access Management (IAM) user for Experience Platform in the S3 console and assign permissions for the following actions:
s3:GetObject
s3:GetObjectVersion
The following permissions are also required for exploring and testing connectivity:
s3:ListAllMyBuckets
s3:ListBucket
s3:GetBucketLocation
A file path like myBucket/folder/subfolder/subsubfolder/abc.csv
may lead you to only access subsubfolder/abc.csv
. If you want to access the subfolder, you can specify the bucket
parameter in your S3 console as myBucket
and the folderPath
as folder/subfolder
to ensure that file exploration starts at subfolder
as opposed to subsubfolder/abc.csv
.
Use temporary security credentials to connect Amazon S3
You can connect Amazon S3 with temporary security credentials using the s3SessionToken
. This allows you to connect Amazon S3 to Experience Platform without having to create permanent IAM credentials with Amazon Web Services, or provide access to your Amazon S3 bucket to users in untrusted environments.
Temporary security credentials work similarly to regular, long-term access key credentials, except you can configure a shorter expiry date for your temporary credentials. Expirations can be set to a few minutes after activation or up to several hours. Temporary credentials are also not contained with the user. This means that you must request for a new set of temporary credentials, when they expire.
For steps on how to generate your temporary session token, see this AWS document on temporary session tokens.
Set up your Amazon S3 source for Experience Platform on Amazon Web Services
Follow the steps below to learn how you can set up your Amazon S3 account for Experience Platform on Amazon Web Services (AWS).