EC2 Windows Server instance unreachable (provisioned with EC2Launch)





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have been provisioning Windows instances on AWS EC2 using the Windows Server 1803 AMI image family on AWS. I have used the following AMI Ids:




  • ami-08a02a307592e1af7

  • ami-0246254cf1985c372

  • ami-0f7768a8e6b521299


In addition I use EC2Launch (via user-data) to execute a set of powershell commands on the Windows instance. Depending on the contents of the user data sometimes the instance fails to get correctly provisioned. When that occurs the following problems are present:




  • I am unable to get a Windows password from the instance. In the EC2 console a dialog pops up and tells me to wait at least 4 minutes.

  • The system log in the EC2 console is empty and only shows a black background.

  • I can still request a screenshot that shows my instance is up and running but I cannot login, since I cannot get a password.


I have so far started about 10 instances, each time the only difference was that I modified the user data. My problem is that since I cannot get access to the instance, I also do not know what change in the user data is causing a problem.



Of course I can debug that, by making one line changes at a time and start a new instance, but that is not only slow it also prevents me from learning about which kind of error occurred. I only know that a certain change line causes the failure, but I do not know not why?



Is there any way to recover from an error in a EC2Launch so that I still get access to the machine and can inspect the EC2Launch log?



Update
So far I have started about 20-30 instances. In about 50% of all instance starts the instance fails to successfully provision (I get no default password and cannot login), while in the other 50% the same instance configuration starts just fine.










share|improve this question































    0















    I have been provisioning Windows instances on AWS EC2 using the Windows Server 1803 AMI image family on AWS. I have used the following AMI Ids:




    • ami-08a02a307592e1af7

    • ami-0246254cf1985c372

    • ami-0f7768a8e6b521299


    In addition I use EC2Launch (via user-data) to execute a set of powershell commands on the Windows instance. Depending on the contents of the user data sometimes the instance fails to get correctly provisioned. When that occurs the following problems are present:




    • I am unable to get a Windows password from the instance. In the EC2 console a dialog pops up and tells me to wait at least 4 minutes.

    • The system log in the EC2 console is empty and only shows a black background.

    • I can still request a screenshot that shows my instance is up and running but I cannot login, since I cannot get a password.


    I have so far started about 10 instances, each time the only difference was that I modified the user data. My problem is that since I cannot get access to the instance, I also do not know what change in the user data is causing a problem.



    Of course I can debug that, by making one line changes at a time and start a new instance, but that is not only slow it also prevents me from learning about which kind of error occurred. I only know that a certain change line causes the failure, but I do not know not why?



    Is there any way to recover from an error in a EC2Launch so that I still get access to the machine and can inspect the EC2Launch log?



    Update
    So far I have started about 20-30 instances. In about 50% of all instance starts the instance fails to successfully provision (I get no default password and cannot login), while in the other 50% the same instance configuration starts just fine.










    share|improve this question



























      0












      0








      0








      I have been provisioning Windows instances on AWS EC2 using the Windows Server 1803 AMI image family on AWS. I have used the following AMI Ids:




      • ami-08a02a307592e1af7

      • ami-0246254cf1985c372

      • ami-0f7768a8e6b521299


      In addition I use EC2Launch (via user-data) to execute a set of powershell commands on the Windows instance. Depending on the contents of the user data sometimes the instance fails to get correctly provisioned. When that occurs the following problems are present:




      • I am unable to get a Windows password from the instance. In the EC2 console a dialog pops up and tells me to wait at least 4 minutes.

      • The system log in the EC2 console is empty and only shows a black background.

      • I can still request a screenshot that shows my instance is up and running but I cannot login, since I cannot get a password.


      I have so far started about 10 instances, each time the only difference was that I modified the user data. My problem is that since I cannot get access to the instance, I also do not know what change in the user data is causing a problem.



      Of course I can debug that, by making one line changes at a time and start a new instance, but that is not only slow it also prevents me from learning about which kind of error occurred. I only know that a certain change line causes the failure, but I do not know not why?



      Is there any way to recover from an error in a EC2Launch so that I still get access to the machine and can inspect the EC2Launch log?



      Update
      So far I have started about 20-30 instances. In about 50% of all instance starts the instance fails to successfully provision (I get no default password and cannot login), while in the other 50% the same instance configuration starts just fine.










      share|improve this question
















      I have been provisioning Windows instances on AWS EC2 using the Windows Server 1803 AMI image family on AWS. I have used the following AMI Ids:




      • ami-08a02a307592e1af7

      • ami-0246254cf1985c372

      • ami-0f7768a8e6b521299


      In addition I use EC2Launch (via user-data) to execute a set of powershell commands on the Windows instance. Depending on the contents of the user data sometimes the instance fails to get correctly provisioned. When that occurs the following problems are present:




      • I am unable to get a Windows password from the instance. In the EC2 console a dialog pops up and tells me to wait at least 4 minutes.

      • The system log in the EC2 console is empty and only shows a black background.

      • I can still request a screenshot that shows my instance is up and running but I cannot login, since I cannot get a password.


      I have so far started about 10 instances, each time the only difference was that I modified the user data. My problem is that since I cannot get access to the instance, I also do not know what change in the user data is causing a problem.



      Of course I can debug that, by making one line changes at a time and start a new instance, but that is not only slow it also prevents me from learning about which kind of error occurred. I only know that a certain change line causes the failure, but I do not know not why?



      Is there any way to recover from an error in a EC2Launch so that I still get access to the machine and can inspect the EC2Launch log?



      Update
      So far I have started about 20-30 instances. In about 50% of all instance starts the instance fails to successfully provision (I get no default password and cannot login), while in the other 50% the same instance configuration starts just fine.







      amazon-ec2 amazon-cloudformation






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 3 '18 at 8:11







      lanoxx

















      asked Nov 23 '18 at 10:49









      lanoxxlanoxx

      5,85254991




      5,85254991
























          0






          active

          oldest

          votes












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445252%2fec2-windows-server-instance-unreachable-provisioned-with-ec2launch%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445252%2fec2-windows-server-instance-unreachable-provisioned-with-ec2launch%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Paul Cézanne

          UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

          Angular material date-picker (MatDatepicker) auto completes the date on focus out