You can now use the Amazon S3 source when running Adobe Experience Platform on Amazon Web Services (AWS). Experience Platform running on AWS is currently available to a limited number of customers. To learn more about the supported Experience Platform infrastructure, see the Experience Platform multi-cloud overview.
Adobe Experience Platform provides native connectivity for cloud providers like AWS, Google Cloud Platform, and Azure. You can bring your data from these systems into Experience Platform.
Cloud storage sources can bring your own data into Experience Platform without the need to download, format, or upload. Ingested data can be formatted as XDM JSON, XDM Parquet, or delimited. Every step of the process is integrated into the Sources workflow. Experience Platform allows you to bring in data from S3 through batches.
Follow the steps below to learn how you can set up your Amazon S3 account for Experience Platform on Azure.
A list of IP addresses must be added to an allow list prior to working with source connectors. Failing to add your region-specific IP addresses to your allow list may lead to errors or non-performance when using sources. See the IP address allow list page for more information.
The following is a list of constraints you must account for when naming your cloud storage file or directory.
/
). If provided, it will be automatically removed.! ' ( ) ; @ & = + $ , % # [ ]
" \ / : | < > * ?
.\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.To ingest a single directory with S3, you must create an Identity and Access Management (IAM) user for 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
.
You can connect Amazon S3 with temporary security credentials using the s3SessionToken
. This allows you to connect Amazon S3 to 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.
This section applies to implementations of Experience Platform running on Amazon Web Services (AWS). Experience Platform running on AWS is currently available to a limited number of customers. To learn more about the supported Experience Platform infrastructure, see the Experience Platform multi-cloud overview.
Follow the steps below to learn how you can set up your Amazon S3 account for Experience Platform on Amazon Web Services (AWS).
To connect your Amazon S3 account to Experience Platform on AWS, you must have the following:
s3:GetObject
and s3:ListBucket
actions.You must configure the necessary permissions in your Amazon S3 bucket to successfully ingest data from an AWS region. The policy of the bucket that you want to access must be associated with the credentials that you are using.
Follow the steps below to update your Amazon S3 bucket:
Ensure that you update the value for AWS
with your IAM role and the value for Resource
with your Amazon S3 bucket or folder.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AEP Get Object Related Policy Prod",
"Effect": "Allow",
"Principal": {
"AWS": "{IAM_ROLE_TO_ALLOW_LIST}"
},
"Action": "s3:Get*",
"Resource": "arn:aws:s3:::{YOUR_BUCKET_NAME}/{YOUR_FOLDER_NAME}"
},
{
"Sid": "AEP List Bucket Prod",
"Effect": "Allow",
"Principal": {
"AWS": "{IAM_ROLE_TO_ALLOW_LIST}"
},
"Action": "s3:ListBucket",
"Resource": "arn:aws:s3:::{YOUR_BUCKET_NAME}"
}
]
}
Once you have set up your permissions, return to the sources catalog in the Experience Platform UI and navigate to the Amazon S3 source set up page. Provide the name of the Amazon S3 bucket that you want to connect to and if applicable, provide the path to the specific folder within the bucket. To verify your set up, select Test connection. If successful, you can then proceed and create a dataflow to ingest cloud storage data to Experience Platform.
The documentation below provides information on how to connect Amazon S3 to Experience Platform using APIs or the user interface: