In a spring cloud function usage, you don’t want your database connection to keep existing in the database. Once the spring cloud function finishes its process, is the following way to close the function appropriate? How do we validate if the spring cloud function inherently closes the connection even if we don’t do the implementation above? I saw the log
Tag: amazon-web-services
Where did the package software.amazon.awssdk.core.auth.policy go in the AWS Java SDK V2?
I found this piece of documentation for a way to build policies for accessing S3 Buckets (among other things) programmatically, but I can’t find seem to find it. (Based on the file path, I would’ve guessed that it would be in either auth or sdk-core). Has this been deprecated and moved somewhere else? There seems to be a similar (possibly
Missing data in response body
I have a web service(FastAPI) deployed on AWS EC2. In java client code, when I call the api, i got this error In postman, when I call this api, the response is returned but not enough like this image Seem the server (Fast API web service) do not return all data in response body. I already check this question, the
FileNotFoundException for properties file in aws-cdk
I’ve been trying to read a properties file and want it to be dynamic, I’m doing this in aws-cdk. My project layout: Main Project resources config.properties src main/java/com/myorg xxxstage.java The class xxxstage.java has following code: The line where I’m trying to print System.out.println(“inputStream is -> “+inputStream); is showing null, and hence the FileNotFoundException. It worth noting that this is working
Send cross AWS account message from Lambda to SQS
I want to send a message to SQS queue on another account (Ohio) from lambda in North Virginia account. How can I achieve this? Things I tried so far: Created a queue in Ohio and gave lambda role arn to the queue. Sent message from the lambda in North Virigina , got following error: “errorMessage”: “An error occurred (AWS.SimpleQueueService.NonExistentQueue) when
SelfMutate stage failing with CodePipeline
I’m trying to create a CI/CD using CDK pipeline with the import software.amazon.awscdk.pipelines.CodePipeline in Java. This pipeline creates another stack named xxxJavaxxxStack. The pipeline is able to connect to external github, which, when change is detected, triggers the pipeline. In the class xxxPipelinexxxApp.java I’m calling both the stacks xxxJavaxxxStack and xxxPipelinexxxStack. I have successfully been able to cdk synth both
How to Log/ View AWS Java SDK HTTP(S) Requests
I am developing a Spring Boot Application that uses HTTPS Only. I am using AWS services and the corresponding AWS Java SDK. How can I view the HTTP(S) request that the java sdk methods call on the backend of my application? I want to make sure when doing uploads to S3, etc, that everything is done over HTTPS only as
How to generate trace ID in AWS format
I would like to use opentelemetry-java-instrumentation with AWS OTEL collector and X-Ray. Unfortunately, AWS OTEL aws-xray exporter is not able to export generated traces to X-Ray because generated trace ID is invalid X-Ray trace ID: How to instrument my opentelemetry-java-instrumentation 1.7.0 to generate trace IDs in X-Ray format? I’ve tried to add aws extension + env variables: without success. Answer
Quarkus JWT Returning Unauthorized on deployment
I have a Quarkus project that expose some REST Endpoints. When working on dev mode or running from the local build docker container all work fine, those endpoints annotated with @RolesAllowed and @PermitAll work as supposed to be. But when I deploy to a AWS service with the following steps: Commit to Gitlab Run Gitlab CICD Send result with the
Limit number of requests(read, update, delete) if it exceeds the capacity of AWS Neptune Server?
I’m trying to implement some limits on the database requests made to the Neptune Server. The problem is: Multiple scheduled jobs that do analytics, logs, updates, deletions User activity, anything related to users: read, write, update, delete All of these request depending on when they occur can impact the performance of the database and the availability, so we get sudden