You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting an error on one of the last lines of your .circleci/config.yml file and I think it's because I set up my AWS infrastructure incorrectly. Here's the error that CircleCI is reporting for the aws ecs update-service command: An error occurred (InvalidParameterException) when calling the UpdateService operation: Task definition does not support launch_type FARGATE.
It looks like CircleCI's terrafrom configuration uses AWS Fargate, but your task definition is meant for EC2-type clusters. Is that correct?
Is there any guidance you can add (or a tutorial you can recommend) on how a cluster should be configured for use here? Thanks, in advance, for any pointers.
The text was updated successfully, but these errors were encountered:
FYI, I was hoping that I might get this working by just tweaking register-task-definition command, but a new error is complaining about the option I've added. I'm not sure why, since it seems to work this way in AWS' docs.
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:
aws help
aws <command> help
aws <command> <subcommand> help
Unknown options: --requires-compatibilities, FARGATE
I'm getting an error on one of the last lines of your
.circleci/config.yml
file and I think it's because I set up my AWS infrastructure incorrectly. Here's the error that CircleCI is reporting for theaws ecs update-service
command:An error occurred (InvalidParameterException) when calling the UpdateService operation: Task definition does not support launch_type FARGATE.
I'm new to ECS and couldn't figure out the setup based on your bullet points alone. I followed CircleCI's suggestion of using terraform to create an AWS stack.
It looks like CircleCI's terrafrom configuration uses AWS Fargate, but your task definition is meant for EC2-type clusters. Is that correct?
Is there any guidance you can add (or a tutorial you can recommend) on how a cluster should be configured for use here? Thanks, in advance, for any pointers.
The text was updated successfully, but these errors were encountered: