aws-amplify / aws-amplify/amplify-studio

How to manage contents across different environments [EN/FR]

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

Description

### Which Specific Feature is your question related to?

Environment managing

### Question

Hello,

We have a website with several environments (dev, staging and prod) on Next.JS and I couldn't find how to send content from one environment to another. For example, once I decide that my dev environment is ready to be sent to staging, how do I duplicate the content in staging?

Because when I clone an environment I recover the data-models but not the contents associated with it.

On the tutorials that I find on the internet each time they do not have this problem because they only use one environment.

Can you tell me what is the best way to manage my back-end environments with amplify studio and especially how to easily duplicate my content from one environment to another.

Thanks a lot for your help.
Have a good day.

PS: I am French, so if there are French people who can answer it is with pleasure!

Contributor guide

Open the contributing guide

Research direction

The issue mentions Amplify Studio environment management for a Next.js site, but names no files, tests, or code entry points. Start by reviewing the documented workflow for cloning environments and transferring content; done would be a clear, supported explanation of how to duplicate content from dev to staging or confirmation that the capability is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, next.js
Domain
backend, cloud
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.