# Security in AWS App Studio Cloud security at AWS is the highest priority. As an AWS customer, you benefit from a data center and network architecture that is 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. The effectiveness of our security is regularly tested and verified by third-party auditors as part of the [AWS compliance programs](https://aws.amazon.com/compliance/programs/). To learn about the compliance programs that apply to App Studio, 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 organization’s requirements, and applicable laws and regulations. This documentation will help you understand how to apply the shared responsibility model when using App Studio. The following topics show you how to configure App Studio to meet your security and compliance objectives. You'll also learn how to use other AWS services that can help you to monitor and secure your App Studio resources. **Topics** + [Security considerations and mitigations](security-considerations-and-mitigations.md) + [Data protection in AWS App Studio](data-protection.md) + [AWS App Studio and AWS Identity and Access Management (IAM)](security-iam.md) + [Compliance validation for AWS App Studio](compliance-validation.md) + [Resilience in AWS App Studio](disaster-recovery-resiliency.md) + [Infrastructure Security in AWS App Studio](infrastructure-security.md) + [Configuration and vulnerability analysis in AWS App Studio](vulnerability-analysis-and-management.md) + [Cross-service confused deputy prevention](cross-service-confused-deputy-prevention.md) + [Cross-Region data transfer in AWS App Studio](cross-region-data-transfer.md) # Security considerations and mitigations ## Security considerations When dealing with data connectors, data models, and published applications, several security concerns arise related to data exposure, access control, and potential vulnerabilities. The following list includes the primary security concerns. ### Improper configuration of IAM roles Incorrect configuration of IAM roles for data connectors can lead to unauthorized access and data leaks. Granting overly permissive access to a data connector's IAM role can allow unauthorized users to access and modify sensitive data. ### Using IAM roles to perform data operations Since end users of an App Studio app assume the IAM role provided in the connector configuration to perform actions, those end users might get access to data to which they typically do not have access. ### Deleting data connectors of published applications When a data connector is deleted, the associated secret credentials are not automatically removed from published applications that are already using that connector. In this scenario, if an application has been published with certain connectors, and one of those connectors is deleted from App Studio, the published application will continue to work using the previously stored connector credentials. It is important to note that the published app will remain unaffected and operational despite the connector deletion. ### Editing data connectors on published applications When a data connector is edited, the changes are not automatically reflected in published applications that are using that connector. If an application has been published with certain connectors, and one of those connectors is modified in App Studio, the published application will continue to use the previously stored connector configuration and credentials. To incorporate the updated connector changes, the application must be republished. Until the app is republished, it will remain incorrect and non-operational, or unaffected and operational but will not reflect the latest connector modifications. ## Security risk mitigation recommendations This section lists mitigation recommendations to avoid security risks detailed in the previous security considerations section. 1. **Proper IAM role configuration:** Ensure that IAM roles for data connectors are correctly configured with the principle of least privilege to prevent unauthorized access and data leaks. 1. **Restricted app access:** Only share your apps with users who are authorized to view or perform actions on the application data. 1. **App publishing:** Ensure that apps are republished whenever a connector is updated or deleted. # Data protection in AWS App Studio The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in AWS App Studio. 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](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [AWS Shared Responsibility Model and GDPR](https://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 IAM Identity Center or 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 require TLS 1.2 and recommend TLS 1.3. + Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see [Working with CloudTrail trails](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-trails.html) in the *AWS CloudTrail User Guide*. + 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-3 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-3](https://aws.amazon.com/compliance/fips/). We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a **Name** field. This includes when you work with AWS App Studio or other AWS services using the console, API, 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. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server. ## Data encryption App Studio securely stores and transfers data by encrypting data at rest and in transit. ### Encryption at rest Encryption at rest refers to protecting your data from unauthorized access by encrypting data while stored. App Studio provides encryption at rest by default using AWS KMS keys, and you do not need to do any additional configuration for data encryption at rest. App Studio securely stores the following data for your applications: source code, build artifacts, metadata, and permissions information. When using data sources that are encrypted with a AWS KMS Customer Managed Key (CMK), App Studio resources continue to be encrypted using an AWS managed key, whereas the data in the encrypted data sources are encrypted by the CMK. For more information about using encrypted data sources in App Studio apps, see [Use encrypted data sources with CMKs](encrypted-data-cmk.md). App Studio uses Amazon CloudFront to serve your app to your users. CloudFront uses SSDs which are encrypted for edge location points of presence (POPs), and encrypted EBS volumes for Regional Edge Caches (RECs). Function code and configuration in CloudFront Functions is always stored in an encrypted format on the encrypted SSDs on the edge location POPs, and in other storage locations used by CloudFront. ## Encryption in transit Encryption in transit refers to protecting your data from being intercepted while it moves between communication endpoints. App Studio provides encryption for data in-transit by default. All communication between customers and App Studio, and between App Studio and its downstream dependencies is protected using TLS connections that are signed using the Signature Version 4 signing process. All App Studio endpoints use SHA-256 certificates that are managed by AWS Certificate Manager Private Certificate Authority. ## Key management App Studio does not support managing encryption keys. ## Inter-network traffic privacy When you create an instance in App Studio, you choose the AWS Region where the data and resources will be stored for that instance. Application build artifacts and metadata never leaves that AWS Region. However, note the following information: + Because App Studio uses Amazon CloudFront to serve your application and uses Lambda@Edge to manage authentication to your application, a limited set of authentication data, authorization data, application metadata would be accessed from CloudFront edge locations, which could be in a different Region. + AWS App Studio transfers data across AWS Regions to enable certain generative AI features in the service. For more information about the features enabled by cross-Region data transfers, the type of data that moves across Regions, and how to opt out, see [Cross-Region data transfer in AWS App Studio](cross-region-data-transfer.md). # AWS App Studio and AWS Identity and Access Management (IAM) In AWS App Studio, you manage access and permissions in the service by assigning groups in IAM Identity Center to the appropriate role in App Studio. The permissions of the group members are determined by the role that is assigned, and not by configuring users, roles, or permissions directly in AWS Identity and Access Management (IAM). For more information about managing access and permissions in App Studio, see [Managing access and roles in App Studio](managing-access-and-roles.md). App Studio does integrate with IAM when verifying an instance for billing purposes, and when connected to an AWS account to create and use resources in that AWS account. For information about connecting App Studio to other AWS services for use in your applications, see [Connect to AWS services](add-connector-services.md). When you create an instance in App Studio, you must connect an AWS account as the billing and management account for your instance. To enable key features, App Studio also creates [IAM service roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html#id_roles_terms-and-concepts) to provide the service with necessary permissions to carry out tasks on your behalf. 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 App Studio resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [Identity-based policies for App Studio](#security_iam_service-with-iam-id-based-policies) + [Resource-based policies within App Studio](#security_iam_service-with-iam-resource-based-policies) + [Policy actions for App Studio](#security_iam_service-with-iam-id-based-policies-actions) + [Policy resources for App Studio](#security_iam_service-with-iam-id-based-policies-resources) + [Policy condition keys for App Studio](#security_iam_service-with-iam-id-based-policies-conditionkeys) + [ACLs in App Studio](#security_iam_service-with-iam-acls) + [ABAC with App Studio](#security_iam_service-with-iam-tags) + [Using temporary credentials with App Studio](#security_iam_service-with-iam-roles-tempcreds) + [Cross-service principal permissions for App Studio](#security_iam_service-with-iam-principal-permissions) + [Service roles for App Studio](#security_iam_service-with-iam-roles-service) + [Service-linked roles for App Studio](#security_iam_service-with-iam-roles-service-linked) + [AWS managed policies for AWS App Studio](security-iam-awsmanpol.md) + [Service-linked roles for App Studio](appstudio-service-linked-roles.md) + [Identity-based policy examples for AWS App Studio](security_iam_id-based-policy-examples.md) Before you use IAM to manage access to App Studio, learn what IAM features are available to use with App Studio. **IAM features you can use with AWS App Studio** | IAM feature | App Studio 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) | No | | [ACLs](#security_iam_service-with-iam-acls) | No | | [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | No | | [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 App Studio 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 App Studio **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 App Studio To view examples of App Studio identity-based policies, see [Identity-based policy examples for AWS App Studio](security_iam_id-based-policy-examples.md). ## Resource-based policies within App Studio **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 App Studio **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 App Studio actions, see [Actions Defined by AWS App Studio](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsappstudio.html#awsappstudio-actions-as-permissions) in the *Service Authorization Reference*. Policy actions in App Studio use the following prefix before the action: ``` appstudio ``` To specify multiple actions in a single statement, separate them with commas. ``` "Action": [ "appstudio:action1", "appstudio:action2" ] ``` The following statement lists all of the actions in App Studio: ## Policy resources for App Studio **Supports policy resources:** Yes App Studio permissions only support a wildcard (`*`) in the `Resource` element of a policy. ## Policy condition keys for App Studio **Supports service-specific policy condition keys:** No App Studio does not support policy condition keys. ## ACLs in App Studio **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 App Studio **Supports ABAC (tags in policies):** No App Studio does not support attribute-based access control (ABAC). ## Using temporary credentials with App Studio **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 App Studio **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 App Studio **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*. AWS App Studio uses [IAM service roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html#id_roles_terms-and-concepts) for some features to give App Studio permission to carry out tasks on your behalf. The console automatically creates service roles for supported features when you set up App Studio. **Warning** Changing the permissions for a service role might break App Studio functionality. Edit service roles only when App Studio provides guidance to do so. ## Service-linked roles for App Studio **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 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). Find a service in the table that includes a `Yes` in the **Service-linked role** column. Choose the **Yes** link to view the service-linked role documentation for that service. # AWS managed policies for AWS App Studio To add permissions to users, groups, and roles, it is easier to use AWS managed policies than to write policies yourself. It takes time and expertise to [create IAM customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) that provide your team with only the permissions they need. To get started quickly, you can use our AWS managed policies. These policies cover common use cases and are available in your AWS account. For more information about AWS managed policies, 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 services maintain and update AWS managed policies. You can't change the permissions in AWS managed policies. Services occasionally add additional permissions to an AWS managed policy to support new features. This type of update affects all identities (users, groups, and roles) where the policy is attached. Services are most likely to update an AWS managed policy when a new feature is launched or when new operations become available. Services do not remove permissions from an AWS managed policy, so policy updates won't break your existing permissions. Additionally, AWS supports managed policies for job functions that span multiple services. For example, the **ReadOnlyAccess** AWS managed policy provides read-only access to all AWS services and resources. When a service launches a new feature, AWS adds read-only permissions for new operations and resources. For a list and descriptions of job function policies, see [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. ## AWS managed policy: AppStudioServiceRolePolicy You can't attach `AppStudioServiceRolePolicy` to your IAM entities. This policy is attached to a service-linked role that allows App Studio to perform actions on your behalf. For more information, see [Service-linked roles for App Studio](appstudio-service-linked-roles.md). This policy grants permissions that allow the service-linked role to manage AWS resources. ### Permissions details This policy includes permissions to do the following: + `logs` - Create CloudWatch log groups and log streams. Also gives permission to create log events in those log groups and streams. + `secretsmanager` - Create, read, update, and delete managed secrets that are managed by App Studio. + `sso` - Retrieve application instances. + `sso-directory` - Retrieve information about users and retrieve the list of members in groups. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "AppStudioResourcePermissionsForCloudWatch", "Effect": "Allow", "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:PutLogEvents" ], "Resource": [ "arn:aws:logs:*:*:log-group:/aws/appstudio/*" ], "Condition": { "StringEquals": { "aws:ResourceAccount": "${aws:PrincipalAccount}" } } }, { "Sid": "AppStudioResourcePermissionsForSecretsManager", "Effect": "Allow", "Action": [ "secretsmanager:CreateSecret", "secretsmanager:DeleteSecret", "secretsmanager:DescribeSecret", "secretsmanager:GetSecretValue", "secretsmanager:PutSecretValue", "secretsmanager:UpdateSecret", "secretsmanager:TagResource" ], "Resource": "arn:aws:secretsmanager:*:*:secret:appstudio-*", "Condition": { "ForAllValues:StringEquals": { "aws:TagKeys": [ "IsAppStudioSecret" ] }, "StringEquals": { "aws:ResourceAccount": "${aws:PrincipalAccount}", "aws:ResourceTag/IsAppStudioSecret": "true" } } }, { "Sid": "AppStudioResourcePermissionsForManagedSecrets", "Effect": "Allow", "Action": [ "secretsmanager:DeleteSecret", "secretsmanager:DescribeSecret", "secretsmanager:GetSecretValue", "secretsmanager:PutSecretValue", "secretsmanager:UpdateSecret" ], "Resource": "arn:aws:secretsmanager:*:*:secret:appstudio!*", "Condition": { "StringEquals": { "aws:ResourceAccount": "${aws:PrincipalAccount}", "secretsmanager:ResourceTag/aws:secretsmanager:owningService": "appstudio" } } }, { "Sid": "AppStudioResourceWritePermissionsForManagedSecrets", "Effect": "Allow", "Action": [ "secretsmanager:CreateSecret" ], "Resource": "arn:aws:secretsmanager:*:*:secret:appstudio!*", "Condition": { "StringEquals": { "aws:ResourceAccount": "${aws:PrincipalAccount}" } } }, { "Sid": "AppStudioResourcePermissionsForSSO", "Effect": "Allow", "Action": [ "sso:GetManagedApplicationInstance", "sso-directory:DescribeUsers", "sso-directory:ListMembersInGroup" ], "Resource": "*", "Condition": { "StringEquals": { "aws:ResourceAccount": "${aws:PrincipalAccount}" } } } ] } ``` ------ ## App Studio updates to AWS managed policies View details about updates to AWS managed policies for App Studio since this service began tracking these changes. | Change | Description | Date | | --- | --- | --- | | [AppStudioServiceRolePolicy](#security-iam-awsmanpol-appstudioservicerolepolicy) – Update to an existing policy | App Studio added new permissions to allow managing of App Studio managed secrets in AWS Secrets Manager. | March 14, 2025 | | App Studio started tracking changes | App Studio started tracking changes for its AWS managed policies. | June 28, 2024 | # Service-linked roles for App Studio App Studio uses [AWS Identity and Access Management (IAM) service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html). A service-linked role is a unique type of IAM role that is linked directly to App Studio. Service-linked roles are predefined by App Studio and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role makes setting up App Studio easier because you don’t have to manually add the necessary permissions. App Studio defines the permissions of its service-linked roles, and unless defined otherwise, only App Studio 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 App Studio resources because you can't inadvertently remove permission to access the resources. **Topics** + [Service-linked role permissions for App Studio](#slr-permissions) + [Creating a service-linked role for App Studio](#create-slr) + [Editing a service-linked role for App Studio](#edit-slr) + [Deleting a service-linked role for App Studio](#delete-slr) ## Service-linked role permissions for App Studio App Studio uses the service-linked role named `AWSServiceRoleForAppStudio`. It's a service-linked role required for App Studio to persistently manage AWS services, to maintain the application building experience. The `AWSServiceRoleForAppStudio` service-linked role uses the following trust policy, which only trusts the `appstudio-service.amazonaws.com` service: ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "appstudio-service.amazonaws.com" }, "Action": "sts:AssumeRole" } ] } ``` ------ For permissions, the `AWSServiceRoleForAppStudio` service-linked role provides permissions to the following services: + Amazon CloudWatch: To send logs and metrics for App Studio usage. + AWS Secrets Manager: To manage credentials for connectors in App Studio, used to connect apps to other services. + IAM Identity Center: To read-only access to manage user access. Specifically, the permissions granted with `AWSServiceRoleForAppStudio` are defined by the attached `AppStudioServiceRolePolicy` managed policy. For more information about the managed policy, including the permissions it includes, see [AWS managed policy: AppStudioServiceRolePolicy](security-iam-awsmanpol.md#security-iam-awsmanpol-appstudioservicerolepolicy). ## Creating a service-linked role for App Studio You don't need to manually create a service-linked role. When you create an App Studio instance, App Studio creates the service-linked role for you. If you delete this service-linked role, it is recommended to create an App Studio instance to have another one automatically created for you. While not neccesary, you can also use the IAM console or AWS CLI to create service-linked roles by creating a service-linked role with the `appstudio-service.amazonaws.com` service name, as in the trust policy snippet shown earlier. For more information, see [Creating a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create-service-linked-role.html) in the *IAM User Guide*. ## Editing a service-linked role for App Studio App Studio doesn't allow you to edit the `AWSServiceRoleForAppStudio` service-linked role. After you create a service-linked role, you can't change the name of the role because various entities might reference the role. However, you can edit the description of the role by 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 App Studio You don't need to delete the `AWSServiceRoleForAppStudio` role. When you delete the App Studio instance, App Studio cleans up the resources and deletes the service-linked role automatically. While not recommended, you can use the IAM console or the AWS CLI to delete the service-linked role. To do this, you must first clean up the resources for your service-linked role and then you can delete it. **Note** If App Studio 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** 1. Delete the applications and connectors from your App Studio instance. 1. Use the IAM console, the IAM CLI, or the IAM API to delete the `AWSServiceRoleForAppStudio` 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*. # Identity-based policy examples for AWS App Studio By default, users and roles don't have permission to create or modify App Studio 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 App Studio, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for AWS App Studio](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsappstudio.html) in the *Service Authorization Reference*. **Topics** + [Policy best practices](#security_iam_service-with-iam-policy-best-practices) + [Using the App Studio console](#security_iam_id-based-policy-examples-console) + [Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions) + [Example 1: Allow users to set up an App Studio instance](#security_iam_id-based-policy-examples-set-up-appstudio-instance) + [Example 2: Deny users from setting up an App Studio instance](#security_iam_id-based-policy-examples-deny-set-up-appstudio-instance) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete App Studio 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 App Studio console To access the AWS App Studio console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the App Studio 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. To ensure that users and roles can still use the App Studio console, also attach the App Studio `ConsoleAccess` or `ReadOnly` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*. ## 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": "*" } ] } ``` ## Example 1: Allow users to set up an App Studio instance The following example shows an identity-based policy to allow a role to set up an App Studio instance. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "appstudio:GetAccountStatus", "appstudio:GetEnablementJobStatus", "appstudio:StartEnablementJob", "appstudio:StartRollbackEnablementJob", "appstudio:StartTeamDeployment" ], "Resource": "*" }] } ``` ------ ## Example 2: Deny users from setting up an App Studio instance The following example shows an identity-based policy to deny a role from settting up an App Studio instance. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Effect": "Deny", "Action": [ "appstudio:*" ], "Resource": "*" }] } ``` ------ # Compliance validation for AWS App Studio 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 App Studio 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 App Studio offers several features to help support your data resiliency and backup needs. # Infrastructure Security in AWS App Studio As a managed service, AWS App Studio is protected by the AWS global network security procedures that are described in the [Amazon Web Services: Overview of Security Processes](https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf) whitepaper. You use AWS published API calls to access App Studio through the network. Clients must support at least Transport Layer Security (TLS) 1.2, but TLS 1.3 is recommended. Clients must also support cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes. Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/Welcome.html) (AWS STS) to generate temporary security credentials to sign requests. # Configuration and vulnerability analysis in AWS App Studio Configuration and IT controls are a shared responsibility between AWS and you, our customer. For more information, see the AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/). # Cross-service confused deputy prevention The confused deputy problem is a security issue where an entity that doesn't have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the *calling service*) calls another service (the *called service*). The calling service can be manipulated to use its permissions to act on another customer's resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. We recommend using the [https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourcearn) and [https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-sourceaccount) global condition context keys in resource policies to limit the permissions that gives another service to the resource. Use `aws:SourceArn` if you want only one resource to be associated with the cross-service access. Use `aws:SourceAccount` if you want to allow any resource in that account to be associated with the cross-service use. The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full ARN of the resource. If you don't know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters (`*`) for the unknown portions of the ARN. For example, `arn:aws:servicename:*:123456789012:*`. If the `aws:SourceArn` value does not contain the account ID, such as an Amazon S3 bucket ARN, you must use both global condition context keys to limit permissions. The value of `aws:SourceArn` must be ResourceDescription. The following example shows how you can use the `aws:SourceArn` and `aws:SourceAccount` global condition context keys in to prevent the confused deputy problem. # Cross-Region data transfer in AWS App Studio AWS App Studio transfers data across AWS Regions to enable certain generative AI features in the service. This topic contains information about the features enabled by cross-Region data transfers, the type of data that moves across Regions, and how to opt out. The following features are enabled by cross-Region data transfer, and will not be accessible in your instance if you opt out: 1. Creating an app with AI, used to kickstart app building by describing your app with natural language and creating resources for you. 1. The AI chat in the application studio, used to ask questions about app building, publishing, and sharing. The following data is transferred across Regions: 1. The prompts or user input from the features described previously. To opt out of cross-Region data transfer, and the features enabled by it, use the following procedure to fill out the opt-out request form from the console: 1. Open the App Studio console at [https://console.aws.amazon.com/appstudio/](https://console.aws.amazon.com/appstudio/). 1. Choose **Opt out of data transfer**. 1. Enter your AWS account ID, and provide your email address. 1. Choose **Submit**. 1. Once submitted, your request to opt out of cross-Region data transfer will be processed, which can take up to 60 days.