Many times we are faced with applications that overload the operating system’s TCP ports, normally these applications are those that make many connections to the database.

The main symptom of Windows Server is to stop communicating with the database because all ports are in use.

To solve this, we perform a tuning on the TCP ports via registry editing, below I show how to perform the tunning.

To perform the tunning run the following commands in PowerShell.

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "MaxUserPort" -Value 65534Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "TcpNumConnections" -Value 65534Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "TcpTimedWaitDelay" -Value 60

To check if the records have been added, execute the command.

Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "MaxUserPort"Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "TcpNumConnections"Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "TcpTimedWaitDelay"



We often need to have secure certificates in our applications and load balancers, in this tutorial I will show you how to import secure certificates into ACM.

In this example I will demonstrate how to import a private certificate created with OpenSSL.

Creating an RSA certificate with OpenSSL valid for 365 days in Ubuntu 20.04

openssl req -newkey rsa:2048 -new -nodes -x509 -days 365 -keyout /tmp/key.pem -out /tmp/cert.pem

With the certificate body (cert.pem) and the created key (key.pem) we will import to AWS, first let’s import into ACM.

aws acm import-certificate --certificate fileb:///tmp/cert.pem --private-key fileb:///tmp/key.pem --tags Key=Name,Value=CA-TEST



Daniel Fulgido

Daniel Fulgido

A person in love with my family and DevOps!