Menu
AWS Cloud9
User Guide

Troubleshooting AWS Cloud9

Use the following information to help you identify and address issues with AWS Cloud9.

Error: "Not authorized to perform sts:AssumeRole" When Creating an AWS Cloud9 Development Environment

Issue: When you try to create a new environment, you see this error: "Not authorized to perform sts:AssumeRole," and the environment is not created.

Possible causes: An AWS Cloud9 service-linked role doesn't exist in your AWS account.

Recommended solutions: Create an AWS Cloud9 service-linked role in your AWS account by running the following command with the AWS Command Line Interface (AWS CLI).

aws iam create-service-linked-role --aws-service-name cloud9.amazonaws.com

If you cannot do this, check with your AWS account administrator.

After you run this command, try creating the environment again.

Error: "User is not authorized to perform action on resource" When Using the AWS Cloud9 Console

Issue: When you try to use the AWS Cloud9 console to create or manage an AWS Cloud9 development environment, you see this error: "User USER-ARN is not authorized to perform ACTION on resource RESOURCE-ARN," where:

  • USER-ARN is the Amazon Resource Name (ARN) of the IAM user that tried to access the resource.

  • ACTION is the AWS action the IAM user tried to perform.

  • RESOURCE-ARN is the ARN of the AWS resource that the IAM user tried to access.

Cause: The IAM user you signed in to the AWS Cloud9 console with doesn't have the correct AWS access permissions to perform the action.

Solution: Ensure the IAM user has the correct AWS access permissions, and then try to perform the action again. For more information, see the following:

Federated Identities Cannot Create Environments

Issue: When you try to use an AWS federated identity to create an AWS Cloud9 development environment, an access error message is displayed, and the environment isn't created.

Cause: : AWS Cloud9 uses service-linked roles. The service-linked role is created the first time an environment is created in an account using the iam:CreateServiceLinkedRole call. However, federated users can't call IAM APIs. For more information, see GetFederationToken in the AWS STS API Reference.

Solution: Ask an AWS account administrator to create the service-linked role for AWS Cloud9 either in the IAM console or by running the command aws iam create-service-linked-role --aws-service-name cloud9.amazonaws.com from the AWS Command Line Interface (AWS CLI). For more information, see Using Service-Linked Roles in the IAM User Guide.

Environment Loading Screen Displays for a Long Time

Issue: When you try to open an environment, the IDE does not display after five minutes or longer.

Possible cause: Your web browser does not have third-party cookies enabled.

Recommended solution: Enable third-party cookies in your web browser, and then try opening the environment again. To enable third-party cookies:

If you want to restrict enabling third-party cookies only for AWS Cloud9 and your web browser allows this, specify the following domains, depending on the supported AWS Regions where you want to use AWS Cloud9.

AWS Region Domains

Asia Pacific (Singapore)

*.vfs.cloud9.ap-southeast-1.amazonaws.com

vfs.cloud9.ap-southeast-1.amazonaws.com

EU (Ireland)

*.vfs.cloud9.eu-west-1.amazonaws.com

vfs.cloud9.eu-west-1.amazonaws.com

US East (N. Virginia)

*.vfs.cloud9.us-east-1.amazonaws.com

vfs.cloud9.us-east-1.amazonaws.com

US East (Ohio)

*.vfs.cloud9.us-east-2.amazonaws.com

vfs.cloud9.us-east-2.amazonaws.com

US West (Oregon)

*.vfs.cloud9.us-west-2.amazonaws.com

vfs.cloud9.us-west-2.amazonaws.com

SSH Environment Error: "Python version 2.7 is required to install pty.js"

Issue: After you open an AWS Cloud9 SSH development environment, the terminal in the AWS Cloud9 IDE displays a message that begins with "Python version 2.7 is required to install pty.js."

Cause: To work as expected, an SSH environment requires that Python version 2.7 is installed.

Solution: Install Python version 2.7 in the environment. To check your version, from your server's terminal, run the command python --version . To install Python 2.7 on your server, see one of the following:

Cannot Run Some Commands or Scripts in an EC2 Environment

Issue: After you open an AWS Cloud9 EC2 development environment, you cannot install some types of packages, run commands such as apt, or run scripts containing commands that typically work with Linux operating systems such as Ubuntu.

Cause: The Amazon EC2 instance that AWS Cloud9 uses for an EC2 environment relies on Amazon Linux, which is based on Red Hat Enterprise Linux (RHEL).

Solution: If you install or manage packages or run commands or scripts in the IDE for an EC2 environment, ensure they are compatible with RHEL.

Amazon EC2 Instances Are Not Automatically Updated

Issue: Recent system updates are not automatically applied to an Amazon EC2 instance that connects to an AWS Cloud9 development environment.

Cause: Automatically applying recent system updates could cause your code or the Amazon EC2 instance to behave in unexpected ways, without your prior knowledge or approval.

Recommended solutions:

Apply system updates to the Amazon EC2 instance on a regular basis by following the instructions in Updating Instance Software in the Amazon EC2 User Guide for Linux Instances.

To run commands on the instance, you can use a terminal session in the AWS Cloud9 IDE from the environment that is connected to the instance.

Alternatively, you can use an SSH remote access utility such as ssh or PuTTY to connect to the instance. To do this, from your local computer, use an SSH key pair creation utility such as ssh-keygen or PuTTYgen. Use the AWS Cloud9 IDE from the environment that is connected to the instance to store the generated public key on the instance. Then use the SSH remote access utility along with the generate private key to access the instance. For more information, see your utility's documentation.

After Reloading an Environment, You Must Refresh Application Preview

Issue: After you reload an environment that displays an application preview tab, the tab doesn't display the application preview.

Cause: Sometimes users write code that can run an infinite loop or that otherwise uses so much memory that the AWS Cloud9 IDE can pause or stop when the application preview is running. To keep this from happening, AWS Cloud9 doesn't reload application preview tabs whenever an environment is reloaded.

Solution: After you reload an environment that displays an application preview tab, to display the application preview, choose the Click to load the page button on the tab.

Unable to Preview Application in the AWS Cloud9 IDE with HTTP

Issue: In the address box of an application preview tab in the AWS Cloud9 IDE, the URL always starts with https. If you try to change https in the box to http and then press Enter, the tab doesn't display the application preview.

Cause: To help improve code safety, in the address box of the application preview tab in the IDE, AWS Cloud9 always uses https. This behavior cannot be changed.

Solution: To view an application preview with an address starting with http instead of https, change https in the address box of the tab to http and then press Enter. Then choose the Open your page in a new tab button. This displays the application preview in a separate web browser tab using HTTP.