Should point out that elasticsearch doesn't really fit well with the whole 'serverless' part of Amplify.
I started a little side project a couple of months back to try and see if Amplify could be a potential tool for more serious projects - added an '@searchable' directive early last month and suddenly my usual aws bill of $1.50 is over $40 (the db has zero data on it 😆).
My fault of course, should have read things more clearly, but I think it's easy to miss the fact that elastic-search is charged per hour, every hour, regardless of whether it is being used and whether the rest of your application is 'serverless'.
@Hemal I had the same disappointment. I've spent more than $100 with elasticsearch. Do you know if it is possible to create an elasticsearch with no cost? As if it was included in the Free Tier package?
Yes, you can clone any amplify back end by copying the Amplify folder and running amplify init. Be sure to remove the team-provider-info.json if working from a different account
Yes, this is more of a DynamoDB feature. Check out here for the launch announcement and here for the docs.
For the first question, ok for cloning the back-end with amplify-cli but I would like to clone datas too. To see the impact on datas after the structure change.
Thanks.
For me it's like Amplify has the perfect timing, every time i need something, a brief time passes and then i'm able to easily utilize the feature i needed! <3
Work at Docker Inc. Ex Serverless.com. Ruby, Golang, API Aficionado, Serverless, Docker, Mesosphere. Asst. Scoutmaster at BSA Troop 39. Amateur Photographer. Entrepreneur.
Should point out that elasticsearch doesn't really fit well with the whole 'serverless' part of Amplify.
I started a little side project a couple of months back to try and see if Amplify could be a potential tool for more serious projects - added an '@searchable' directive early last month and suddenly my usual aws bill of $1.50 is over $40 (the db has zero data on it 😆).
My fault of course, should have read things more clearly, but I think it's easy to miss the fact that elastic-search is charged per hour, every hour, regardless of whether it is being used and whether the rest of your application is 'serverless'.
@Hemal I had the same disappointment. I've spent more than $100 with elasticsearch. Do you know if it is possible to create an elasticsearch with no cost? As if it was included in the Free Tier package?
Not that I found no :(
I am really a fan of how Amplify simplifies our life. It gives a boost to development.
Thanks for sharing such valuable articles.
Hi Nader,
I am a big fan of AWS Amplify but I have two remarks/questions :
Hey, sure I'd be happy to help:
Yes, you can clone any amplify back end by copying the Amplify folder and running
amplify init. Be sure to remove the team-provider-info.json if working from a different accountYes, this is more of a DynamoDB feature. Check out here for the launch announcement and here for the docs.
For the first question, ok for cloning the back-end with amplify-cli but I would like to clone datas too. To see the impact on datas after the structure change.
Thanks.
yes!!! great work. these features will be a major benefit to me at current stage of development. perfect timing!!
Do we have the Many-Many relationship yet for model directive?
github.com/aws-amplify/amplify-cli...
For me it's like Amplify has the perfect timing, every time i need something, a brief time passes and then i'm able to easily utilize the feature i needed! <3
Excellent article, Nader