<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Modifying EC2 Size after Cloud Formation Deployment in ArcGIS Enterprise in the cloud Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1324873#M655</link>
    <description>&lt;P&gt;We are attempting to deploy Enterprise 11.1 using the cloud formation templates provided by Esri. I have integrated the templates into my Terraform code and launched them on our AWS profile successfully. For the most part, everything is working swimmingly.&lt;/P&gt;&lt;P&gt;However, there is one thing I noticed when using the Lambda functions to start and stop the stacks: the fileserver instance is&amp;nbsp;&lt;EM&gt;also&lt;/EM&gt; tied to the stack. Our EC2 instance sizes are declared in the parameters of the cloud formation resource. If, for example, my&amp;nbsp; VP decides we need to save some money, and I need to lower the size of my EC2 instance, I would need to modify that in the terraform parameters and re-launch.&lt;/P&gt;&lt;P&gt;Here is where I get a bit confused: if I have integrated an IdP in my portal configuration, but then I launch the stack to change the EC2 size, will the fileserver also be destroyed? Meaning all of the users we have integrated would be deleted and I would have to set up the entire IdP integration with Portal again?&lt;BR /&gt;&lt;BR /&gt;I understand there is a way to persist resources in the cloud formation templates themselves (I have not modified mine, just to stay in scope of support), but I don't think you could hook up the persistent resource to a newly deployed set of resources in the stack without some custom scripting.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Any insight into how to modify the existing resource without relaunching the entire stack would be really helpful!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jason Vignochi&lt;/P&gt;&lt;P&gt;Sr. Software Engineer&lt;/P&gt;</description>
    <pubDate>Fri, 01 Sep 2023 18:13:46 GMT</pubDate>
    <dc:creator>JVig</dc:creator>
    <dc:date>2023-09-01T18:13:46Z</dc:date>
    <item>
      <title>Modifying EC2 Size after Cloud Formation Deployment</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1324873#M655</link>
      <description>&lt;P&gt;We are attempting to deploy Enterprise 11.1 using the cloud formation templates provided by Esri. I have integrated the templates into my Terraform code and launched them on our AWS profile successfully. For the most part, everything is working swimmingly.&lt;/P&gt;&lt;P&gt;However, there is one thing I noticed when using the Lambda functions to start and stop the stacks: the fileserver instance is&amp;nbsp;&lt;EM&gt;also&lt;/EM&gt; tied to the stack. Our EC2 instance sizes are declared in the parameters of the cloud formation resource. If, for example, my&amp;nbsp; VP decides we need to save some money, and I need to lower the size of my EC2 instance, I would need to modify that in the terraform parameters and re-launch.&lt;/P&gt;&lt;P&gt;Here is where I get a bit confused: if I have integrated an IdP in my portal configuration, but then I launch the stack to change the EC2 size, will the fileserver also be destroyed? Meaning all of the users we have integrated would be deleted and I would have to set up the entire IdP integration with Portal again?&lt;BR /&gt;&lt;BR /&gt;I understand there is a way to persist resources in the cloud formation templates themselves (I have not modified mine, just to stay in scope of support), but I don't think you could hook up the persistent resource to a newly deployed set of resources in the stack without some custom scripting.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Any insight into how to modify the existing resource without relaunching the entire stack would be really helpful!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jason Vignochi&lt;/P&gt;&lt;P&gt;Sr. Software Engineer&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 18:13:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1324873#M655</guid>
      <dc:creator>JVig</dc:creator>
      <dc:date>2023-09-01T18:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying EC2 Size after Cloud Formation Deployment</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1324879#M656</link>
      <description>&lt;P&gt;After a bit more investigation, it appears you can resize your EC2's manually from the AWS console. I could probably just update the code to match the changes I make manually and not deploy.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2023 18:26:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1324879#M656</guid>
      <dc:creator>JVig</dc:creator>
      <dc:date>2023-09-01T18:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying EC2 Size after Cloud Formation Deployment</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1325037#M657</link>
      <description>&lt;P&gt;Indeed. You just need to power off the ec2 instance, then change the ec2 instance type to scale up or down and then start the ec2 instance again.&lt;/P&gt;</description>
      <pubDate>Sat, 02 Sep 2023 02:54:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-in-the-cloud-questions/modifying-ec2-size-after-cloud-formation/m-p/1325037#M657</guid>
      <dc:creator>MarceloMarques</dc:creator>
      <dc:date>2023-09-02T02:54:07Z</dc:date>
    </item>
  </channel>
</rss>

