Skip to content

W. Troubleshooting

Jump to bottom
Nicolas Dao edited this page May 6, 2022 · 3 revisions

Table of contents

Terminal utilities are failing with timeout errors ETIMEDOUT

This is most likely due to one of the following:

  • Missing security group inbound or outbound rule.
  • The private subnet is not able to access the public internet because:
    • It has no route table configured with a NAT gateway.
    • Or there is no VPC endpoint configured to access the resource.
  • The VPC's ACL prevents connection to happen.

AWS Lambda cannot access the public internet

Please refer to the A few words about AWS Lambda section.

failed to create '/home/sbx_userxxxx/.pulumi'

Please refer to the Setting it up in Docker section.

no resource plugin 'aws-v4.17.0' found in the workspace or on your $PATH

This typically happens with the Automation API. The AWS Pulumi plugin is not found because:

  • You have not installed the AWS plugin with the stack.workspace.installPlugin('aws', 'v4.17.0').
  • You have installed the incorrect version of this plugin. The tutorial usually shows this example: stack.workspace.installPlugin('aws', 'v4.0.0'). The plugin is version sensitive.

Which version of the AWS SDK is required depends on the Pulumi version you're using. The best way to found out is to try to deploy without installing the AWS SDK, then read the error message to figure the version out.

AWS Lambda: IMAGE Launch error: fork/exec /lambda-entrypoint.sh: exec format error

This typically happens when the image used to run Lambda containers is using an OS that is incompatible with the expected Lambda OS. For example, amazon/aws-lambda-nodejs:14.2021.09.29.20 uses the arm64 architecture. This error will occur if the Lambda has been configured with its default x86_64 architecture.

To fix this issue, please refer to the ARM architecture recommended section.

AWS Aurora: Error creating DB Proxy: InvalidParameterValue: RDS is not authorized to assume service-linked role

Please refer to warning in the Enabling RDS proxy section.

AWS Aurora: error registering RDS DB Proxy ... InvalidDBInstanceState: DB Instance... is in an unsupported state

Please refer to warning in the Enabling RDS proxy section.

Docker: No 'docker' command available on PATH: Please install to use container 'build' mode

This message is misleading. It can either mean that:

  • the docker CLI is not installed on your machine or;
  • the docker daemon is not running on your machine.
Clone this wiki locally