If you have a .NET API that you want to containerize, here are the steps to prepare it. Create docker image Push to repository Setup ECS The TLS 1.0 option is needed if your SQL Server database does not support TLS 1.2. The recommended option is to update your database to the secure protocol. You may also change sdk and aspnet version to 5.0 if you haven't updated to 6.0 yet. This Dockerfile uses a multi-stage build to get an optimal image size. Dockerfile FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build-env WORKDIR /app # Copy csproj and restore as distinct layers COPY *.csproj ./ RUN dotnet restore # Copy everything else and build COPY . ./ RUN dotnet publish -c Release -o out # Build runtime image FROM mcr.microsoft.com/dotnet/aspnet:6.0 WORKDIR /app # Enable TLS 1.0 RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /etc/ssl/openssl.cnf RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@
Ever had a colleague invite you to collaborate on a Google Doc using your work email and get prompted to request access using your gmail account? To avoid this, you can create a Google account using your work email (e.g. @xyzcorp.com) instead of the default @gmail.com or subscribing to GSuite. When your work email is a Google account, you can use it to login wherever there is a prompt for a Google account (Google Drive, Google SSO Login - Gitlab, Trello, Airtable, Jira, Clubhouse, etc.). 1. In your browser, set to Incognito mode and go to https://drive.google.com 2. Click on Create account -> For myself 3. Click on “Use my current email address instead” and type your work email. Fill in the other fields, then click on next. After doing this, your work email is now a Google account and you can be invited to collaborate on other Google services.