[BUILD-942] Enable execute command option for magnolia-mgmt tasks Created: 08/Nov/22  Updated: 04/Jan/23  Resolved: 04/Jan/23

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Roberto Gomez Assignee: Roberto Gomez
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Team: Foundation
Work Started:

 Description   

To access an Amazon ECS container on AWS Fargate or Amazon EC2 there's the AWS ECS execute command in the AWS CLI, which allows to log in to the Amazon ECS container.

See some references:

Right now we can't use this functionality because our terraform defined tasks don't have the functionality enabled.

It's required to enable prerequisites in the terraform scripts and try if we can login with something similar to:

 

aws ecs execute-command --cluster <cluster-name> \
--task <task-id> \
--container <container-name> \
--interactive \
--command "/bin/sh"}}



 Comments   
Comment by Roberto Gomez [ 04/Jan/23 ]

Test performed for validation: # Launched task with utility script ./run-magnolia-mgmt-task.sh magnolia-core-experimental VALIDATE_PR

  1. Setpup validated with amazon-ecs-exec-checker
  2. Successfully logged into the instance with ssh

{{}}

aws ecs execute-command \ 
  > --cluster mgnl-mgmt-cluster \ 
  > --container mgnl-mgmt-container \ 
  > --interactive \ 
  > --command "/bin/sh" \ 
  > --task arn:aws:ecs:eu-central-1:347299396223:task/mgnl-mgmt-cluster/6a394812cbf344a8b6d60d05fc3ec34b 

The Session Manager plugin was installed successfully. Use the AWS CLI to start a session. 

Starting session with SessionId: ecs-execute-command-0349094ea348b6acb 

# ls 
BOOT-INF META-INF org 

# uname -a 
Linux ip-172-31-45-94.eu-central-1.compute.internal 4.14.301-224.520.amzn2.x86_64 #1 SMP Fri Dec 9 09:57:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

{{}}

Generated at Sun Feb 11 23:46:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.