> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/connect/connect-cloud-accounts/onboard-aws/manually-set-up-prisma-cloud-role-for-aws.md). # Manually Set Up Prisma Cloud Role for AWS Accounts To monitor your AWS account, create the roles (manually) and authorize the permissions for Prisma Cloud. If you do not want to use the guided onboarding flow that automates the process of creating the roles required for Prisma Cloud to secure your accounts on AWS, you must create the roles manually. In order to monitor your AWS account, you must create a role that grants Prisma Cloud access to your flow logs and read-only access (to retrieve and view the traffic log data) or a limited read-write access (to retrieve traffic log data and remediate incidents). To authorize permission, you must copy the policies from the relevant template and attach it to the role. Event logs associated with the monitored cloud account are automatically retrieved on Prisma Cloud. 1. Download CFT template from Prisma Cloud. * See [Onboard Your AWS Account](/content-collections/connect/connect-cloud-accounts/onboard-aws/onboard-aws-account.md) and follow the steps to **Download IAM Role CFT**. * Search for the **ExternalID** field within the template. * Copy the **ExternalID** value, which you will need to paste in the AWS console as described in the next Step. 2. Log in to the AWS management console to create a role for Prisma Cloud. Refer to the [AWS documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) for instructions. Create the role in the same region as your AWS account, and use the following values and options when creating the role: * Type of trusted entity: **Another AWS Account** and enter the **Account ID**: **188619942792** * Select **Require external ID** and paste the **ExternalID** value that you copied in Step 1 above. * Do not enable MFA. Verify that **Require MFA** is not selected.
add aws manual role 1
* Click **Next** and add the AWS Managed Policy for **Security Audit**.
add aws manual policy 2 1
Add a role name and create the role. In this workflow, later, you will create the granular policies and edit the role to attach the additional policies. 3. Get the granular permissions from the AWS CFT for your AWS environment. The Prisma Cloud S3 bucket has read-only templates and read-and-write templates for the public AWS, AWS GovCloud, and AWS China environments. 1. Download the template you need. 2. Identify the permissions you need to copy. To create the policy manually, you will need to add the required permissions inline using the JSON editor. From the read-only template you can get the granular permissions for the **PrismaCloud-IAM-ReadOnly-Policy**, and the read-write template lists the granular permissions for the **PrismaCloud-IAM-ReadOnly-Policy** and the **PrismaCloud-IAM-Remediation-Policy**. For AWS accounts you onboard to Prisma Cloud, if you do not use the host, serverless functions, and container capabilities enabled with Prisma Cloud Runtime Security, you do not need the permissions associated with these roles: * **PrismaCloud-ReadOnly-Policy-Compute** role—CFT used for Monitor mode, includes additional permissions associated with this new role to enable monitoring of resources that are onboarded for Prisma Cloud Runtime Security. * **PrismaCloud-Remediation-Policy-Compute** role—CFT used for Monitor & Protect mode, includes additional permissions associated with this new role to enable read-write access for monitoring and remediating resources that are onboarded for Prisma Cloud Runtime Security. * Open the appropriate template using a text editor. * Find the policies you need and copy it to your clipboard. Copy the details for one or both permissions, and make sure to include the open and close brackets for valid syntax, as shown below.
add aws manual policy 1
add aws manual policy 2
4. Create the policy that defines the permissions for the Prisma Cloud role. Both the read-only role and the read-write roles require the AWS Managed Policy **SecurityAudit Policy**. In addition, you will need to enable granular permissions for the **PrismaCloud-IAM-ReadOnly-Policy** for the read-only role, or for the read-write role add the **PrismaCloud-IAM-ReadOnly-Policy** and the limited permissions for **PrismaCloud-IAM-Remediation-Policy**. 1. Select **IAM** on the AWS Management Console. 2. In the navigation pane on the left, choose **Access Management > Policies > Create policy**. 3. Select the **JSON** tab. Paste the JSON policies that you copied from the template within the square brackets for Statement.
add aws manual policy 3
add aws manual policy 4
If you are enabling read and read-write permissions, make sure to append the read-write permissions within the same Action statement.
add aws manual policy 5
4. Review and create the policy. 5. Edit the role you created previously and attach the policy to the role.
add aws manual policy roles
6. tt:\[Required only if you want to use the same role to access your CloudWatch log group] Update the trust policy to allow access to the CloudWatch log group. Edit the **Trust Relationships** to add the permissions listed below. This allow you to ensure that your role has a trust relationship for the flow logs service to assume the role and publish logs to the CloudWatch log group. ``` { "Effect": "Allow", "Principal": { "Service": "vpc-flow-logs.amazonaws.com" }, "Action": "sts:AssumeRole" } ``` 7. Copy the **Role ARN**.
add aws manual policy role arn
8. Resume with the account onboarding flow in [Onboard Your AWS Account](/content-collections/connect/connect-cloud-accounts/onboard-aws/onboard-aws-account.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.prismacloud.io/content-collections/connect/connect-cloud-accounts/onboard-aws/manually-set-up-prisma-cloud-role-for-aws.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.