2 Answers
- Newest
- Most votes
- Most comments
2
Hello.
I usually use IAM Identity Center to access my AWS accounts, and I don't see any particular disadvantages to it.
When migrating, I think it would be a good idea to pay attention to the following points.
For example, if you are issuing an access key as an IAM user and hard-coding it into your application, or if you are using it in an AWS CLI shell script, it may stop working.
Therefore, when migrating to IAM Identity Center, I recommend that you do not delete IAM users suddenly, but instead check to see if they have issued access keys before deleting them.
0
Hi! We did a livestream this week on Twitch where we covered your question in greater depth. You can check out a recording of the show.
Thank you, @StephenH_AWS. I will check it out.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 5 months ago
Thanks for your answer and suggestion. Should I also move programatic access to IAM Identity Center as well? Currently, I use IAM and long-term credentials for my applications. The keys are not hardcoded in the application code, but I store those credentials in the database.
If the application is running on-premises, you will need an access key issued by an IAM user, so there is no need to migrate it. Consider using IAM roles if your application is hosted on AWS, such as EC2.