- Newest
- Most votes
- Most comments
It looks like you're encountering an error while trying to migrate from Amazon Elastic Transcoder to AWS Elemental MediaConvert. The error message indicates that your script is trying to import a module called 'job' that cannot be found.
This is likely because you need to download all the necessary JavaScript files for the migration tool. The error "Cannot find module 'job'" suggests that your convert-job.js script is trying to require a file named job.js that should be in the same directory.
When migrating from Elastic Transcoder to MediaConvert, you need to ensure you have all the required script files in your CloudShell environment. The migration tools typically include multiple JavaScript files that work together.
Please ensure that all js and other dependencies files are present in the directory while running the command.
Additionally, you might be experiencing a permissions issue with CloudShell itself. The error could be related to missing permissions like cloudshell:PutCredentials or cloudshell:ApproveCommand. Adding the cloudshell:* permission to your IAM role might help resolve this issue.
Remember that Amazon Elastic Transcoder will be discontinued on November 13, 2025, so it's important to complete your migration to AWS Elemental MediaConvert before that date. MediaConvert offers more advanced features and better pricing compared to Elastic Transcoder.
Sources
Support for Amazon Elastic Transcoder ending soon | AWS for M&E Blog
Migrating workflows from Amazon Elastic Transcoder to AWS Elemental MediaConvert | AWS for M&E Blog
Migrating workflows from Elastic Transcoder to Amazon Elemental MediaConvert | AWS for M&E Blog
AWS CLI permissions error? when running "aws ec2 describe-instances --output text > ec2s.txt" | AWS re:Post
For further troubleshooting. Please open a support case with AWS using the following https://support.console.aws.amazon.com/support/home#/case/create
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 7 months ago
