This GitHub Action is designed to assume a specific AWS role based on a provided environment name. It is particularly useful for workflows that require different AWS roles for different deployment or operational environments.
Required The name of the environment for which to assume the role. Current supported environments are:
biscred-devbiscred-prodbisnowvapor
-
Set AWS Role ARN for Environment: This step maps the provided environment input to its corresponding AWS Role ARN. It uses a Bash script to select the right ARN from a predefined list of environments and their associated roles.
-
Assume GitHub Actions Role: This step assumes a GitHub Actions role, which is a prerequisite for assuming the environment-specific AWS role.
-
Assume Environment-Specific AWS Role: Finally, this step assumes the AWS role that corresponds to the specified environment, allowing for subsequent actions to perform tasks using that role's permissions.
To use this action in your workflow, add a step that references it and provide the required input. Here's an example:
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Assume Role For Environment
uses: bisnow/github-actions-assume-role-for-environment
with:
environment: 'biscred-dev'Replace biscred-dev with the environment you wish to assume the role for.
Ensure that the AWS credentials needed to assume the GitHub Actions role are correctly configured in your repository's secrets. Test this action in a controlled environment before integrating it into production workflows.