Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
While configuring Hyperlane nodes on AWS, I noticed that AWS officially recommends using temporary credentials associated with an IAM role, rather than using static access keys when creating an IAM user.
Would it be possible to add support for configuring this part of the setup with an IAM role? This would align with AWS best practices and enhance the security of the deployment process.
Using role would have extra step for hyperlane node configuration, but still it would be good for user that they do not have to Access_key
Solution
Describe the solution you'd like
Update code to functional with configs that takes AWS IAM role instead of IAM access key
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Nice to Have
Describe non-essential extensions to the solution
Additional features which should be implemented if they are easy to accommodate but otherwise can be skipped
mild-design
commented
2 months ago
Problem
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is.
While configuring Hyperlane nodes on AWS, I noticed that AWS officially recommends using temporary credentials associated with an IAM role, rather than using static access keys when creating an IAM user. Would it be possible to add support for configuring this part of the setup with an IAM role? This would align with AWS best practices and enhance the security of the deployment process.
Using role would have extra step for hyperlane node configuration, but still it would be good for user that they do not have to Access_key
Solution
Describe the solution you'd like
Update code to functional with configs that takes AWS IAM role instead of IAM access key
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Nice to Have
Describe non-essential extensions to the solution Additional features which should be implemented if they are easy to accommodate but otherwise can be skipped