RFC: Importing Existing AWS Resources to Amplify Project using the Amplify CLI

Currently, the CLI provisions new AWS resources based on the categories that you add to your Amplify project. This RFC is to gauge community interest and hear more thoughts around the CLI being able to import existing resources into an Amplify project. As an MVP, we’re planning to support importing of resources in the following categories: * Auth * Storage (S3 & DynamoDB) * API - REST and GraphQL (to use existing data sources and auth resources) We’ll be relying heavily on the new CloudFormation import functionality - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/resource-import-existing-stack.html for this feature **Auth** * Ability to add an existing Cognito user pool to an Amplify backend environment as a part of the amplify add auth flow * Ability to specify a new or use the same Cognito user pool used in an existing environment when creating a new Amplify backend environment * Ability to update and manage the imported Cognito user pool via the CLI as a part of the amplify update auth flow to add features like Lambda triggers to your existing Cognito user pool **Storage** * Ability to add an existing S3 bucket as a part of the amplify add storage flow * Ability to add an existing DynamoDB table as a part of the amplify add storage flow * Ability to update and manage the imported and S3 and DynamoDB tables as a part of the amplify update storage flow * Ability to specify a new or use the same S3 & DynamoDB tables used in an existing environment w

Posted by kaustavghosh06 on Apr 15, 2020, 11:45 PM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [RFC] Roadmap to v2.0