dkatzz

Now there are issues with initializing ebean: ``` Caused by: java.lang.NoClassDefFoundError: Could not initialize class io.ebean.DB at repository.SettingsGroupRepository.(SettingsGroupRepository.java:23) at repository.SettingsGroupRepository$$FastClassByGuice$$ccd7bc.GUICE$TRAMPOLINE() at repository.SettingsGroupRepository$$FastClassByGuice$$ccd7bc.apply() at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:82) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:300)...

Tried updating HTTPS -> HTTP ``` Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place +/- create...

Still getting error around ebean connection after vpce added - looking into other reasons why this may not be working ``` Caused by: java.lang.NoClassDefFoundError: Could not initialize class io.ebean.DB at...

Trying now with a new app prefix (`charlotte-vpc9`) and running from the [clt-test4](https://github.com/civiform/cloud-deploy-infra/compare/clt-test4?expand=1) branch, which changes the protocol back from HTTPS to HTTP (https://github.com/civiform/cloud-deploy-infra/commit/ecf3218de8ef49c330338fd6ca40ba3f42e735f6)

After the most recent deployment, we aren't seeing errors in the logs and the task is running and RDS has connections - I think we now just have to make...

Seeing unhealthy on the NLB. Tried navigating to NLb-Testing-fixing-IP-205c34e73dd3af17.elb.us-east-2.amazonaws.com and NLb-Testing-fixing-IP-205c34e73dd3af17.elb.us-east-2.amazonaws.com:443 with no luck

@wukimmy did a curl in an ec2 instance on the same VPC and got the same results as doing a curl to [exygy-civiform-lb-1702473953.us-east-1.elb.amazonaws.com](http://exygy-civiform-lb-1702473953.us-east-1.elb.amazonaws.com/). Based on this, I'll ensure the changes...

Latest issue we got was `ResourceInitializationError: unable to pull secrets or registry auth: unable to retrieve secret from asm: There is a connection issue between the task and AWS Secrets...

We were getting that secrets error a few times, but most recently we got past that and then got an error: `CannotPullContainerError: The task cannot pull [docker.io/civiform/civiform@sha256:d47cebfda1b31c70e78e1e10f959fb8c9aaba1f0ce1fe7a3c72ec9dc2b586f5d](http://docker.io/civiform/civiform@sha256:d47cebfda1b31c70e78e1e10f959fb8c9aaba1f0ce1fe7a3c72ec9dc2b586f5d) from the registry...

Now the error is: `ResourceInitializationError: failed to validate logger args: The task cannot find the Amazon CloudWatch log group defined in the task definition. There is a connection issue between...