Add a sample `.tfvars` file for production set up - WISCALERTS-27

See merge request !18

Add a user guide for Secure Agent documentation - WISCALERTS-27

See merge request !16

Add Secure Agent architecture diagram on AWS - WISCALERTS-29

See merge request !17

Update to use an Amazon Linux 2 image - WISCALERTS-2

See merge request !15

* In order to increase disk space allocated for Docker container utilize Amazon Linux 2. By default Amazon Linux 2 uses `overlay2` storage driver, which gives the base storage size of the space left on the disk.
* Removed SSM agent as it's shipped with all Amazon Linux 2 AMIs.
* Utilized `SSM` param store for storing `IICS` user credentials.
* Increased `EBS` volume size to allocate more disk space.

* In order to increase disk space allocated for Docker container utilize Amazon Linux 2. By default Amazon Linux 2 uses `overlay2` storage driver, which gives the base storage size of the space left on the disk.
* Removed SSM agent as it's shipped with all Amazon Linux 2 AMIs.
* Utilized `SSM` param store for storing `IICS` user credentials.
* Increased `EBS` volume size to allocate more disk space.

Add all Secure Agent's resources into EFS for AWS hosted instance - WISCALERTS-2

See merge request !14

Update `README` instructions on how to access Secure Agent's file system - WISCALERTS-2

See merge request !12

Update Secure Agent's EC2 instance for a better instance - WISCALERTS-2

See merge request !13

* Adjusted the instance to be a `t2.xlarge` since we are going to have more load.
* Increased container memory to 15 GiB.
* Increased EC2 instance's EBS root volume to 40 GB.
* Re-named the profile to indicate the environment it's associated to.

Add SSM agent policy to instance profile, add name tag to autoscaling group

See merge request !11

Mount EFS volume in the same AZ as the ECS instance

See merge request interop/iics_secure_agent!10

* Added a configurable hostname for container.
* Now everything from agent's home is mounted into a EFS file system for persistence.
* Added documentation on how to use this Secure Agent infra.
* Extracted role and profile for prod environment

Add an EFS volume into Secure Agent infrastructure

See merge request interop/iics_secure_agent!9

This volume will act as the persistence storage for Secure Agent's logs and configurations.

Pass informatica username/password into terraform and update docker image tags to be immutable

See merge request interop/iics_secure_agent!7

Tag Secure Agent images for each build

See merge request interop/iics_secure_agent!8

Tag has the format `git-${CI_COMMIT_SHA:0:8}`. `CI_COMMIT_SHA` is the GitLab CI/CD variable for this commit has.

Externalize Secure Agent configurations so that those can be persisted and re-use

See merge request interop/iics_secure_agent!6

* Add instructions on how to mount various configurations for Secure Agent so those can be re-used.
* Updated `README.md` with descriptions on how to mount volumes.
* Documented various ports in Secure Agents.
* Fixed punctuations.

Add ECR resource for publishing Secure Agent image

See merge request interop/iics_secure_agent!5

Image will be built and publish by the CI/CD process

Add ci/cd file into changes set to build

See merge request interop/iics_secure_agent!4

Make default build push to prod tier

See merge request interop/iics_secure_agent!3

Since we are planning to run a single instance of Secure Agent, let that be the prod instance.

Add initial terraform scripts for automating infra. for Informatica Secure Agent

See merge request interop/iics_secure_agent!2

Since our licensing restrict us from more than 1 instance of Secure Agent, before deploying a new instance existing instance need to be shutdown (after adjusting any resources that depends on that instance). Due to this reason terraform is not part of CI/CD.