- Newest
- Most votes
- Most comments
Hi seargex,
The problem you are currently experiencing seems to be caused by the expiration of the IAM Role attached to EC2.
This problem will be resolved if you modify IAM Role which is attached to the instance.
- Modify IAM Role: EC2 > Choose EC2 Instance to modify > [Actions] > [Security] > "Modify IAM role"
You can refer to the document below for the required permissions:
[+] Create an IAM Policy with Fleet Manager permissions (AWS Documentation)
Please refer to the case in Stack Overflow which includes an answer from AWS Support Team for S3 about a similar situation: [+] stack-overflow aws credentials refreshed but still expired
FYI. You can also check the expiration of the credentials with the command below:
TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` && curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/meta-data/iam/security-credentials/<YOUR+EC2+IAM+ROLE>]
[+] Retrieve security credentials from instance metadata
If I have missed anything or answered wrong, please feel free to ask me again. Also you have any questions, comment please!
turns out there's a problem with the local time on the OS instances, i have to use Amazon Time Sync Service to sync up the time with it and it solves the problem.
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago