1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Please review the following documentation https://docs.aws.amazon.com/chatbot/latest/adminguide/chatbot-cli-commands.html
As a workaround,
- you can Create a Lambda function and
- Create an IAM role for your Lambda function with the necessary permissions to update the ECS service and then
- Configure AWS ChatBot to allow invoking the Lambda function. This requires adding the necessary permissions to the AWS ChatBot IAM role.
- Use AWS ChatBot to invoke the Lambda function from Slack, passing the required parameters like cluster-name and service-name.
like the following
@aws lambda invoke --function-name your_lambda_function_name --payload '{"cluster-name": "cluster-a", "service-name": "service-a"}'
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa