AWS Batch JobQueue does not provide computeResources required for managed ComputeEnvironment
See original GitHub issueAWS 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
- Create a
JobQueue
- 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:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top 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 >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@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?
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 likeComputeEnvironment.lotsOfMemory()
to help users, rather than implicitly creating the defaults.@andrestone Feel like whipping up a PR?