1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
If the deployment status is stuck in "In process", it is possible that there is a permissions issue causing the deployment to fail. Here are some steps you can take to troubleshoot the issue:
- Check the AWS CloudTrail logs to see if there are any errors or permission issues related to the S3 bucket or the service role. You can use CloudTrail to track the activities and events in your AWS account.
- Ensure that the S3 bucket is not encrypted with an unsupported encryption type.
- Verify that the AWS IoT Greengrass service role has the necessary permissions to access the S3 bucket. The role should have permission to read objects from the bucket and list the contents of the bucket.
respondido hace un año
Contenido relevante
OFICIAL DE AWSActualizada hace un año- OFICIAL DE AWSActualizada hace 4 meses
- OFICIAL DE AWSActualizada hace un año
Hi Nik. I think you need to improve this question and give us more information so we can help you. Are you deploying to a group or a single thing? Have you ever successfully deployed? Are you sure it says "in process"? I can't think of anything to do with Greengrass deployments that would say that, so maybe a screenshot would help.
Yeah Greg_B, I am doing deploying to a group, and done local deployments successfully. Now I am deploying the component using s3 bucket, yes I am sure it is ‘In process’ I have checked /greengrass/v2/deployments, that shows ongoing deployment.