Aws faq

The use of Microsoft software is subject to Microsoft's terms. You are responsible for complying with Microsoft licensing. This document is only a guide for your convenience and you are not entitled to rely on its descriptions and it does not constitute legal advice. If you have questions about your licensing or rights to Microsoft software, please consult your legal team, Microsoft, or your Microsoft reseller.

This page is up to date with current Microsoft Product Terms. What is the relationship between Microsoft and Amazon Web Services? What is the expanded support agreement between Amazon and Microsoft and how does it benefit me? Does the expanded support agreement between AWS and Microsoft cover all support issues related to my applications running on Windows Server or Windows desktop?

Does the extended support agreement between AWS and Microsoft replace my Microsoft support agreement? Are there regional restrictions on accessing the benefit of the expanded Support agreement with Microsoft?

How do I know if a specific Microsoft product is eligible for License Mobility? When can I bring my own license using EC2 instances with default tenancy? What's the difference between Dedicated Hosts and Dedicated Instances? Can I run multiple instance types on a Dedicated Host?

aws faq

How do I determine the number of licenses of Windows Server to bring in? Which AWS regions are supported? Which one should I use? How do I switch to the new Windows Server Start screen? What are my options for running Microsoft software that is approaching EOS?

Amazon EC2 FAQs

What Amazon products and services are affected by EOS and when will changes be made? Q: What options I have for in-places upgrade of my Win and Win instances? Will customers have to recreate their environment using other technologies in order to receive support from AWS or Microsoft? AWS is also an authorized license mobility partner. Now AWS has further enhanced our support capabilities with a new additional direct engagement between AWS Support and Microsoft Support, to help ensure high quality support and issue resolution for our customers.

To find more information on end of support EOS for Microsoft products go here. What is the expanded support agreement between Amazon and Microsoft, and how does it benefit me? As a result of this expanded support agreement, AWS can engage directly with Microsoft to create the best possible support experience. If necessary, AWS Support can escalate issues directly to Microsoft and work with dedicated Microsoft support engineers to help ensure issues are addressed and resolved.What is the difference between the Ballots, Drafts, and Discussions tabs?

Why are there no listings for Ex-Officio or Officer roles in Specbuilder? I selected 'Attach Vote File' but my vote didn't save. What is wrong? Does 4. Depending on your organization's security settings, the emails may be initially flagged as spam.

In addition, email frequency and bundling can be changed via the ' Specbuilder Email Settings ' link under your profile. All browsers are compatible with Specbuilder. Using the most recent version will guarantee an improved user experience.

We have created an overview video that walks users through the basics of Specbuilder. By default, your username is the email address associated with your AWS Committee work.

Due to the way Specbuilder redirects, if you just bookmark within Specbuilder, and your company also has a Compass subscription, you may run into issues. Once you login to Specbuilder, all of your Committees will appear under 'My Committees' on the dashboard. Once you click a Committee on the main dashboard, click the 'Files' tab. The files here will be listed individually or within folders. Click a file to view or download it. This group will be accessible for all Committee volunteers.

Within Specbuilder, there is currently a limitation on how many roles can be shown. What this means is that Chairs will still be shown as Members same voting roles.

Ex-Officios will be shown as Advisors same voting roles. Once CRM and Specbuilder are linked, this will be resolved. In order to submit or save your vote, you will only need to click 'Save Vote'.

After attaching, you will still need to click 'Save Vote'.It is designed to make web-scale computing easier for developers. Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing you to quickly scale capacity, both up and down, as your computing requirements change. Amazon EC2 changes the economics of computing by allowing you to pay only for capacity that you actually use. You must have an Amazon Web Services account to access this service; if you do not already have one, you will be prompted to create one when you begin the Amazon EC2 sign-up process.

Amazon EC2 registration requires you to have a valid phone number and email address on file with AWS in case we ever need to contact you. Verifying your phone number takes only a couple of minutes and involves receiving a phone call during the registration process and entering a PIN number using the phone key pad.

Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load.

Amazon CEO Jeff Bezos: It Is Always Day One.

Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements. When computing requirements unexpectedly change up or downAmazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time.

In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals. Once you have set up your account and select or create your AMIs, you are ready to boot your instance. You simply need to indicate how many instances you wish to launch.

