Description
Bug reports which fail to provide the required information will be closed without action.
Required Basic Info
- Accelerator Version: 1.5.10
- Install Type: Clean
- Upgrade from version: N/A
- Which State did the Main State Machine Fail in: Phase 0 (Get or Create Configuration from S3)
Describe the bug
Step function failes because CodeCommit is disabled for new AWS accounts since July 25 https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/
Failure Info
"cause": {
"errorType": "OperationNotAllowedException",
"errorMessage": "CreateRepository request is not allowed because there is no existing repository in this AWS account or AWS Organization",
"trace": [
"OperationNotAllowedException: CreateRepository request is not allowed because there is no existing repository in this AWS account or AWS Organization",
" at constructor.Mgn (/var/task/index.js:1:4761)",
" at constructor.callListeners (/var/task/index.js:1:47227)",
" at constructor.emit (/var/task/index.js:1:46935)",
" at constructor.emitEvent (/var/task/index.js:2:29765)",
" at constructor.n (/var/task/index.js:2:25318)",
" at jpe.runTo (/var/task/index.js:2:1221)",
" at /var/task/index.js:2:1433",
" at constructor. (/var/task/index.js:2:25533)",
" at constructor. (/var/task/index.js:2:29820)",
" at constructor.callListeners (/var/task/index.js:1:47332)"
]
},
"error": "OperationNotAllowedException"
The problem i think is that CodeCommit is disabled for new users since 2024 july 25 according to https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/
Required files
not needed
Steps To Reproduce
- Go to 'Step Functions'
- Click on 'ASEA-MainStateMachine_sm'
- See error
Expected behavior
Step functions should run smoothly and create accounts added in config.json
Additional context
Are there any alternatives to setup the automation without using codecommit repository ?