Hi Roshan, it is possible to do what you want by installing a new Greengrass Core instance on the same server in a different root folder. From the Sitewise console, select Create Gateway and go through the Default Setup. Once the installation script has been dowloaded, open it and edit the line with
"/greengrass" with another folder.
If you are installing on Windows, just pass the new folder name as
-InstallPath parameter to the script
NOTE: This will not work if you are also installing the data processing pack, as this pack will open some ports that will conflict with those opened by the existing gateway.
How do we make different stages like dev, pre-prod and prod in amplify ?Accepted Answerasked 7 months ago
Data movement from prod to dev with anonymization of PIIAccepted Answerasked 5 years ago
is it possible to deploy two (2) SiteWise gateway configuration on single EC2 machine?asked 4 months ago
Best way to set up dev, staging and prod environments in LoRaWAN?Accepted Answerasked 10 months ago
Unable to Run DBT Glue Job in eu-west-2 in DEV Accountasked 5 months ago
Creating Dev and Prod deployments using CDKAccepted Answerasked a year ago
Amazon Connect > Dev -> UAT -> Productionasked 10 months ago
Connecting code commit from one aws account to amplify in other aws accountasked 5 months ago
Should I use one account or multiple accounts?Accepted Answerasked 9 months ago
What services should I use if I want to do live monitoring the data?asked 4 years ago