2 個答案
- 最新
- 最多得票
- 最多評論
1
Hi guys everything is working now
However i've a question my last one :) My colleague created exactly the same resource scheduler although as tag he wrote
- tag = Nico_WorkingHours value = true
On my side i wrote
- tag = ResourceScheduled value = true
Only because he change this it's working for him . And i've checked before there is no whitespace after or before the tag name. so my question is :
Are there any tags not to use?
已回答 2 個月前
0
thanks for your help i 've checked https://docs.aws.amazon.com/fr_fr/systems-manager/latest/userguide/running-simple-automations.html
And then i run the following command to check if it's work .
| Head |
|---|
| aws ssm start-automation-execution --document-name "AWS-RestartEC2Instance" --mode Interactive --region $AWS_REGION --parameters "InstanceId=i-0fdccec2XXXXXX" |
When i go to AWS systems Manager > Documents > AWS-RestartEC2Instance
and then i click on details in permissions i 've
POLICY ACCESS:
- AWS_ACCOUNT_test1 : Administrator access policy
- OU=Infra USERS=Test2 : AmazonSSMManagedInstanceCore policy ( i can START/STOP/DELETE ec2 instance from that account )
已回答 2 個月前
相關內容
AWS 官方已更新 3 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Could you please do this below steps troubleshoot to ensure that the stop and start actions are working as expected:
Check IAM Policies: Ensure that the IAM policies attached to the Test2 user and AWS_ACCOUNT_test1 account include the necessary permissions to perform the ssm:StartInstance and ssm:StopInstance actions on EC2 instances. The policies should also include permissions for the necessary Systems Manager actions.
Review Logging: Check the AWS Systems Manager Run Command logs and CloudWatch Logs for any errors or messages related to the stop and start actions. This can help identify any issues or failures that occur during the execution of the scheduled actions.
Test Manually: Try manually triggering the stop and start actions using AWS Systems Manager Run Command to see if they work as expected. This can help isolate whether the issue lies with Resource Scheduler configuration or with the underlying permissions or settings.