# Security in AWS Transform
Cloud security at AWS is the highest priority. As an AWS customer, you benefit from data centers and network architectures that are built to meet the requirements of the most security-sensitive organizations.
Security is a shared responsibility between AWS and you. The [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) describes this as security *of* the cloud and security *in* the cloud:
+ **Security of the cloud** – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the effectiveness of our security as part of the [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/). To learn about the compliance programs that apply to AWS Transform, see [AWS Services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/).
+ **Security in the cloud** – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations.
This documentation helps you understand how to apply the shared responsibility model when using AWS Transform. The following topics show you how to configure AWS Transform to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your AWS Transform resources.
**Topics**
+ [Data protection in AWS Transform](data-protection.md)
+ [Identity and access management for AWS Transform](security-iam.md)
+ [Compliance validation for AWS Transform](compliance-validation.md)
+ [Resilience in AWS Transform](disaster-recovery-resiliency.md)
+ [AWS Transform and interface endpoints (AWS PrivateLink)](vpc-interface-endpoints.md)
+ [Accessing the AWS Transform WebApp from a VPC](vpc-webapp-access.md)
# Data protection in AWS Transform
The AWS [shared responsibility model](http://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in AWS Transform. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the [Data Privacy FAQ](http://aws.amazon.com/compliance/data-privacy-faq). For information about data protection in Europe, see the [AWS Shared Responsibility Model and GDPR](http://aws.amazon.com/blogs/security/the-aws-shared-responsibility-model-and-gdpr) blog post on the *AWS Security Blog*.
For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS Identity and Access Management (IAM). That way each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:
+ Use multi-factor authentication (MFA) with each account.
+ Use SSL/TLS to communicate with AWS resources. We recommend TLS 1.2 or later.
+ Set up API and user activity logging with AWS CloudTrail.
+ Use AWS encryption solutions, along with all default security controls within AWS services.
+ Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3.
+ If you require FIPS 140-2 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see [Federal Information Processing Standard (FIPS) 140-2](http://aws.amazon.com/compliance/fips/).
We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into [tags](https://docs.aws.amazon.com/tag-editor/latest/userguide/security_data-protection.html) or free-form text fields such as a **Name** field. This includes when you work with AWS Transform or other AWS services using the AWS Management Console, API, AWS Command Line Interface (AWS CLI), or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. For more information about how AWS Transform uses content, see [AWS Transform service improvement](service-improvement.md).
AWS Transform stores your questions, its responses, and additional context, such as console metadata and code in your IDE, to generate responses to your questions. For information about how data is encrypted, see [Data encryption in AWS Transform](data-encryption.md). For information about how AWS may use some questions that you ask AWS Transform and its responses to improve our services, see [AWS Transform service improvement](service-improvement.md).
In AWS Transform, your data is stored in the AWS Region where your AWS Transform profile was created.
With cross-inferencing, your requests to AWS Transform may be processed in a different Region within the geography where your data is stored. For more information, see [Cross-Region inference](cross-region-processing.md#cross-region-inference).
**Topics**
+ [Cross-region processing in AWS Transform](cross-region-processing.md)
+ [Data encryption in AWS Transform](data-encryption.md)
+ [AWS Transform service improvement](service-improvement.md)
# Cross-region processing in AWS Transform
The following sections describe how cross-region inference and cross-region calls are used to provide the AWS Transform service.
## Cross-region inference
AWS Transform is powered by Amazon Bedrock, and uses cross-region inference to distribute traffic across different AWS Regions to enhance large language model (LLM) inference performance and reliability. With cross-region inference, you get:
+ Increased throughput and resilience during high demand periods
+ Improved performance
+ Access to newly launched AWS Transform capabilities and features that rely on the most powerful LLMs hosted on Amazon Bedrock
Cross-region inference requests are kept within the AWS Regions that are part of the geography where the data originally resides. For example, a request made from a AWS Transform configuration in the US is kept within the AWS Regions in the US. Although cross-region inferencing doesn’t change where your data is stored, your requests and output results may move outside of the Region where the data originally resides. All data will be encrypted while transmitted across Amazon's secure network. There's no additional cost for using cross-region inference.
Cross region inference doesn’t affect where your data is stored. For information on where data is stored when you use AWS Transform, see [Data protection in AWS Transform](data-protection.md).
### Supported regions for AWS Transform cross-region inference
Certain requests you make to AWS Transform might require cross-region calls. The following table describes what Regions your requests may be routed to depending on the geography where the request originated.
| Source Region | Destination Regions |
| --- | --- |
| US East (N. Virginia) (us-east-1) | US East (N. Virginia) (us-east-1)US East (Ohio) (us-east-2)US West (Oregon) (us-west-2) |
| Europe (Frankfurt) (eu-central-1) | Europe (Frankfurt) (eu-central-1)Europe (Stockholm) (eu-north-1)Europe (Milan) (eu-south-1)Europe (Spain) (eu-south-2)Europe (Ireland) (eu-west-1)Europe (Paris) (eu-west-3) |
| Asia Pacific (Mumbai) (ap-south-1) | Asia Pacific (Tokyo) (ap-northeast-1)Asia Pacific (Seoul) (ap-northeast-2)Asia Pacific (Osaka) (ap-northeast-3)Asia Pacific (Mumbai) (ap-south-1)Asia Pacific (Hyderabad) (ap-south-2)Asia Pacific (Singapore) (ap-southeast-1)Asia Pacific (Sydney) (ap-southeast-2)Asia Pacific (Melbourne) (ap-southeast-4) |
| Asia Pacific (Tokyo) (ap-northeast-1) | Asia Pacific (Tokyo) (ap-northeast-1)Asia Pacific (Osaka) (ap-northeast-3) |
| Asia Pacific (Seoul) (ap-northeast-2) | Asia Pacific (Tokyo) (ap-northeast-1)Asia Pacific (Seoul) (ap-northeast-2)Asia Pacific (Osaka) (ap-northeast-3)Asia Pacific (Mumbai) (ap-south-1)Asia Pacific (Hyderabad) (ap-south-2)Asia Pacific (Singapore) (ap-southeast-1)Asia Pacific (Sydney) (ap-southeast-2)Asia Pacific (Melbourne) (ap-southeast-4) |
| Asia Pacific (Sydney) (ap-southeast-2) | Asia Pacific (Sydney) (ap-southeast-2)Asia Pacific (Melbourne) (ap-southeast-4) |
| Europe (London) (eu-west-2) | Europe (Frankfurt) (eu-central-1)Europe (Stockholm) (eu-north-1)Europe (Milan) (eu-south-1)Europe (Spain) (eu-south-2)Europe (Ireland) (eu-west-1)Europe (London) (eu-west-2)Europe (Paris) (eu-west-3) |
| Canada (Central) (ca-central-1) | Commercial AWS Regions \$1 Canada (Central) (ca-central-1) |
For a complete list of Regions where you can use AWS Transform, see [Supported Regions for AWS Transform](regions.md).
## Cross-Region knowledge
When you ask a general question about AWS Transform services, transformation workflows, or related AWS documentation, AWS Transform might make cross-region requests to US East (Virginia) (us-east-1) for US regions or Europe (Frankfurt) (eu-central-1) for all other regions to retrieve documentation and fulfill your request. For example, when you ask questions about how to use other AWS services such as Lambda, AWS Transform might make a cross-region call to retrieve relevant AWS documentation to respond to your question. The following table describes what Regions your requests may be routed to depending on the geography where the request originated.
| Source Region | Destination Regions |
| --- | --- |
| US East (N. Virginia) (us-east-1) | US East (N. Virginia) (us-east-1) |
| Europe (Frankfurt) (eu-central-1) | Europe (Frankfurt) (eu-central-1) |
| Europe (London) (eu-west-2) | Europe (Frankfurt) (eu-central-1) |
| Asia Pacific (Tokyo) (ap-northeast-1) | Europe (Frankfurt) (eu-central-1) |
| Asia Pacific (Sydney) (ap-southeast-2) | Europe (Frankfurt) (eu-central-1) |
| Asia Pacific (Seoul) (ap-northeast-2) | Europe (Frankfurt) (eu-central-1) |
| Asia Pacific (Mumbai) (ap-south-1) | Europe (Frankfurt) (eu-central-1) |
| Canada (Central) (ca-central-1) | Europe (Frankfurt) (eu-central-1) |
This setting is enabled by default. An account administrator can modify this setting. Disabling this feature results in the loss of access to features that require AWS Transform to retrieve knowledge from other regions. This might result in less accurate responses.
To disable cross-region calls made by AWS Transform:
1. When first setting up AWS Transform, navigate to the **Get Started** page and complete the configuration. For for an existing AWS Transform configuration, navigate to the **Settings** page.
1. Toggle **Enable cross-region calls to answer general AWS related questions** to the *off* position.
## AWS Transform for Windows cross-region inference
The following table shows the source Regions from which you can call the inference profile and the destination Regions to which the requests can be routed:
| Source Region | Inference Destination Regions |
| --- | --- |
| US East (N. Virginia) (us-east-1) | US East (N. Virginia) (us-east-1)US East (Ohio) (us-east-2)US West (Oregon) (us-west-2) |
| Europe (Frankfurt) (eu-central-1) | Europe (Frankfurt) (eu-central-1)Europe (Stockholm) (eu-north-1)Europe (Milan) (eu-south-1)Europe (Spain) (eu-south-2)Europe (Ireland) (eu-west-1)Europe (Paris) (eu-west-3) |
| Asia Pacific (Tokyo) (ap-northeast-1) | Asia Pacific (Tokyo) (ap-northeast-1)Asia Pacific (Osaka) (ap-northeast-3) |
| Asia Pacific (Sydney) (ap-southeast-2) | Asia Pacific (Sydney) (ap-southeast-2)Asia Pacific (Melbourne) (ap-southeast-4) |
| Asia Pacific (Seoul) (ap-northeast-2) | All commercial regions |
| Asia Pacific (Mumbai) (ap-south-1) | All commercial regions |
| Canada (Central) (ca-central-1) | All commercial regions |
## AWS Transform for Migrations cross-region inference
The following table shows the source Regions from which you can call the inference profile and the destination Regions to which the requests can be routed:
| Source Region | Inference Destination Regions |
| --- | --- |
| US East (N. Virginia) (us-east-1) | All commercial regions |
| Europe (Frankfurt) (eu-central-1) | All commercial regions |
| Europe (London) (eu-west-2) | All commercial regions |
| Asia Pacific (Tokyo) (ap-northeast-1) | Asia Pacific (Tokyo) (ap-northeast-1)Asia Pacific (Osaka) (ap-northeast-3) |
| Asia Pacific (Sydney) (ap-southeast-2) | Asia Pacific (Sydney) (ap-southeast-2)Asia Pacific (Melbourne) (ap-southeast-4) |
| Asia Pacific (Seoul) (ap-northeast-2) | All commercial regions |
| Asia Pacific (Mumbai) (ap-south-1) | All commercial regions |
| Canada (Central) (ca-central-1) | All commercial regions |
## AWS Transform Custom
AWS Transform custom is available in US East (N. Virginia) (us-east-1) and Europe (Frankfurt) (eu-central-1) and uses Amazon Bedrock geographic cross-region inference. This means that some of your calls might be routed to AWS Regions outside of your source region within the same geographic region. You can access AWS Transform custom features from workspaces deployed in supported regions.
| Source Region | Inference Destination Regions |
| --- | --- |
| US East (N. Virginia) (us-east-1) | US East (N. Virginia) (us-east-1)US East (Ohio) (us-east-2)US West (Oregon) (us-west-2) |
| Europe (Frankfurt) (eu-central-1) | Europe (Frankfurt) (eu-central-1)Europe (Stockholm) (eu-north-1)Europe (Milan) (eu-south-1)Europe (Spain) (eu-south-2)Europe (Ireland) (eu-west-1)Europe (Paris) (eu-west-3) |
| Europe (London) (eu-west-2) | n/a |
| Asia Pacific (Tokyo) (ap-northeast-1) | n/a |
| Asia Pacific (Sydney) (ap-southeast-2) | n/a |
| Asia Pacific (Seoul) (ap-northeast-2) | n/a |
| Asia Pacific (Mumbai) (ap-south-1) | n/a |
| Canada (Central) (ca-central-1) | n/a |
# Data encryption in AWS Transform
This topic provides information specific to AWS Transform about encryption in transit and encryption at rest.
AWS Transform provides encryption by default to protect sensitive customer data at rest with encryption using AWS owned keys.
## Encryption types
### Encryption in transit
Communication between customers and AWS Transform and between AWS Transform and its downstream dependencies is protected using TLS 1.2 or higher connections.
**Important**
When you [Connect a discovery account](https://docs.aws.amazon.com/transform-vmware-connect-discovery-account.html), AWS Transform creates an Amazon S3 bucket on your behalf in that account. That bucket does not have `SecureTransport` enabled by default. If you want the bucket policy to include secure transport you must update the policy. For more information, see [Security best practices for Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/security-best-practices.html).
### Encryption at rest
AWS Transform stores data at rest using Amazon DynamoDB and Amazon Simple Storage Service (Amazon S3). The data at rest is encrypted using AWS encryption solutions by default. AWS Transform encrypts your data with encryption using AWS owned keys from AWS Key Management Service (AWS KMS). You don’t have to take any action to protect the AWS managed keys that encrypt your data. For more information, see [AWS owned keys](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk) in the *AWS Key Management Service Developer Guide*.
| Data type | AWS-owned key encryption | Customer managed key encryption (Optional) |
| --- | --- | --- |
| Customer bucket data Customer inputs and outputs such as code and documentation stored in an Amazon S3 bucket | Enabled | Enabled |
| Artifact Store Intermediate artifacts as part of code transformation stored in an S3 bucket | Enabled | Enabled |
| Job Objective The customer's intent for the job stored in an Amazon S3 bucket | Enabled | Enabled |
| Chat messages Messages between the customer and AWS Transform stored in an Amazon S3 bucket | Enabled | Enabled |
| Chat Knowledge Base Indexed data relevant to AWS Transform and customer chat stored in Amazon OpenSearch and processed via AWS Bedrock | Enabled | Enabled |
Note: The customer can register their own Customer Managed Key (CMK) to be used for encrypting all of the above data types.
Customer managed keys are KMS keys in your AWS account that you create, own, and manage to directly control access to your data by controlling access to the KMS key. Only symmetric keys are supported. For information on creating your own KMS key, see [Creating keys](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html) in the *AWS Key Management Service Developer Guide*.
When you use a customer managed key, AWS Transform makes use of KMS grants, allowing authorized users, roles, or applications to use a KMS key. When an AWS Transform administrator chooses to use a customer managed key for encryption during configuration, a grant is created for them. This grant is what allows the end user to use the encryption key for data encryption at rest. For more information on grants, see [Grants in AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/grants.html).
#### AWS Owned Keys (Default)
**Note**
**AWS owned keys** — AWS Transform uses these keys by default to automatically encrypt personally identifiable data. You can't view, manage, or use AWS owned keys, or audit their use. However, you don't have to take any action or change any programs to protect the keys that encrypt your data. For more information, see AWS owned keys in the AWSKey Management Service Developer Guide.
Encryption of data at rest by default helps reduce the operational overhead and complexity involved in protecting sensitive data. At the same time, it enables you to build secure applications that meet strict encryption compliance and regulatory requirements.
While you can't disable this layer of encryption or select an alternate encryption type, you can add a second layer of encryption over the existing AWS owned encryption keys by choosing a customer managed key when you create your transformation:
#### Customer managed keys (Optional)
**Customer managed keys **— AWS Transform supports the use of a symmetric customer managed key that you create, own, and manage to add a second layer of encryption over the existing encryption using AWS owned keys. Because you have full control of this layer of encryption, you can perform such tasks as:
+ Establishing and maintaining key policies
+ Establishing and maintaining IAM policies and grants
+ Enabling and disabling key policies
+ Rotating key cryptographic material
+ Adding tags
+ Creating key aliases
+ Rotating key cryptographic material
+ Adding tags
+ Creating key aliases
+ Scheduling keys for deletion
+ For more information, see [customer managed key](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk) in the *AWS Key Management Service Developer Guide*.
**Note**
AWS Transform automatically enables encryption at rest using AWS owned keys to protect personally identifiable data at no charge. However, AWS KMS charges apply for using a customer managed key. For more information about pricing, see the [AWS Key Management Service pricing](https://docs.aws.amazon.com/kms/pricing/).
For more information on AWS KMS, see [What is AWS Key Management Service?](https://docs.aws.amazon.com/kms/latest/developerguide/overview.html)
### How AWS Transform uses grants in AWS Key Management Service
AWS Transform requires a grant to use your customer managed key.
When you create a [Resource Name] encrypted with a customer managed key, AWS Transform creates a grant on your behalf by sending a CreateGrant request to AWS Key Management Service. Grants in AWS Key Management Service are used to give AWS Transform access to a KMS key in a customer account.
AWS Transform requires the grant to use your customer managed key for the following internal operations:
+ Send [KMS API] requests to AWS KMS to verify that the symmetric customer managed KMS key ID entered when creating [Resource Name] is valid.
+ Send [KMS API] requests to AWS KMS to generate data keys encrypted by your customer managed key.
+ Send [KMS API] requests to AWS KMS to decrypt the encrypted data keys so that they can be used to encrypt your data.
You can revoke access to the grant, or remove the service's access to the customer managed key at any time. If you do, AWS Transform won't be able to access any of the data encrypted by the customer managed key, which affects operations that are dependent on that data. For example, if you attempt to get [Resource Name] from an encrypted [Resource Name]that AWS Transform can't access, then the operation would return an AccessDeniedException error.
## Create a customer managed key
You can create a symmetric customer managed key by using the AWS Management Console, or the AWS Key Management Service APIs.
To create a symmetric customer managed key, follow the steps for [Creating symmetric customer managed key](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html#create-symmetric-cmk) in the *AWS Key Management Service Developer Guide*.
To use your customer managed key with your AWS Transform resources, the following API operations must be permitted in the key policy:
kms:CreateGrant – Adds a grant to a customer managed key. Grants control access to a specified KMS key, which allows access to grant operations AWS Transform requires. For more information about [Using Grants](https://docs.aws.amazon.com/), see the *AWS Key Management Service Developer Guide*.
This allows AWS Transform to do the following:
+ Call [KMS API ([GenerateDataKeyWithoutPlainText](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateDataKeyWithoutPlaintext)/[GenerateDatakey](https://docs.aws.amazon.com//kms/latest/APIReference/API_GenerateDataKey)) to generate an encrypted data key and store it, because the data key isn't immediately used to encrypt.
+ Call [KMS API ([Decrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt))] to use the stored encrypted data key to access encrypted data.
+ Set up a retiring principal to allow the service to [RetireGrant](https://docs.aws.amazon.com//kms/latest/APIReference/API_RetireGrant).
+ [kms:DescribeKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_DescribeKey) – Provides the customer managed key details to allow [Service Name] to validate the key.
### Encryption for SQL modernization
During the [SQL Server modernization](sql-server-modernization.md) process AWS Transform creates resources in your account, such as EC2 instances, ECS clusters, ECR images and S3 objects. You have the option of providing a customer managed key to encrypt data in your account. You will need to tag your KMS key with key **CreatedFor** and value **AWSTransform** . This example policy lists the minimum permissions required in your key policy if you don’t have a default key policy. If you have a default key policy, you still need to manually update the KMS key in addition to your default key policy to allow ECS to use your key.
```
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::111122223333:root"
},
"Action": [
"kms:Decrypt",
"kms:GenerateDataKey"
],
"Resource": "*",
"Condition": {
"StringLike": {
"kms:ViaService": "s3.*.amazonaws.com",
"kms:EncryptionContext:aws-transform": "*"
},
"ArnLike": {
"aws:PrincipalArn": "arn:aws:iam::*:role/*AWSTransform*"
}
}
},
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::111122223333:root"
},
"Action": [
"kms:Decrypt",
"kms:GenerateDataKey",
"kms:GenerateDataKeyWithoutPlaintext",
"kms:ReEncrypt*"
],
"Resource": "*",
"Condition": {
"StringLike": {
"kms:ViaService": "ec2.*.amazonaws.com"
},
"ArnLike": {
"aws:PrincipalArn": "arn:aws:iam::*:role/*AWSTransform*"
}
}
},
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::111122223333:root"
},
"Action": "kms:CreateGrant",
"Resource": "*",
"Condition": {
"StringLike": {
"kms:ViaService": [
"ec2.*.amazonaws.com",
"ecr.*.amazonaws.com"
]
},
"Bool": {
"kms:GrantIsForAWSResource": "true"
},
"ArnLike": {
"aws:PrincipalArn": "arn:aws:iam::*:role/*AWSTransform*"
}
}
},
{
"Effect": "Allow",
"Principal": {
"Service": "fargate.amazonaws.com"
},
"Action": "kms:GenerateDataKeyWithoutPlaintext",
"Resource": "*",
"Condition": {
"StringLike": {
"kms:EncryptionContext:aws:ecs:clusterName": "AWSTransform*"
}
}
},
{
"Effect": "Allow",
"Principal": {
"Service": "fargate.amazonaws.com"
},
"Action": "kms:CreateGrant",
"Resource": "*",
"Condition": {
"StringLike": {
"kms:EncryptionContext:aws:ecs:clusterName": "AWSTransform*"
},
"ForAllValues:StringEquals": {
"kms:GrantOperations": "Decrypt"
}
}
}
]
```
### Encryption for database migration
During the database migration process, AWS Transform uses AWS Database Migration Service (DMS) to migrate your database data. You can optionally provide a customer managed key to encrypt your database data during migration.
The following policy contains three statements. The first statement grants root account permissions for the AWS KMS key. The second statement allows the connector role to validate the key during discovery. The third statement allows the connector role to use the key for DMS operations.
```
"Statement": [
{
"Sid": "Enable IAM User Permissions",
"Effect": "Allow",
"Principal": { "AWS": "arn:aws:iam::111122223333:root" },
"Action": "kms:*",
"Resource": "*"
},
{
"Sid": "Allow connector role to validate key during discovery",
"Effect": "Allow",
"Principal": { "AWS": "connector-role-arn" },
"Action": "kms:DescribeKey",
"Resource": "*"
},
{
"Sid": "Allow connector role to use key via DMS",
"Effect": "Allow",
"Principal": { "AWS": "connector-role-arn" },
"Action": [
"kms:CreateGrant",
"kms:Decrypt",
"kms:DescribeKey",
"kms:Encrypt",
"kms:GenerateDataKey*",
"kms:ReEncrypt*"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"kms:ViaService": "dms.us-east-1.amazonaws.com"
}
}
}
]
```
## Using customer managed KMS keys
After creating a customer managed KMS key, an AWS Transform administrator must provide the key in the AWS Transform console to use it to encrypt data.
To set up a customer managed key to encrypt data in AWS Transform, administrators need permissions to use AWS KMS.
To use functionality that is encrypted with a customer managed key, users need permissions to allow AWS Transform to access the customer managed key.
If you see an error related to KMS grants while using AWS Transform, you likely need to update your permissions to allow AWS Transform to create grants. To automatically configure the needed permissions, go to the AWS Transform console and choose **Update permissions** in the banner at the top of the page. In order to allow AWS Transform to create grants, you need to update the permissions on the AWS Transform console page.
## Allow AWS Transform access to customer managed keys
The following example policy statement grants users permissions to access features encrypted with a customer managed key by allowing AWS Transform access to the key. This policy is required to use AWS Transform if an administrator has set up a customer managed key for encryption.
**Note**
This information does not apply to SQL Server modernization deployment workflow using CMK.
```
"Statement": [
{
"Sid": "QKMSDecryptGenerateDataKeyPermissions",
"Effect": "Allow",
"Action": [
"kms:Decrypt",
"kms:GenerateDataKey",
"kms:GenerateDataKeyWithoutPlaintext",
"kms:ReEncryptFrom",
"kms:ReEncryptTo"
],
"Resource": [
"arn:aws:kms:arn:aws::111122223333:key/[[key_id]]"
],
"Condition": {
"StringLike": {
"kms:ViaService": [
"q.us-east-1.amazonaws.com"
]
}
}
}
]
```
# AWS Transform service improvement
To help AWS Transform provide the most relevant information, we may use certain content from AWS Transform, such as questions that you ask AWS Transform and its responses, for service improvement. This page explains what content we use and how to opt out.
## AWS Transform content used for service improvement
We may use certain content from AWS Transform for service improvement. AWS Transform may use this content, for example, to provide better responses to common questions, fix AWS Transform operational issues, for de-bugging, or for model training.
Content that AWS may use for service improvement includes, for example, your questions to AWS Transform and the responses and code that AWS Transform generates.
## How to opt out
The way you opt out of AWS Transform using content for service improvement depends on the environment where you use AWS Transform.
For AWS Transform configure an AI services opt-out policy in AWS Organizations. For more information, see [AI services opt-out policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_ai-opt-out.html) in the *AWS Organizations User Guide*.
To opt out of sharing your content in Visual Studio IDE, use the following procedure.
Go to **Tools** -> **Options** -> **AWS Toolkit** -> **Amazon Q**
Toggle **Share Amazon Q Content with AWS** to **True** or **False**.
To opt out of sharing your telemetry data in the AWS Toolkit for Visual Studio, use this procedure:
1. Under **Tools**, choose **Options**.
1. In the **Options** pane, choose **AWS Toolkit**, and then choose **General**.
1. Deselect **Allow AWS Toolkit to collect usage information**.
# Identity and access management for AWS Transform
AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use AWS Transform resources. IAM is an AWS service that you can use with no additional charge.
**Topics**
+ [Audience](#security_iam_audience)
+ [Authenticating with identities](#security_iam_authentication)
+ [Managing access using policies](#security_iam_access-manage)
+ [How AWS Transform works with IAM](security_iam_service-with-iam.md)
+ [Identity-based policy examples for AWS Transform](security_iam_id-based-policy-examples.md)
+ [Troubleshooting AWS Transform identity and access](security_iam_troubleshoot.md)
+ [Using service-linked roles for AWS Transform](using-service-linked-roles.md)
+ [AWS managed policies for AWS Transform](security-iam-awsmanpol.md)
+ [AWS Transform permissions reference](security_iam_permissions.md)
## Audience
How you use AWS Identity and Access Management (IAM) differs based on your role:
+ **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting AWS Transform identity and access](security_iam_troubleshoot.md))
+ **Service administrator** - determine user access and submit permission requests (see [How AWS Transform works with IAM](security_iam_service-with-iam.md))
+ **IAM administrator** - write policies to manage access (see [Identity-based policy examples for AWS Transform](security_iam_id-based-policy-examples.md))
## Authenticating with identities
Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role.
You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*.
For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*.
### AWS account root user
When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*.
### Federated identity
As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials.
A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials.
For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*.
### IAM users and groups
An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*.
An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*.
### IAM roles
An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.
IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Managing access using policies
You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*.
Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**.
By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation.
### Identity-based policies
Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*.
### Resource-based policies
Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.
Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy.
### Other policy types
AWS supports additional policy types that can set the maximum permissions granted by more common policy types:
+ **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*.
+ **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*.
+ **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*.
+ **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*.
### Multiple policy types
When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*.
# How AWS Transform works with IAM
Before you use IAM to manage access to AWS Transform, learn what IAM features are available to use with AWS Transform.
| IAM feature | AWS Transform support |
| --- | --- |
| [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes |
| [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No |
| [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes |
| [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes |
| [Policy condition keys](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes |
| [ACLs](#security_iam_service-with-iam-acls) | No |
| [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | Partial |
| [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes |
| [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes |
| [Service roles](#security_iam_service-with-iam-roles-service) | Yes |
| [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | Yes |
To get a high-level view of how AWS Transform and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Identity-based policies for AWS Transform
**Supports identity-based policies:** Yes
Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*.
### Identity-based policy examples for AWS Transform
To view examples of AWS Transform identity-based policies, see [Identity-based policy examples for AWS Transform](security_iam_id-based-policy-examples.md).
## Resource-based policies within AWS Transform
**Supports resource-based policies:** No
Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.
To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Policy actions for AWS Transform
**Supports policy actions:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation.
To see a list of AWS Transform actions, see [Actions, resources, and condition keys for AWS Transform ](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awstransform.html) in the *Service Authorization Reference*.
To see a list of actions for AWS Transform *custom*, see [Actions, resources, and condition keys for AWS Transform custom ](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awstransformcustom.html) in the *Service Authorization Reference*.
Policy actions in AWS Transform use the following prefix before the action:
```
transform
```
To specify multiple actions in a single statement, separate them with commas.
```
"Action": [
"transform:action1",
"transform:action2"
]
```
To view examples of AWS Transform identity-based policies, see [Identity-based policy examples for AWS Transform](security_iam_id-based-policy-examples.md).
## Policy resources for AWS Transform
**Supports policy resources:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources.
```
"Resource": "*"
```
To see a list of AWS Transform resource types and their ARNs, and with which actions you can specify the ARN of each resource, see [Actions, resources, and condition keys for AWS Transform ](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awstransform.html) in the *Service Authorization Reference*.
To see a list of resource types and their ARNs, and with which actions you can specify the ARN of each resource for AWS Transform *custom*, see [Actions, resources, and condition keys for AWS Transform custom ](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awstransformcustom.html) in the *Service Authorization Reference*.
To view examples of AWS Transform identity-based policies, see [Identity-based policy examples for AWS Transform](security_iam_id-based-policy-examples.md).
## Policy condition keys for AWS Transform
**Supports service-specific policy condition keys:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*.
To see a list of AWS Transform condition keys, and with which actions and resources you can use a condition key, see [Actions, resources, and condition keys for AWS Transform ](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awstransform.html) in the *Service Authorization Reference*.
To see a list of condition keys, and with which actions and resources you can use a condition key for AWS Transform *custom*, see [Actions, resources, and condition keys for AWS Transform custom ](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awstransformcustom.html) in the *Service Authorization Reference*.
To view examples of AWS Transform identity-based policies, see [Identity-based policy examples for AWS Transform](security_iam_id-based-policy-examples.md).
## ACLs in AWS Transform
**Supports ACLs:** No
Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.
## ABAC with AWS Transform
**Supports ABAC (tags in policies):** Partial
Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.
To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys.
If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**.
For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*.
## Using temporary credentials with AWS Transform
**Supports temporary credentials:** Yes
Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Cross-service principal permissions for AWS Transform
**Supports forward access sessions (FAS):** Yes
Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html).
## Service roles for AWS Transform
**Supports service roles:** Yes
A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*.
**Warning**
Changing the permissions for a service role might break AWS Transform functionality. Edit service roles only when AWS Transform provides guidance to do so.
## Service-linked roles for AWS Transform
**Supports service-linked roles:** Yes
A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.
For details about creating or managing AWS Transform service-linked roles, see [Using service-linked roles for AWS Transform](using-service-linked-roles.md).
# Identity-based policy examples for AWS Transform
By default, users and roles don't have permission to create or modify AWS Transform resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.
To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*.
For details about actions and resource types defined by AWS Transform, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for AWS Transform ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html) in the *Service Authorization Reference*.
**Topics**
+ [Policy best practices](#security_iam_service-with-iam-policy-best-practices)
+ [Using the AWS Transform console](#security_iam_id-based-policy-examples-console)
+ [Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions)
+ [Allow administrators to accept a connector request from the account with AWS Transform](#id-based-policy-examples-admin-connector)
+ [Allow administrators to assign existing IAM Identity Center users and create new IAM Identity Center users to assign to AWS Transform](#id-based-policy-examples-admin-idc-users)
+ [Allow administrators to enable AWS Transform](#id-based-policy-examples-admin-enable-transform)
## Policy best practices
Identity-based policies determine whether someone can create, access, or delete AWS Transform resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:
+ **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*.
+ **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.
+ **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*.
+ **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*.
+ **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*.
For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.
## Using the AWS Transform console
To access the AWS Transform console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AWS Transform resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy.
You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform.
## Allow users to view their own permissions
This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ViewOwnUserInfo",
"Effect": "Allow",
"Action": [
"iam:GetUserPolicy",
"iam:ListGroupsForUser",
"iam:ListAttachedUserPolicies",
"iam:ListUserPolicies",
"iam:GetUser"
],
"Resource": ["arn:aws:iam::*:user/${aws:username}"]
},
{
"Sid": "NavigateInConsole",
"Effect": "Allow",
"Action": [
"iam:GetGroupPolicy",
"iam:GetPolicyVersion",
"iam:GetPolicy",
"iam:ListAttachedGroupPolicies",
"iam:ListGroupPolicies",
"iam:ListPolicyVersions",
"iam:ListPolicies",
"iam:ListUsers"
],
"Resource": "*"
}
]
}
```
## Allow administrators to accept a connector request from the account with AWS Transform
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"transform:GetConnector",
"transform:AssociateConnectorResource",
"transform:RejectConnector"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:GetBucketPublicAccessBlock",
"s3:GetAccountPublicAccessBlock"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"iam:CreateRole",
"iam:AttachRolePolicy",
"iam:PassRole"
],
"Resource": "arn:aws:iam::111122223333:role/service-role/AWSTransform-*"
},
{
"Effect": "Allow",
"Action": [
"iam:CreatePolicy"
],
"Resource": "arn:aws:iam::111122223333:policy/service-role/AWSTransform-*"
}
]
}
```
------
## Allow administrators to assign existing IAM Identity Center users and create new IAM Identity Center users to assign to AWS Transform
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [{
"Sid": "AllowKmsAccessViaIdentityCenter",
"Effect": "Allow",
"Action": [
"kms:Decrypt"
],
"Resource": "*",
"Condition": {
"ArnLike": {
"kms:EncryptionContext:aws:sso:instance-arn": "arn:*:sso:::instance/*"
},
"StringLike": {
"kms:ViaService": "sso.*.amazonaws.com"
}
}
},
{
"Sid": "AllowKmsAccessViaIdentityStore",
"Effect": "Allow",
"Action": [
"kms:Decrypt"
],
"Resource": "*",
"Condition": {
"ArnLike": {
"kms:EncryptionContext:aws:identitystore:identitystore-arn": "arn:*:identitystore::*:identitystore/*"
},
"StringLike": {
"kms:ViaService": "identitystore.*.amazonaws.com"
}
}
}
]
}
```
------
## Allow administrators to enable AWS Transform
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"sso:ListInstances",
"sso:CreateInstance",
"sso:CreateApplication",
"sso:PutApplicationAuthenticationMethod",
"sso:PutApplicationGrant",
"sso:PutApplicationAssignmentConfiguration",
"sso:ListApplications",
"sso:GetSharedSsoConfiguration",
"sso:DescribeInstance",
"sso:PutApplicationAccessScope",
"sso:DescribeApplication",
"sso:DeleteApplication",
"sso:UpdateApplication",
"sso:DescribeRegisteredRegions",
"sso:GetSSOStatus"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"sso-directory:GetUserPoolInfo",
"sso-directory:DescribeUsers",
"sso-directory:DescribeGroups",
"sso-directory:SearchGroups",
"sso-directory:SearchUsers",
"sso-directory:DescribeDirectory"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"organizations:DescribeAccount",
"organizations:DescribeOrganization",
"organizations:ListAWSServiceAccessForOrganization",
"organizations:DisableAWSServiceAccess",
"organizations:EnableAWSServiceAccess"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"kms:ListAliases",
"kms:CreateGrant",
"kms:Encrypt",
"kms:Decrypt",
"kms:GenerateDataKey*",
"kms:RetireGrant",
"kms:DescribeKey"
],
"Resource": [
"*"
]
},
{
"Effect": "Allow",
"Action": [
"iam:CreateServiceLinkedRole"
],
"Resource": [
"arn:aws:iam::*:role/aws-service-role/transform.amazonaws.com/AWSServiceRoleForAWSTransform"
]
},
{
"Effect": "Allow",
"Action": [
"transform:UpdateProfile",
"transform:ListProfiles",
"transform:CreateProfile",
"transform:DeleteProfile"
],
"Resource": [
"*"
]
}
]
}
```
------
# Troubleshooting AWS Transform identity and access
Use the following information to help you diagnose and fix common issues that you might encounter when working with AWS Transform and IAM.
**Topics**
+ [I am not authorized to perform an action in AWS Transform](#security_iam_troubleshoot-no-permissions)
+ [I am not authorized to perform iam:PassRole](#security_iam_troubleshoot-passrole)
+ [I want to allow people outside of my AWS account to access my AWS Transform resources](#security_iam_troubleshoot-cross-account-access)
## I am not authorized to perform an action in AWS Transform
If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action.
The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `my-example-widget` resource but doesn't have the fictional `AWS Transform:GetWidget` permissions.
```
User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: AWS Transform:GetWidget on resource: my-example-widget
```
In this case, the policy for the `mateojackson` user must be updated to allow access to the `my-example-widget` resource by using the `AWS Transform:GetWidget` action.
If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.
## I am not authorized to perform iam:PassRole
If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to AWS Transform.
Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service.
The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in AWS Transform. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service.
```
User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole
```
In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action.
If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.
## I want to allow people outside of my AWS account to access my AWS Transform resources
You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.
To learn more, consult the following:
+ To learn whether AWS Transform supports these features, see [How AWS Transform works with IAM](security_iam_service-with-iam.md).
+ To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*.
+ To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*.
+ To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*.
+ To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
# Using service-linked roles for AWS Transform
AWS Transform uses AWS Identity and Access Management (IAM) [ service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to AWS Transform. Service-linked roles are predefined by AWS Transform and include all the permissions that the service requires to call other AWS services on your behalf.
## Using service-linked roles for AWS Transform
AWS Transform uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to AWS Transform. Service-linked roles are predefined by AWS Transform and include all the permissions that the service requires to call other AWS services on your behalf.
A service-linked role makes setting up AWS Transform easier because you don't have to manually add the necessary permissions. AWS Transform defines the permissions of its service-linked roles, and unless defined otherwise, only AWS Transform can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity.
You can delete a service-linked role only after first deleting their related resources. This protects your AWS Transform resources because you can't inadvertently remove permission to access the resources.
For information about other services that support service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and look for the services that have **Yes** in the **Service-linked roles** column. Choose a **Yes** with a link to view the service-linked role documentation for that service.
### Service-linked role permissions for AWS Transform
AWS Transform uses the service-linked role named [AWSServiceRoleForAWSTransform](security-iam-awsmanpol.md#security-iam-awsmanpol-AWSServiceRoleForAWSTransform) – This Service-Linked Role provides AWS Transform with the ability to provide usage information.
The AWSServiceRoleForAWSTransform service-linked role trusts the following services to assume the role:
+ `transform.amazonaws.com`
The role permissions policy named AWSServiceRoleForAWSTransform allows AWS Transform to complete the following actions on the specified resources:
+ cloudwatch:PutMetricData
+ Send custom metrics to CloudWatch for AWS Transform operations
+ Track transformation progress, success rates, and performance metrics
+ Enable monitoring and alerting on transformation workflows
+ sso:DescribeApplication
+ View details about a specific application in Identity Center
+ Get application metadata like name, description, status, and configuration
+ sso:GetApplicationAssignmentConfiguration
+ Retrieve assignment configuration settings for an application
+ See how users/groups are configured to be assigned to the application
+ sso:ListApplicationAssignmentsForPrincipal
+ List all applications assigned to a specific user or group (principal)
+ View which applications a particular identity has access to
+ Enables decryption of KMS-encrypted data when accessed through IAM Identity Center. Only works when the encryption context contains a valid IAM Identity Center instance ARN and must be accessed via IAM Identity Center service endpoints.
+ Allows decryption of KMS-encrypted data when accessed through Identity Store. Only works when the encryption context contains a valid Identity Store ARN and must be accessed via Identity Store service endpoints.
+ secretsmanager:GetSecretValue
+ Access AWS Transform service-linked secrets used to store client secrets for external identity providers
+ Resource: arn:aws:secretsmanager:\$1:\$1:secret:transform-preprod\$1\$1
+ Condition: Must be owned by transform-preprod service and accessed from same account
+ support:CreateCase, support:DescribeCases, support:DescribeCommunications, support:AddCommunicationToCase, support:ResolveCase
+ Create and manage premium support cases from the AWS Transform web application
+ View case details and communications
+ Add communications and resolve support cases
You must configure permissions to allow your users, groups, or roles to create, edit, or delete a service-linked role. For more information, see [Service-linked role permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*.
### Creating a service-linked role for AWS Transform
You don't need to manually create a service-linked role. When you create a profile for AWS Transform in the AWS Management Console, AWS Transform creates the service-linked role for you.
If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you update the settings, AWS Transform creates the service-linked role for you again.
You can also use the IAM console or AWS CLI to create a service-linked role with the `transform.amazonaws.com` service name. For more information, see [Creating a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#create-service-linked-role) in the *IAM User Guide*. If you delete this service-linked role, you can use this same process to create the role again.
### Editing a service-linked role for AWS Transform
AWS Transform does not allow you to edit the AWSServiceRoleForAWSTransform service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*.
### Deleting a service-linked role for AWS Transform
If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don't have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it.
**Note**
If the AWS Transform service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again.
**To manually delete the service-linked role using IAM**
Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAWSTransform service-linked role. For more information, see [Deleting a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*.
### Supported Regions for AWS Transform service-linked roles
AWS Transform does not support using service-linked roles in every Region where the service is available. You can use the AWSServiceRoleForAWSTransform role in the following Regions. For more information, see [AWS Regions and endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html).
****
| Region name | Region identity | Support in AWS Transform |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | Yes |
| Europe (Frankfurt) | eu-central-1 | Yes |
## Using service-linked roles for AWS Transform Custom
AWS Transform Custom uses the service-linked role named **AWSServiceRoleForAWSTransformCustom** to publish metrics to your account on your behalf. These metrics let you monitor transformation counts, latencies, and status codes directly in your dashboards.
This [service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role) is predefined by AWS Transform Custom and includes only the permissions the service needs. You don't have to manually add any permissions, and the role can only be assumed by AWS Transform Custom. For general information about service-linked roles, see [Using service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) in the *IAM User Guide*.
### Service-linked role permissions for AWS Transform Custom
The AWSServiceRoleForAWSTransformCustom service-linked role trusts the following services to assume the role:
+ `transform-custom.amazonaws.com`
The role permissions policy named AWSServiceRoleForAWSTransformCustom allows AWS Transform Custom to complete the following actions on the specified resources:
+ `cloudwatch:PutMetricData` on all AWS resources
+ Publish operational metrics to under the `AWS/TransformCustom` namespace
+ Track transformation counts, latencies, and status codes
+ Scoped to the `AWS/TransformCustom` namespace via the `cloudwatch:namespace` condition key
You must configure permissions to allow your users, groups, or roles to create, edit, or delete a service-linked role. For more information, see [Service-linked role permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*.
### Creating a service-linked role for AWS Transform Custom
You don't need to manually create a service-linked role. When you run a transformation using the AWS Transform Custom CLI, AWS Transform Custom creates the service-linked role for you.
If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you run a transformation using the AWS Transform Custom CLI, AWS Transform Custom creates the service-linked role for you again.
You can also use the IAM console to create a service-linked role with the **AWSServiceRoleForAWSTransformCustom** use case. In the AWS CLI or the AWS API, create a service-linked role with the `transform-custom.amazonaws.com` service name. For more information, see [Creating a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#create-service-linked-role) in the *IAM User Guide*. If you delete this service-linked role, you can use this same process to create the role again.
### Editing a service-linked role for AWS Transform Custom
AWS Transform Custom does not allow you to edit the AWSServiceRoleForAWSTransformCustom service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*.
### Deleting a service-linked role for AWS Transform Custom
If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don't have an unused entity that is not actively monitored or maintained.
The AWSServiceRoleForAWSTransformCustom service-linked role does not create persistent resources in your account. You can delete it directly without any resource cleanup.
If you delete this role and later run a transformation using the AWS Transform Custom CLI, the service-linked role is automatically recreated.
**To manually delete the service-linked role using IAM**
Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAWSTransformCustom service-linked role. For more information, see [Deleting a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*.
### Supported Regions for AWS Transform Custom service-linked roles
AWS Transform Custom does not support using service-linked roles in every Region where the service is available. You can use the AWSServiceRoleForAWSTransformCustom role in the following Regions. For more information, see [AWS Regions and endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html).
****
| Region name | Region identity | Support in AWS Transform Custom |
| --- | --- | --- |
| US East (N. Virginia) | us-east-1 | Yes |
| Europe (Frankfurt) | eu-central-1 | Yes |
# AWS managed policies for AWS Transform
An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles.
Keep in mind that AWS managed policies might not grant least-privilege permissions for your specific use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases.
You cannot change the permissions defined in AWS managed policies. If AWS updates the permissions defined in an AWS managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services.
For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*.
## AWS Transform updates for AWS managed policies
View details about updates to AWS managed policies for AWS Transform since March 1, 2021.
| Change | Description | Date |
| --- | --- | --- |
| [AWSTransformCustomFullAccess](#security-iam-awsmanpol-AWSTransformCustomFullAccess) – Updated policy | Added permission to create the AWS Transform custom service-linked role (`AWSServiceRoleForAWSTransformCustom`) to enable CloudWatch metrics emission to customer accounts. | April 7, 2026 |
| [AWSServiceRoleForAWSTransformCustom](#security-iam-awsmanpol-AWSServiceRoleForAWSTransformCustom) – New policy | Added a new AWS managed policy for the AWS Transform custom service-linked role. This policy allows AWS Transform custom to publish CloudWatch metrics to your account. | March 23, 2026 |
| [DBModProvisioningAndMigration](#security-iam-awsmanpol-DBModProvisioningAndMigration) – New policy | This policy grants database provisioning and migration capabilities. | March 24, 2026 |
| [DBModDiscoveryAndAssessment](#security-iam-awsmanpol-DBModDiscoveryAndAssessment) – New policy | Added a new AWS managed policy that provides comprehensive database modernization discovery and assessment capabilities. | March 24, 2026 |
| [AWSTransformCustomFullAccess](#security-iam-awsmanpol-AWSTransformCustomFullAccess) – New policy | Added a new AWS managed policy that provides full access to AWS Transform custom. | December 5, 2025 |
| [AWSTransformCustomExecuteTransformations](#security-iam-awsmanpol-AWSTransformCustomExecuteTransformations) – New policy | Added a new AWS managed policy that provides access to execute transformations in AWS Transform custom. | December 5, 2025 |
| [AWSTransformCustomManageTransformations](#security-iam-awsmanpol-AWSTransformCustomManageTransformations) – New policy | Added a new AWS managed policy that provides access to create, update, read, and delete transformation resources in AWS Transform custom, as well as execute transformations. | December 5, 2025 |
| [AWSServiceRoleForAWSTransform](#security-iam-awsmanpol-AWSServiceRoleForAWSTransform) – Updated policy | Added permissions to access the AWS Transform service-linked secret used to store the client secret for external identity providers. Added permissions to create a premium support case from the AWS Transform web app. | December 1, 2025 |
| [AWSTransformApplicationECSDeploymentPolicy](#security-iam-awsmanpol-AWSTransformApplicationECSDeploymentPolicy) – Updated policy | Added IAM role inspection permissions, ECS service-linked role creation, and KMS permissions for ECR encryption support. | November 22, 2025 |
| [AWSTransformApplicationDeploymentPolicy](#security-iam-awsmanpol-AWSTransformApplicationDeploymentPolicy) – Updated policy | Added EC2 networking permissions, IAM role inspection permissions, S3 bucket listing permissions, and KMS encryption support for enhanced deployment capabilities. | November 22, 2025 |
| [AWSServiceRoleForAWSTransform](#security-iam-awsmanpol-AWSServiceRoleForAWSTransform) – Updated policy | Added support for customer managed keys in IAM Identity Center. | September 17, 2025 |
| [AWSTransformApplicationDeploymentPolicy](#security-iam-awsmanpol-AWSTransformApplicationDeploymentPolicy) – New policy | Added a new AWS managed policy that enables AWS Transform to deploy transformed .NET applications by creating and managing Amazon EC2 instances, CloudFormation stacks, and associated resources. | August 28, 2025 |
| [AWSServiceRoleForAWSTransform](#security-iam-awsmanpol-AWSServiceRoleForAWSTransform) – Updated policy | Added a new policy. | May 15, 2025 |
## AWS managed policy: AWSServiceRoleForAWSTransform
This policy is attached to the [AWSServiceRoleForAWSTransform](using-service-linked-roles.md) service-linked role (SLR).
**Permissions details**
To view the policy permission details see [AWSServiceRoleForAWSTransform](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSServiceRoleForAWSTransform.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: AWSServiceRoleForAWSTransformCustom
This policy is attached to the [AWSServiceRoleForAWSTransformCustom](using-service-linked-roles.md#using-service-linked-roles-custom) service-linked role (SLR). This role allows AWS Transform custom to publish CloudWatch metrics to your account on your behalf.
**Description**
This policy includes the following permissions:
+ **Amazon CloudWatch** – Allows publishing metrics to CloudWatch under the `AWS/TransformCustom` namespace. This enables monitoring of transformation counts, latencies, and status codes in your CloudWatch dashboards.
## AWS managed policy: AWSTransformApplicationDeploymentPolicy
This policy enables AWS Transform to deploy transformed .NET applications by creating and managing Amazon EC2 instances, CloudFormation stacks, and associated resources.
**Description**
This policy includes the following permissions:
+ **CloudFormation** – Allows creating, updating, deleting, and describing CloudFormation stacks with names that start with AWSTransform. Stack operations are restricted to resources tagged with CreatedBy: AWSTransform and limited to the same AWS account.
+ **Amazon EC2** – Allows describing VPCs, subnets, security groups, images, instances, route tables, and internet gateways. Permits running, starting, stopping, terminating, and modifying EC2 instances, but only when called through CloudFormation. Tag creation is restricted to specific allowed tag keys and only during CloudFormation operations.
+ **AWS Identity and Access Management (IAM)** – Allows getting and passing specific IAM roles for AWSTransform deployment instances. Includes permissions to inspect role policies and attachments. Access is restricted to the same AWS account.
+ **Amazon EC2 Systems Manager (SSM)** – Allows retrieving Amazon Linux AMI parameters from the AWS-managed parameter store and sending commands to AWSTransform-tagged instances.
+ **Amazon S3** – Allows managing objects in AWSTransform deployment buckets, including listing buckets and getting bucket locations within the same AWS account.
+ **AWS Key Management Service (KMS)** – Allows encryption and decryption operations using KMS keys tagged for AWSTransform, with restrictions to S3 and EC2 service usage.
The policy implements least-privilege access through resource-level permissions, tag-based conditions, service control restrictions using `aws:CalledVia`, account-level restrictions, and explicit deny statements to prevent unauthorized tag modifications outside of CloudFormation operations.
**Permissions details**
To view the policy permission details see [AWSTransformApplicationDeploymentPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformApplicationDeploymentPolicy.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: AWSTransformApplicationECSDeploymentPolicy
This policy enables AWS Transform to deploy transformed applications to Amazon ECS by creating and managing ECS clusters, services, tasks, and associated resources.
**Description**
This policy includes the following permissions:
+ **CloudFormation** – Allows creating, updating, deleting, and describing CloudFormation stacks with names that start with AWSTransform. Stack operations are restricted to resources tagged with CreatedBy: AWSTransform and limited to the same AWS account.
+ **Amazon ECS** – Allows creating, updating, and deleting ECS clusters, services, and task definitions. Permits running tasks, listing tasks, and describing task status. All operations are restricted to resources with names starting with AWSTransform and tagged with CreatedBy: AWSTransform.
+ **AWS Identity and Access Management (IAM)** – Allows getting and passing specific IAM roles for ECS tasks (AWSTransform-Deploy-ECS-Task-Role and AWSTransform-Deploy-ECS-Execution-Role). Includes permissions to inspect role policies and create the ECS service-linked role when needed.
+ **Amazon CloudWatch Logs** – Allows creating, deleting, and managing log groups with names starting with /aws/ecs/AWSTransform. Permits retrieving log events for troubleshooting deployed applications.
+ **Amazon ECR** – Allows creating container repositories with names starting with awstransform for storing application container images.
+ **AWS Key Management Service (KMS)** – Allows creating grants and generating data keys for ECR encryption when using customer-managed KMS keys.
The policy implements least-privilege access through resource-level permissions, tag-based conditions, and account-level restrictions to ensure operations are limited to AWSTransform-managed resources within the same AWS account.
**Permissions details**
To view the policy permission details see [AWSTransformApplicationECSDeploymentPolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformApplicationECSDeploymentPolicy.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: AWSTransformCustomFullAccess
This policy provides full access to AWS Transform custom.
**Description**
This policy includes the following permissions:
+ **AWS Transform Custom** – Allows all actions on all AWS Transform custom resources. This provides complete administrative access to the service.
+ **AWS Identity and Access Management (IAM)** – Allows creating the AWS Transform custom [service-linked role](using-service-linked-roles.md#using-service-linked-roles-custom) (`AWSServiceRoleForAWSTransformCustom`). This role is required for AWS Transform custom to emit CloudWatch metrics to your account. The permission is scoped to only allow creating this specific service-linked role.
**Permissions details**
To view the policy permission details see [AWSTransformCustomFullAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformCustomFullAccess.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: AWSTransformCustomExecuteTransformations
This policy provides access to execute transformations in AWS Transform custom.
**Description**
This policy includes the following permissions:
+ **AWS Transform Custom** – Allows streaming conversations, executing transformations, and managing campaigns. Includes permissions to get campaign details, update campaign repository status, and update campaigns.
**Permissions details**
To view the policy permission details see [AWSTransformCustomExecuteTransformations](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformCustomExecuteTransformations.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: AWSTransformCustomManageTransformations
This policy provides access to create, update, read, and delete transformation resources in AWS Transform custom, as well as execute transformations.
**Description**
This policy includes the following permissions:
+ **AWS Transform Custom** – Allows comprehensive management of transformation resources including streaming conversations, executing transformations, and managing transformation packages. Permits creating, getting, and deleting transformation package URLs and completing package uploads.
+ **Knowledge Management** – Allows listing, getting, deleting, and updating knowledge items and their configurations and status.
+ **Campaign Management** – Allows getting campaign details, updating campaign repository status, and updating campaigns.
+ **Resource Tagging** – Allows listing, adding, and removing tags for AWS Transform custom resources.
**Permissions details**
To view the policy permission details see [AWSTransformCustomManageTransformations](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSTransformCustomManageTransformations.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: DBModDiscoveryAndAssessment
This policy provides comprehensive database modernization discovery and assessment capabilities for AWS Transform.
**Description**
This policy includes the following permissions:
+ **Amazon EC2** – Allows describing infrastructure components including instances, VPCs, subnets, security groups, availability zones, VPC endpoints, and internet gateways.
+ **Amazon RDS** – Allows describing database instances, clusters, and subnet groups. Allows modifying DB subnet groups within the same AWS account for migration preparation.
+ **Amazon RDS Data API** – Allows enabling and disabling HTTP endpoints and executing SQL statements on database clusters tagged for the database modernization project.
+ **AWS DMS** – Allows describing endpoints, replication instances, tasks, subnet groups, and orderable instances. Allows listing data providers, instance profiles, and migration projects. Allows describing table statistics, assessment runs, and metadata model operations. Detailed describe and metadata operations are restricted to resources tagged for the database modernization project.
+ **** – Allows listing secrets for discovering database credentials.
+ **AWS Identity and Access Management (IAM)** – Allows inspecting specific AWS DMS service roles and their attached policies. Includes access to read AWS-managed AWS DMS policies.
+ **AWS Key Management Service (KMS)** – Allows listing key aliases and describing keys. Allows decryption of secrets through integration, restricted to the same AWS account.
The policy implements least-privilege access through resource-level permissions, tag-based conditions, and account-level restrictions to ensure operations are limited to database modernization project resources within the same AWS account.
**Permissions details**
To view the policy permission details see [DBModDiscoveryAndAssessment](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/DBModDiscoveryAndAssessment.html) in the AWS Managed Policy Reference Guide.
## AWS managed policy: DBModProvisioningAndMigration
This policy provides database provisioning and migration capabilities for AWS Transform database modernization projects. It includes permissions to create and manage migration infrastructure, provision target databases, and store migration data.
**Description**
This policy includes the following permissions:
+ **AWS DMS** – Allows creating and managing replication subnet groups, instance profiles, data providers, migration projects, endpoints, replication instances, and replication tasks. Includes schema conversion operations such as metadata model import, conversion, export, and assessment. Allows lifecycle management of replication instances (create, delete, modify, reboot) and replication tasks (delete, start, stop, assess). All write operations are restricted to resources tagged for the database modernization project.
+ **Amazon RDS** – Allows creating database subnet groups, database clusters, and database instances. All resources must be tagged for the database modernization project.
+ **** – Allows creating, updating, and tagging secrets with the database modernization naming prefix. Allows retrieving secret values and describing secrets for tagged resources.
+ **Amazon S3** – Allows creating and managing S3 buckets and objects for migration data storage. Includes bucket tagging, versioning, and object lifecycle operations. Restricted to buckets with the database modernization naming prefix.
+ **AWS Identity and Access Management (IAM)** – Allows passing specific AWS DMS service roles to AWS DMS and schema conversion services. Allows creating the Amazon RDS service-linked role required for database operations.
The policy implements least-privilege access through resource-level permissions, tag-based conditions, and account-level restrictions to ensure operations are limited to database modernization project resources within the same AWS account.
**Permissions details**
To view the policy permission details see [DBModProvisioningAndMigration](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/DBModProvisioningAndMigration.html) in the AWS Managed Policy Reference Guide.
# AWS Transform permissions reference
This section provides information about the APIs used by AWS Transform, and what they do.
**Topics**
+ [AWS Transform APIs](#transform-permissions)
## AWS Transform APIs
+ transform:BatchGetMessage
+ transform:BatchGetUserDetails
+ transform:CompleteArtifactUpload
+ transform:CreateArtifactDownloadUrl
+ transform:CreateArtifactUploadUrl
+ transform:CreateAssetDownloadUrl
+ transform:CreateConnector
+ transform:CreateFeedback
+ transform:CreateJob
+ transform:CreateSession
+ transform:CreateWorkspace
+ transform:DeleteConnector
+ transform:DeleteJob
+ transform:DeleteSelfRoleMappings
+ transform:DeleteUserRoleMappings
+ transform:DeleteWorkspace
+ transform:DetectIsAllowedForOperation
+ transform:GetConnector
+ transform:GetFeedbackQuestions
+ transform:GetHitlTask
+ transform:GetJob
+ transform:GetLoginRedirectUri
+ transform:GetUserDetails
+ transform:GetUserPreferences
+ transform:GetWorkspace
+ transform:ListArtifacts
+ transform:ListConnectors
+ transform:ListHitlTasks
+ transform:ListJobPlanSteps
+ transform:ListJobs
+ transform:ListMessages
+ transform:ListPlanUpdates
+ transform:ListUserRoleMappings
+ transform:ListWorklogs
+ transform:ListWorkspaces
+ transform:PutUserPreferences
+ transform:PutUserRoleMappings
+ transform:RevokeSession
+ transform:SearchUsers
+ transform:SearchUsersTypeahead
+ transform:SendMessage
+ transform:StartJob
+ transform:StopJob
+ transform:SubmitCriticalHitlTask
+ transform:SubmitStandardHitlTask
+ transform:TestReleaseTraitPreProd
+ transform:TestReleaseTraitProd
+ transform:UpdateHitlTask
+ transform:UpdateJob
+ transform:UpdateWorkspace
+ transform:VerifySession
# Compliance validation for AWS Transform
To learn whether an AWS service is within the scope of specific compliance programs, see [AWS services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/) and choose the compliance program that you are interested in. For general information, see [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/).
You can download third-party audit reports using AWS Artifact. For more information, see [Downloading Reports in AWS Artifact](https://docs.aws.amazon.com/artifact/latest/ug/downloading-documents.html).
Your compliance responsibility when using AWS services is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations. For more information about your compliance responsibility when using AWS services, see [AWS Security Documentation](https://docs.aws.amazon.com/security/).
# Resilience in AWS Transform
The AWS global infrastructure is built around AWS Regions and Availability Zones. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low-latency, high-throughput, and highly redundant networking. With Availability Zones, you can design and operate applications and databases that automatically fail over between zones without interruption. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures.
For more information about AWS Regions and Availability Zones, see [AWS Global Infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/).
In addition to the AWS global infrastructure, AWS Transform offers several features to help support your data resiliency and backup needs.
# AWS Transform and interface endpoints (AWS PrivateLink)
You can establish a private connection between your VPC and AWS Transform by creating an *interface VPC endpoint*. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access the AWS Transform console without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Traffic between your VPC and AWS Transform does not leave the Amazon network.
Each interface endpoint is represented by one or more [Elastic Network Interfaces](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html) in your subnets.
For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html) in the *Amazon VPC User Guide*.
**Note**
For AWS Transform custom PrivateLink documentation, see [AWS Transform custom and interface endpoints (AWS PrivateLink)](vpc-interface-endpoints-transform-custom.md).
## Considerations for AWS Transform VPC endpoints
Before you set up an interface VPC endpoint for AWS Transform, ensure that you review [Interface endpoint properties and limitations](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#vpce-interface-limitations) in the *Amazon VPC User Guide*.
## Prerequisites
Before you begin any of the procedures below, ensure that you have the following:
+ An AWS account with appropriate permissions to create and configure resources.
+ A VPC already created in your AWS account.
+ Familiarity with AWS services, especially Amazon VPC and AWS Transform.
## Creating an interface VPC endpoint for AWS Transform
You can create a VPC endpoint for the AWS Transform service using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Creating an interface endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint) in the *Amazon VPC User Guide*.
The following VPC endpoint service names are available for AWS Transform:
+ `com.amazonaws.region.transform`
+ `com.amazonaws.region.api.transform` – Required for the AWS Transform WebApp. This endpoint **must** have private DNS enabled (the *Enable DNS name* option) so that `api.transform.region.on.aws` resolves to a private IP address in your VPC.
Replace *region* with the AWS Region where your AWS Transform profile is installed, for example, *com.amazonaws.us-east-1.transform*.
**Note**
If you use the AWS Transform WebApp, the `api.transform` endpoint is required. For the full setup guide, see [Accessing the AWS Transform WebApp from a VPC](vpc-webapp-access.md).
For more information, see [Supported Regions for AWS Transform](regions.md) and [Accessing a service through an interface endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#access-service-though-endpoint) in the *Amazon VPC User Guide*.
## Using an on-premises computer to connect to a AWS Transform endpoint
This section describes the process of using an on-premises computer to connect to AWS Transform through a AWS PrivateLink endpoint in your AWS VPC.
1. [Create a VPN connection between your on-premises device and your VPC.](https://docs.aws.amazon.com/vpn/latest/clientvpn-user/client-vpn-user-what-is.html)
1. [Create an interface VPC endpoint for AWS Transform.](#vpc-endpoint-create)
1. [Set up an inbound Amazon Route 53 endpoint.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-vpc-interface-endpoint.html) This will enable you to use the DNS name of your AWS Transform endpoint from your on-premises device.
# Accessing the AWS Transform WebApp from a VPC
When you use AWS PrivateLink to access the AWS Transform API privately from your VPC, the webapp requires additional network configuration. It serves static content (HTML, JavaScript, CSS) through CloudFront, which requires internet connectivity. API calls from the webapp go through your VPC endpoint and remain fully private.
This guide shows you how to configure controlled internet egress from your VPC so the webapp can load while keeping your VPC locked down to only the required domains.
## How it works
The AWS Transform WebApp uses two network paths:
+ **API calls** – When you interact with the webapp (starting jobs, viewing workspaces, and so on), the browser sends API requests to `api.transform.region.on.aws`. With the `com.amazonaws.region.api.transform` VPC endpoint and private DNS enabled, these requests resolve to a private IP address in your VPC and never leave the AWS network.
+ **Static content** – The webapp's HTML, JavaScript, and CSS files are served through CloudFront via `tenant-id.transform.region.on.aws`. Loading these files requires internet connectivity because CloudFront content delivery is only available over the public internet.
+ **Authentication** – AWS IAM Identity Center sign-in flows use `region.signin.aws`, which also requires internet connectivity.
To enable the webapp while maintaining security, you create a controlled egress path using AWS Network Firewall with domain-based filtering. This allows your VPC to reach *only* the specific domains required by the webapp while blocking all other internet traffic.
## Architecture
The following diagram shows the network path for webapp traffic:
```
EC2 Instance / Workspace (Private Subnet)
|
| Route: 0.0.0.0/0 → Network Firewall Endpoint
v
AWS Network Firewall (Firewall Subnet)
| Allows: *.cloudfront.net, *.transform..on.aws,
| .signin.aws, SSO domains, S3 presigned URLs
| Blocks: everything else (TLS SNI inspection)
|
| Route: 0.0.0.0/0 → NAT Gateway
v
NAT Gateway (Public Subnet)
|
| Route: 0.0.0.0/0 → Internet Gateway
v
Internet Gateway → CloudFront Edge Locations
```
**Important**
The Network Firewall must see both directions of traffic (symmetric routing) to perform TLS SNI inspection. You must configure a return route in the NAT Gateway subnet that sends traffic destined for the private subnet back through the firewall. Without this, domain-based filtering rules will not work.
## Prerequisites
Before you begin, ensure you have:
+ An AWS account with permissions to create VPC resources, Network Firewall, and NAT Gateways.
+ A VPC with a private subnet where your instances or workloads run.
+ An internet gateway attached to the VPC (or permissions to create one).
+ A AWS Transform VPC endpoint for `com.amazonaws.region.api.transform` with private DNS enabled. This is the endpoint used by the WebApp browser client. For instructions on creating endpoints, see [AWS Transform and interface endpoints (AWS PrivateLink)](vpc-interface-endpoints.md).
## Setting up controlled internet egress
Complete the following steps to configure Network Firewall with domain-based filtering for the AWS Transform WebApp.
### Step 1: Create the firewall subnet
Create a small /28 subnet dedicated to the Network Firewall endpoint. This subnet must be in the same Availability Zone as your private subnet.
```
aws ec2 create-subnet \
--vpc-id your-vpc-id \
--cidr-block firewall-subnet-cidr \
--availability-zone your-az \
--region region
```
### Step 2: Create a public subnet for the NAT Gateway
```
aws ec2 create-subnet \
--vpc-id your-vpc-id \
--cidr-block public-subnet-cidr \
--availability-zone your-az \
--region region
```
### Step 3: Configure the public subnet route table
Create a route table for the public subnet that routes internet traffic to the internet gateway.
```
# Create route table
PUB_RTB=$(aws ec2 create-route-table \
--vpc-id your-vpc-id \
--region region \
--query 'RouteTable.RouteTableId' --output text)
# Add default route to internet gateway
aws ec2 create-route \
--route-table-id $PUB_RTB \
--destination-cidr-block 0.0.0.0/0 \
--gateway-id your-igw-id \
--region region
# Associate with public subnet
aws ec2 associate-route-table \
--route-table-id $PUB_RTB \
--subnet-id public-subnet-id \
--region region
```
### Step 4: Create the NAT Gateway
```
# Allocate an Elastic IP
EIP=$(aws ec2 allocate-address --domain vpc \
--region region --query 'AllocationId' --output text)
# Create NAT Gateway in the public subnet
NAT_ID=$(aws ec2 create-nat-gateway \
--subnet-id public-subnet-id \
--allocation-id $EIP \
--region region \
--query 'NatGateway.NatGatewayId' --output text)
# Wait for NAT Gateway to become available (~2 minutes)
aws ec2 wait nat-gateway-available \
--nat-gateway-ids $NAT_ID --region region
```
### Step 5: Create the Network Firewall rule group
Create a stateful rule group that allows traffic only to the domains required by the AWS Transform WebApp.
```
aws network-firewall create-rule-group \
--rule-group-name transform-webapp-domains \
--type STATEFUL \
--capacity 100 \
--rule-group '{
"StatefulRuleOptions": {
"RuleOrder": "STRICT_ORDER"
},
"RulesSource": {
"RulesSourceList": {
"Targets": [
".cloudfront.net",
".transform.region.on.aws",
"region.signin.aws",
".s3.region.amazonaws.com",
"oidc.region.amazonaws.com",
"portal.sso.region.amazonaws.com",
"assets.sso-portal.region.amazonaws.com",
"directory-id.awsapps.com"
],
"TargetTypes": ["TLS_SNI", "HTTP_HOST"],
"GeneratedRulesType": "ALLOWLIST"
}
}
}' \
--region region
```
Replace *region* with the AWS Region where your AWS Transform profile is installed (for example, `us-east-1`). Replace *directory-id* with your IAM Identity Center directory ID (for example, `d-1234567890`). You can find your directory ID in the IAM Identity Center console.
The following table explains the allowed domains.
| Domain | Purpose |
| --- | --- |
| .cloudfront.net | CloudFront CDN – serves webapp static assets (JavaScript, CSS, images) |
| .transform.region.on.aws | Webapp tenant URL – the browser loads the initial page from this domain via CloudFront |
| region.signin.aws | SSO sign-in redirect page |
| .s3.region.amazonaws.com | S3 presigned URLs – artifact uploads and downloads |
| oidc.region.amazonaws.com | OIDC token exchange for SSO authentication |
| portal.sso.region.amazonaws.com | SSO portal login page |
| assets.sso-portal.region.amazonaws.com | SSO portal static assets (CSS, JavaScript) |
| directory-id.awsapps.com | IAM Identity Center portal for your organization |
**Note**
The `.cloudfront.net` wildcard allows traffic to any CloudFront distribution, not only the AWS Transform WebApp's. A narrower domain filter is not possible because CloudFront edge IPs are shared across distributions and TLS SNI inspection cannot distinguish individual distributions behind the same domain.
**Note**
API calls to `api.transform.region.on.aws` go through AWS PrivateLink and do not require internet egress. They are not affected by the firewall.
### Step 6: Create the firewall policy
The policy must use `STRICT_ORDER` rule evaluation with `drop_established` as the default action. This ensures that any traffic not matching the allowlist is dropped.
```
# Get the rule group ARN
RG_ARN=$(aws network-firewall describe-rule-group \
--rule-group-name transform-webapp-domains \
--type STATEFUL --region region \
--query 'RuleGroupResponse.RuleGroupArn' --output text)
# Create the firewall policy
aws network-firewall create-firewall-policy \
--firewall-policy-name transform-webapp-policy \
--firewall-policy "{
\"StatelessDefaultActions\": [\"aws:forward_to_sfe\"],
\"StatelessFragmentDefaultActions\": [\"aws:forward_to_sfe\"],
\"StatefulRuleGroupReferences\": [
{
\"ResourceArn\": \"$RG_ARN\",
\"Priority\": 1
}
],
\"StatefulEngineOptions\": {
\"RuleOrder\": \"STRICT_ORDER\"
},
\"StatefulDefaultActions\": [\"aws:drop_established\", \"aws:alert_established\"]
}" \
--region region
```
### Step 7: Create the Network Firewall
```
# Get the policy ARN
FW_POLICY_ARN=$(aws network-firewall describe-firewall-policy \
--firewall-policy-name transform-webapp-policy \
--region region \
--query 'FirewallPolicyResponse.FirewallPolicyArn' --output text)
# Create the firewall
aws network-firewall create-firewall \
--firewall-name transform-webapp-firewall \
--firewall-policy-arn $FW_POLICY_ARN \
--vpc-id your-vpc-id \
--subnet-mappings SubnetId=firewall-subnet-id \
--region region
# Wait for the firewall to become READY (3-5 minutes)
while true; do
STATUS=$(aws network-firewall describe-firewall \
--firewall-name transform-webapp-firewall \
--region region \
--query 'FirewallStatus.Status' --output text)
echo "Status: $STATUS"
if [ "$STATUS" = "READY" ]; then break; fi
sleep 15
done
```
### Step 8: Get the firewall endpoint ID
```
FW_ENDPOINT=$(aws network-firewall describe-firewall \
--firewall-name transform-webapp-firewall \
--region region \
--query "FirewallStatus.SyncStates.\"your-az\".Attachment.EndpointId" \
--output text)
echo "Firewall endpoint: $FW_ENDPOINT"
```
### Step 9: Configure the firewall subnet route table
Route internet-bound traffic from the firewall subnet to the NAT Gateway.
```
FW_RTB=$(aws ec2 create-route-table \
--vpc-id your-vpc-id \
--region region \
--query 'RouteTable.RouteTableId' --output text)
aws ec2 create-route \
--route-table-id $FW_RTB \
--destination-cidr-block 0.0.0.0/0 \
--nat-gateway-id $NAT_ID \
--region region
aws ec2 associate-route-table \
--route-table-id $FW_RTB \
--subnet-id firewall-subnet-id \
--region region
```
### Step 10: Update the private subnet route table
Route all internet-bound traffic from the private subnet through the firewall.
```
aws ec2 create-route \
--route-table-id private-subnet-route-table-id \
--destination-cidr-block 0.0.0.0/0 \
--vpc-endpoint-id $FW_ENDPOINT \
--region region
```
If a default route already exists, use `replace-route` instead of `create-route`.
### Step 11: Add the symmetric return route (required)
**Important**
This step is critical. Network Firewall uses TLS SNI inspection and must see both directions of a TCP connection. Add a route in the NAT Gateway subnet's route table that sends return traffic destined for the private subnet back through the firewall.
```
aws ec2 create-route \
--route-table-id $PUB_RTB \
--destination-cidr-block private-subnet-cidr \
--vpc-endpoint-id $FW_ENDPOINT \
--region region
```
Replace *private-subnet-cidr* with the CIDR block of your private subnet (for example, `10.0.144.0/20`).
Without symmetric routing, the firewall only sees one direction of traffic. The TLS inspection engine cannot extract the Server Name Indication (SNI) from the TLS handshake, and all domain-based rules will fail silently.
### Step 12: Remove the IPv6 default route (if present)
If the private subnet route table has an IPv6 default route (`::/0`) pointing directly to an internet gateway, it will bypass the firewall for IPv6-capable destinations. Remove it:
```
aws ec2 delete-route \
--route-table-id private-subnet-route-table-id \
--destination-ipv6-cidr-block ::/0 \
--region region
```
## Verification
From an instance in the private subnet, verify the configuration:
```
# Should SUCCEED - webapp content via CloudFront (allowed)
curl -vL --connect-timeout 15 \
'https://tenant-id.transform.region.on.aws'
# Should SUCCEED - API via PrivateLink (does not use firewall)
curl -v --connect-timeout 15 \
'https://api.transform.region.on.aws/'
# Should FAIL - non-allowlisted domain (blocked by firewall)
curl -v --connect-timeout 15 'https://www.example.com'
# Expected: TLS connection error (firewall drops after SNI inspection)
```
## Troubleshooting
API calls to api.transform are blocked by your firewall
The domain `api.transform.region.on.aws` should resolve to a private IP address via the VPC endpoint and should not reach your internet firewall.
+ Verify you have created the `com.amazonaws.region.api.transform` endpoint.
+ Verify private DNS is enabled on the endpoint:
```
aws ec2 describe-vpc-endpoints \
--filters "Name=service-name,Values=com.amazonaws.region.api.transform" \
--query 'VpcEndpoints[*].[State,PrivateDnsEnabled]' \
--output table
```
Expected output: `available | True`
The webapp does not load (connection timeout)
+ Verify the private subnet route table has a `0.0.0.0/0` route pointing to the firewall endpoint.
+ Verify the firewall subnet route table has a `0.0.0.0/0` route pointing to the NAT Gateway.
+ Verify the NAT Gateway is in an `available` state.
Non-allowlisted domains are not blocked
+ Check for an IPv6 `::/0` route pointing to the internet gateway. This bypasses the firewall. Remove it (Step 12).
+ Verify symmetric routing is configured. The NAT Gateway subnet route table must have a return route through the firewall for the private subnet CIDR (Step 11).
+ Verify the firewall policy uses `STRICT_ORDER` with `drop_established` and `alert_established` as default actions.
## Cost considerations
| Resource | Approximate cost |
| --- | --- |
| Network Firewall | \$1\$10.395/hr (\$1\$1288/month) per Availability Zone |
| NAT Gateway | \$1\$10.045/hr (\$1\$133/month) \$1 data processing fees |
| Elastic IP (public IPv4) | \$1\$10.005/hr (\$1\$13.60/month) |
| Network Firewall data processing | \$10.065/GB |
| NAT Gateway data processing | \$10.045/GB |
Estimated base cost is approximately \$1325/month for a single Availability Zone deployment. For production deployments, deploy the firewall, NAT Gateway, and associated subnets in each Availability Zone where private subnets exist.
## Cleanup
To remove all resources created by this guide, run the following commands in reverse order. Replace the placeholders with the resource IDs from your deployment. You can find these values in the AWS Management Console or by using the `describe` commands from the setup steps.
```
# Remove return route from NAT Gateway subnet
aws ec2 delete-route --route-table-id pub-rtb-id \
--destination-cidr-block private-subnet-cidr \
--region region
# Remove route from private subnet
aws ec2 delete-route \
--route-table-id private-subnet-route-table-id \
--destination-cidr-block 0.0.0.0/0 --region region
# Delete Network Firewall (takes ~5 minutes)
aws network-firewall delete-firewall \
--firewall-name transform-webapp-firewall \
--region region
# Delete firewall policy and rule group
aws network-firewall delete-firewall-policy \
--firewall-policy-name transform-webapp-policy \
--region region
aws network-firewall delete-rule-group \
--rule-group-name transform-webapp-domains \
--type STATEFUL --region region
# Delete NAT Gateway (wait ~5 minutes for full deletion)
aws ec2 delete-nat-gateway --nat-gateway-id nat-gateway-id \
--region region
# Release Elastic IP
aws ec2 release-address --allocation-id eip-allocation-id \
--region region
# Delete subnets
aws ec2 delete-subnet --subnet-id firewall-subnet-id \
--region region
aws ec2 delete-subnet --subnet-id public-subnet-id \
--region region
```