☁️ AWS Errors

49 error notes

AWS EventBridgeでのLambda「Permission Denied」エラーの修正方法

The service principal events.amazonaws.com does not have permission to invoke the resource: arn:aws:lambda:region:account-id:function:function-name

aws-eventbridgeaws-lambdaiam-policydevops

awsintermediate

スロットリングの停止：Kinesis の ProvisionedThroughputExceededException を解決する方法

ProvisionedThroughputExceededException: Rate exceeded for shard shardId-000000000000 in stream <stream-name> under account <account-id>.

awskinesisスロットリングデータストリーム

awsbeginner

解決策：AWS CDK における 'This stack uses assets' エラー

Error: This stack uses assets, so the toolkit stack must be deployed to the environment (Run "cdk bootstrap aws://<account-id>/<region>")

awscdkdevopscloudformation

awsintermediate

AccessDeniedExceptionの解決：User s3.amazonaws.com is Not Authorized to Perform lambda:InvokeFunction

An error occurred (AccessDeniedException) when calling the Invoke operation: User: s3.amazonaws.com is not authorized to perform: lambda:InvokeFunction on resource

awslambdas3iam-policy

awsintermediate

API Gatewayの修正: Execution failed due to configuration error: Invalid permissions on Lambda function

Execution failed due to configuration error: Invalid permissions on Lambda function

api-gatewaylambdaiamawsトラブルシューティング

awsintermediate

AWS KMS AccessDeniedExceptionの解決：IAM権限だけでは不十分な理由

AccessDeniedException: User: arn:aws:iam::123456789012:role/MyRole is not authorized to perform: kms:Decrypt on resource: arn:aws:kms:ap-northeast-1:123456789012:key/abc-123

awskmsiamセキュリティ

awsintermediate

CloudFrontの502エラーを解決する：SSLハンドシェイク失敗時の対処法

502 Bad Gateway: CloudFront was unable to establish a secure connection with the origin server.

cloudfront502-bad-gatewayssl-handshakeawsトラブルシューティング

awsintermediate

AWS AthenaのHIVE_CURSOR_ERROR: Row is not a valid JSON objectの解決方法

HIVE_CURSOR_ERROR: Row is not a valid JSON object

aws-athenas3jsonトラブルシューティング

awsintermediate

AWS Cognitoの「Refresh Token has expired」を修正し、不規則なログアウトを停止する

NotAuthorizedException: Refresh Token has expired

awscognitosecurityauthentication

awsintermediate

AWS Lambda デプロイ時の「Code uncompressed size is greater than max allowed size」エラーの修正

An error occurred (InvalidParameterValueException) when calling the UpdateFunctionCode operation: Code uncompressed size is greater than 262144000 bytes

aws-lambdadeploymentserverless

awsbeginner

AWS Step FunctionsのStates.HeartbeatTimeoutを修正する：タスクが60秒で失敗する理由

States.HeartbeatTimeout: State machine execution failed: Task timed out after 60 seconds

awsstep-functionslambdaserverless

awsintermediate

AWS VPC ピアリングの修正：「Request timeout」および「No route to host」の解決

Request timeout for icmp_seq — no route to host across VPC peering connection

awsvpcピアリングネットワーク

awsintermediate

EC2インスタンスの起動時に発生する「InsufficientInstanceCapacity」エラーの修正方法

An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation: We currently do not have sufficient capacity in the Availability Zone you requested.

awsec2キャパシティdevops

awsbeginner

AWS CLI の「RequestExpired」エラーをシステムクロックのずれから修正する

RequestExpired: Request has expired. (Service: AmazonS3; Status Code: 403, Error Code: RequestExpired)

aws-clitime-syncntpauthentication

awsintermediate

AWS EC2で「connect: No route to host」を修正する — Internet GatewayまたはNAT Gatewayの設定漏れ

connect: No route to host

awsvpcec2internet-gateway

awsintermediate

AWS RDSの「storage-full」状態からの復旧：即時の解決策と長期的な予防策

DB instance is in storage-full state. The instance may not be able to accept connections or perform writes.

awsrdsストレージデータベース

aws中級

AWS ECRのプッシュエラー「no basic auth credentials」の解決方法

Error response from daemon: no basic auth credentials

ecrdocker認証aws-cli