If Amazon EC2 is able to fulfill your request, RunInstances will return success, and we will start launching your instances. You can also programmatically terminate any number of your instances using the TerminateInstances API call. If you have a running instance using an Amazon EBS boot partition, you can also use the StopInstances API call to release the compute resources but preserve the data on the boot partition.

In addition, you have the option to use Spot Instances to reduce your computing costs when you have flexibility in when your applications can run. Read more about Spot Instances for a more detailed explanation on how Spot Instances work. If you prefer, you can also perform all these actions from the AWS Management Console or through the command line using our command line tools, which have been implemented with this web service API.

When you launch your Amazon EC2 instances you have the ability to store your root device data on Amazon EBS or the local instance store. By using Amazon EBS, data on the root device will persist independently from the lifetime of the instance.

This enables you to stop and restart the instance at a subsequent time, which is similar to shutting down your laptop and restarting it when you need it again. Alternatively, the local instance store only persists during the life of the instance. This is an inexpensive way to launch instances where data is not stored to the root device.

For example, some customers use this option to run large web sites where each instance is a clone to handle web traffic. It typically takes less than 10 minutes from the issue of the RunInstances call to the point where all requested instances begin their boot sequences. This time depends on a number of factors including: the size of your AMI, the number of instances you are launching, and how recently you have launched that AMI.

Images launched for the first time may take slightly longer to boot. Amazon EC2 allows you to set up and configure everything about your instances from your operating system up to your applications.

An Amazon Machine Image AMI is simply a packaged-up environment that includes all the necessary bits to set up and boot your instance. Your AMIs are your unit of deployment. Once you create a custom AMI, you will need to bundle it. If you are bundling an image with a boot partition on the instance store, then you will need to use the AMI Tools to upload it to Amazon S3.

You can choose from a number of globally available AMIs that provide useful instances. For example, if you just want a simple Linux server, you can choose one of the standard Linux distribution AMIs. The RunInstances call that initiates execution of your application stack will return a set of DNS names, one for each system that is being booted.

aws faq

This name can be used to access the system exactly as you would if it were in your own data center. You own that machine while your operating system stack is executing on it. Yes, Amazon EC2 is used jointly with Amazon S3 for instances with root devices backed by local instance storage. By using Amazon S3, developers have access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of web sites.A network access control list ACL is an optional layer of security for your VPC that acts as a firewall for controlling traffic in and out of one or more subnets.

You might set up network ACLs with rules similar to your security groups in order to add an additional layer of security to your VPC.

For more information about the differences between security groups and network ACLs, see Comparison of security groups and network ACLs. By default, it allows all inbound and outbound IPv4 traffic and, if applicable, IPv6 traffic. You can create a custom network ACL and associate it with a subnet. By default, each custom network ACL denies all inbound and outbound traffic until you add rules. If you don't explicitly associate a subnet with a network ACL, the subnet is automatically associated with the default network ACL.

You can associate a network ACL with multiple subnets. However, a subnet can be associated with only one network ACL at a time. When you associate a network ACL with a subnet, the previous association is removed. A network ACL contains a numbered list of rules.

We evaluate the rules in order, starting with the lowest numbered rule, to determine whether traffic is allowed in or out of any subnet associated with the network ACL. The highest number that you can use for a rule is We recommend that you start by creating rules in increments for example, increments of 10 or so that you can insert new rules where you need to later on. A network ACL has separate inbound and outbound rules, and each rule can either allow or deny traffic.

Network ACLs are stateless, which means that responses to allowed inbound traffic are subject to the rules for outbound traffic and vice versa. For more information, see Amazon VPC quotas. When you add or remove rules from a network ACL, the changes are automatically applied to the subnets that it's associated with.

Rule number. Rules are evaluated starting with the lowest numbered rule. As soon as a rule matches traffic, it's applied regardless of any higher-numbered rule that might contradict it. The type of traffic; for example, SSH. You can also specify all traffic or a custom range. You can specify any protocol that has a standard protocol number. For more information, see Protocol Numbers. Port range.When you launch a new EC2 instance, the EC2 service attempts to place the instance in such a way that all of your instances are spread out across underlying hardware to minimize correlated failures.

You can use placement groups to influence the placement of a group of interdependent instances to meet the needs of your workload. Depending on the type of workload, you can create a placement group using one of the following placement strategies:. Cluster — packs instances close together inside an Availability Zone. This strategy enables workloads to achieve the low-latency network performance necessary for tightly-coupled node-to-node communication that is typical of HPC applications.

