Remove and clean up
Cleanup runs in the reverse order of creation: first the device stops running the component, then the stack goes, then the resources the stack retained, then the device and its identity, and finally the instance profile.
Task 1: Remove the component from the device
Section titled “Task 1: Remove the component from the device”Deleting a deployment resource removes deployment management state. It does not uninstall anything from a device. The device only removes a component when it receives a deployment revision that no longer lists it. Change the stack so the deployment lists no components while the published version stays managed:
import { GreengrassArtifactBucket, GreengrassDeployment, Pulse,} from '@greengrass-tutorial/common-constructs';import { CfnParameter, Stack, type StackProps } from 'aws-cdk-lib';import { Role } from 'aws-cdk-lib/aws-iam';import type { Construct } from 'constructs';
export class ApplicationStack extends Stack { constructor(scope: Construct, id: string, props?: StackProps) { super(scope, id, props);
// Both values are written to .greengrass-tutorial.env by the setup script // and passed with --parameters on every deploy. const tokenExchangeRoleArn = new CfnParameter( this, 'TokenExchangeRoleArn', { type: 'String', description: 'ARN of the core device token exchange role', }, ); const thingGroupArn = new CfnParameter(this, 'ThingGroupArn', { type: 'String', description: 'ARN of the thing group that holds the core device', });
// The retained artifact repository, and the read grant the core device // needs to fetch this component's artifacts from it. const artifacts = new GreengrassArtifactBucket(this, 'Artifacts'); const tokenExchangeRole = Role.fromRoleArn( this, 'TokenExchangeRole', tokenExchangeRoleArn.valueAsString, ); artifacts.grantReadTo(tokenExchangeRole, 'com.example.Pulse/*');
// The published version stays managed. This deployment revision lists no // components, so the core device uninstalls com.example.Pulse. new Pulse(this, 'Pulse', { bucket: artifacts }); new GreengrassDeployment(this, 'Fleet', { targetArn: thingGroupArn.valueAsString, }); }}import { GreengrassArtifactBucket, GreengrassDeployment, Pulse,} from '@greengrass-tutorial/common-constructs';import { CfnParameter, Stack, type StackProps } from 'aws-cdk-lib';import { Role } from 'aws-cdk-lib/aws-iam';import type { Construct } from 'constructs';
export class ApplicationStack extends Stack { constructor(scope: Construct, id: string, props?: StackProps) { super(scope, id, props);
// Both values are written to .greengrass-tutorial.env by the setup script // and passed with --parameters on every deploy. const tokenExchangeRoleArn = new CfnParameter( this, 'TokenExchangeRoleArn', { type: 'String', description: 'ARN of the core device token exchange role', }, ); const thingGroupArn = new CfnParameter(this, 'ThingGroupArn', { type: 'String', description: 'ARN of the thing group that holds the core device', });
// The retained artifact repository, and the read grant the core device // needs to fetch this component's artifacts from it. const artifacts = new GreengrassArtifactBucket(this, 'Artifacts'); const tokenExchangeRole = Role.fromRoleArn( this, 'TokenExchangeRole', tokenExchangeRoleArn.valueAsString, ); artifacts.grantReadTo(tokenExchangeRole, 'com.example.Pulse/*');
// Publishes the artifact built by pulse-artifact, then deploys it to the // existing thing group. addComponent carries the resolved NEXT_PATCH // version and orders the deployment after the component version. const pulse = new Pulse(this, 'Pulse', { bucket: artifacts }); const fleet = new GreengrassDeployment(this, 'Fleet', { // The published version stays managed. This deployment revision lists no // components, so the core device uninstalls com.example.Pulse. new Pulse(this, 'Pulse', { bucket: artifacts }); new GreengrassDeployment(this, 'Fleet', { targetArn: thingGroupArn.valueAsString, }); fleet.addComponent(pulse); }}Deploy the revision:
AWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" pnpm nx run @greengrass-tutorial/infra:deploy -- "greengrass-tutorial-infra-sandbox/**" --parameters TokenExchangeRoleArn="$TUTORIAL_TOKEN_EXCHANGE_ROLE_ARN" --parameters ThingGroupArn="$TUTORIAL_THING_GROUP_ARN"AWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" yarn nx run @greengrass-tutorial/infra:deploy -- "greengrass-tutorial-infra-sandbox/**" --parameters TokenExchangeRoleArn="$TUTORIAL_TOKEN_EXCHANGE_ROLE_ARN" --parameters ThingGroupArn="$TUTORIAL_THING_GROUP_ARN"AWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" npx nx run @greengrass-tutorial/infra:deploy -- "greengrass-tutorial-infra-sandbox/**" --parameters TokenExchangeRoleArn="$TUTORIAL_TOKEN_EXCHANGE_ROLE_ARN" --parameters ThingGroupArn="$TUTORIAL_THING_GROUP_ARN"AWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" bunx nx run @greengrass-tutorial/infra:deploy -- "greengrass-tutorial-infra-sandbox/**" --parameters TokenExchangeRoleArn="$TUTORIAL_TOKEN_EXCHANGE_ROLE_ARN" --parameters ThingGroupArn="$TUTORIAL_THING_GROUP_ARN"Wait until the component disappears from the device and the device stays healthy:
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 list-installed-components \ --core-device-thing-name "$TUTORIAL_THING_NAME" \ --query 'installedComponents[].componentName' --output textaws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 get-core-device \ --core-device-thing-name "$TUTORIAL_THING_NAME" --query status --output textThe first command must not list com.example.Pulse any more. The second must print HEALTHY. The MQTT test client stops receiving heartbeats.
Task 2: Destroy the stack
Section titled “Task 2: Destroy the stack”AWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" pnpm nx run @greengrass-tutorial/infra:destroy -- "greengrass-tutorial-infra-sandbox/**" --forceAWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" yarn nx run @greengrass-tutorial/infra:destroy -- "greengrass-tutorial-infra-sandbox/**" --forceAWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" npx nx run @greengrass-tutorial/infra:destroy -- "greengrass-tutorial-infra-sandbox/**" --forceAWS_PROFILE="$TUTORIAL_AWS_PROFILE" AWS_REGION="$TUTORIAL_AWS_REGION" bunx nx run @greengrass-tutorial/infra:destroy -- "greengrass-tutorial-infra-sandbox/**" --forceThe stack is gone, but three kinds of resources are retained on purpose, because component versions are immutable and outlive any single deployment:
- Both component versions of
com.example.Pulse,1.0.0and1.0.1. - The three deployment revisions to the thing group.
- The artifact bucket, with one archive per published version.
The CDK bootstrap stack CDKToolkit also remains. It is shared by every CDK application in the account and Region, so leave it unless you created it for this tutorial.
CDK leaves the Lambda log groups for component version resolution, the
custom-resource framework, and BucketDeployment after stack deletion; delete
them separately if you no longer need their logs.
Task 3: Delete the retained Greengrass resources
Section titled “Task 3: Delete the retained Greengrass resources”List the deployments to the thing group. Cancel the one still ACTIVE, then delete each of them:
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 list-deployments \ --target-arn "$TUTORIAL_THING_GROUP_ARN" --history-filter ALL \ --query 'deployments[].[deploymentId,deploymentStatus]' --output text
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 cancel-deployment \ --deployment-id <active-deployment-id>aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 delete-deployment \ --deployment-id <deployment-id>Delete every published version of the component:
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 list-component-versions \ --arn "arn:aws:greengrass:${TUTORIAL_AWS_REGION}:${TUTORIAL_ACCOUNT_ID}:components:com.example.Pulse" \ --query 'componentVersions[].arn' --output text
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" greengrassv2 delete-component \ --arn <component-version-arn>Find the artifact bucket through the ownership tag the construct applies, confirm that the list holds only this tutorial’s bucket, then delete its object versions and the bucket:
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" resourcegroupstaggingapi get-resources \ --tag-filters Key=greengrass-artifact-repository,Values=true \ --resource-type-filters s3:bucket \ --query 'ResourceTagMappingList[].ResourceARN' --output text
export TUTORIAL_BUCKET=<bucket-name>aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" s3api list-object-versions \ --bucket "$TUTORIAL_BUCKET" \ --query '{Objects: Versions[].{Key: Key, VersionId: VersionId}}' --output json \ > /tmp/greengrass-tutorial-versions.jsonaws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" s3api delete-objects \ --bucket "$TUTORIAL_BUCKET" --delete file:///tmp/greengrass-tutorial-versions.jsonaws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" s3api delete-bucket \ --bucket "$TUTORIAL_BUCKET"The bucket is versioned, so delete-objects must name each version. If list-object-versions also reports DeleteMarkers, repeat the delete with those entries before deleting the bucket.
Task 4: Remove the core device and its identity
Section titled “Task 4: Remove the core device and its identity”The script’s cleanup operation reads .greengrass-tutorial.env, checks that it belongs to the same account, Region and prefix, and then terminates the instance, detaches and deletes the certificate with every policy attached to it, deletes the core device record, the thing and the thing group, both IoT policies, the role alias, the token exchange role with its attachments, and the access policy.
./setup-greengrass-tutorial.sh cleanup \ --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" --prefix "$TUTORIAL_PREFIX"Each step prints deleted or absent. An object that is already gone is skipped. Any other error stops the run and keeps the state file, so you can fix the cause and rerun the same command.
Task 5: Remove the instance profile
Section titled “Task 5: Remove the instance profile”The instance profile was yours, so the script leaves it alone:
aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" iam remove-role-from-instance-profile \ --instance-profile-name "${TUTORIAL_PREFIX}-instance" --role-name "${TUTORIAL_PREFIX}-instance"aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" iam delete-instance-profile \ --instance-profile-name "${TUTORIAL_PREFIX}-instance"aws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" iam detach-role-policy \ --role-name "${TUTORIAL_PREFIX}-instance" \ --policy-arn arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCoreaws --profile "$TUTORIAL_AWS_PROFILE" --region "$TUTORIAL_AWS_REGION" iam delete-role \ --role-name "${TUTORIAL_PREFIX}-instance"rm -f .greengrass-tutorial.envWhat you learned
Section titled “What you learned”- A generated component publishes over local IPC by default. Cloud MQTT needs
publish_to_iot_core, aaws.greengrass.ipc.mqttproxyauthorization in the recipe, andiot:Publishin the device’s IoT policy. - The generator vends building blocks. Your CDK stack owns the artifact repository, the read grant, and the deployment, and
addComponentcarries the resolved version and the ordering edge. NEXT_PATCHallocates a version from content. A source change publishes the next patch version through the normaldeploy.- Removing a component is a deployment revision. Deleting infrastructure is a separate, later step that leaves retained versions, deployments and the bucket for you to delete.
For versioning and artifact retention, read the versioning and artifact storage sections of the component guide. The same guide lists the service limits to consider for larger deployments.