Error Retrieving Availability Zone Status
Contents |
from AWS MarketplaceAMIs from All SourcesArticles & TutorialsAWS Product InformationCase StudiesCustomer AppsDocumentationDocumentation - This ProductDocumentation - This GuidePublic Data SetsRelease NotesPartnersSample Code & LibrariesWhat Is Auto
The Requested Configuration Is Currently Not Supported
Scaling?Benefits of Auto ScalingAuto Scaling LifecycleAuto Scaling LimitsSetting vpc security groups may not be used for a non-vpc launch UpGetting StartedTutorial: Set Up a Scaled and Load-Balanced ApplicationLaunch ConfigurationsCreating a Launch ConfigurationCreating aws status a Launch Configuration Using an EC2 InstanceLaunching Auto Scaling Instances in a VPCLaunching Spot Instances in Your Auto Scaling GroupAuto
Aws::ec2::securitygroup
Scaling GroupsCreating an Auto Scaling GroupCreating an Auto Scaling Group Using an EC2 InstanceCreating an Auto Scaling Group Using the Amazon EC2 Launch WizardTagging Auto Scaling Groups and InstancesUsing a Load Balancer With an Auto Scaling GroupAttach and Detach Load
Aws Outage
BalancersAdding an ELB Health CheckAdding an Availability ZoneMerging Auto Scaling GroupsDeleting Your Auto Scaling InfrastructureScaling Your GroupMaintaining the Size of Your Auto Scaling GroupManual ScalingAttach EC2 Instances to Your Auto Scaling GroupDetach EC2 Instances From Your Auto Scaling GroupScheduled ScalingDynamic ScalingScaling Based on MetricsScaling Based on Amazon SQSAuto Scaling CooldownsAuto Scaling Instance TerminationLifecycle HooksTemporarily Removing InstancesSuspending and Resuming ProcessesMonitoring Your Auto Scaling Instances and GroupsHealth ChecksAmazon CloudWatch MetricsAmazon CloudWatch Events Amazon SNS NotificationsAWS CloudTrail LoggingControlling Access to Your Auto Scaling ResourcesLaunch Auto Scaling Instances with an IAM RoleTroubleshootingInstance Launch FailureAMI IssuesLoad Balancer IssuesCapacity LimitsResourcesDocument HistoryAWS Documentation » Auto Scaling » User Guide » Troubleshooting Auto Scaling » Troubleshooting Auto Scaling: EC2 Instance Launch FailuresTroubleshooting Auto Scaling: EC2 Instance Launch Failu
Reference (API http://docs.aws.amazon.com/autoscaling/latest/userguide/ts-as-instancelaunchfailure.html Version 2016-09-15)Entire SiteAMIs from AWS MarketplaceAMIs from All http://docs.aws.amazon.com/AWSEC2/latest/APIReference/errors-overview.html SourcesArticles & TutorialsAWS Product InformationCase StudiesCustomer AppsDocumentationDocumentation - This ProductDocumentation - This GuidePublic Data SetsRelease NotesPartnersSample Code & LibrariesWelcomeList of Actions by FunctionActionsAcceptReservedInstancesExchangeQuoteAcceptVpcPeeringConnectionAllocateAddressAllocateHostsAssignPrivateIpAddressesAssociateAddressAssociateDhcpOptionsAssociateRouteTableAttachClassicLinkVpcAttachInternetGatewayAttachNetworkInterfaceAttachVolumeAttachVpnGatewayAuthorizeSecurityGroupEgressAuthorizeSecurityGroupIngressBundleInstanceCancelBundleTaskCancelConversionTaskCancelExportTaskCancelImportTaskCancelReservedInstancesListingCancelSpotFleetRequestsCancelSpotInstanceRequestsConfirmProductInstanceCopyImageCopySnapshotCreateCustomerGatewayCreateDhcpOptionsCreateFlowLogsCreateImageCreateInstanceExportTaskCreateInternetGatewayCreateKeyPairCreateNatGatewayCreateNetworkAclCreateNetworkAclEntryCreateNetworkInterfaceCreatePlacementGroupCreateReservedInstancesListingCreateRouteCreateRouteTableCreateSecurityGroupCreateSnapshotCreateSpotDatafeedSubscriptionCreateSubnetCreateTagsCreateVolumeCreateVpcCreateVpcEndpointCreateVpcPeeringConnectionCreateVpnConnectionCreateVpnConnectionRouteCreateVpnGatewayDeleteCustomerGatewayDeleteDhcpOptionsDeleteFlowLogsDeleteInternetGatewayDeleteKeyPairDeleteNatGatewayDeleteNetworkAclDeleteNetworkAclEntryDeleteNetworkInterfaceDeletePlacementGroupDeleteRouteDeleteRouteTableDeleteSecurityGroupDeleteSnapshotDeleteSpotDatafeedSubscriptionDeleteSubnetDeleteTagsDeleteVolumeDeleteVpcDeleteVpcEndpointsDeleteVpcPeeringConnectionDeleteVpnConnectionDeleteVpnConnectionRouteDeleteVpnGatewayDeregisterImageDescribeAccountAttributesDescribeAddressesDescribeAvailabilityZonesDescribeBundleTasksDescribeClassicLinkInstancesDescribeConversionTasksDescribeCustomerGatewaysDescribeDhcpOptionsDescribeExportTasksDescribeFlowLogsDescribeHostReservationOfferingsDescribeHostReservationsDescribeHostsDescribeIdentityIdFormatDescribeIdFormat
Guide (API Version 2014-11-13)Entire SiteAMIs from AWS MarketplaceAMIs from All SourcesArticles & TutorialsAWS Product InformationCase StudiesCustomer AppsDocumentationDocumentation - This ProductDocumentation - This GuidePublic Data SetsRelease NotesPartnersSample Code & LibrariesWhat is Amazon ECS?Setting http://docs.aws.amazon.com/AmazonECS/latest/developerguide/troubleshooting.html UpDocker BasicsGetting StartedCleaning UpClustersCreating a ClusterScaling a ClusterDeleting a http://docs.rightscale.com/faq/clouds/aws/How_come_I_get_an_insufficient_capacity_error_when_launching_an_EC2_instance.html ClusterContainer InstancesContainer Instance AMIsAmazon ECS-optimized AMILaunching a Container InstanceConnect to your Container InstanceCloudWatch LogsManaging Container Instances RemotelyStarting a Task at Container Instance Launch TimeDeregister Container InstanceContainer AgentInstalling the Amazon ECS Container AgentContainer Agent VersionsUpdating the Amazon ECS error retrieving Container AgentAmazon ECS Container Agent ConfigurationAutomated Task and Image CleanupPrivate Registry AuthenticationAmazon ECS Container Agent IntrospectionHTTP Proxy ConfigurationTask DefinitionsApplication ArchitectureCreating a Task DefinitionUsing a Docker Image in a Task DefinitionTask Definition ParametersUsing Data Volumes in TasksUsing the awslogs Log DriverExample Task DefinitionsDeregistering Task DefinitionsScheduling TasksRunning TasksTask Life error retrieving availability CycleServicesService Definition ParametersService Load BalancingCheck the Service Role for your AccountCreating a Load BalancerCreating an Application Load BalancerCreating a Classic Load BalancerService Auto ScalingTutorial: Service Auto ScalingCreating a ServiceUpdating a ServiceDeleting a ServiceRepositoriesCloudWatch MetricsViewing Amazon ECS MetricsTutorial: Scaling with CloudWatch AlarmsIAM Policies, Roles, and PermissionsPolicy StructureSupported Resource-Level PermissionsCreating IAM PoliciesManaged PoliciesAmazon ECS Managed PoliciesAmazon ECR Managed PoliciesAmazon ECS Container Instance IAM RoleAmazon ECS Service Scheduler IAM RoleAmazon ECS Service Auto Scaling IAM RoleAmazon EC2 Container Service Task RoleIAM Roles for TasksAmazon ECS IAM Policy ExamplesUsing the ECS CLIInstalling the Amazon ECS CLIConfiguring the Amazon ECS CLIAmazon ECS CLI TutorialECS CLI Command Line Referenceecs-cliecs-cli configureecs-cli upecs-cli downecs-cli scaleecs-cli psecs-cli licenseecs-cli composeecs-cli compose serviceUsing the AWS CLIService LimitsCloudTrail LoggingTroubleshootingAWS GlossaryAWS Documentation » Amazon EC2 Container Service » Developer Guide » Amazon ECS TroubleshootingAmazon ECS TroubleshootingYou may need to troublesh
based on the features they offer.FeedbackGet in touch and we’ll get back to you as soon as we can.Release NotesSee the notes for the latest releases of each application and what’s changed.RightScale Docs / RightScale General FAQs / Cloud Providers / Amazon Web ServicesWhy do I receive an "Insufficient capacity" error when launching an EC2 instance?Background Information You try to launch an instance in EC2, but you receive an InsufficientInstanceCapacity: Insufficient capacity error message and are unable to successfully launch a server. Answer The reason you receive this error is because the availability zone (into which you are attempting to launch an instance) is out of capacity. For example, if you attempt to launch an 'm1.xlarge' instance in the 'us-east-1a' availability zone, but there are no more 'm1.xlarge' instances available for provisioning, you will receive an insufficient capacity error message. It's important to note that availability zones are not common across all accounts. i.e. The 'us-east-1a' availability zone for my account may be a different actual zone than the 'us-east-1a' availability zone for your account. When you receive this type of error, you have several different options: Simply wait for that instance type to become available. Launch a different instance size. Launch an instance in a different availability zone and migrate back at a later time, if necessary. This provides a temporary solution until you can replace it at a later time with one in the desired availability zone. However, you will be charged cross-zone data transfer costs. Launch an instance in the -Any- availability zone Purchase a reserved instance (for that instance type) in the desired availability zone. This will also prevent you from receiving this error in the future. © 2016 RightScale, Inc.RightScale HomeWe're HiringEngineering BlogFeedbackChat with us!Copy Path