Answers: <p>The amount of time it takes a cloud to create a specific cloud resource is an implementation detail of that cloud. And so you will not be in a position to change the amount of time it takes Azure to create a Redis cache unless you are also in a position to change the underlying implementation of how Azure creates that Redis cache.</p>
  <p>If a cloud implementation takes an unacceptably long time to create a specific resource, you have two options as a user: create a different kind of resource, or create it in advance of when you need it so that you don't have to spend the creation time during your low-latency deploy process.</p>
  
Answers: CC BY-SA 4.0
Answers: 2023-09-26T20:06:16.043Z
Answers: 2023-09-26T20:06:16.043Z
Answers: Jesusaur
Body: <p>Provisioning a 1 GB Redis cache service on AWS takes around 8 minutes. Doing the same on Azure takes around 16 minutes. Ours Terraform scripts need the call back from the Redis systems. Why is this taking so long and <strong>how can we make this process faster</strong> for immutable infrastructure?</p>
  
  <ul>
  <li>ideally, we would like to create related infra less than 4 minutes</li>
  <li>some tests even take longer 8 and 16 minutes are the averages </li>
  <li>we are using a managed Redis service by cloud providers.</li>
  <li>Doing manually also takes that much time to complete it. Infrastructure gets set up but the Redis is not usable for Terraform or X.</li>
  <li>This happens in any random account in cloud providers with or without Terraform</li>
  </ul>
  
  <p><a href="https://i.sstatic.net/WLk6s.png" rel="noreferrer"><img src="https://i.sstatic.net/WLk6s.png" alt="enter image description here"></a></p>
  
Comments: CC BY-SA 4.0
Comments: 2019-12-23T10:28:16.347Z
Comments: Could you post an answer?
Comments: 030
Comments: CC BY-SA 4.0
Comments: 2018-07-03T09:17:53.980Z
Comments: How can we have an idea of which type of instance or managed service you're starting, with which parameters and which configuration, is there some data ? Out of thin air, I don't think someone can answer your specific case. At least show your terraform plan so we may have an idea of what you're doing. I think that's too broad anyway and should be directed to your cloud's customer support as they are the only one with hands on the infrastructure to tell you "Why".
Comments: Tensibai
Comments: CC BY-SA 4.0
Comments: 2018-07-03T10:36:17.677Z
Comments: thanks for the comments update the questions. it is a hosted service. Configuration 1 GB Redis Server. Will create tickets in both Azure and AWS today.
Comments: Rıfat Erdem Sahin
Comments: CC BY-SA 4.0
Comments: 2018-07-03T12:53:25.887Z
Comments: I don't think someone can answer your specific case. : this happens in any random account. Easy to test and find out
Comments: Rıfat Erdem Sahin
Comments: CC BY-SA 4.0
Comments: 2018-07-23T09:30:09.287Z
Comments: I guess if the speed is necessary Docker and Kubernetes is the way to go.
Comments: Rıfat Erdem Sahin
Comments: CC BY-SA 4.0
Comments: 2018-07-23T09:38:28.503Z
Comments: re" his happens in any random account. Easy to test and find out " <- No one else than Cloud providers teams knows how the redis cluster is set up behind the scene, so reproducing it is easy, finding why it takes that much time is not possible for an outsider. regarding your last comment, probably, if you're up to handle the whole life cycle a SaaS service handle for you to gain a few minutes on deploy (I can't image a need to deploy dozen of redis clusters per day).
Comments: Tensibai
Comments: CC BY-SA 4.0
Comments: 2018-08-03T16:38:14.873Z
Comments: I am running in to the same problem (around 20 minutes for the smallest Redis cache in Azure to spin up).  A different question would be, how can we build our pipeline with long provisioning times in the design?  Not sure of the answer yet.
Comments: Chris
Comments: CC BY-SA 4.0
Comments: 2018-08-09T21:29:01.833Z
Comments: I guess the answer to this question is using things like packer. https://www.packer.io/
Comments: Rıfat Erdem Sahin
Tags: <amazon-web-services><terraform><azure><redis>
Title: Provisioning times for Redis in cloud taking too long, how can we shorten it?
UserDisplayName: Rıfat Erdem Sahin
ThreadText: # Provisioning times for Redis in cloud taking too long, how can we shorten it?
  
  (Asked by: username_0 on 2018-07-03)
  
  Provisioning a 1 GB Redis cache service on AWS takes around 8 minutes. Doing the same on Azure takes around 16 minutes. Ours Terraform scripts need the call back from the Redis systems. Why is this taking so long and **how can we make this process faster** for immutable infrastructure?
  
  * ideally, we would like to create related infra less than 4 minutes
  * some tests even take longer 8 and 16 minutes are the averages
  * we are using a managed Redis service by cloud providers.
  * Doing manually also takes that much time to complete it. Infrastructure gets set up but the Redis is not usable for Terraform or X.
  * This happens in any random account in cloud providers with or without Terraform
  
  [![enter image description here](https://i.sstatic.net/WLk6s.png)](https://i.sstatic.net/WLk6s.png)
  
  **Tags:** amazon-web-services, terraform, azure, redis
  
  > **Comments:**
  > **username_2**: How can we have an idea of which type of instance or managed service you're starting, with which parameters and which configuration, is there some data ? Out of thin air, I don't think someone can answer your specific case. At least show your terraform plan so we may have an idea of what you're doing. I think that's too broad anyway and should be directed to your cloud's customer support as they are the only one with hands on the infrastructure to tell you "Why".  
  > **username_0**: thanks for the comments update the questions. it is a hosted service. Configuration 1 GB Redis Server. Will create tickets in both Azure and AWS today.  
  > **username_0**: I don't think someone can answer your specific case. : this happens in any random account. Easy to test and find out  
  > **username_0**: I guess if the speed is necessary Docker and Kubernetes is the way to go.  
  > **username_2**: re" his happens in any random account. Easy to test and find out " <- No one else than Cloud providers teams knows how the redis cluster is set up behind the scene, so reproducing it is easy, finding why it takes that much time is not possible for an outsider. regarding your last comment, probably, if you're up to handle the whole life cycle a SaaS service handle for you to gain a few minutes on deploy (I can't image a need to deploy dozen of redis clusters per day).  
  > **username_3**: I am running in to the same problem (around 20 minutes for the smallest Redis cache in Azure to spin up).  A different question would be, how can we build our pipeline with long provisioning times in the design?  Not sure of the answer yet.  
  > **username_0**: I guess the answer to this question is using things like packer. https://www.packer.io/  
  > **username_1**: Could you post an answer?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_4 on 2023-09-26. Score: 0
  
  The amount of time it takes a cloud to create a specific cloud resource is an implementation detail of that cloud. And so you will not be in a position to change the amount of time it takes Azure to create a Redis cache unless you are also in a position to change the underlying implementation of how Azure creates that Redis cache.
  
  If a cloud implementation takes an unacceptably long time to create a specific resource, you have two options as a user: create a different kind of resource, or create it in advance of when you need it so that you don't have to spend the creation time during your low-latency deploy process.
  
  
  ---
  
  