- Newest
- Most votes
- Most comments
To run a .bat file inside an EC2 Windows instance using a service account, you can use AWS Systems Manager Run Command. With Run Command, you can remotely execute commands on your EC2 instances without having to log in to each instance.
https://docs.aws.amazon.com/systems-manager/latest/userguide/run-command.html
Or you can also do it manually by Remote Desktop with elevated privileges: Connect to the EC2 instance using RDP with an account that has administrative privileges. Once connected, navigate to the directory containing the .bat file and run it as usual.
FEW approaches for automatic execution:
User Data Script: When launching a new EC2 instance, you can leverage the User Data field. Paste the contents of your .bat file there, and it will be executed automatically during the first boot. However, this won't involve a service account.
Scheduled Tasks with Service Account: Configure a scheduled task to run the .bat file at the desired time. You can set the task to run under the specific service account using its credentials.
Relevant content
- asked 3 months ago
- Accepted Answer
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 7 months ago
Thank you akad. I tried to configure a scheduled task to run the .bat time using a service account.
I was just wondering why would saving the scheduled task work after entering the credentials for a service account, but not after entering the credentials for a user account? Is it because the service account credentials are not stored in the AWS EC2 instance, while user account credentials will be stored in the EC2 instance for running the scheduled task?