Skip to content

Using STS assume role with persistent secret fails #132

Description

@kekwan

I have the following persistent secret configured on session initialization.

CREATE OR REPLACE PERSISTENT SECRET persistent_credential_chain (
      TYPE s3,
      PROVIDER credential_chain,
      CHAIN 'sts',
      assume_role_arn 'arn:aws:iam::x:role/my-role',
      external_id 'generic-role',
      region 'us-west-2'
  );

This configuration results in the following error.

Exception thrown while trying to refresh secret persistent_credential_chain. To fix this, please recreate or remove the secret and try again. Error: 'Invalid Input Error: Cannot create temporary secrets in a persistent secret storage!'

This looks like a bug to me. When using sts, credentials are automatically refreshed and it seems that it replace existing credentials with persistent storage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions