Integrating the AWS Security Token Service (STS) with Data Fabric
Describes how the HPE Ezmeral Data Fabric can access AWS services by using the Security Token Service (STS) rather than a secret key and access key.
Data Fabric releases 7.5 and later support importing an external S3 object store into the global namespace. This feature requires the user to provide an access key and secret key to access the external S3 object store.
With release 7.7.0, Data Fabric provides an option for
gaining access to AWS S3 object stores. You can import an external AWS S3 server by
using the maprcli clustergroup addexternal
command and specifying an
Amazon Resource Name (ARN) to enable STS authentication. For configuration steps, see
Configuring STS for Data Fabric.
With release 7.8.0, you can use the Data Fabric UI to enable STS authentication and specify the ARN when you import the external S3 object store. See Importing an External S3 Object Store.
Using STS simplifies the process of accessing AWS services by using STS tokens for authentication. With STS tokens, the Data Fabric user can assume an AWS role and get temporary credentials to perform S3 actions. Once the external S3 object store is imported into the global namespace, all S3 operations automatically use STS.
How STS Works with Keycloak and Data Fabric
- The user logs in to the Data Fabric.
- Keycloak authenticates the user and generates a JWT token for the user.
- The Data Fabric requests a temporary access key and secret key for the user using the Keycloak JWT token from STS.
- STS verifies the token validity.
- If the token is valid, STS responds with temporary credentials to access the user's AWS account.
- Data Fabric accesses the user account to perform the infrastructure or S3 actions.
Limitations for STS Support
- The option to use STS when importing an S3 object store is available only for AWS S3 object stores. Non-AWS S3 object stores may not use STS with Data Fabric.
- Enabling STS requires Keycloak to be deployed on a public network IP address so that AWS STS can communicate with Keycloak and verify that the JWT tokens are from the Data Fabric software. If your Keycloak deployment resides on an intranet and is not reachable by a public network, you cannot use STS. However, you can still use the access key and secret key import method.