Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I am trying to develop a Spring Cloud microservices using Spring MVC and Spring boot. And I would like to deploy in AWS cloud. When I exploring the AWS I found the computing service EC2 and Storage services EBS and Elastic Beanstalk. I found that when creating EC2 getting a default EBS volume.
Here my doubt is that when I deploying my Spring Cloud microservice in Tomcat environment. I also need to create a RDS instance for my microservice, can I choose S3 as storage?
And also I need to deploy my Angular 2 application using S3 and static web site hosting method. So can I use separate buckets for both microservices and Angular application hosting?
I am new to AWS and cloud service platform.
On S3 you can save files; its more like extensible storage as a sevice.
RDS is like RDBMS as a service..
Surely you can use separate buckets ; or different folders in same buckets.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
We are building a small micro service architecture which we would like to deploy to AWS.
The number of services is growing, so we need solution that allows scaling (horizontal).
What's the best way to build this on AWS? We don't have too much experience with docker, we used EC2 based stuff in the past.
I'm thinking about something like:
Use ECR, create a private docker repository. We push release images there.
Use ECS to automatically deploy those images.
Is this correct? Or should we go for Kubernetes instead? Which one is better?
Our needs:
Automated deployments based on docker images
Deploy to test and prod environments
Prod cluster should be able to handle multiple instances of certain services with load balancing.
Thanks in advance for any advice!
AWS container service team member here. Agreed with others that answers may potentially be very skewed to personal opinions. If you come in with good AWS knowledge but no container knowledge I would suggest ECS/Fargate. Note that deploying on ECS would require a bit of CloudFormation mechanics because you need to deploy a number of resources (load balancers, IAM roles, etc) in addition to ECS tasks that embeds your containers. It could be daunting if not abstracted.
We have created a few tools that allows you to offload some of that boiler plating. In order of what I would suggest for your use case:
Copilot which is a CLI tool that can prepare environments and deploy your app according to specific patterns. Have a look here
Docker Compose integration with ECS. This is a new integration we built with Docker that allows you to start from a simple Docker Compose file and deploy to ECS/Fargate. See here.
CDK is a sw development framework to define your AWS infrastructure as code. See here. These are the specific CDK ECS patterns if you want to go down that route.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
An AWS EKS Cluster can be created using the AWS CLI or eksctl commands. And AWS is supporting both of them. Both of them at the end of day creates a EKS cluster.
When to use what? I am not able to find any differences between the two.aws
AWS CLI is an imperative way to do it. With eksctl you can use both imperative and declarative way (e.g. when using yaml-manifests).
In addition, you can create EKS cluster declaratively when using CloudFormation EKS cluster or Terraform AWS EKS module.
What is best for you depends on your situation. For laboratory exploration, it is easiest to use imperative commands. But when you are setting up something like a production environment, you want your changes version controlled in e.g. git - so a declarative way to work is a better fit.
What declarative method to use depends on if you e.g. also provision other AWS resources. It is easiest to use same tool for all your infrastructure, e.g. CloudFormation for everything or Terraform for everything. An advantage with Terraform is that it is available for other cloud providers as well, e.g. both AWS and GCP.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
We are getting ready to deploy a new app in the Amazon cloud, using EC2, RDS, and elastic load balancers. RDS would be sharded. Looking at the difficulties of manageing and monitoring anything beyond a few servers, one can see how quickly the task could become pretty crazy. Amazon's interfaces allow you to do all this, but we would have to script it all ourselves.
I was wondering what others have done. There is RightScale, for managed solutions. Has anyone found any other companies, or open source frame works, that do this kind of thing? Looking at:
Monitoring EC2, load balancers, RDS.
Spinning up new instances of the above automatically on predefined load levels.
Sending alerts and taking resources offline automatically when thesholds occur.
Promoting new software/upgrades in PHP and MySQL.
Taking numbers of servers offline for maintenance/troubleshooting.
Any thoughts would be much appreciated.
The type of services you are looking for - automated provisioning, scaling in/out and monitoring is generally referred as PaaS - Platform as a Service. The idea is that you submit your application to the PaaS system and it manages the complete life-cycle of your application.
There are several PaaS providers available that might fit your needs. There's a comparison available here: Looking for PaaS providers recommendations
You should consider your requirements carefully and see which provider is right for you in terms of:
Cloud Support: Do you need just EC2 or maybe additional clouds?
Language support: Some providers target specific coding frameworks and languages
Support
Pricing
Open/Closed source
Disclaimer: I work for GigaSpaces, developer of the Cloudify open-source PaaS Stack.
You could have a look at scalr. They offer this services on their own platform but you can also download the software they're using and set it up on your own.
After Amazon EC2 they started expanding into other cloud services as well, so you can run your scalr managed instances on literally all huge cloud providers.
Very feature rich, but so far I haven't tested it by myself.
You could try Xervmon. They offer integrated cloud management suite of tools to deploy, manage, monitor Amazon AWS along with several other providers. They do offer managed services as well.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Ive been delving into the world of AWS and, with very little server management experience under my belt, I'm quickly getting lost!
I'm looking at creating a system that uses Route 53, Elastic Load Balancing, EC2, RDS, S3 (possibly with CloudFront as well) so I can host a user generated content website that also streams video.
So Ive been looking at the following books:
Host Your Web Site On The Cloud: Amazon Web Services Made Easy
Programming Amazon Web Services: S3, EC2, SQS, FPS, and SimpleDB
Programming Amazon EC2: Run Applications on Amazon's Infrastructure with EC2, S3, SQS, SimpleDB, and Other Services
If I had to go for one of these what would you recommend?
Most importantly are there any resources you can recommend for a newbie like myself to quickly learn and understand the nuances to AWS?
TIA
Although all of those resources are good, the best way to dive into using AWS is in my experience CloudFormation. With CloudFormation you are able to script most if not all of your AWS resources in a single json script. By writing your cloudformation scripts and looking through the documentation and sample scripts, you will start to get aquatinted with how all of the AWS toolsets work.
Most importantly are there any resources you can reconmend for a
newbie like myself to quickly learn and understand the nuances to AWS?
As mentioned above, CloudFormation
However to make sure I answer your question:
If I had to go for one of these what would you recommend?
I have read all 3 resources listed and I found Programming EC2 to be the most useful in understanding the AWS toolset
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
There are two major offering of cloud computing environment by Amazon through AWS and by Rackspace through Rackspace cloud. I wanted to know more about What are cons/pros of one platform over other. That will help me in deciding platform for my future applications.
Please see some of these links to better analyze & understand the difference between Amazon Cloud Server with Rackspace Cloud.
Things come into my mind:
Amazon server stack has CHOICES possibly everything, but Rackspace server stack is fixed.
Control everything on your server stack with Amazon but Rackspace - NOPE.
You can play around with various services (EBS, EIP, S3, etc) in Amazon server to suite your price, you can't with Rackspace, since you are priced for the whole stack.
In Amazon - single EBS AMI, you can have many different instance types of machine.
Difference:
http://www.distractable.net/tech/amazon-aws-ec2-vs-rackspace-high-level-comparison/
Goodby Rackspace:
http://code.mixpanel.com/amazon-vs-rackspace/
Performance Analysis:
http://www.thebitsource.com/featured-posts/rackspace-cloud-servers-versus-amazon-ec2-performance-analysis/