New to both these technologies.I am trying to do the below steps
1)Install Kong with aws marketplace
I simply clicked on installation on getkong.org
then selected AWS marketplace
2) I am in UK.
So selected region as Ireland
since I have not got any other region to select from.
Then clicked manual launch
I opened ec2 management console
selected free tier
t2.micro
I gave my windows IP and created security groups and instructed but i am getting error
The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=8enaazwzxnn2uypvc4p8u39da for more information about supported instance types, regions, and operating systems.
t2.micro does not appear in the pricing options for this Marketplace offering (it does for other Marketpace images), this leads me to suspect t2.micro isn't supported.
We know from experience that Cassandra may struggle being run on low memory 2 gig machines
I suspect Mashape are trying to prevent you hitting complicated tuning issues (although I cannot see any docs to back this up).
Perhaps start with an M4 Large which is one of the "smallest", cheapest yet memory optimised options for experimentation.
The list of Kong supported ec2 instances for Ireland appear as:
Related
I have nearly reached my AWS S3 usage limit for the month, after having started it just a couple of weeks ago, and I'm trying to understand why. I've never used AWS before, and I'm a newb in general. I literally have 3 jpegs in storage, nothing else.
Is usage solely determined by hours? I read that hours are instances where the storage is made available. Right now I have the Django project hosted on Heroku with media on AWS. I am very much still in dev mode, and only need AWS when testing project on Heroku, but most of the time I'm in local environment. Given that, I am confused how my usage limit could be nearly reached within a couple of weeks. Any guidance is appreciated.
Update: I was mistaken. The account number listed in the warning email is the same used for my AWS S3, but it is referring instead to RDS. When I see all products under the account it shows S3 (which is well below the limit) and RDS (which is nearly at the limit). The quandary now though is that I never intended to create an RDS instance. And, when I click on "databases" under RDS, it actually says I don't have any RDS instances. So I don't have RDS yet I do because I am soon to be charged for going over the limit. I've never used AWS before, and I'm a newb in general. I initiated S3, the only product I intended to have under the account, for the sole purpose of serving media files not served by Heroku.
In the AWS management console:
Click your username (in the top-right, to the left of the Region name)
Select My Billing Dashboard
Click Bill Details in the top-right
This will give you a breakdown of costs by service and region.
It is possible that your Amazon RDS instance is running in a different region, so find the region where the RDS costs are occurring and:
Go to Amazon RDS in the management console
Change the Region in the top-right to the one that was shown in the billing console
Delete the database (if you are sure you aren't using it)
My instance is running on Linux (kubernetes deployed by kops). From the billing I saw they are classified as "Linux/UNIX", but I think it is deployed in VPC via kops.
Now I want to buy reserved instance, and the choices of platform has two:
Linux/UNIX (Amazon VPC)
Linux/UNIX
Which one should I use? What are the difference?
BTW, once I bought a RI, do I have to wait to the next day to see the reservation coverage from billing UI? Can I see if it covers some of my running instance immediately?
I have access to multiple aws accounts and I found something interesting.
As of today (2020-02-26), when looking at ca-central-1 region's platforms when trying to buy reserved instances, I only see Linux/UNIX, and I don't see Linux/UNIX (Amazon VPC) in the list:
This list is the same in both older and recent AWS accounts.
When I look at us-east-1 region's platforms when trying to buy reserved instances, I see the same list as ca-central-1 when using the recent account **But when I use a much older aws account which used to have m1 ec2 instances (which can't be created anymore), here's what I see:
Note that we already reserved a plan for an m1 instance back in the days (which is now expired) so that could be related to why I see two kind platform for each of them.
Funny thing is I can only reserve Linux/UNIX (Amazon VPC), not Linux/UNIX as you can see from the two screenshots:
Linux/UNIX list empty on older account:
Linux/UNIX (Amazon VPC) list not empty on older account:
So my assumption is if you see both, Linux/UNIX (Amazon VPC) will be the one you need, otherwise, use Linux/UNIX.
Update 2020-02-27: I did purchase them, I will verify usage once it's effective, but I'm quite sure everything is fine.
Update 2020-03-06: I confirm it works as expected. I have 100% coverage in both regions starting from 2020-02-27 in the billing dashboard. 🎉
Linux/UNIX is EC2-Classic which is legacy.
"The EC2-Classic platform was introduced in the original release of Amazon EC2."
AWS EC2-Classic
Use Linux/UNIX (Amazon VPC) which will spawn the instance in your own VPC.
Newbie to Amazon Web Services here. I launched an instance from a Public AMI and found that I could not ssh into the instance - I received the error "Connection timed out." I checked the security groups to verify that Port 22 was associated with 0.0.0.0/0. Additionally, I checked the route tables to verify that 0.0.0.0/0 is associated with target gateway attached to the VPC.
I find that only 1/2 status checks have passed - the instance status check failed. I have tried stopping and starting the instance as well as terminated and launching a new instance, both to no avail. The error that I see in the system log is:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1).
From this previous question, it appears that this could be a virtualization issue, but I'm not sure if that was due to something I did on my end when launching the instance or something that occurred from the creators of the AMI? Ec2 1/2 checks passed
Any help would be appreciated!
Can you share any more details about how you deployed the instance? Did you use the AWS Management Console, or one of the command line tools or SDKs to deploy it? Which public AMI did you use? Was it one of the ones provided by Amazon?
Depending on your needs, I would make sure that you use one of the AMIs provided by Amazon, such as Ubuntu, Amazon Linux, CentOS, etc. Here's the links to the docs on AMIs, but you can learn quite a bit by just searching for images. Since you mentioned virtualization types though, I'd suggest reading up briefly on the HVM vs. Paravirtual virtualization types on AWS. Each of the instance types / families uses a certain virtualization type, which is indicated in the chart on this page.
Instance Status Checks
This documentation page covers the instance status checks, which you'll probably want to familiarize yourself with. It's entirely possible that shutting down (not restart, but shutdown) and then starting the instance back up might resolve the instance status check.
Spot Instances - cost savings!
By the way, I'll just mention this since you indicated that you're new to AWS ... if you're just playing around right now, you can save a ton of cost by deploying EC2 Spot Instances, instead of paying the normal, on-demand rates. Depending on current rates, you can save more than 50%, and per-second billing still applies. Although there's the possibility that your EC2 instance could get "interrupted" based on market demand, you can configure your Spot Instance to just "Hibernate" or "Stop" instead of terminating and relaunching. That way, your work is instance state is saved for when it relaunches.
Hope this helps!
1) Use well-known images or contact with the image developer. Perhaps it requires more than one drive or tricky partitioning.
2) make sure you selected proper HVM/PV image according to the instance type.
3) (after checks are passed) make sure the instance has public ip
I need to launch a Amazon EC2 instance, in particular a GPU accelerated one. I already tried with free tiers using t2.micro
instances and everything is fine. When I try to select a non free one such as g2.2xlarge I get this error
Launch Failed
You have requested more instances (1) than your current instance limit of 0 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit.
(Service: AmazonEC2; Status Code: 400; Error Code: InstanceLimitExceeded; Request ID: 4ebf71ee-e927-42c2-8377-697a3a6cfd4b)
I'm trying to use a machine with Deep Learning AMI Ubuntu Version (but I also tried with other ones). I get this error even if I'm not running any other instance and according to the documentation the limit for these one is 5 at a time.
I have also tried to select different regions (my country is not among the choices) but it doesn't seem to change the result.
My only guess about this issue is that somehow I'm registered as a free user and I'm not allowed to use the priced services, but I'm not so sure about that.
Edit: I have a credit card on file on Amazon (they require it to register) and they should charge me from that.
Am I missing something?
Every amazon account has limits - even big corporate accounts. These limitations are set by Amazon, but you can request a limit increase. You can find your limits by clicking the Limits link in the top left hand side inside the EC2 Dashboard.
For example, if you have a t2.micro already running and you try to launch a g2.xlarge that had a limit of 1, you would not be able to since your limit of 1 has already been hit with your t2.micro that is running.
More Info:
How do I manage my AWS service limits?
AWS FAQ Overview
Q: How many instances can I run in Amazon EC2?
To request a limit increase, submit a support request through the AWS Support Center
To view your limits:
Yes you must check the limits of usage. More info in the FQA or the limits section. Amazon is not so clear on this.
Amazon reference Forum
I am working on a project and am at a point where the POC is done and now want to move towards a real product. I am trying to understand the Amazon cloud offerings just to see if I need to be aware of them at development time. I have a bunch of questions that I cannot get answered from the Amazon site. Its probably because I am new to the whole web services thing and have never hosted a site before. I am hoping someone out here will explain this to me like I am a C programmer :)
I see amazon has a bunch of offerings -
EC2
Elastic Block Store
Simple DB
AuotScaling
Elastic Load Balancing
I understand EC2 is virtual server instances that I can use and these could come pre-loaded with what I want (say Apache + python). I have the following questions -
If I want a custom instance of something (like say a custom apache module I wrote for my project). Can I create a server instance using the exact modules and make it the default the next time I create a new instance or in Autoscaling?
Do I get an IP Address to access this? Can I set my own hostname to it? I mean do I get a DNS record? Or is it what Elastic IP is?
How do I access it from the outside? SSH? Remote Desktop? Or is it entirely up to how I configure the instance?
What do they mean by Inter-Region or Intra-Region data transfer? What is data transfer to begin with? Is it just people using my instance? So if I go live with it that will be the cost I have to pay for people using it?
What is the difference between AutoScaling and Elastic Load Balancing?
What is Elastic Block Store? Is it storage? If so do I have to worry about backups or do they take care of it?
About the Simple DB -
It looks like the interface to use this is different to my regular SQL calls. Am I correct?
If so the whole development needs to be tailored specifically for Amazon. Which kind of sucks. Is there a better alternative?
Do I get data backups or do I have to worry about it myself?
Will I be able to connect to the DB using regular tools to inspect the DB (during or afte development). Or do I get other tools made by Amazon for it?
What about security? The DB is obviously somewhere in the cloud farm away from the EC2 instance. My DB password is going over the wire and so is all my data totally unencrypted. Don't I have to worry about that? The question comes up only because I don't own any of the hardware.
I really hope some one points me in the right direction here.
Thanks for taking the time to read.
P
I just went through the question and here I tried to answer few of them,
1) AWS EC2 instances doesnt publish pre-configured instances, in fact its configured by the developers and made it publicly available to the users so that they can use it. One can any one of those instances or you can just opt for what ever OS you want which is raw and provision it accordingly and create a snap shot of it so that you can use it for autos caling.The snap shot becomes the base AMI in your case.
2) Every instance you boot will have a public DNS attach to it, you can use the public DNS to connect to that instance using ssh if your are a linux user or using putty if you are a windows users. Apart from that, you can also attach a elastic IP which comes with a cost will is like peanuts and attach it to the instance and access your instance through the elastic IP and you can either map the public DNS or elastic ip to map to a website by adding a A record or Cname respectively.
3)AWS owns databases in the different parts of the world. For example you deploy your application depending upon your customer base, if you target customers are based out of India, the nearest region available is Singapore which is called as ap-southeast-1 by AWS. Each region will have multiple availability zones, example ap-southeast-1a and ap-southeast-1b, which are two different databases and geographically part. Intre region means from ap-southeast-1a to ap-southeast-1b. Inter Region means, from ap-southeast-1 to us-east-1 which is Northern Virginia Data centre. AWS charges from in coming and out going bandwidth, trust me its nothing.
They chargge 1/8th of a cent per GB. Its a thing to even think about it.
4)Elastic Load balancer is cluster which divides the load equally to all your regions across availability zones (if you are running in multi AZ) ELB sits on top the AWS EC2 instances and monitors the instance health periodically and enables auto scaling
5) To help you understand what is autoscaling please go through this document http://aws.amazon.com/autoscaling/
6)Elastic Block store or EBS are like hard disk which is a persistent data storage which can be attached to your instance.Regarding back up yes dependents upon your use case. I do backups of EBS periodically.
7)Simple Db now renamed as dynamo DB is nosql DB, I hope you understand what is nosql db, its a non RDMS db systems. Please read some documentation to understand what is nosql db is.
8)If you have mysql or oracle db you can opt for RDS, please read the documents.
9)I personally feel you are newbie to the entire cloud eco system, you need to understand what exactly cloud does first.
10)You dont have to make large number of changes to development as such, just make sure it works fine in your local box, it can be deployed to cloud with out much ado.
11) You dont have to use any extra tool for that, change the database end point to RDS(if your use it) or else install mysql in your ec2 instance and connect to the local db which resides in the ec2 instance and connect to it,which is as simple as your development mode.
12)You dont have to worry about any security issues aws, it is secured. Dont follow the myths, I am have been using aws since 3 years running I dont even know remember how many applications, like(e-commerce,m-commerce,social media apps) I never faced any kind of security issues and also aws allows to set your security how ever you want.
Go ahead, happy coding. Contact me if you have any problem.
The answer above is a good summary on AWS. Just wanted to add
AWS offers full data center, so it depends what you are trying to achieve. For starters you will need,
EC2 - This is your server, it comes with instance storage, which will be lost on restart
EBS - Your mounted storage, the data is persisted across reboots
S3 - Provides storage (RESTful API's on top, the cost is usage based rather than "provisioned" as in EBS)
Databases - can start with Amazon RDS, which provides managed database services, you can chose between various available databases. You can also install your own database using EC2 + EBS, you will have to take care of managing the database yourself.
Elastic IP: Public facing IP address, you can point your DNS server to this.
One great tool to calculate the pricing,
http://calculator.s3.amazonaws.com/calc5.html
Some other services to take in account are:
VPC (Virtual Private Cloud). This is your own private network. You can define subnets, route tables and internet gateways there. I would strongly recommend to use VPC for any serious deployment of more than one instance.
Glacier - this will replace your tape library to storing backups.
Cloud Formation - great tool for deployment and automation of instances.