question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AWS Batch JobQueue does not provide computeResources required for managed ComputeEnvironment

See original GitHub issue

AWS Batch JobQueue does not provide computeResources required for managed ComputeEnvironment. Since JobQueue does not require the user to provide a computeEnvironmentOrder, the default ComputeEnvironment created by it should provide some computeResources as required by ComputeEnvironment.

Need to be fixed after the change in #6549

Reproduction Steps

  1. Create a JobQueue
  2. Try to deploy.

Error Log

You will get the following error

computeResources is missing but required on a managed compute environment

Environment

  • CLI Version : 1.27.0
  • Framework Version:
  • OS :
  • Language :

Other


This is 🐛 Bug Report

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
iliapolocommented, Mar 7, 2020

@ayush987goyal You’re right. It was an oversight in the initial PR that introduced these L2’s.

@andrestone Has already added some content to the page with the launch template support PR.

I wouldn’t want to overwhelm this PR with adding all this content right now. I will create a separate issue for completing the README with all the necessary examples and explanations.

Sound good?

1reaction
iliapolocommented, Mar 7, 2020

I agree that making the computeEnvironments property required at this stage is better. It makes more sense to me for any use case that isn’t just sanity testing. Maybe we can think of a default compute environment later on. And even then I would probably prefer having something like ComputeEnvironment.lotsOfMemory() to help users, rather than implicitly creating the defaults.

@andrestone Feel like whipping up a PR?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Compute environment - AWS Batch
Job queues are mapped to one or more compute environments. Compute environments contain the Amazon ECS container instances that are used to run ......
Read more >
AWS::Batch::ComputeEnvironment ComputeResources
Details about the compute resources managed by the compute environment. This parameter is required for managed compute environments.
Read more >
Compute environment parameters - AWS Batch
Choose MANAGED to have AWS Batch manage the EC2 or Fargate compute resources that ... These jobs are from an associated job queue...
Read more >
AWS::Batch::ComputeEnvironment - AWS CloudFormation
The ComputeResources property type specifies details of the compute resources managed by the compute environment. This parameter is required for managed compute ...
Read more >
AWS::Batch::JobQueue - AWS CloudFormation
AWS Batch doesn't support mixing compute environment architecture types in a single job queue. Required: Yes. Type: List of ComputeEnvironmentOrder.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found