Partition — spreads your instances across logical partitions such that groups of instances in one partition do not share the underlying hardware with groups of instances in different partitions. This strategy is typically used by large distributed and replicated workloads, such as Hadoop, Cassandra, and Kafka. Spread — strictly places a small group of instances across distinct underlying hardware to reduce correlated failures.

A cluster placement group is a logical grouping of instances within a single Availability Zone. A cluster placement group can span peered VPCs in the same Region. The following image shows instances that are placed into a cluster placement group.

Cluster placement groups are recommended for applications that benefit from low network latency, high network throughput, or both. They are also recommended when the majority of the network traffic is between the instances in the group. To provide the lowest latency and the highest packet-per-second network performance for your placement group, choose an instance type that supports enhanced networking. For more information, see Enhanced Networking.

Use a single launch request to launch the number of instances that you need in the placement group. If you try to add more instances to the placement group later, or if you try to launch more than one instance type in the placement group, you increase your chances of getting an insufficient capacity error. If you stop an instance in a placement group and then start it again, it still runs in the placement group. However, the start fails if there isn't enough capacity for the instance.

If you receive a capacity error when launching an instance in a placement group that already has running instances, stop and start all of the instances in the placement group, and try the launch again. Starting the instances may migrate them to hardware that has capacity for all of the requested instances. Partition placement groups help reduce the likelihood of correlated hardware failures for your application. When using partition placement groups, Amazon EC2 divides each group into logical segments called partitions.

Amazon EC2 ensures that each partition within a placement group has its own set of racks.

aws faq

Each rack has its own network and power source. No two partitions within a placement group share the same racks, allowing you to isolate the impact of hardware failure within your application. The following image is a simple visual representation of a partition placement group in a single Availability Zone.

It shows instances that are placed into a partition placement group with three partitions— Partition 1Partition 2and Partition 3. Each partition comprises multiple instances. The instances in a partition do not share racks with the instances in the other partitions, allowing you to contain the impact of a single hardware failure to only the associated partition.

Partition placement groups can be used to deploy large distributed and replicated workloads, such as HDFS, HBase, and Cassandra, across distinct racks.

When you launch instances into a partition placement group, Amazon EC2 tries to distribute the instances evenly across the number of partitions that you specify.

You can also launch instances into a specific partition to have more control over where the instances are placed. A partition placement group can have partitions in multiple Availability Zones in the same Region.

A partition placement group can have a maximum of seven partitions per Availability Zone. The number of instances that can be launched into a partition placement group is limited only by the limits of your account. In addition, partition placement groups offer visibility into the partitions — you can see which instances are in which partitions.

These applications use this information to make intelligent data replication decisions for increasing data availability and durability.An elastic network interface is a logical networking component in a VPC that represents a virtual network card. It can include the following attributes:. You can create and configure network interfaces in your account and attach them to instances in your VPC. Your account might also have requester-managed network interfaces, which are created and managed by AWS services to enable you to use other resources and services.

You cannot manage these network interfaces yourself. For more information, see Requester-managed network interfaces. Therefore, we use "network interface" in this documentation instead of "elastic network interface". The term "network interface" in this documentation always means "elastic network interface".

You can create a network interface, attach it to an instance, detach it from an instance, and attach it to another instance. The attributes of a network interface follow it as it's attached or detached from an instance and reattached to another instance. When you move a network interface from one instance to another, network traffic is redirected to the new instance. You can also modify the attributes of your network interface, including changing its security groups and managing its IP addresses.

Every instance in a VPC has a default network interface, called the primary network interface. You cannot detach a primary network interface from an instance. You can create and attach additional network interfaces. The maximum number of network interfaces that you can use varies by instance type. For more information, see IP addresses per network interface per instance type.

In a VPC, all subnets have a modifiable attribute that determines whether network interfaces created in that subnet and therefore instances launched into that subnet are assigned a public IPv4 address.

When you launch an instance, the IP address is assigned to the primary network interface that's created. When you create a network interface, it inherits the public IPv4 addressing attribute from the subnet. If you later modify the public IPv4 addressing attribute of the subnet, the network interface keeps the setting that was in effect when it was created.

