From their UI, I can only see it is in AWS us-east-1, anywhere I can find out is it in us-east-1b/1c/1d ?
As discussed in this blog, availability zones are logical, not physical. So even if we did show which of our account's logical AZs your server was in (we put each server in a cluster in a different AZ), it wouldn't be meaningful to you. Rather than confuse, we leave the information out.
Availability Zones are not the same across AWS accounts. There is a common misconception that an AZ name like "US-east-1a" identifies a specific physical availability zone for everyone. The fact is that AWS can map/remap the same AZ name to different physical availability zones across multiple accounts. The Availability Zone us-east-1a for account A is not necessarily the same as us-east-1a for account B. Zone assignments are mapped independently for each account. This is important when our infrastructure or use cases spans across multiple accounts. Example: Infrastructure provisioned through Account-A and Load Testing Agents are launched through Account-B, and both pointing to "US-east-1a" may not map to same AZ.
Related
How to configure failover for ServiceNow MidServer in Azure VMs. Should i choose the option of Azure VMSS for failover ?
What options do we have for failover of ServiceNow in Azure VMs . Is it azure availability zones ?
Please help.
All the options you think are good choices. But there are also differences between them. I'll show you the differences as I know and you choose one of them or combine them to match your requirement.
The virtual machine scale set is a group of load-balanced VMs. Due to its feature, when one instance failed, then it will not send the requests to the failed instance and balances the requests t other instances if the scale set has more then one instance. So it's not the failover for ServiceNow MidServer, but it can achieve the same destination.
Availability Zones are unique physical locations within an Azure region. The physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone-redundant services replicate your applications and data across Availability Zones to protect from single-points-of-failure. I think it's the things that you mean failover for ServiceNow MidServer.
You can choose one of them. Or it will have higher availability if you combine both them.
Whenever we want to configure failover cluster option for servicenow's MidServer , we have to configure that option in the ServiceNow.com SaaS portal. There we have to specify what is the name of the failover VM. Hence the only option is to specify failover server name and keep it in different availability zone (for zone level redundancy) or availability set.
I'm from Canada. I'm building a web app with node js and mongoDB. I am very interested by AWS for 2 reasons: the scalable feature and the s3 service. The users of my app will upload a lot of photos and s3 look perfect for my project.
At this time, the cloud server regions available on AWS Marketplace are:
They don't have any cloud server in Canada. You can see where I live (green) on the image. Do you think my physical location will cause some performance issue for my users?
AWS are talking about 'availability zone'...if I'm living outside an availability zone (no availability zone in Canada) can I choose my zone for hosting my app?
Do you think my physical location will cause some performance issue for my users?
Not at all. The company I work for has a website dedicated for Canadian users that is run out of the us-east-1 region. We have never had any reports of issues from Canadian users of the site.
AWS are talking about 'availability zone'...if I'm living outside an availability zone (no availability zone in Canada) can I choose my zone for hosting my app?
Availability zones have nothing (directly) to do with your geographic location. Each of Amazons different regions have multiple availability zones. In a nutshell, each availability zone is a physically and electrically isolated datacenter. For example, in the eu-west-1 region there are currently 5 availability zones. What this essentially means is that the eu-west-1 region, which is physically located in Northern Virginia, consists of 5 independent datacenters. A power failure, network issue, etc. that impacts one of those 5 datacenters should have no impact on the other 4 datacenters.
If you were to design a highly fault-tolerant website then Amazon would recommend that you distribute each component of your site across multiple availability zones within the same region, and to ensure that the site can function if all the services in one availability zone were to fail. This is why they provide multiple availability zones in each region.
To answer your specific question, however, you can choose both the region and the availability zone within a region when you launch a server instance. When you launch an instance through the AWS web interface it will default to choosing a random availability zone for you, but you can also pick a specific availability zone if you so desire.
The region you choose will dictate the geographic area where your instance resides (Northern Virginia for us-east-1, Oregon for us-west-2, etc). Depending on the region you choose there will be between 2 and 5 availability zones to choose from.
My company uses AWS heavily and has several Amazon Direct Connect network links from our points of presence into Amazon. These reduce our latency and costs.
http://aws.amazon.com/directconnect/
We would like to be able to use Heroku more extensively with our internal applications, but the dynos would need to exist inside our Amazon VPCs in order for us to get the latency and cost benefits. I can't see a way to do this.
Is there any way for Heroku customers to run their dynos inside specific Amazon VPCs?
Amazon's Virtual Private Cloud (Amazon VPC) allows me to open a VPN connection to the EC2 cluster.
It looks like the number of EC2 instances you can run within a virtual private cloud is 24 hosts - is that correct?
Update
The beta limitations mentioned in the initial answer have meanwhile been lifted, the new ones (which can be raised as outlined) are addressed by the respective FAQ How many Amazon EC2 instances can I use within a VPC?:
You can run any number of Amazon EC2 instances within a VPC, so long
as your VPC is appropriately sized to have an IP address assigned to
each instance. You are initially limited to launching 20 Amazon EC2
instances per VPC at any one time and a maximum VPC size of /16
(65,536 IPs). If you would like to exceed these limits, please
complete the following form.
Furthermore, the initial Number of VPCs per region is 5 and the initial Number of subnets per VPC is 20, see Appendix B: Limits for details regarding these and other limitations in place.
Initial Answer
You can currently have 1 VPC per AWS account with up to 20 subnets. These are the beta limitations, complete their form if you need to lift them.
There is also a limit of instances you can run with a single AWS account, but again -- you can get them to up this limit. AWS has all kinds of limits in place, also on EBS volumes, elastic IPs, etc.. They can all be upped.
Things Have Changed.
Q: How many instances can I run in Amazon EC2?
You are limited to running up to 20 On-Demand instances, purchasing 20
Reserved Instances, and requesting Spot Instances per your dynamic
Spot limit per region. New AWS accounts may start with limits that are
lower than the limits described here. Certain instance types are
further limited per region as follows...
Source:
http://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2
I highly doubt it. My understanding is that VPC is just a VPN, where you can tunnel as much traffic as it can support through the pipe. Are you confusing hosts with subnets? There is a restrictions on the number of subnets available. There is also a restriction on the number of hosts (I think it's a max of 20 hosts), but that's a general EC2 concern and not specific to VPC. Note that both restrictions can be overturned if you send an email to Amazon.
It depends on the type of the instance. Check your limits using the following instruction: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html
Is it possible to have multiple users to manage an Amazon EC2 environment? I want to give access to several additional people to create machines on my existing billing account.
Amazon just announced AWS Identity and Access Management - http://aws.amazon.com/iam/
As of right now, it's in 'preview' mode, but this will allow you to have multiple AWS management accounts.
A few months ago Amazon announced Consolidated Billing. I never used it, but I think that is what you're looking for:
Consolidated Billing enables you to see a combined view of AWS costs incurred by all accounts in your department or company, as well as obtain a detailed cost report for each individual AWS account associated with your paying account. Consolidated Billing may also lower your overall costs since the rolled up usage across all of your accounts could help you reach lower-priced volume tiers more quickly.
Consolidated Billing Guide
This is absolutely possible using IAM service of AWS. With the help of IAM you can create users and give them specific permissions on various services of amazon.
You can try http://LabSlice.com. It's primarily for Virtual Lab Management (ie. playground environments), but may suit your needs.