Increase limit for maximum concurrent executions beyond 1000

internal/service/lambda/event_source_mapping.go

@@ -251,7 +251,7 @@ func resourceEventSourceMapping() *schema.Resource {
 						"maximum_concurrency": {
 							Type:         schema.TypeInt,
 							Optional:     true,
-							ValidateFunc: validation.IntBetween(2, 1000),
+							ValidateFunc: validation.IntAtLeast(2),
 						},
 					},
 				},

website/docs/r/lambda_event_source_mapping.html.markdown

@@ -199,8 +199,7 @@ resource "aws_lambda_event_source_mapping" "example" {
 
 ### scaling_config Configuration Block
 
-* `maximum_concurrency` - (Optional) Limits the number of concurrent instances that the Amazon SQS event source can invoke. Must be between `2` and `1000`. See [Configuring maximum concurrency for Amazon SQS event sources](https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#events-sqs-max-concurrency).
-
+* `maximum_concurrency` - (Optional) Limits the number of concurrent instances that the Amazon SQS event source can invoke. Must be greater than or equal to `2`. See [Configuring maximum concurrency for Amazon SQS event sources](https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#events-sqs-max-concurrency). You need to raise a [Service Quota Ticket](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) to increase the concurrency beyond 1000.
 ### self_managed_event_source Configuration Block
 
 * `endpoints` - (Required) A map of endpoints for the self managed source.  For Kafka self-managed sources, the key should be `KAFKA_BOOTSTRAP_SERVERS` and the value should be a string with a comma separated list of broker endpoints.