Deploying to new regions not working
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws
- Domain
- cloud, observability-sre
Research direction
Start with the AWS Integration and Lambda Forwarder CloudFormation guidance referenced in the issue, then compare the us-east-1 and us-west-2 Lambda and API Gateway configuration, including the ARN list. Done means logs from API Gateway in the second region arrive in Datadog, not only logs from a test invocation.
Written by the indexing model from the issue text.
Description
I'm trying to get the AWS Integration working and the initial setup works fine via CFN for the first region , us-east-1 in my case. I'm following https://docs.datadoghq.com/logs/guide/forwarder/?tab=cloudformation
“If you had previously enabled your AWS Integration using the following CloudFormation template from your AWS integration page in Datadog, your account may already be provisioned with a Datadog Lambda Forwarder function if you decided to include it. In that case, you will only need to install the Datadog Lambda in additional AWS regions in your account where you wish to export logs.” So I've manually created a Lambda in a different region, us-west-2, exactly the same as in the first region and added it to the list of ARNs in the AWS Integration config page, enabled API Gateway access/execution logs. but nothing is coming through to DD logs from the second region.
Test invoking the function from the console shows the function's log coming through ok:
- Dominant language
- Python
- Stars
- 351
- Forks
- 397
- Avg merge
- 6h 13m
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DataDog/datadog-serverless-functions
-
rds_enhanced_monitoring: unguarded message["numVCPUs"] KeyError when RDS omits the fieldPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
DataDog/datadog-serverless-functions#1219 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
DataDog/datadog-serverless-functions#1187 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
DataDog/datadog-serverless-functions#1148 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 22/100
DataDog/datadog-serverless-functions#1254 · 1 reaction ·
Maintainers usually reply within 1 day
-
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
DataDog/datadog-serverless-functions#1198 ·
Maintainers usually reply within 1 day
All issues in DataDog/datadog-serverless-functions
Similar issues
-
bump patch
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
autowarefoundation/autoware_carla_scenario#1321 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
QuantConnect/Documentation#2838 ·
Maintainers usually reply within 1 day
-
get_all_subclasses must deduplicate by class identityPossibly taken @Gambit-Checkmate claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 15 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
awslabs/route53-dynamic-dns-with-lambda#67 · 1 comment ·