You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To deploy ODM containers on AWS ECS Fargate from [docker-compose](docker-compose-http.yaml) file, you must meet the following requirements:
@@ -41,7 +41,7 @@ To deploy ODM containers on AWS ECS Fargate from [docker-compose](docker-compose
41
41
* Install python3.6+ and later version.
42
42
* Ensure you have an [AWS Account](https://aws.amazon.com/getting-started/).
43
43
* Install [ECS Compose-x](https://github.com/compose-x/ecs_composex?tab=readme-ov-file#installation), preferably in a virtual environment.
44
-
* Ensure that you have an existing internet-facing Application Elastic Load balancer and a VPC with public subnets [setup](https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-manage-subnets.html) on Amazon Web Services(AWS).
44
+
* Ensure that you have an existing internet-facing Application Elastic Load balancer based on a VPC with public subnets [setup](https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-manage-subnets.html) on Amazon Web Services(AWS).
45
45
* If you want to run ODM Decision services in HTTPS mode, you need to have an [ACM public certificate](https://console.aws.amazon.com/acm/home).
46
46
47
47
*Note*: The commands and tools have been tested on macOS.
@@ -138,6 +138,11 @@ For example:
138
138
...
139
139
```
140
140
141
+
#### 2.3.4 Create VPC endpoint to access ASW Secrets Manager service
142
+
143
+
Since the ECS tasks need to access to the secret from Secrets Manager service, you might need to create an AWS Secrets Manager VPC endpoint. This inteface endpoint should use the VPC that you plan to deploy ODM. Choose the subnets and security group of this VPC to setup the endpoint. For more information, see [Using an AWS Secrets Manager VPC endpoint](https://docs.aws.amazon.com/secretsmanager/latest/userguide/vpc-endpoint-overview.html).
144
+
145
+
141
146
### 2.4 Create S3 bucket and IAM policy for IBM licensing service
142
147
143
148
In this tutorial, we have included IBM Licensing service for tracking license usage of ODM that is deployed on AWS ECS Fargate.
@@ -212,7 +217,7 @@ If you want to run ODM Decision services in HTTPS mode, it is required to provid
212
217
- Rename the downloaded `AmazonRootCA1.pem` file to `AmazonRootCA1.crt`.
213
218
- In the S3 bucket created by `ecs-compose-x init`, create a folder named `certificate`.
214
219
- Upload this `AmazonRootCA1.crt` file into this folder. <br><imgsrc="images/S3-certificate.png"width="80%"/>
215
-
- Create a new file system name `odm-filesystem` in [Amazon EFS](https://console.aws.amazon.com/efs/home) using the same VPC where you plan to create ECS Fargate cluster with ODM services. This file system will be used as a volume for Decision Center. See :
220
+
- Create a new file system name `odm-filesystem` in [Amazon EFS](https://console.aws.amazon.com/efs/home) using the *same VPC* where you plan to create ECS Fargate cluster with ODM services. This file system will be used as a volume for Decision Center. See :
216
221
```
217
222
volumes:
218
223
app:
@@ -250,7 +255,7 @@ volumes:
250
255
251
256
## 3. Deploy ODM to AWS ECS Fargate
252
257
253
-
ODM can be deployed either in [HTTP](docker-compose-http.yaml) or [HTTPS](docker-compose-https.yaml) mode. Each of the ODM components are configured to be deployed as separate ECS task due to IBM licensing service which logs CPU usage per ECS task. The IBM Licensing service will be deployed to the ECS tasks of Decision Center, Decision Server Runtime and Decision Runner for tracking purpose. Inspect the docker-compose file for more details.
258
+
ODM can be deployed either in [HTTP](docker-compose-http.yaml) or [HTTPS](docker-compose-https.yaml) mode. Each of the ODM components are configured to be deployed as separate ECS task due to IBM licensing service which logs CPU usage per ECS task. The IBM Licensing service will be deployed to the ECS tasks of Decision Center, Decision Server Runtime and Decision Runner for tracking purpose. Inspect the docker-compose file for more details.
254
259
255
260
<br><imgsrc="images/topology.png"width="80%"/>
256
261
@@ -288,7 +293,6 @@ x-elbv2:
288
293
```
289
294
- For the parameter `RES_URL` that is defined in `environment` section of `odm-decisionrunner` service, look for the DNS value of your [load balancer](https://console.aws.amazon.com/ec2/home?#LoadBalancers:) and assign it to the parameter as `https://your_loadbalancer_dns/res`. This is required for running `Testing and Simulation` in Decision Center.
290
295
291
-
292
296
### 3.2 Create the AWS CloudFormation stacks
293
297
294
298
- Run the following command to generate the CFN templates, validate the templates, and create the stacks in CFN.
0 commit comments