Normally, for authentication of GitHub workflow with a cloud provider, we have to give the credentials, these credentials are usually stored as a secret in GitHub to get our job done. But, having long-lived credentials is not a good security practice. So, instead of generating and hard-coding the credentials in GitHub, we can use short-lived credentials using OpenID connect.
At ScaleReal, we have a multi-account AWS setup and recently we came across a situation where we wanted to apply our terraform scripts across two AWS accounts where some of the resources would get created in one AWS account and some of the resources would get created in another AWS account.
At ScaleReal, we have a multi-account AWS setup and recently we came across a situation where we wanted to apply our terraform scripts across two AWS accounts where some of the resources would get created in one AWS account and some of the resources would get created in another AWS account.