# Security in AWS AppFabric 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 AppFabric, 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 AppFabric. The following topics show you how to configure AppFabric to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your AppFabric resources. **Topics** + [Data protection in AWS AppFabric](data-protection.md) + [Identity and access management for AWS AppFabric](security-iam.md) + [Compliance validation for AWS AppFabric](compliance-validation.md) + [Security best practices for AWS AppFabric](security-best-practices.md) + [Resilience in AWS AppFabric](disaster-recovery-resiliency.md) + [Infrastructure security in AWS AppFabric](infrastructure-security.md) + [Configuration and vulnerability analysis in AWS AppFabric](configuration-vulnerability-analysis.md) # Data protection in AWS AppFabric The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in AWS AppFabric. 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 AppFabric 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. **Note** For more information about data protection as it applies to AppFabric for security, see [Data processing in AppFabric](productivity-data-processing.md). ## Encryption at rest AWS AppFabric supports encryption at rest, a server-side encryption feature in which AppFabric transparently encrypts all data related to your app bundles when it is persisted to disk, and decrypts them when you access the data. By default, AppFabric encrypts your data using an AWS owned key from AWS Key Management Service (AWS KMS). You can also choose to encrypt your data using your own customer managed key from AWS KMS. When you delete an app bundle, all its metadata is permanently deleted. ## Encryption in transit When you configure an app bundle, you can choose either an AWS owned key or a customer managed key. When collecting and normalizing the data for an audit log ingestion, AppFabric stores data temporarily in an intermediate Amazon Simple Storage Service (Amazon S3) bucket and encrypts it using this key. This intermediate bucket is deleted after 30 days, using a bucket lifecycle policy. AppFabric secures all data in transit using TLS 1.2 and signs API requests for AWS services with AWS Signature V4. ## Key management AppFabric supports encrypting data with an AWS owned key or a customer managed key. We recommend that you use a customer managed key because it puts you in full control over your encrypted data. When you choose a customer managed key, AppFabric attaches a resource policy to the customer managed key that grants it access to the customer managed key. ### Customer managed key To create a customer managed key, follow the steps for [Creating symmetric encryption KMS keys](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html#create-symmetric-cmk) in the *AWS KMS Developer Guide*. ## Key policy Key policies control access to your customer managed keys. Every customer managed key must have exactly one key policy, which contains statements that determine who can use the key and how they can use it. When you create your customer managed key, you can specify a key policy. For information about creating a key policy, see [Creating a key policy](https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-overview.html) in the *AWS KMS Developer Guide*. To use a customer managed key with AppFabric, the AWS Identity and Access Management (IAM) user or role creating your AppFabric resources must have permission to use your customer managed key. We recommend that you create a key that you use only with AppFabric and add your AppFabric users as users of the key. This approach limits the scope of access to your data. The permissions your users require are as follows: + `kms:DescribeKey` + `kms:CreateGrant` + `kms:GenerateDataKey` + `kms:Decrypt` The AWS KMS console guides you through creating a key with the appropriate key policy. For more information about key policies, see [Key policies in AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-users) in the *AWS KMS Developer Guide*. Following is an example key policy that permits: + The AWS account root user full control of the key. + Users permitted to use AppFabric to use your customer managed key with AppFabric. + A key policy for an app bundle setup in `us-east-1`. ## How AppFabric uses grants in AWS KMS AppFabric requires a grant to use your customer managed key. For more information, see [Grants in AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/grants.html) in the *AWS KMS Developer Guide*. When you create an app bundle, AppFabric creates a grant on your behalf by sending a `[https://docs.aws.amazon.com/kms/latest/APIReference/API_CreateGrant.html](https://docs.aws.amazon.com/kms/latest/APIReference/API_CreateGrant.html)` request to AWS KMS. Grants in AWS KMS are used to give AppFabric access to an AWS KMS key in a customer account. AppFabric requires that the grant to use your customer managed key for the following internal operations: + Send `[https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateDataKey.html](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateDataKey.html)` requests to AWS KMS to generate data keys encrypted by your customer managed key. + Send `[https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html)` requests to AWS KMS to decrypt the encrypted data keys so that they can be used to encrypt your data and to decrypt application access tokens in transit. + Send `[https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html](https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html)` requests to AWS KMS to encrypt application access tokens in transit. Following is an example of a grant. ``` { "KeyId": "arn:aws:kms:us-east-1:111122223333:key/ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE", "GrantId": "0ab0ac0d0b000f00ea00cc0a0e00fc00bce000c000f0000000c0bc0a0000aaafSAMPLE", "Name": "ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE", "CreationDate": "2022-10-11T20:35:39+00:00", "GranteePrincipal": "appfabric.us-east-1.amazonaws.com", "RetiringPrincipal": "appfabric.us-east-1.amazonaws.com", "IssuingAccount": "arn:aws:iam::111122223333:root", "Operations": [ "Decrypt", "Encrypt", "GenerateDataKey" ], "Constraints": { "EncryptionContextSubset": { "appBundleArn": "arn:aws:fabric:us-east-1:111122223333:appbundle/ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE" } } }, ``` When you delete an app bundle, AppFabric retires issued grants on your customer managed key. ## Monitoring your encryption keys for AppFabric When you use AWS KMS customer managed keys with AppFabric, you can use AWS CloudTrail logs to track requests that AppFabric sends to AWS KMS. Following is an example of an CloudTrail event logged when AppFabric uses `CreateGrant` for your customer managed key. ``` { "eventVersion": "1.08", "userIdentity": { "type": "AssumedRole", "principalId": "AROAIGDTESTANDEXAMPLE:SampleUser", "arn": "arn:aws:sts::111122223333:assumed-role/AssumedRole/SampleUser", "accountId": "111122223333", "accessKeyId": "AKIAIOSFODNN7EXAMPLE", "sessionContext": { "sessionIssuer": { "type": "Role", "principalId": "AROAIGDTESTANDEXAMPLE", "arn": "arn:aws:iam::111122223333:role/AssumedRole", "accountId": "111122223333", "userName": "SampleUser" }, "webIdFederationData": {}, "attributes": { "creationDate": "2023-04-28T14:01:33Z", "mfaAuthenticated": "false" } } }, "eventTime": "2023-04-28T14:05:48Z", "eventSource": "kms.amazonaws.com", "eventName": "CreateGrant", "awsRegion": "us-east-1", "sourceIPAddress": "appfabric.amazonaws.com", "userAgent": "appfabric.amazonaws.com", "requestParameters": { "granteePrincipal": "appfabric.us-east-1.amazonaws.com", "constraints": { "encryptionContextSubset": { "appBundleArn": "arn:aws:appfabric:us-east-1:111122223333:appbundle/ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE" } }, "keyId": "arn:aws:kms:us-east-1:111122223333:key/EXAMPLEID", "retiringPrincipal": "appfabric.us-east-1.amazonaws.com", "operations": [ "Encrypt", "Decrypt", "GenerateDataKey" ] }, "responseElements": { "grantId": "ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE", "keyId": "arn:aws:kms:us-east-1:111122223333:key/KEY_ID" }, "additionalEventData": { "grantId": "0ab0ac0d0b000f00ea00cc0a0e00fc00bce000c000f0000000c0bc0a0000aaafSAMPLE" }, "requestID": "ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE", "eventID": "ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE", "readOnly": false, "resources": [ { "accountId": "AWS Internal", "type": "AWS::KMS::Key", "ARN": "arn:aws:kms:us-east-1:111122223333:key/key_ID" } ], "eventType": "AwsApiCall", "managementEvent": true, "recipientAccountId": "111122223333", "sharedEventID": "ff000af-00eb-00ce-0e00-ea000fb0fba0SAMPLE", "eventCategory": "Management", "tlsDetails": { "tlsVersion": "TLSv1.3", "cipherSuite": "TLS_AES_256_GCM_SHA384", "clientProvidedHostHeader": "kms.us-east-1.amazonaws.com" } } ``` # Identity and access management for AWS AppFabric 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 AppFabric 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 AppFabric works with IAM](security_iam_service-with-iam.md) + [Identity-based policy examples for AWS AppFabric](security_iam_id-based-policy-examples.md) + [Using service-linked roles for AppFabric](using-service-linked-roles.md) + [AWS managed policies for AWS AppFabric](security-iam-awsmanpol.md) + [Troubleshooting AWS AppFabric identity and access](security_iam_troubleshoot.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 AppFabric identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How AWS AppFabric works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [Identity-based policy examples for AWS AppFabric](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 AppFabric works with IAM Before you use IAM to manage access to AppFabric, learn what IAM features are available to use with AppFabric. **IAM features you can use with AWS AppFabric** | IAM feature | AppFabric 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) | Yes | | [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | No | | [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes | | [Service roles](#security_iam_service-with-iam-roles-service) | No | | [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | Yes | To get a high-level view of how AppFabric 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 AppFabric **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 AppFabric To view examples of AppFabric identity-based policies, see [Identity-based policy examples for AWS AppFabric](security_iam_id-based-policy-examples.md). ## Resource-based policies within AppFabric **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 AppFabric **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 AppFabric actions, see [Actions defined by AWS AppFabric](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_appfabric.html#your_service-actions-as-permissions) in the *Service Authorization Reference*. Policy actions in AppFabric use the following prefix before the action: ``` appfabric ``` To specify multiple actions in a single statement, separate them with commas. ``` "Action": [ "appfabric:action1", "appfabric:action2" ] ``` You can specify multiple actions using wildcard characters (`*`). For example, to specify all actions that begin with the word `List`, include the following action. ``` "Action": "appfabric:List*" ``` To view examples of AppFabric identity-based policies, see [Identity-based policy examples for AWS AppFabric](security_iam_id-based-policy-examples.md). ## Policy resources for AppFabric **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 AppFabric resource types and their ARNs, see [Resource types defined by AWS AppFabric](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_appfabric.html#your_service-resources-for-iam-policies) in the *Service Authorization Reference*.To learn with which actions you can specify the ARN of each resource, see [Actions defined by AWS AppFabric](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_appfabric.html#your_service-actions-as-permissions). To view examples of AppFabric identity-based policies, see [Identity-based policy examples for AWS AppFabric](security_iam_id-based-policy-examples.md). ## Policy condition keys for AppFabric **Supports service-specific policy condition keys:** No 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 AppFabric condition keys, see [Condition keys for AWS AppFabric](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_appfabric.html#your_service-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions defined by AWS AppFabric](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_appfabric.html#your_service-actions-as-permissions). To view examples of AppFabric identity-based policies, see [Identity-based policy examples for AWS AppFabric](security_iam_id-based-policy-examples.md). ## ACLs in AppFabric **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 AppFabric **Supports ABAC (tags in policies):** Yes 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 AppFabric **Supports temporary credentials:** No 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 AppFabric **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 AppFabric **Supports service roles:** No 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 AppFabric functionality. Edit service roles only when AppFabric provides guidance to do so. ## Service-linked roles for AppFabric **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 AppFabric service-linked roles, see [Using service-linked roles for AppFabric](using-service-linked-roles.md). # Identity-based policy examples for AWS AppFabric By default, users and roles don't have permission to create or modify AppFabric 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 AppFabric, including the format of the ARNs for each of the resource types, see [Actions, resources, and condition keys for AWS AppFabric](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_appfabric.html) in the *Service Authorization Reference*. **Contents** + [Policy best practices](#security_iam_service-with-iam-policy-best-practices) + [Using the AppFabric console](#security_iam_id-based-policy-examples-console) + [AppFabric for security IAM policy examples](#appfabric-for-security-policy-examples) + [Allow access to app bundles](#security_iam_id-based-policy-examples-allow-app-bundle-access) + [Restrict access to app bundles](#security_iam_id-based-policy-examples-restrict-app-bundle-access) + [Restrict deleting or stopping ingestions](#security_iam_id-based-policy-examples-restrict-delete-stop-ingestion) + [AppFabric for productivity IAM policy examples](#appfabric-for-productivity-policy-examples) + [Allow access read-only access to productivity features](#security_iam_id-based-policy-examples-productivity-read-only) + [Allow full access to productivity features](#security_iam_id-based-policy-examples-productivity-full-access) + [Allow access to create AppClients](#security_iam_id-based-policy-examples-productivity-create-appclient) + [Allow access to get details of AppClients](#security_iam_id-based-policy-examples-productivity-get-appclient) + [Allow access to list AppClients](#security_iam_id-based-policy-examples-productivity-list-appclient) + [Allow access to update AppClients](#security_iam_id-based-policy-examples-productivity-update-appclient) + [Allow access to delete AppClients](#security_iam_id-based-policy-examples-productivity-delete-appclient) + [Allow access to authorize applications](#security_iam_id-based-policy-examples-productivity-token) + [Other IAM policy examples](#other-iam-policy-examples) + [Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete AppFabric 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 AppFabric console Attach the `AWSAppFabricReadOnlyAccess` AWS managed policy to your IAM identities to grant them read-only permission to the AppFabric service, including the AppFabric console in the AWS Management Console. Or, you can attach the `AWSAppFabricFullAccess` AWS managed policy to your IAM identities to grant them full administrative permission to the AppFabric service. For more information, see [AWS managed policies for AWS AppFabric](security-iam-awsmanpol.md). ## AppFabric for security IAM policy examples The following policy examples apply to the AppFabric for security features. ### Allow access to app bundles The following policy example grants access to app bundles in the AppFabric service. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "appfabric:StartUserAccessTasks", "appfabric:BatchGetUserAccessTasks" ], "Resource": ["arn:aws:appfabric:*:*:appbundle/*"] } ] } ``` ------ ### Restrict access to app bundles The following policy example restricts access to app bundles in the AppFabric service. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Action": ["appfabric:*"], "Effect": "Allow", "Resource": "*" }, { "Effect": "Deny", "Action": [ "appfabric:StartUserAccessTasks", "appfabric:BatchGetUserAccessTasks" ], "Resource": ["arn:aws:appfabric:*:*:appbundle/*"] } ] } ``` ------ ### Restrict deleting or stopping ingestions The following policy example restricts the deletion or stopping of ingestions in the AppFabric service. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Action": ["appfabric:*"], "Effect": "Allow", "Resource": "*" }, { "Effect": "Deny", "Action": [ "appfabric:StopIngestion", "appfabric:DeleteIngestion", "appfabric:DeleteIngestionDestination" ], "Resource": ["arn:aws:appfabric:*:*:appbundle/*"] } ] } ``` ------ ## AppFabric for productivity IAM policy examples | | | --- | | The AWS AppFabric for productivity feature is in preview and is subject to change. | The following policy examples apply to the AppFabric for productivity features. ### Allow access read-only access to productivity features The following policy example grants read-only access to the AppFabric for productivity features. **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow full access to productivity features The following policy example grants full access to the AppFabric for productivity features. **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow access to create AppClients The following policy example grants access to create AppClients. For more information, see [Create an AppFabric for productivity AppClient](getting-started-appdeveloper-productivity.md#create_appclient). **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow access to get details of AppClients The following policy example grants access to get details of AppClients. For more information, see [Get details of an AppClient](manage-appclients.md#get_appclient_details). **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow access to list AppClients The following policy example grants access to list AppClients. For more information, see [Get details of an AppClient](manage-appclients.md#list_appclients). **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow access to update AppClients The following policy example grants access to update AppClients. For more information, see [Update an AppClient](manage-appclients.md#update_appclient). **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow access to delete AppClients The following policy example grants access to delete AppClients. For more information, see [Update an AppClient](manage-appclients.md#delete_appclient). **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ### Allow access to authorize applications The following policy example grants access to authorize applications using the Token API. For more information, see [Authenticate and authorize your application](getting-started-appdeveloper-productivity.md#authorize_data_access). **Important** You might see an invalid action error when adding this policy in the JSON policy editor of the IAM console. This is because the AppFabric for productivity features are currently in preview. You should ignore the error and proceed to create the policy. ## Other IAM policy examples ### 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": "*" } ] } ``` # Using service-linked roles for AppFabric AWS AppFabric 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 AppFabric. Service-linked roles are predefined by AppFabric and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role makes setting up AppFabric easier because you don’t have to manually add the necessary permissions. AppFabric defines the permissions of its service-linked roles, and unless defined otherwise, only AppFabric can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy can't be attached to any other IAM entity. You can delete a service-linked role only after first deleting their related resources. This protects your AppFabric 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 AppFabric AppFabric uses the service-linked role named `AWSServiceRoleForAppFabric` – Allows AppFabric to put data in the an ingestion destination resource, such as an Amazon S3 bucket or an Amazon Data Firehose delivery stream. It also allows AppFabric to put CloudWatch metric data in the `AWS/AppFabric` namespace.. The `AWSServiceRoleForAppFabric` service-linked role trusts the following services to assume the role: + `appfabric.amazonaws.com` The role permissions policy named `AWSAppFabricServiceRolePolicy` allows AppFabric to complete the following actions on the specified resources: + Action: `cloudwatch:PutMetricData` in the `AWS/AppFabric` namespace. This action grants permission for AppFabric to put metric data into the Amazon CloudWatch `AWS/AppFabric` namespace. For more information about the AppFabric metrics available in CloudWatch, see [Monitoring AWS AppFabric with Amazon CloudWatch](monitoring-cloudwatch.md). + Action: `s3:PutObject` in an Amazon S3 bucket. This action grants permission for AppFabric to put ingested data into an Amazon S3 bucket that you specify. + Action: `firehose:PutRecordBatch` in an Amazon Data Firehose delivery stream. This action grants permission for AppFabric to put ingested data into an Amazon Data Firehose delivery stream that you specify. For more information, see [AWS managed policies for AppFabric](security-iam-awsmanpol.md). 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 AppFabric You don't need to manually create a service-linked role. When you create an AppFabric app bundle in the AWS Management Console, the AWS CLI, or the AWS API, AppFabric creates the service-linked role for you. ## Editing a service-linked role for AppFabric AppFabric doesn't allow you to edit the `AWSServiceRoleForAppFabric` 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 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 AppFabric 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 delete all of your AppFabric app bundles before you can delete the service-linked role. ### Cleaning up a service-linked role Before you can use IAM to delete a service-linked role, you must first delete any resources used by the role. App bundles that you create in AppFabric are used by the role. For more information, see [Delete AWS AppFabric for security resources](delete-resources.md). **Note** If the AppFabric 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. ### Manually delete the service-linked role Use the IAM console, the AWS CLI, or the AWS API to delete the `AWSServiceRoleForAppFabric` 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 AppFabric service-linked roles AppFabric supports using service-linked roles in all of the AWS Regions where the service is available. For more information, see [AppFabric endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/appfabric.html) in the *AWS General Reference*. # AWS managed policies for AWS AppFabric 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 don't 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: AWSAppFabricReadOnlyAccess You can attach the `AWSAppFabricReadOnlyAccess` policy to your IAM identities. This policy grants read-only permissions to the AppFabric service. **Note** The `AWSAppFabricReadOnlyAccess` policy does not grant read-only access to the AppFabric for productivity features. **Permissions details** This policy includes the following permissions: + `appfabric` – Grants permission to get an app bundle, list app bundles, get an app authorization, list app authorizations, get an ingestion, list ingestions, get an ingestion destination, list ingestion destinations, and list resource tags. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "appfabric:GetAppAuthorization", "appfabric:GetAppBundle", "appfabric:GetIngestion", "appfabric:GetIngestionDestination", "appfabric:ListAppAuthorizations", "appfabric:ListAppBundles", "appfabric:ListIngestionDestinations", "appfabric:ListIngestions", "appfabric:ListTagsForResource" ], "Resource": "*" } ] } ``` ------ ## AWS managed policy: AWSAppFabricFullAccess You can attach the `AWSAppFabricFullAccess` policy to your IAM identities. This policy grants administrative permissions to the AppFabric service. **Important** The `AWSAppFabricFullAccess` policy does not grant access to the AppFabric for productivity features because they are currently in preview. For more information about ranting access to the AppFabric for productivity features, see [AppFabric for productivity IAM policy examples](security_iam_id-based-policy-examples.md#appfabric-for-productivity-policy-examples). **Permissions details** This policy includes the following permissions: + `appfabric` – Grants full administrative permission to AppFabric. + `kms` – Grants permission to list aliases. + `s3` – Grants permission to list all of your Amazon S3 buckets, and get bucket location. + `firehose` – Grants permission to list Amazon Data Firehose delivery streams, and describe delivery streams. + `iam` – Grants permission to create the `AWSServiceRoleForAppFabric` service-linked role for AppFabric. For more information, see [Using service-linked roles for AppFabric](using-service-linked-roles.md). ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": ["appfabric:*"], "Resource": "*" }, { "Sid": "KMSListAccess", "Effect": "Allow", "Action": ["kms:ListAliases"], "Resource": "*" }, { "Sid": "S3ReadAccess", "Effect": "Allow", "Action": [ "s3:GetBucketLocation", "s3:ListAllMyBuckets" ], "Resource": "*" }, { "Sid": "FirehoseReadAccess", "Effect": "Allow", "Action": [ "firehose:DescribeDeliveryStream", "firehose:ListDeliveryStreams" ], "Resource": "*" }, { "Sid": "AllowUseOfServiceLinkedRole", "Effect": "Allow", "Action": ["iam:CreateServiceLinkedRole"], "Condition": { "StringEquals": {"iam:AWSServiceName": "appfabric.amazonaws.com"} }, "Resource": "arn:aws:iam::*:role/aws-service-role/appfabric.amazonaws.com/AWSServiceRoleForAppFabric" } ] } ``` ------ ## AWS managed policy: AWSAppFabricServiceRolePolicy You can't attach the `AWSAppFabricServiceRolePolicy` policy to your IAM entities. This policy is attached to a service-linked role that allows AppFabric to perform actions on your behalf. For more information, see [Using service-linked roles for AppFabric](using-service-linked-roles.md). **Permissions details** This policy includes the following permissions: + `cloudwatch` – Grants permission for AppFabric to put metric data into the Amazon CloudWatch `AWS/AppFabric` namespace. For more information about the AppFabric metrics available in CloudWatch, see [Monitoring AWS AppFabric with Amazon CloudWatch](monitoring-cloudwatch.md). + `s3` – Grants permission for AppFabric to put ingested data into an Amazon S3 bucket that you specify. + `firehose` – Grants permission for AppFabric to put ingested data into an Amazon Data Firehose delivery stream that you specify. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "CloudWatchEmitMetric", "Effect": "Allow", "Action": ["cloudwatch:PutMetricData"], "Resource": "*", "Condition": { "StringEquals": {"cloudwatch:namespace": "AWS/AppFabric"} } }, { "Sid": "S3PutObject", "Effect": "Allow", "Action": ["s3:PutObject"], "Resource": "arn:aws:s3:::*/AWSAppFabric/*", "Condition": { "StringEquals": {"s3:ResourceAccount": "${aws:PrincipalAccount}"} } }, { "Sid": "FirehosePutRecord", "Effect": "Allow", "Action": ["firehose:PutRecordBatch"], "Resource": "arn:aws:firehose:*:*:deliverystream/*", "Condition": { "StringEqualsIgnoreCase": {"aws:ResourceTag/AWSAppFabricManaged": "true"} } } ] } ``` ------ ## AppFabric updates to AWS managed policies View details about updates to AWS managed policies for AppFabric since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the [AppFabric Document history](doc-history.md) page. | Change | Description | Date | | --- | --- | --- | | [AWSAppFabricReadOnlyAccess](#security-iam-awsmanpol-AWSAppFabricReadOnlyAccess) – New policy | AppFabric added a new policy to grant read-only permissions to the AppFabric service. | June 27, 2023 | | [AWSAppFabricFullAccess](#security-iam-awsmanpol-AWSAppFabricFullAccess) – New policy | AppFabric added a new policy to grant administrative permissions to the AppFabric service. | June 27, 2023 | | [AWSAppFabricServiceRolePolicy](#security-iam-awsmanpol-AWSAppFabricServiceRolePolicy) – New policy | AppFabric added a new policy for the `AWSServiceRoleForAppFabric` service-linked role. | June 27, 2023 | | AppFabric started tracking changes | AppFabric started tracking changes for its AWS managed policies. | June 27, 2023 | # Troubleshooting AWS AppFabric identity and access Use the following information to help you diagnose and fix common issues that you might encounter when working with AppFabric and IAM. **Topics** + [I am not authorized to perform an action in AppFabric](#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 AppFabric resources](#security_iam_troubleshoot-cross-account-access) ## I am not authorized to perform an action in AppFabric 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 `appfabric:GetWidget` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: appfabric: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 `appfabric: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 AppFabric. 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 AppFabric. 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 AppFabric 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 AppFabric supports these features, see [How AWS AppFabric 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*. # Compliance validation for AWS AppFabric 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/). # Security best practices for AWS AppFabric AWS AppFabric provides several security features to consider as you develop and implement your own security policies. The following best practices are general guidelines and don't represent a complete security solution. Because these best practices might not be appropriate or sufficient for your environment, treat them as helpful considerations rather than prescriptions. ## Monitor for application without admin access With the read-only AWS Identity and Access Management (IAM) permission, anyone can integrate AppFabric with Amazon Quick and other security information and event management (SIEM) tools, such as Splunk. To monitor application security, data is delivered to an Amazon Simple Storage Service (Amazon S3) bucket or an Amazon Data Firehose delivery stream. ## Monitor for AppFabric events You can monitor AppFabric using Amazon CloudWatch metrics. CloudWatch collects data from AppFabric every minute and processes it into metrics. You can set alarms that set off notifications when metrics match specified thresholds. For more information, see [Monitoring AWS AppFabric with Amazon CloudWatch](monitoring-cloudwatch.md). # Resilience in AWS AppFabric 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/). # Infrastructure security in AWS AppFabric As a managed service, AWS AppFabric 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 AppFabric through the network. Clients must support TLS 1.0 or later. We recommend TLS 1.2 or later. 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, to generate temporary security credentials to sign requests, you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/Welcome.html) (AWS STS) . # Configuration and vulnerability analysis in AWS AppFabric 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/).