Long running EC2s with Cloudformation and ServiceCatalog

0

My organisation runs with a number of fairly tight controls for how we can build our environments. One of these is that infrastructure must be deployed via the service catalog using products that have been validated before being published for use. This means we rely on Cloudformation to build the EC2 servers we use.

My use case for EC2 is as long running compute nodes within a cluster that store data. This requirement comes from the software in use. This means they are not sacrificial like a web server or app server might be.

As such using autoscaling groups for the EC2s is not ideal, as I don't want the EC2s being terminated unexpectedly as this can cause data loss, and also new nodes need to be configured into the cluster which would mean a loss of capacity.

What I'm looking for is suggestions on how to manage the EC2s using Cfn and ServiceCatalog without having to push new versions of the Service Catalog products when we want to make changes to the EC2s, such as volume sizes, or instance types. One option could be custom macros and various lambdas but this gets complex quickly.

Terraform works well for this but is not an option due to the restrictions I mention around service catalog.

TIA....

demandé il y a un an245 vues
1 réponse
0

Hello,

Service Catalog basically operates similar to Cloudformation. If you don't want to create new versions for every new changes, you can parameterize the attributes and just update the cloudformation stack with new values to update the EC2. An important point to keep in mind is that update to some properties can trigger resource replacement and you mentioned you don't want your EC2 to be replaced and If you are looking to update any value without replacement, it won't be possible for properties that require replacement natively.

If you need granular review of your environment for the use case , we require details that are non-public information. Therefore, kindly open a support case with AWS using the following https://console.aws.amazon.com/support/home#/case/create

AWS
répondu il y a un an

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions

Contenus pertinents