AWS ECS Express Mode¶
1. Create an ECS Express Mode Service¶
Go to the ECS console and select Express mode in the navigation pane on the left-hand side
Image URI:
public.ecr.aws/xlwings/xlwings-lite:1.0.0.94
Task execution role: Select an existing role or choose
Create new roleInfrastructure role: Select an existing role or choose
Create new roleExpand the Additional configurations section:
Container port:
8000Environment variables > Add environment variable:
Key:
XLWINGS_LICENSE_KEYValue type:
Environment variableValue or value from:
<your license key>
CPU: 0.25 vCPU, Memory: 0.5 GB
Networking: Configure according to your requirements (leaving the checkbox unchecked will expose the service to the public internet)
Click Create
2. Configuration (optional)¶
You can configure xlwings Lite via optional environment variables. For an overview, see Configuration. To add environment variables to your existing service, click on your service > Update service (orange button on the top right) > Additional configurations. Once added, click on Update (orange button at the bottom right) to deploy.
3. Add-in installation¶
In your browser, go to
https://<your-hostname>/manifest, which will downloadxlwings-lite-manifest.xml.Go to Microsoft 365 admin center
Click on
Show all>Settings>Integrated Apps.If you have xlwings Lite installed, uninstall it first.
Click on
Upload custom appsand selectOffice Add-in(App type).Select
Upload manifest file (.xml) from device. ClickChoose File, then select thexlwings-lite-manifest.xmlfrom the previous step.Click
Next, then assign the desired users.Click
Nextand accept permission requests.Click
NextandFinish deployment.
The users will get the add-in to show up automatically although it may take a few hours.
4. Updating¶
To update xlwings Lite:
Go to the ECS console and navigate to your cluster > your service
Click on Update service (orange button on the top right). Update the Image URI to the following:
public.ecr.aws/xlwings/xlwings-lite:1.0.0.94
Once added, click on Update (orange button at the bottom right) to deploy.
Normally, you don’t need to update the manifest after deploying a new version of the container. Occasionally, this is required if e.g., if the URL of your container changed. In this case, the Office 365 admin center offers a link to Update Add-in.