A workload onboarding plan identifies machines that have been data-collected from a cloud account endpoint but that are not yet managed by a Cloud Assembly project.
If you add a cloud account/region to Cloud Assembly that contains machines that were deployed outside of Cloud Assembly, you can bring those machines into Cloud Assembly management by first data-collecting them and then adding them to a workload onboarding plan. When you add the machines to an workload onboarding plan, you can group all or some of them into a single deployment, or onboard each machine as a separate deployment.
Use an onboarding plan to bring unmanaged machines into Cloud Assembly management. You create a plan, populate it with machines, and then run the plan to import the machines and create Cloud Assembly deployments. You can also generate a blueprint as part of this process.
To more easily onboard a group of machines you can create filtering rules to select machines for onboarding based on criteria such as machine name, status, IP address, and tags.
Machines that are available for workload onboarding are listed on the Discovered in the Origin column. Only machines that have been data-collected are listed. Once the machines have been onboarded, they appear in the Origin column as Deployed and are then managed by Cloud Assembly.page relative to a specific cloud account type and region and labeled as
The person who runs the workload onboarding plan is automatically assigned as the machine owner.
A Deployment Onboarded event is created when you run the plan. Using Extensibility tab options, you can subscribe to these deployment events and perform actions on them.
For examples of onboarding techniques, see Onboard select Amazon Web Services machines as a single deployment and Onboard multiple unmanaged machines by using filtering rules and creating separate deployments.