awslabs / awslabs/aws-deployment-framework
aws-deployment-framework-base-templates CodeBuild project timeout
- Dominant language
- Python
- Stars
- 699
- Forks
- 235
- Avg merge
- 20h 53m
- Merged PRs (30d)
- 7
Description
## Description
We use a lot of regions and have a lot of accounts. When performing an upgrade you might not have enough time to perform all the necessary steps. For this reason we updated the timeout of the `aws-deployment-framework-base-templates` project from `40` to `240`. But after an hour the temporary credentials expire and the project stops.
## Workaround
Trigger the pipeline again by clicking the "Release" button.
## Solution(s)
There are 2 solutions possible:
* When the credentials almost expire they need to be renewed.
* Replace the whole process with StepFunctions (preferred option as it also includes cost savings)
I know that there are some initiatives to move to StepFunctions already. This is just another reason why it's a good idea.
Contributor guide
Research direction
Start by reviewing the aws-deployment-framework-base-templates CodeBuild project and how its temporary credentials are used during upgrades. Compare credential renewal with the proposed StepFunctions replacement, noting the existing Release-button workaround. Done means a multi-region, multi-account upgrade can run beyond the credential lifetime without stopping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100