When you use AWS CodeCommit from within Visual Studio, your traditional AWS credentials are used for working with the service itself, for example, when you’re creating and listing repositories. Note that you can delete and recreate credentials at any time. You can create up to two sets of these credentials for the service and, although you can mark a set of credentials as inactive, inactive sets still count toward your limit of two sets. You cannot create them for a root account. You can create the Git credentials for AWS CodeCommit only for Identity and Access Management (IAM) user accounts. You can read about these kinds of credentials (a user name and password) at Setup for HTTPS Users Using Git Credentials in the AWS CodeCommit user guide. However, to work with Git itself we need additional credentials, specifically, Git credentials for HTTPS connections. The integration of AWS CodeCommit with Team Explorer also uses these credential profiles. These credential profiles are used in the Toolkit for Visual Studio to enable the Toolkit to call service APIs on your behalf, for example, to list your Amazon S3 buckets in AWS Explorer or to launch an Amazon EC2 instance.
If you’re an existing user of the AWS Toolkit for Visual Studio, you’re aware of setting up AWS credential profiles that contain your access and secret keys.
In this post, we take a look at getting started with setting up credentials, and then how to create and clone repositories from within Team Explorer. We recently announced support for new features in the AWS Toolkit for Visual Studio that make working with AWS CodeCommit repositories easy and convenient from within Visual Studio Team Explorer.
0 kommentar(er)
