AI-generated summary
Genesys Cloud accesses AWS S3 functions through a structured IAM policy and role configuration process that enables secure integration between the two platforms. The integration requires creating an IAM policy that designates S3 as the service and grants specific permissions: PutObject for write access, GetBucketLocation and GetEncryptionConfiguration for read access, and PutObjectAcl for permission management on a designated S3 bucket. The policy must specify the bucket name and allow actions on any object within that bucket.
An IAM role must be established with "Another AWS Account" as the trusted entity type, using Genesys Cloud's production account ID (765628985471 for Core/Satellite regions, or the appropriate FedRAMP region account ID for US-East-2). The role configuration requires an external ID matching the organization's Genesys Cloud organization ID for trusted entity verification. Users must verify that the trusted entity account number matches the Genesys Cloud production AWS account ID before role creation. For FedRAMP region-specific account IDs, users should contact their Genesys representative.
Once the policy is attached to the role, Genesys Cloud can assume the role and access S3 capabilities for recording bulk actions integration. By default, exported files stored in the S3 bucket are encrypted using AWS Managed Keys (KMS). Genesys Cloud supports optional Customer Managed Key (CMK) functionality for export operations, allowing organizations to maintain enhanced security control over exported data. role creation and configuration, the AWS S3 Recording Bulk Actions Integration can be added to the Genesys Cloud environment