Browse through the questions and answers listed below or filter and sort to narrow down your results.
1
answers
0
votes
3
views
Nathaniel
asked 9 days ago
0
answers
0
votes
2
views
AWS-User-7955457
asked 14 days ago
0
answers
0
votes
0
views
ianliu
asked 14 days ago
2
answers
0
votes
3
views
acrookes-fe
asked 18 days ago
1
answers
0
votes
3
views
AWS-User-4573028
asked 18 days ago
0
answers
0
votes
4
views
Yass
asked 25 days ago
0
answers
0
votes
6
views
steffew
asked a month ago
2
answers
0
votes
5
views
AWS-User-13413
asked a month ago
1
answers
0
votes
9
views
AWS-User-7732475
asked 2 months ago
1
answers
0
votes
4
views
FabreLambeau
asked 2 months ago
1
answers
0
votes
3
views
AWS-User-6786633
asked 2 months ago
0
answers
0
votes
6
views
Nathaniel Ng
asked 2 months ago
1
answers
0
votes
6
views
Nathaniel Ng
asked 2 months ago
0
answers
0
votes
3
views
Nuthinking
asked 2 months ago
1
answers
0
votes
2
views
AWS-User-4115193
asked 2 months ago
1
answers
0
votes
6
views
PaulSPNW
asked 2 months ago
0
answers
0
votes
7
views
Nathaniel Ng
asked 2 months ago
0
answers
0
votes
6
views
Tomas Linhart
asked 3 months ago
1
answers
0
votes
4
views
Tomas Linhart
asked 3 months ago
0
answers
0
votes
5
views
AWS-User-9170141
asked 3 months ago
1
answers
0
votes
4
views
FabreLambeau
asked 3 months ago
1
answers
0
votes
3
views
FabreLambeau
asked 3 months ago
1
answers
0
votes
11
views
Jacques Blom
asked 3 months ago
0
answers
0
votes
7
views
fatihbayhan
asked 4 months ago
2
answers
0
votes
15
views
AWS-User-7169533
asked 4 months ago
1
answers
0
votes
4
views
AWS-User-7211613
asked 4 months ago
First Batch job fails with CannotPullContainerError
I am trying to walk through the simple ["Submit your first Batch job"](https://us-east-2.console.aws.amazon.com/batch/home?region=us-east-2#firstRun) for AWS Batch. I go through all of the 5 steps, choosing Fargate as the platform, and leaving all items at default values, and finally submit the job. However, the job fails with this status reason:
CannotPullContainerError: inspect image has been retried 5 time(s): failed to resolve ref "docker.io/library/amazonlinux:latest": failed to do request: Head https://registry-1.docker.io/v2/library/amazonlinux/manifests/latest: dial tcp 34.237.244.67:44...
I am probably missing something very basic, but have no idea what. Thanks!
Accepted AnswerAWS Batch
1
answers
2
votes
8
views
AWS-User-1284415
asked 4 months ago
1
answers
0
votes
4
views
yodiggity
asked 4 months ago
1
answers
0
votes
7
views
yodiggity
asked 4 months ago
2
answers
0
votes
10
views
Walesa
asked 4 months ago
1
answers
0
votes
9
views
Nuthinking
asked 4 months ago
G5 instances support
Hello,
I wonder if there are plans to add support for AWS G5 instances for AWS Batch? They are much better than G4dn instances and there is much more availability compared to G4dn instances. I often have to wait the entire day to get access to a single G4dn instance in `us-east-1` and the same problem is starting to occur in `us-west-2`.
Accepted AnswerAWS Batch
1
answers
1
votes
6
views
Ekami
asked 5 months ago
1
answers
0
votes
9
views
SDOne
asked 5 months ago
1
answers
0
votes
8
views
Humayun Ahmed
asked 5 months ago
1
answers
0
votes
17
views
AWS-User-9709756
asked 5 months ago
1
answers
0
votes
21
views
Jesse
asked 5 months ago
how to delete compute environment that is invalid ?
I run the command
```
aws batch delete-compute-environment --compute-environment batch-environment
```
It returns with no other messages but the compute environment still persist.
Accepted AnswerAWS Batch
3
answers
0
votes
15
views
Nicholas Yue
asked 5 months ago
1
answers
0
votes
1
views
dirkh
asked 9 months ago
1
answers
0
votes
0
views
zeds
asked a year ago
2
answers
0
votes
0
views
mihaj
asked a year ago
2
answers
0
votes
0
views
4TufZB
asked 2 years ago
1
answers
0
votes
8
views
AWS-User-8131993
asked 2 years ago
1
answers
0
votes
4
views
Maciom
asked 2 years ago
2
answers
0
votes
4
views
4TufZB
asked 2 years ago
1
answers
0
votes
1
views
Netanel
asked 2 years ago
1
answers
0
votes
2
views
epchaves
asked 3 years ago
Can I force each job to run on a dedicated instance?
Hi folks,
I have some ETL jobs that is already containerized and as of today we do all orchestration by our self's in a kind of "in house made aws-batch version".
I'm considering to move to AWS Batch but in order to do so I would like to have each Job to run on a dedicate instance due to disk space requirements. By sharing an instance we risk running out space in the middle of the job execution.
From what I could see in terms of how AWS Batch handle compute requirements the decisions on when to launch a new instance is based solely on vCpu and Memory. Is there a way to instruct Batch to never send two jobs to the same running instance?
Thanks in advance,
Accepted AnswerAWS Batch
2
answers
0
votes
3
views
epchaves
asked 3 years ago
3
answers
0
votes
0
views
looloo
asked 3 years ago
Managed compute environment, launches m4 instead of m5
Hi,
We migrated a few of our scheduled jobs to run aws batch and i have a few questions about the behaviour that i cant find online.
The auto scaling groups provisions m4 instances instead of m5s? which would be cheaper, is there a reason for this?
The allowed instances is on "optimal" which indicates this(i'll admit i didnt read this at the time of creating the environment).
The other question is, whenever it scales up an instance, it keeps it alive for a minimum of 10 minutes even if there are no jobs in a runnable status,
is this intended? I read that at the end of the ec2 billing cycle it will check if there are no jobs that are runnable and then scale down, which is weird to me because i read that ec2 is per second billing?
Kind Regards and thanks in advance
Accepted AnswerAWS Batch
1
answers
0
votes
0
views
looloo
asked 3 years ago
1
answers
0
votes
0
views
parker9
asked 3 years ago
1
answers
0
votes
0
views
steffew
asked 3 years ago
2
answers
0
votes
0
views
markotitel
asked 3 years ago
1
answers
0
votes
1
views
arian
asked 3 years ago
2
answers
0
votes
0
views
jakehagen
asked 3 years ago
1
answers
0
votes
0
views
Siddharthvij
asked 3 years ago
Does AWS Batch support EC2 Spot stop/start and hibernation
Does AWS Batch have support for EC2 spot stop/start and hibernation options to handle interruptions?
The options are documented here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
But I am unable to find reference of whether AWS Batch can support this. From my understanding, if a Spot instance is terminated, AWS Batch retries the job from the start.
Accepted AnswerAWS Batch
1
answers
0
votes
2
views
AWS-User-1615037
asked 4 years ago
1
answers
0
votes
2
views
AWS-KH
asked 4 years ago