Skip to content

Commit af1c8ed

Browse files
himsharma01JV0812
andauthored
AWSO - Added common troubleshooting error for (#5076)
* Added common troubleshooting error * Update docs/observability/aws/deploy-use-aws-observability/deploy-with-aws-cloudformation/index.md * Update docs/observability/aws/deploy-use-aws-observability/deploy-with-terraform.md --------- Co-authored-by: Jagadisha V <[email protected]>
1 parent fe53627 commit af1c8ed

File tree

2 files changed

+11
-0
lines changed

2 files changed

+11
-0
lines changed

docs/observability/aws/deploy-use-aws-observability/deploy-with-aws-cloudformation/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -237,6 +237,7 @@ Below are some common errors that can occur while using the CloudFormation templ
237237
| The API rate limit for this user has been exceeded. | This error indicates that AWS CloudFormation execution has exceeded the API rate limit set on the Sumo Logic side. It can occur if you install the AWS CloudFormation template in multiple regions or accounts using the same Access Key and Access ID. | - Re-deploy the deployment stack without updating the stack in the template. Re-running will detect the drift and create remaining resources. <br/> - If the throttling problem persists, try to break down the multi-region deployment into parts and use distinct access IDs and access keys for each part. |
238238
| S3 Bucket already exists. | The error can occur if:<br/>- An S3 bucket with the same name exists in S3, or<br/>- The S3 Bucket is not present in S3 but is referenced by some other AWS CloudFormation stack which created it. | - Remove the S3 bucket from S3 or select “No” in the AWS Cloudformation template for S3 bucket creation. <br/>- Remove the AWS CloudFormation Stack which references the S3 bucket. |
239239
| The S3 bucket you tried to delete is not empty. | The error can occur when deleting the stack with a non-empty S3 bucket. | Delete the S3 bucket manually if you do not need the bucket or its content in the future. |
240+
| Invalid IAM role OR AccessDenied | This error can occur when Sumo Logic access keys are disabled or do not have the required permissions. | - Refer to [Edit, deactivate, or delete access keys](/docs/manage/security/access-keys/#edit-deactivate-or-delete-access-keys) for access keys activation. <br/>- Refer to [Role capabilities](/docs/observability/aws/deploy-use-aws-observability/before-you-deploy/#prerequisites) for permissions related issues. |
240241

241242
### Rolling back the AWS Observability Solution
242243

docs/observability/aws/deploy-use-aws-observability/deploy-with-terraform.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1668,6 +1668,16 @@ The package is [sumologic-sdk](https://pypi.org/project/sumologic-sdk/) and inst
16681668
```sql
16691669
pip install sumologic-sdk
16701670
```
1671+
### Invalid IAM role OR AccessDenied
1672+
#### Error Message
1673+
1674+
```
1675+
Invalid IAM role OR AccessDenied
1676+
```
1677+
#### Solution
1678+
1679+
- Refer to [Edit, deactivate, or delete access keys](/docs/manage/security/access-keys/#edit-deactivate-or-delete-access-keys) for access keys activation.
1680+
- Refer to [Role capabilities](/docs/observability/aws/deploy-use-aws-observability/before-you-deploy/#prerequisites) for permissions related issues.
16711681
16721682
### Argument named *managed_apps* is not expected
16731683
#### Error Message

0 commit comments

Comments
 (0)