If you launch an instance and specify an existing network interface as the primary network interface, the public IPv4 address attribute is determined by this network interface. All subnets have a modifiable attribute that determines whether network interfaces created in that subnet and therefore instances launched into that subnet are automatically assigned an IPv6 address from the range of the subnet.

When you launch an instance, the IPv6 address is assigned to the primary network interface that's created. For more information, see IPv6 addresses. You can enable a VPC flow log on your network interface to capture information about the IP traffic going to and from a network interface. After you've created a flow log, you can view and retrieve its data in Amazon CloudWatch Logs. The following table lists the maximum number of network interfaces per instance type, and the maximum number of private IPv4 addresses and IPv6 addresses per network interface.

The limit for IPv6 addresses is separate from the limit for private IPv4 addresses per network interface. Not all instance types support IPv6 addressing. IPv6 addresses are public and reachable over the Internet.Unlike the data stored on a local instance store which persists only as long as that instance is alivedata stored on an Amazon EBS volume can persist independently of the life of the instance. Therefore, we recommend that you use the local instance store only for temporary data.

For data requiring a higher level of durability, we recommend using Amazon EBS volumes or backing up the data to Amazon S3. These volume types differ in performance characteristics and price, allowing you to tailor your storage performance and cost to the needs of your applications.

For more performance information see the EBS product details page. Q: Since io2 provides higher volume durability, should I still take snapshots and plan to replicate io2 volumes across Availability Zones AZs for high durability? High volume durability, snapshots, and replicating volumes across AZs protect against different types of failures, and customers can choose to use one, two, or all of these approaches based on their data durability requirements. Higher volume durability reduces the probability of losing the primary copy of your data.

Snapshots protect against the unlikely event of a volume failure. Replicating volumes across AZs protects against an AZ level failure and also provides faster recovery in case of failure.

Changing a volume configuration is easy. The Elastic Volumes feature allows you to increase capacity, tune performance, or change your volume type with a single CLI call, API call or a few console clicks.

For more information about Elastic Volumes, see the Elastic Volumes documentation. Any existing volumes will not have been changed as a result of this and there are no functional differences in the EBS Magnetic offering compared to EBS Standard. The name of this offering was changed to avoid confusion with our General Purpose SSD gp2 volume type which is our recommended default volume type. Yes, it does. For maximum performance consistency with new volumes created from a snapshot, we recommend enabling Fast Snapshot Restore FSR on your snapshots.

For maximum consistency, a Provisioned IOPS volume must maintain an average queue depth rounded to the nearest whole number of one for every provisioned IOPS in a minute. For example, for a volume provisioned with IOPS, the queue depth average must be 3. For more information about ensuring consistent performance of your volumes, see Increasing EBS Performance. There are several factors that could affect the level of consistency you see. Your throughput rate may also be lower depending on the instance selected.

Another factor is taking a snapshot which will decrease expected write performance down to the baseline rate, until the snapshot completes. This is specific to st1 and sc1. However, performance for st1 and sc1 scales linearly with volume size so there may not be as much of a benefit to stripe these volumes together. EBS is a multi-tenant block storage service. We employ rate limiting as a mechanism to avoid resource contention.

This starts with having defined performance criteria for the volumes — our volume types gp2, PIOPS, st1, and sc1 all have defined performance characteristics in terms of IOPS and throughput. The next step is defining performance at the instance level.

A customer can, therefore, size instances and volumes to get the desired level of performance. In addition, customers can use our reported metrics to observe instance level and volume level performance. They can set alarms to determine if what they are seeing does not match the expected performance — the metrics can also help determine if customers are configured at the right type of instance with the right amount of performance at the volume level or not. On the EBS end, we use the configured performance to inform how we allocate the appropriate instance and EBS infrastructure to support the volumes.

By appropriately allocating infrastructure, we avoid resource contention.

AWS Whitepapers & Guides

Additionally, we constantly monitor our infrastructure. This monitoring allows us to detect infrastructure failure or imminent infrastructure failure and therefore, move the volumes pro-actively to functioning hardware while the underlying infrastructure is either repaired or replaced as appropriate.

No, snapshots can be done in real time while the volume is attached and in use. However, snapshots only capture data that has been written to your Amazon EBS volume, which might exclude any data that has been locally cached by your application or OS.