Answers: <p>The 200 limit can be raised, however this is a grinding process that can take months. You work through customer support to get "elevated" as a client to more AWS privileges.</p>
  
  <p>Resources:
  - Worked under a company that specifically ran into this problem, took 8 months before that limit was lifted. </p>
  
Answers: CC BY-SA 4.0
Answers: 2019-02-12T04:38:45.357Z
Answers: Gee, 8 months. There must be some really weird effects larger amount of resources have
Answers: jdog
Answers: CC BY-SA 4.0
Answers: 2019-02-11T06:33:35.977Z
Answers: 2019-02-11T06:33:35.977Z
Answers: Alan-Cugler
Body: <p>Not sure I get it. If my service layer is completely maintainable, indepedent services and very easy to maintain taking only a few minutes to deploy and has no bugs, AWS still won't let me deploy it if it uses 201 resources. This seems like dogma or am I wrong?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-02-08T01:22:35.753Z
Comments: Service limits are usually nor hard limit s, but can be raised with a support request. Most likely this is either to protect their SLA or to stop you from a stupid common behaviour
Comments: jdog
Tags: <microservices><serverless><aws-cloudformation>
Title: Practical reasons for 200 limit of AWS resources in CF templates
UserDisplayName: Niklas Rosencrantz
ThreadText: # Practical reasons for 200 limit of AWS resources in CF templates
  
  (Asked by: username_0 on 2019-02-07)
  
  Not sure I get it. If my service layer is completely maintainable, indepedent services and very easy to maintain taking only a few minutes to deploy and has no bugs, AWS still won't let me deploy it if it uses 201 resources. This seems like dogma or am I wrong?
  
  **Tags:** microservices, serverless, aws-cloudformation
  
  > **Comments:**
  > **username_1**: Service limits are usually nor hard limit s, but can be raised with a support request. Most likely this is either to protect their SLA or to stop you from a stupid common behaviour  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-02-11. Score: 2 | Accepted answer
  
  The 200 limit can be raised, however this is a grinding process that can take months. You work through customer support to get "elevated" as a client to more AWS privileges.
  
  Resources:
  - Worked under a company that specifically ran into this problem, took 8 months before that limit was lifted.
  
  > **Comments:**
  > **username_1**: Gee, 8 months. There must be some really weird effects larger amount of resources have  
  
  ---
  
  