awsintermediate

EKSの「Unauthorized」エラーの修正：KubeconfigとIAMのトラブルシューティング

error: You must be logged in to the server (Unauthorized)

ekskubectlkubeconfigiam

awsintermediate

Boto3 ThrottlingExceptionの解決方法：AWS Pythonスクリプトでの「Rate exceeded」エラーへの対処

ThrottlingException: Rate exceeded

スロットリングboto3apiaws

awsintermediate

AWS CloudFront 403 ERROR（S3オリジン）を修正する — OACバケットポリシーが未設定の場合

403 ERROR: The request could not be satisfied. Request blocked. We can't connect to the server for this app or website at this time.

cloudfronts3oacbucket-policy

awsintermediate

AWS S3 403 Forbidden修正: バケットポリシーまたはACLによるHeadObject操作のブロック

An error occurred (403) when calling the HeadObject operation: Forbidden

awss3バケットポリシーacl

awsintermediate

AWS Elastic Beanstalk デプロイ失敗を修正: WSGIPathが存在しない & ヘルスチェックSevere

ERROR: Your WSGIPath refers to a file that does not exist. / Instance deployment failed. For details, see 'eb-engine.log'. / Environment health has transitioned from Ok to Severe

awselastic-beanstalkhealth-checkdeploy

awsintermediate

AWS ECS ResourceInitializationError: unable to retrieve ecr registry auth の修正方法

ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to retrieve ecr registry auth: service call has been retried 3 time(s): RequestError: send request failed

ecsecrdockeriam

awsintermediate

AWS CodeDeploy デプロイ失敗を修正: 指定場所のスクリプトが300秒以内に完了しなかった

Script at specified location: scripts/before_install.sh failed to complete in 300 seconds

codedeployデプロイライフサイクルフックタイムアウト

awsintermediate

SQSの重複メッセージとReceiptHandleIsInvalidExceptionの解決方法

com.amazonaws.services.sqs.model.ReceiptHandleIsInvalidException: The input receipt handle is not a valid receipt handle (Service: AmazonSQS; Status Code: 404)

aws-sqs可視性タイムアウト分散システムcloudwatch

awsintermediate

AWS Secrets Manager EndpointConnectionErrorの修正：エンドポイントURLに接続できない（VPCエンドポイント未設定）

EndpointConnectionError: Could not connect to the endpoint URL: https://secretsmanager.us-east-1.amazonaws.com / ConnectionError: HTTPSConnectionPool: Max retries exceeded

awssecrets-managervpcendpoint

awsintermediate

AWS CloudWatchでのPutLogEventsによるAccessDeniedExceptionの修正

An error occurred (AccessDeniedException) when calling the PutLogEvents operation: User: arn:aws:sts::123456789012:assumed-role/MyAppRole is not authorized to perform: logs:PutLogEvents on resource: arn:aws:logs:us-east-1:123456789012:log-group:/aws/lambda/my-func:*

awscloudwatchiamトラブルシューティング

awsbeginner

AWS API GatewayのCORSエラー：「No Access-Control-Allow-Origin」ヘッダーの修正方法

Access to fetch at 'https://xxxxxxxx.execute-api.ap-northeast-1.amazonaws.com/prod/resource' from origin 'https://example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

api-gatewaycorslambdaaws

awsbeginner

依存関係なしでデプロイした際のAWS Lambda「Runtime.ImportModuleError: No module named requests」を修正する

Runtime.ImportModuleError: Unable to import module 'lambda_function': No module named 'requests'

lambdapythonレイヤーデプロイ

awsbeginner

AWS SES MessageRejected: メールアドレスが未確認（サンドボックスモード）の修正方法

MessageRejected: Email address is not verified. The following identities failed the check in region US-EAST-1: recipient@example.com

sesメールサンドボックスsmtp

awsbeginner

AWS CLI エラー「InvalidClientTokenId」の修正：リクエストに含まれるセキュリティトークンが無効です

An error occurred (InvalidClientTokenId) when calling the GetCallerIdentity operation: The security token included in the request is invalid.

awscliiamアクセスキー

awsintermediate

AWS DynamoDBのProvisionedThroughputExceededExceptionを修正する

ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API.

dynamodbthroughputcapacityaws

awsintermediate