Hi William, On Tuesday, October 17, 2017 at 8:32:53 AM UTC+2, William Saxton wrote: > > I'd like to use AWS to host my Angular web app, as well as use all of the > Amazon cloud services as necessary (DynamoDB, ElasticCache, etc). I > planned on using Elastic Beanstalk because I have experience with Heroku so > I assumed it was similar. > > But now I see a lot of advice to deploy apps to AWS via S3 instead. Is > this only for stack sites with static pages? Can you still deploy your > site to S3 and interact with other AWS services, such as authentication, > web services, etc? I don't see ANY examples of people deploying Angular to > Elastic Beanstalk, so I'm wondering if that's because S3 is the best way to > do it. >
You can deploy a static site on S3 (and then put Cloudfront in front of it, that's the usual way). As for interacting with other AWS services, it depends on services themselves and the design of your system. An Angular app can, from the client directly (e.g. browser) you can access AWS services using AWS Cognito or similar. E.g. for DynamoDB you'd use AWS JavaScript SDK which can sign your requests etc. The SDK will encrypt your payload etc. Other services, you might need to also deploy some sort of API or proxy, usually on ElasticBeanstalk or you can use an AWS Lambda function. The benefits of this direct approach is that you have no "backend" to maintain. The disadvantage is that each and all of your clients must what your datastructures look like, constrains etc. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
