Make CodeCommit accessable using a configured AWS profile

[SpielerNogard]

Is your feature request related to a problem? Please describe.
Hey i wanted to try daytona, and was impressed, that i supports AWS CodeCommit, which is not supported by most other software. But since we are using AWS SSO, i would need support for already configured profiles from my machine.

Describe the solution you'd like
I would wish for instead of the need for configuring AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to just use my already configured AWS profile

[Tpuljak]

Hi @SpielerNogard,

Thanks for pointing this out.

We initialize the AWS CodeCommit client with default options.
From what I can see in the function definition, it should automatically load configured profiles.

That being said, we might need to explicitly set the shared profile that should be loaded.

We could implement an additional environment variable (e.g. DAYTONA_AWS_SHARED_PROFILE) that you could set to the name of the profile that should be used. Then we could read that env and load the appropriate profile.
What do you think about that approach?

[SpielerNogard]

Nice idea, would be a good start. But i would like to see it in the git-provider add command, that i can specify the profile name.

[SpielerNogard]

And would also be nice if we can do the same for the AWS provider for workspaces

[Tpuljak]

And would also be nice if we can do the same for the AWS provider for workspaces

Do you mind opening an issue for that on https://github.com/daytonaio/daytona-provider-aws?

Nice idea, would be a good start. But i would like to see it in the git-provider add command, that i can specify the profile name.

I suggest we start with the env var that both the server and provider can read. Also, adding such an exclusive property to a git provider will require more significant changes which we can implement at a later point.