Integrate with Amazon SNS without IAM User Credentials
Pega OOTB SMS account has configurations with Amazon SNS account user credentials with key, secret and sender id. But our enterprise AWS account does not allow IAM users. Policy requires that all AWS logins must be federated thru IAM roles.
Is there any way to integrate with Amazon SNS using IAM roles instead of static IAM user credentials? Please provide any recommendation or suggestions.
Updated: 31 Dec 2024 6:20 EST
Pegasystems Inc.
GB
@SriK3119 are you following the documentation?
Configuring an outbound SMS account
Creating Kinesis Data Sets as profile data sources
I am unable to find reference to AWS Identity and Access Management roles used for the managed service Amazon Simple Notification Service. MSK, or Amazon Managed Streaming for Apache Kafka, is an external Kafka that the Pega Platform can connect to. Pega can connect to any external Kafka, but it doesn't support vendor-specific security features like IAM roles.
HCA Healthcare
US
To integrate Pega with Amazon SNS without using static IAM user credentials, you can configure the integration to use IAM roles with AWS Security Token Service (STS). First, set up an IAM role with the necessary permissions for SNS and configure trust relationships to allow Pega's service or application to assume the role. Then, use temporary credentials generated by AWS STS when the role is assumed, rather than static keys. Pega can call AWS services using these temporary credentials by configuring the AWS SDK or custom code to assume the IAM role during runtime. This approach adheres to enterprise policies requiring federated access while maintaining secure and dynamic credential management.