Update AWS account permissions

Update your permissions so that the Client Portal can access your AWS account.

  • This topic only applies to the AWS accounts that are added using the Add Cloud Account option on the Cloud Tenant Setup page.

  • You must have an advanced understanding of AWS, CloudFormation, and IAM policies and roles to execute these steps.

Update permissions

Follow these steps to update your AWS account permissions:

  1. Sign in to the AWS Console as a user with permission to modify IAM resources.

  2. In the AWS console, select Services to open the list of services. Under the Management and Governance group, select CloudFormation.

  1. Locate the Stack. In the CloudFormation console, select the correct region at the top right corner of the screen. You may need to cycle through the region until you find the stack (typically named, PyraCloud-Onboarding).

  2. Select the stack and then select Update.

  1. On the Update Stack page, do the following:

    1. Select the Replace Current Template option.

    2. Select Next.

  1. On the Specify stack details page, leave the ExternalId, PyraCloudProcessId, and PyraCloudTenantId fields as they are. Select Next.

  1. On the Configure stack options page, leave all values as they are. Select Next.

  1. On the Review PyraCloud-Onboarding page, do the following:

    1. Review the changes that will be made to the stack.

    2. Select the I acknowledge that AWS CloudFormation might create IAM resources with custom names checkbox.

    3. Select Update Stack.

  2. Refresh the page until the stack moves from the UPDATE_IN_PROGRESS status to UPDATE_COMPLETE.

After the process is completed, it might take up to 24 hours for your AWS account to become healthy.

Re-onboard AWS Recommendations

The following permissions are required to view the AWS Recommendations from AWS Trusted Advisor.

  • support:*

  • trustedadvisor:Describe*

Follow Updating permissions to re-onboard your AWS account with these permissions.

Update read and write-back permissions for AWS resources

If you're unable to read resources, that is, you are missing read permissions for AWS resources, follow the Updating permissions section.

If you're unable to tag resources, that is, you are missing write-back permissions for AWS resources), follow these steps:

  1. Navigate to IAM within the AWS portal and locate PyraCloudRole.

  1. Navigate to the details of the role and ensure that ReadWritePolicy is attached.

  • If the role is not attached, select Attach policies. Type PyraCloudReadWrite policy in the search box and then select the checkbox and select Attach policy.

The role is attached and the write-back permissions are added. To confirm, check the Resources module by syncing the relevant AWS accounts.

Last updated

SoftwareOne is a trademark of SoftwareOne, Inc. "The Software Licensing Experts" is a service mark of SoftwareOne, Inc. VAR assist is a trademark of SoftwareOne, Inc. "It pays to partner" is a service mark of SoftwareOne, Incorporated.