The triple asterisks you're seeing in the generated URL are likely placeholders for sensitive information, such as your AWS access key and security token. GitHub Actions automatically masks these values to prevent exposing sensitive data in your workflow logs for security reasons.

To make these presigned S3 URLs usable by your developers without exposing sensitive information, you can consider the following approaches:

-Use GitHub Secrets: Store your AWS access key and security token as secrets in your GitHub repository. Then, you can reference these secrets in your GitHub Actions workflow.

Define secrets in your GitHub repository settings, such as AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.

Modify your workflow to use these secrets when generating the presigned URL:

By using secrets and setting env in the workflow step, you can securely access your AWS credentials and generate the presigned URL.

-AWS IAM Roles: Consider using AWS IAM roles with temporary credentials instead of long-term access keys. This way, you can grant your GitHub Actions workflow temporary access to your S3 bucket without needing to store access keys in GitHub Secrets.

Create an IAM role in AWS with the necessary permissions for your S3 bucket.

In your GitHub Actions workflow, use the aws-actions/configure-aws-credentials action to assume the IAM role and obtain temporary credentials. You won't need to set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in this case.

Here, the first option is more convenient for your developers, as they don't need to log in to AWS manually, and it keeps the sensitive information securely stored in GitHub Secrets. However, ensure that you follow AWS security best practices when managing secrets and access credentials.

@jjwatson Did you manage to solve that? I'm having something similar

Hi, having the same issue. Is there a workaround for this?