Separation of Prod and Non-Prod accounts for Amplify Console when using CodeCommit

[timothy-baker]

Is your feature request related to a problem? Please describe.

Per AWS best practices, I'd like to keep my non-prod and prod environments in separate accounts with varying degrees of IAM access based on least-priviledges. I am using CodeCommit as a repository for my application code. The Amplify Console requires a connection to a specific CodeCommit branch within the same account. CodeCommit does not allow me to initiate and accept pull requests across accounts, so I have no way to maintain my master code branch in one account, then promote it to production via pull request to my prod account to trigger a build and deploy.

Describe the solution you'd like

I see two possible resolutions to this problem:

1. Allow Amplify Console access to CodeCommit resources in separate accounts, or
2. Allow cross-account / cross-repo pull requests in CodeCommit

[rfpedrosa]

I also need this. It is frustrating that we can connect to Github from multiple AWS accounts on Amplify but not to Code Commit (own by AWS itself!)

[rfpedrosa]

another problem of the console is that amplifyPush --simple does not pick settings from team-provider-info.json

[TLaue]

Will this feature be supported in the near future? Any information about this?

[swaminator]

@TLaue @rfpedrosa @timothy-baker we have prioritized this work and will update you when we have it ready.

[swaminator]

another problem of the console is that amplifyPush --simple does not pick settings from team-provider-info.json

@rfpedrosa can you be a little more explicit about what you mean?

[rfpedrosa]

@swaminator I think I was using amplifyPush --simple in Amplify Console and amplifyPush --simpledidn't look on team-provider-info.json file to find out, for example, what is the AmplifyAppId to use for the environment I was deploying. That makes amplifyPush --simple to fail when I was using a single Amplify console setup and 2 AWS regions for prod & non-prod environments. Does that make sense?

It is being a while since I comment this and I'm not working with Amplify currently so I may be missing something

[akshaymishi]

Any update on this request, facing same problem wherein want to access Code Commit Repo from cross/another account.

@swaminator any update you have on this? Seems like feature is in discussion for long.

[ericwolf08]

any update here?

[ddongEee]

can you plz update this one? @swaminator Thanks!

[creativeleep-zz]

+1 please update. I have a project stalled. I don't want to get to the point where they rip out Amplify.

[danfreid]

+1. Forcing us to use GitHub if CodeCommit not enabled within next few weeks. Is it close?

[macamhi]

+1 for allowing Amplify access to CodeCommit in other accounts.

[HeejongLee-aws]

+1 Please update. I have a same problem. we will change github to code commit, but AWS Amplify can't access code commit repo in another account.

[katsa9]

+1 Please can this feature be implemented. Most organisations want a separate prod account that can access the same code as the dev environment.

[sasedlock]

+1 from another team that is facing the same challenge.

[adnan-iqbal-ch]

+1

[jkelting]

+1

[vinoth12988]

@swaminator - Any update or roadmap for allowing cross account code commit repo in amplify? pls update so that we can plan.. This became must need for projects where we maintain central Code commits in another account.

[heejonglee]

+1

[MishFTW]

Hey all, any new updates to this?

[ConnectivityChris]

+1

[macamhi]

We actually went past this by having a CodeCommit on each account, and pushing the required branch from (a local clone of) the dev repo to the Pre-prod or Prod repo (using Git Remote CodeCommit ). This is actually very simple once set up and allows for good control of deployment. One needs to remember that contrary to CVS or SVN, Git is distributed by nature, so it makes no sense trying to have a 'central' Git repository.

[koxon]

+1

[maziarzamani]

+1

[mageyuki]

+1

[yaguirre]

@swaminator do you have any updates about this issue??

[rickspark4]

its 2023, any update ?

[rayrapetyan]

Seems AWS is not going to provide an access to code repos hosted in AWS. Maybe because they think GitHub is good enough for everyone?

[jatin1201]

Guys any plans for this?

[dhaval-s]

It would be beneficial if we could enable cross-region CodeCommit access for Amplify when creating an Amplify app using CDK. so please prioritize this feature.