New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS CDK provider #171

Open
0xdevalias opened this Issue Sep 15, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@0xdevalias

0xdevalias commented Sep 15, 2018

Describe the solution you'd like

Currently Amplify only supports direct CloudFormation as a provider, and does so by using JSON templates. I read somewhere that other providers can be implemented, and that a future goal is to support multiple providers. It would be great to have an AWS CDK provider, that constructs similar features, but in CDK code.

I feel like this would make it easier to implement new features in Amplify, leveraging common usecases and improvements (eg. asset upload, AWS SAM transformations, YAML output, etc)

Currently I wasn't able to find much of any information/documentation on what is required to implement a custom/new provider, so maybe documenting that/making it easier to discover would be useful as part of this also.

Describe alternatives you've considered

Using AWS CDK / SAM separately, and/or consuming externally generated resources through exports.

Additional context

See also: #160

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment