You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the AWS CodeCommit migration page, the users no longer need to provide https_git_credentials_password and https_git_credentials_username along with aws_access_key_id and aws_secret_access_key to form the remote clone Url. Just AWS credentials are already enough to derive the git auth username and password, by using aws_access_key_id as username and {amazonDateStr}Z{AWSSigv4Signature} as password.
This feature simplifies the process of gathering credentials from AWS for the migration, and also, reduces the confusion to users as to why they need to generate both HTTP (normal git credentials) and AWS Credentials at the same time.
Feature Description
Proposal
In the AWS CodeCommit migration page, the users no longer need to provide
https_git_credentials_password
andhttps_git_credentials_username
along withaws_access_key_id
andaws_secret_access_key
to form the remote clone Url. Just AWS credentials are already enough to derive the git auth username and password, by usingaws_access_key_id
as username and{amazonDateStr}Z{AWSSigv4Signature}
as password.This feature simplifies the process of gathering credentials from AWS for the migration, and also, reduces the confusion to users as to why they need to generate both HTTP (normal git credentials) and AWS Credentials at the same time.
The AWS already has a mechanism and tool for such features to derive the clone URL by just using AWS IAM credentials. The references are source and https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-git-remote-codecommit.html
The PR I will create is based on the implementation of the tool.
Screenshots
The text was updated successfully, but these errors were encountered: