Feature Request: Use Cognito Federated Pool IDs

Some of the other packages use Cognito Federated Pool IDs. I find these easier to manage than passing through access keys and secret keys. Could you add the option to use a cognito pool id instead of the access and secret keys?

The client does not talk to Cognito — it signs requests with AWS credentials.
The usual way to combine the two is to exchange the Cognito identity for
temporary S3 credentials (STS AssumeRoleWithWebIdentity) and hand those to
the client. In the fork they can be supplied through a provider callback, so
they can be renewed while the application runs:

credentialsProvider: () async {
  final credentials = await exchangeCognitoIdentityForS3Credentials();
  return MinioCredentials(
    accessKey: credentials.accessKey,
    secretKey: credentials.secretKey,
    sessionToken: credentials.sessionToken,
  );
},

This ships in zuraffa_minio — the maintained fork of this package, which upstream has not touched since August 2025.

The fork keeps the API of the original package unchanged, so moving over is an import swap:

// before
import 'package:minio/minio.dart';
// after
import 'package:zuraffa_minio/minio.dart';

Source, the changelog and the sweep of the open issues of this tracker: https://github.com/arrrrny/zuraffa_minio

Navigation Menu

Repository navigation

Feature Request: Use Cognito Federated Pool IDs #47

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Feature Request: Use Cognito Federated Pool IDs #47

Description

Activity

arrrrny commented on Oct 22, 2026

arrrrny commented on Oct 22, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions