aws-amplify / aws-amplify/amplify-studio

Manage access to allow devs to only work on a specific environment.

Open
#968 2 comments 3 reactions 0 assignees View on GitHub
feature-request general
Dominant language
No language data
Stars
135
Forks
32
PR merge metrics
No merged PRs in 30d

Description

### Describe the feature you'd like to request

Lets say we have two environments, (prod and dev) and I want to give access to only dev environment to my team.
By default, in manage access section of amplify you can only give full access wich gives access to every environments...

![image](https://github.com/aws-amplify/amplify-cli/assets/70602862/3c682e0b-faef-4d32-a7d0-d0011bf39173)

But I want to restrict team permission to only be able to interact with the `env` environment

So far, only thread ive found about this were left with no answers.

### Describe the solution you'd like

1. Add an option to manage access on specific environnement

or

2. Provide a step by step guide on how to do it either in the doc or simply in this feature request discussion, so people can refer to this..

Thank you in advance.

### Describe alternatives you've considered

So far, only thread ive found about this were left with no answers.

I was thinking about creating a custom role for a specific environnment. Add required policies to the role then assign that role to users..

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Amplify Studio Manage access flow described in the issue and the proposed custom IAM role and policies. Done means either team members can interact only with the specified environment, or a step-by-step guide explains how to configure those environment-scoped permissions.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
authorization, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.