Deploy IIS into an existing VPC (Console) - AWS Launch Wizard

Deploy IIS into an existing VPC (Console)

The following steps guide you through an IIS deployment with AWS Launch Wizard after you have launched it from the console for an existing virtual private cloud (VPC).

Important

When you deploy IIS to an existing VPC, you must have an existing Active Directory domain. Also, the Domain Name System (DNS) must allow for the discovery of the Active Directory domain, such as with VPC DHCP options sets.

  1. When you select Choose application from the AWS Launch Wizard landing page, you are directed to the Choose application wizard where you are prompted to select the type of application that you want to deploy.

  2. Select Internet Information Services, select the deployment type, then select Create deployment.

  3. You are prompted to enter the specifications for the new deployment. The following tabs provide information about the specification fields of the deployment model.

    General settings

    • Deployment name. Enter a unique application name for your deployment.

    • Amazon Simple Notification Service (Amazon SNS) topic ARN — optional. Specify an Amazon SNS topic where AWS Launch Wizard can send notifications and alerts. For more information, see the Amazon Simple Notification Service Developer Guide.

    • Deactivate rollback on failed deployment. By default, if a deployment fails, your provisioned resources will be deleted. You can enable this setting during deployment to prevent this behavior.

    • Tags - optional. Enter a key and value to assign metadata to your deployment. For help with tagging, see Tagging Your Amazon EC2 Resources.

    Network configuration
    Parameter label (name) Default value Description
    VPC ID for workload (VPCID) Requires input ID of the VPC (for example, vpc-0abcdef0).
    Security group with access to domain (DomainMemberSecurityGroup) Requires input Choose the EC2 security group that allows for Active Directory communication.
    Private subnet 1 (PrivateSubnet1ID) Requires input ID of private subnet 1 in Availability Zone 1 for the EC2 target group (for example, subnet-abcdef01).
    Private subnet 2 (PrivateSubnet2ID) Requires input ID of private subnet 1 in Availability Zone 2 for the EC2 target group (for example, subnet-abcdef02).
    Elastic Load Balancer subnet 1 (ELBSubnet1ID) Requires input ID of subnet 1 in Availability Zone 1 for the ELB (for example, subnet-a0246dcd). Specify a public subnet ID if the ELBSchemeParameter parameter is defined as internet-facing. Otherwise, you can specify a private subnet ID.
    Elastic Load Balancer subnet 2 (ELBSubnet12D) Requires input ID of subnet 2 in Availability Zone 2 for the ELB (for example, subnet-a0246dcd). Specify a public subnet ID if the ELBSchemeParameter parameter is defined as internet-facing. Otherwise, you can specify a private subnet ID.
    Active Directory configuration
    Parameter label (name) Default value Description
    Domain administrator name (DomainAdminUser) Admin Used to specify the user name for the domain administrator account of a self managed directory.
    Domain administrator password (DomainAdminPassword) Requires input Password for the domain administrator account. Must be at least 8 characters containing letters, numbers, and symbols.
    Domain NetBIOS name (DomainNetBIOSName) Requires input NetBIOS name of the domain for users of earlier Windows versions (up to 15 characters).
    Domain DNS name (DomainDNSName) Requires input Fully qualified domain name (FQDN) of the forest root domain.
    Note

    The domain administrator user name is separate from the default administrator account.

    IIS webpage
    Parameter label (name) Default value Description
    Amazon S3 Bucket webpage Location (WebBucketName) Blank string Bucket name where the HTML file is located for IIS. If left blank, a sample page will be used.
    Amazon S3 Key webpage Location (WebBucketKey) webfiles/index.html Bucket Key where the HTML file is located for IIS. Only change this value if an Amazon S3 Bucket webpage Location is specified, otherwise leave as default.
    Auto Scaling group/ELB configuration
    Parameter label (name) Default value Description
    Desired capacity of the Auto Scaling group (ASGDesiredCapacity) 2 Desired capacity of the Auto Scaling group.
    Auto Scaling group maximum instance size (ASGMaxSize) 4 Maximum instance size for the Auto Scaling group.
    Auto Scaling group minimum instance size (ASGMinSize) 2 Minimum instance size for the Auto Scaling group.
    Elastic Load Balancers CIDR range (WebAccessCIDR) 10.0.0.0/16 The CIDR IP range that is permitted to access the Elastic Load Balancers.
    Elastic Load Balancing scheme (ELBSchemeParameter) internet-facing Choose whether the Elastic Load Balancing is public or private.

  4. When you are satisfied with your infrastructure selections, select Next. If you don't want to complete the configuration, select Cancel. If you cancel, all of the selections on the specification page are lost and you are returned to the landing page. To go to the previous screen, select Previous.

  5. On the Review and deploy page, review your configuration details. If you want to make changes, select Previous. To stop, select Cancel. When you select Cancel, all of the selections on the specification page are lost and you are returned to the landing page. When you choose Deploy, you agree to the terms of the Acknowledgment. Launch Wizard validates the inputs and notifies you of any issues you must address.

  6. When validation is complete, Launch Wizard deploys your AWS resources and configures your IIS application. Launch Wizard provides you with status updates about the progress of the deployment on the Deployments page. From the Deployments page, you can view the list of current and previous deployments.

  7. When your deployment is ready, a notification informs you that the IIS application is successfully deployed. If you have set up an Amazon SNS notification, you are also alerted through Amazon SNS. To manage and access all of the resources related to your application, select the deployment, and from the Actions dropdown list, select Manage.

  8. When the application is deployed, you can access your instances through the Amazon EC2 console.