AWS .NET Modernization Tools Porting Assistant (PA) for .NET, AWS App2Container (A2C), AWS Toolkit for .NET Refactoring (TR), and AWS Microservice Extractor (ME) for .NET is no longer open to new customers. If you would like to use the service, sign up prior to November 7, 2025. Alternatively use AWS Transform
AWS Identity and Access Management (IAM)
If you use Toolkit for .NET Refactoring with a license included Visual Studio Amazon Machine Image
(AMI) on Amazon EC2, you can use the
refactoringtoolkit-RefactoringToolkitCallerRole without providing credentials
or modifying configuration files. For more information, see Install Toolkit for .NET Refactoring
in this guide.
If you are not using Toolkit for .NET Refactoring with Amazon EC2 or if you prefer to create a user and assign roles to the user, follow the steps in this section to create the user, create access keys, and configure your AWS profile.
Sign up for an AWS account
To get started with AWS, you need an AWS account. For information about creating an AWS account, see Getting started with an AWS account in the AWS Account Management Reference Guide.
Create access keys for your user
Users need programmatic access if they want to interact with AWS outside of the AWS Management Console. The way to grant programmatic access depends on the type of user that's accessing AWS.
To grant users programmatic access, choose one of the following options.
| Which user needs programmatic access? | To | By |
|---|---|---|
| IAM | (Recommended) Use console credentials as temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |
Following the instructions for the interface that you want to use.
|
|
Workforce identity (Users managed in IAM Identity Center) |
Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |
Following the instructions for the interface that you want to use.
|
| IAM | Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions in Using temporary credentials with AWS resources in the IAM User Guide. |
| IAM | (Not recommended) Use long-term credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |
Following the instructions for the interface that you want to use.
|
Configure your AWS profile
After you have created a user, you can configure your AWS named profile to apply settings and credentials to be applied when you run commands.
Configure AWS profile in the assessment tool
-
In the Toolkit for .NET Refactoring assessment tool, navigate to Set up Toolkit for .NET Refactoring.
-
Choose Add a profile under AWS named profile.
-
Enter your new Profile name, AWS access key ID, and AWS secret access key.
-
Choose Add.
Configure AWS profile using the AWS CLI
-
Run the following AWS CLI command to create a profile for Toolkit for .NET Refactoring. The profile is named
defaultin the credentials file.aws configure -
For each prompt, enter the corresponding information.
-
AWS Access Key ID -
AWS Secret Access Key -
Default region name(For example,us-west-2) -
Default output format
-
-
After you configure the profile using the AWS CLI, Toolkit for .NET Refactoring will display the
defaultprofile under AWS named profile on the Set up Toolkit for .NET Refactoring page of the assessment tool.
For more information about configuring the AWS CLI, see Configuring the AWS CLI in the AWS CLI User Guide.