kandi background

ssm | 手把手教你整合最优雅SSM框架：SpringMVC Spring MyBatis | Object-Relational Mapping library

by liyifeng1994 Java Version: Current License: MIT

by liyifeng1994 Java Version: Current License: MIT

Download this library from

kandi X-RAY | ssm Summary

ssm is a Java library typically used in Utilities, Object-Relational Mapping, Spring Boot, Spring applications. ssm has no vulnerabilities, it has build file available, it has a Permissive License and it has high support. However ssm has 1 bugs. You can download it from GitHub.

手把手教你整合最优雅SSM框架：SpringMVC + Spring + MyBatis

Support

Support

Quality

Quality

Security

Security

License

License

Reuse

Reuse

kandi-support Support

ssm has a highly active ecosystem.
It has 5616 star(s) with 2768 fork(s). There are 311 watchers for this library.
It had no major release in the last 12 months.
There are 24 open issues and 20 have been closed. On average issues are closed in 142 days. There are 16 open pull requests and 0 closed requests.
It has a negative sentiment in the developer community.
The latest version of ssm is current.

ssm Support

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

ssm Support

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

quality kandi Quality

ssm has 1 bugs (0 blocker, 0 critical, 1 major, 0 minor) and 21 code smells.

ssm Quality

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

ssm Quality

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

security Security

ssm has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
ssm code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.

ssm Security

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

ssm Security

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

license License

ssm is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

ssm License

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

ssm License

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

build Reuse

ssm releases are not available. You will need to build from source code and install.
Build file is available. You can build the component from source.
ssm saves you 343 person hours of effort in developing the same functionality from scratch.
It has 821 lines of code, 78 functions and 31 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.

ssm Reuse

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

ssm Reuse

Best in #Object-Relational Mapping

Average in #Object-Relational Mapping

Top functions reviewed by kandi - BETA

kandi has reviewed ssm and discovered the below as its top functions. This is intended to give you an instant insight into ssm implemented functionality, and help decide if they suit your requirements.

Performs transactional operation .
Find appoint .
Returns the book with the given id .
Returns a string representation of this result .
Set the number .
The gauge number .
Set the book .
Gets the book .
Sets the boolean value .
Gets the state .

ssm Key Features

手把手教你整合最优雅SSM框架：SpringMVC + Spring + MyBatis

ssm Examples and Code Snippets

See all related Code Snippets

How to show tag names with Ansible Dynamic Inventory for AWS?

Copy

Download

hostnames:
  - 'tag:Name'
compose:
  ansible_host: instance_id

hostnames:
  - name: 'instance-id'                                                         
    separator: '_'                                                              
    prefix: 'tag:Name' 
compose:
  ansible_host: instance_id

-----------------------

hostnames:
  - 'tag:Name'
compose:
  ansible_host: instance_id

hostnames:
  - name: 'instance-id'                                                         
    separator: '_'                                                              
    prefix: 'tag:Name' 
compose:
  ansible_host: instance_id

How to get the ssm parameter to a yaml file?

Copy

Download

BucketName: !Sub '{{resolve:ssm:/opentext/config/automated-ot-archival-data-migration/migration.bucket.name:1}}-${Environment}'

Search for a value in a column and return value from the same row but different column using Python and pandas

Copy

Download

result = df.loc[df.iloc[:,0].eq(4)]['specify the column name here']
result = df.loc[df.iloc[:,0].eq(4)].iloc[:,'specify the column index here']

How do I properly use the VpcId Property inside Security Group?

Copy

Download

ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       InstanceId: !Ref ContainerSG
       GroupDescription :  "ECS Containers Security Group"
       VpcId : !Sub '{{resolve:ssm:/ca/config/network/vpc_id:${ParamVersion}}}'
       GroupName :  !Sub   ${Env}-${ServiceName}-sg
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16

How do I properly format this YAML snippet?

Copy

Download

ContainerSecurityGroup:
  Type: AWS::EC2::SecurityGroup
  Properties:
    InstanceId: !Ref ContainerSG
    GroupDescription: "ECS Containers Security Group"
    VpcId: {{resolve:ssm:/ca/config/network/vpc_id:1}}
    GroupName: !Sub ${Env}-${ServiceName}-sg
    SecurityGroupIngress:
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.49.63.0/24
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.93.0.0/16
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.97.0.0/16
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.50.128.0/21
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.50.144.0/24
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 172.25.0.0/16

How do I properly use the Fn::Join object inside a CloudFormation Template?

Copy

Download

ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       InstanceId: !Ref ContainerSG
       GroupDescription :  "ECS Containers Security Group"
       VpcId : 
         !Join :
                -  ""
                - -  "{{resolve:ssm:"
                  -  /
                  -  "ca"
                  -  /
                  -  "config"
                  -  /
                  -  "network"
                  -  /
                  -  "vpc_id:"
                  -  !Sub   "${ParamVersion}"
                  -  "}}"
       GroupName :  !Sub   ${Env}-${ServiceName}-sg
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16

Building a multi-architecture Docker image, but Dockerfile requires different packages depending on architecture

Copy

Download

FROM ...
# Must be explicitly declared, and after FROM
ARG TARGETOS
# Then it can be used like a normal environment variable
RUN curl https://s3.amazonaws.com/ec2-downloads-$TARGETOS/...

ARG TARGETPLATFORM
RUN DEBARCH="$TARGETPLATFORM"; \
    if [ "$DEBARCH" = "arm" ]; then DEBARCH=arm64; fi; \
    curl .../debian-$DEBARCH/...

-----------------------

FROM ...
# Must be explicitly declared, and after FROM
ARG TARGETOS
# Then it can be used like a normal environment variable
RUN curl https://s3.amazonaws.com/ec2-downloads-$TARGETOS/...

ARG TARGETPLATFORM
RUN DEBARCH="$TARGETPLATFORM"; \
    if [ "$DEBARCH" = "arm" ]; then DEBARCH=arm64; fi; \
    curl .../debian-$DEBARCH/...

Stacked barchart with a single column in ggplot?

Copy

Download

library(tibble)
library(ggplot2)
sse <- c(2527.5, 716.3)
model <- c('ssm', 'ssr')
value <- c('sst')

bar <- tibble(sse, model, value)

ggplot(bar, aes(x = value, y = sse, fill = sse, label = sse)) +
  geom_bar(position = "stack", stat = "identity", width = .3) +
  geom_text(size = 3, position = position_stack(vjust = 0.5))

-----------------------

library(tidyverse)
sse <- c(3243.784, 2527.5, 716.3)
model <- c('sst', 'ssm', 'ssr')
foo <- tibble(sse, model)

ggplot(foo, aes(x = "", y = sse, fill = model)) +
  geom_col()

Implementing If function in UserData

Copy

Download

Type: 'AWS::EC2::Instance'
    Properties:
        <OMIT>
        BlockDeviceMappings:
        - DeviceName: /dev/sda1
            Ebs:
            VolumeSize: 50
        - !If [VolumeCreationCondition, {DeviceName: xvdh, Ebs:{VolumeSize: 150, VolumeType: st1}}, !Ref AWS::NoValue]
        UserData:
            Fn::Base64: !Sub |
            #!/bin/bash
            
            export need_to_init="${VolumeCreationCondition}"
            if [[ "${need_to_init}" != "" ]]
            then
                # "Run your command to init disk here"
            fi

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${CreateProdResources}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml

An error occurred (ValidationError) when calling the ValidateTemplate operation: Template format error: Unresolved resource dependencies [CreateProdResources] in the Resources block of the template

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${Production}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml
{
    "Parameters": [
        {
            "ParameterKey": "Production",
            "DefaultValue": "",
            "NoEcho": false
        }
    ]
}

-----------------------

Type: 'AWS::EC2::Instance'
    Properties:
        <OMIT>
        BlockDeviceMappings:
        - DeviceName: /dev/sda1
            Ebs:
            VolumeSize: 50
        - !If [VolumeCreationCondition, {DeviceName: xvdh, Ebs:{VolumeSize: 150, VolumeType: st1}}, !Ref AWS::NoValue]
        UserData:
            Fn::Base64: !Sub |
            #!/bin/bash
            
            export need_to_init="${VolumeCreationCondition}"
            if [[ "${need_to_init}" != "" ]]
            then
                # "Run your command to init disk here"
            fi

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${CreateProdResources}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml

An error occurred (ValidationError) when calling the ValidateTemplate operation: Template format error: Unresolved resource dependencies [CreateProdResources] in the Resources block of the template

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${Production}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml
{
    "Parameters": [
        {
            "ParameterKey": "Production",
            "DefaultValue": "",
            "NoEcho": false
        }
    ]
}

-----------------------

Type: 'AWS::EC2::Instance'
    Properties:
        <OMIT>
        BlockDeviceMappings:
        - DeviceName: /dev/sda1
            Ebs:
            VolumeSize: 50
        - !If [VolumeCreationCondition, {DeviceName: xvdh, Ebs:{VolumeSize: 150, VolumeType: st1}}, !Ref AWS::NoValue]
        UserData:
            Fn::Base64: !Sub |
            #!/bin/bash
            
            export need_to_init="${VolumeCreationCondition}"
            if [[ "${need_to_init}" != "" ]]
            then
                # "Run your command to init disk here"
            fi

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${CreateProdResources}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml

An error occurred (ValidationError) when calling the ValidateTemplate operation: Template format error: Unresolved resource dependencies [CreateProdResources] in the Resources block of the template

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${Production}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml
{
    "Parameters": [
        {
            "ParameterKey": "Production",
            "DefaultValue": "",
            "NoEcho": false
        }
    ]
}

-----------------------

Type: 'AWS::EC2::Instance'
    Properties:
        <OMIT>
        BlockDeviceMappings:
        - DeviceName: /dev/sda1
            Ebs:
            VolumeSize: 50
        - !If [VolumeCreationCondition, {DeviceName: xvdh, Ebs:{VolumeSize: 150, VolumeType: st1}}, !Ref AWS::NoValue]
        UserData:
            Fn::Base64: !Sub |
            #!/bin/bash
            
            export need_to_init="${VolumeCreationCondition}"
            if [[ "${need_to_init}" != "" ]]
            then
                # "Run your command to init disk here"
            fi

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${CreateProdResources}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml

An error occurred (ValidationError) when calling the ValidateTemplate operation: Template format error: Unresolved resource dependencies [CreateProdResources] in the Resources block of the template

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${Production}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml
{
    "Parameters": [
        {
            "ParameterKey": "Production",
            "DefaultValue": "",
            "NoEcho": false
        }
    ]
}

-----------------------

Type: 'AWS::EC2::Instance'
    Properties:
        <OMIT>
        BlockDeviceMappings:
        - DeviceName: /dev/sda1
            Ebs:
            VolumeSize: 50
        - !If [VolumeCreationCondition, {DeviceName: xvdh, Ebs:{VolumeSize: 150, VolumeType: st1}}, !Ref AWS::NoValue]
        UserData:
            Fn::Base64: !Sub |
            #!/bin/bash
            
            export need_to_init="${VolumeCreationCondition}"
            if [[ "${need_to_init}" != "" ]]
            then
                # "Run your command to init disk here"
            fi

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${CreateProdResources}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml

An error occurred (ValidationError) when calling the ValidateTemplate operation: Template format error: Unresolved resource dependencies [CreateProdResources] in the Resources block of the template

Parameters:
  Production:
    Type: String
    Default: ''

Conditions:
  CreateProdResources: !Not [!Equals [!Ref Production, '']]

Resources:
  CloudNetPingTargetInstance:
    Type: AWS::EC2::Instance
    Properties:
      InstanceType: t2.micro
      ImageId: amzn2-ami-hvm-2.0.20210427.0-x86_64-gp2
      NetworkInterfaces:
        - DeviceIndex: '0'
          DeleteOnTermination: true
          SubnetId: subnet-11111c86
      UserData:
        Fn::Base64: !Sub |
          #!/bin/bash

          export PRODUCTION="${Production}"
          if [[ "$PRODUCTION" != "" ]]
          then
            echo "##### IS PRODUCTION"
          fi

$ aws cloudformation validate-template --template-body file://test.yaml
{
    "Parameters": [
        {
            "ParameterKey": "Production",
            "DefaultValue": "",
            "NoEcho": false
        }
    ]
}

Python/AWS Parameter Store: updated SSM values

Copy

Download

import boto3
import json

client = boto3.client('ssm')

def lambda_handler(event, context):
    old_parameter = client.get_parameter(Name='/config/db')
    print(old_parameter)
    parameter_value = json.loads(old_parameter['Parameter']['Value'])
    parameter_value['my_version'] = '1.0'
    client.put_parameter(Name='/config/db', Overwrite=True, Value=json.dumps(parameter_value))

See all related Code Snippets

Community Discussions

Trending Discussions on ssm

SSM Send Command Failed,Is it possible to run ssm command from one aws account to another
AWS SSM session manager not showing instances
How to show tag names with Ansible Dynamic Inventory for AWS?
How to get the ssm parameter to a yaml file?
How to free up space on AWS ec2 Ubuntu instance running nginx and jenkins?
Not enough space for drivers in AWS g4dn.4xlarge instance
Search for a value in a column and return value from the same row but different column using Python and pandas
How do I attribute values to parameters created within stacks in a template?
How do I properly use the VpcId Property inside Security Group?
How do I properly format this YAML snippet?

Trending Discussions on ssm

QUESTION

SSM Send Command Failed,Is it possible to run ssm command from one aws account to another

Asked 2021-Jun-15 at 10:06

I have the Jenkins node in Account A that builds the angular application For Deploying the dist folder I need to copy files from s3 to the angular instance. But the angular Instance is in Account B

Script:

aws --region us-west-2 ssm send-command --instance-ids i-xxxxxx --document-name AWS-RunShellScript --comment 'Deployment from Pipeline xxx-release-pipeline' --cloud-watch-output-config 'CloudWatchOutputEnabled=true,CloudWatchLogGroupName=SSMDocumentRunLogGroup' --parameters '{"commands":["aws --region us-west-2 s3 cp s3://xxxx/dist/*.zip /var/www/demo.com/html", "unzip -q *.zip"]}' --output text --query Command.CommandId

So when I run ssm send-command from node(in Account A) it shows Invalid Instance Id.

An error occurred (InvalidInstanceId) when calling the SendCommand operation

Jenkins node -> Account A Angular Instance(with ssm agent) -> Account B

In the pipeline for deploy stage I need to copy files from s3 to instance in Account B Is there a way to implement this use case in a better way with or without ssm?

ANSWER

Answered 2021-Jun-15 at 09:56

I don't think you can directly run run-command accross account. But you could run in through AWS Systems Manager Automation. In your automation document you can use aws:runCommand.

This is possible because SSM Automation supports cross-account and cross-region deployments.

Source https://stackoverflow.com/questions/67983886

QUESTION

How to free up space on AWS ec2 Ubuntu instance running nginx and jenkins?

Asked 2021-May-27 at 08:52

I have an Ubuntu ec2 instance running nginx and Jenkins. There is no more space available to do updates, and every command I try to free up space doesn't work. Furthermore, when trying to reach Jenkins I'm getting 502 Bad Gateway.

When I run sudo apt-get update I get a long list of errors but the main one that stood out was E: Write error - write (28: No space left on device)

I have no idea why there is no more space, or what caused it but df -h gives the following output:

Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           394M  732K  393M   1% /run
/dev/xvda1       15G   15G     0 100% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
/dev/loop1       56M   56M     0 100% /snap/core18/1988
/dev/loop3       34M   34M     0 100% /snap/amazon-ssm-agent/3552
/dev/loop0      100M  100M     0 100% /snap/core/10958
/dev/loop2       56M   56M     0 100% /snap/core18/1997
/dev/loop4      100M  100M     0 100% /snap/core/10908
/dev/loop5       33M   33M     0 100% /snap/amazon-ssm-agent/2996
tmpfs           394M     0  394M   0% /run/user/1000

I tried to free up the space by running sudo apt-get autoremove and it gave me E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.

I ran sudo dpkg --configure -a and got pkg: error: failed to write status database record about 'libexpat1-dev:amd64' to '/var/lib/dpkg/status': No space left on device

Lastly, I ran sudo apt-get clean; sudo apt-get autoclean and it gave me the following errors:

Reading package lists... Error!
E: Write error - write (28: No space left on device)
E: IO Error saving source cache
E: The package lists or status file could not be parsed or opened.

Any help to free up space and get the server running again will be greatly appreciated.

ANSWER

Answered 2021-May-27 at 08:52

For a server (If you're not testing Jenkins & Nginx) running Jenkins & Nginx you must manage the disk partition in a better way. Following are the few possible ways to fix your issue.

Expand the existing EC2 root EBS volume size from 15 GB to a higher value from the AWS EBS console.

OR
Find out the files consuming the high disk space and remove them if not required. Most probably log files consuming the disk spaces. You can execute the following commands to find out the locations that occupied with more space.

cd /

du -sch * | grep G

OR
Add extra EBS volume to your instance and mount it to Jenkins home directory, or to the location where more disk space is using.

Source https://stackoverflow.com/questions/67714393

QUESTION

Not enough space for drivers in AWS g4dn.4xlarge instance

Asked 2021-May-26 at 10:38

Premise: I'm a bit of a newbie in using Amazon AWS or Linux partitioning in general.

So, I need to train a Tensorflow 2.0 Deep Learning model on a g4dn.4xlarge instance (the one with a signle Nvidia T4 GPU). The setup went smoothly and the machine was correctly initialized. As I see in the configuration of my machine I have:

8GB root folder;
200GB of storage (that I was able to mount on startup using this guide https://devopscube.com/mount-ebs-volume-ec2-instance/#:~:text=Step%201%3A%20Head%20over%20to,text%20box%20as%20shown%20below)

And here is the result of lsblk:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0         7:0    0  33.3M  1 loop /snap/amazon-ssm-agent/3552
loop1         7:1    0  32.3M  1 loop /snap/snapd/11588
loop2         7:2    0  70.4M  1 loop /snap/lxd/19647
loop3         7:3    0  55.5M  1 loop /snap/core18/1997
loop4         7:4    0  55.4M  1 loop /snap/core18/2066
nvme1n1     259:0    0 209.6G  0 disk /newvolume
nvme0n1     259:1    0     8G  0 disk
└─nvme0n1p1 259:2    0     8G  0 part /

The problem: I was following this guide https://medium.com/quantrium-tech/installing-tensorflow-2-with-nvidia-gpu-on-google-cloud-instance-a8dde3746f23 to install the necessary drivers to be able to use the GPU with tensorflow but I ran into a "no space left on the device" problem as all the packages required are more than what I have available as space (8 GB).

What I've Tried: I tried installing the drivers on the disk I've mounted (/newvolume) but they go to the root anyway (probably that was stupidly done). I've tried merging the two disks with some sketchy guide but with no success or progress.

The Question: Is there any way to merge the two partitions to have 200GB+ of root so I can install the necessary drivers without having space problems? Or are there any other workarounds?

My goal is not expanding the root folder through the configuration of another instance with more space but to make use of the 200GB disk (nvme1n1).

Many thanks!

ANSWER

Answered 2021-May-26 at 10:38

Expand the existing EC2 root EBS volume size from 8 GB to 200 GB from the AWS EBS console. Then you can detach and delete the EBS volume mounted on /newvolume

OR

Terminate this instance and launch a new EC2. While launching the instance, increase the size of root volume from 8 GB to 200 GB.

Source https://stackoverflow.com/questions/67701269

QUESTION

How do I attribute values to parameters created within stacks in a template?

Asked 2021-May-21 at 19:26

I'm getting the following error when deploying my CloudFormation template.

✖ Failed to create the stack.
An error occurred (ValidationError) when calling the CreateStack operation: Parameters: [ClusterArn, TaskRoleArn, Env, Subnets, ExecRoleArn, ClusterLogGroup, ContainerSG] must have values

I don't know how to attribute values to the parameters specified because they are being created within the stack. For instance, the ContainerSG and LogGroup :

Parameters:

  ContainerSG:
    Description: The container security group
    Type: String

  ClusterLogGroup:
    Description: The cluster log group
    Type: String

Resources

  LogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Join [ '/', ['/aws', 'ecs', !Ref Env]]

  ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       GroupDescription :  "ECS Containers Security Group"
       VpcId :  '{{resolve:ssm:/ca/config/network/vpc_id:1}}'
       GroupName: security-group-cmr
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16

The bottom-line question is, how do I attribute values to parameters that are being created along with stacks inside a CloudFormation Template?

Would appreciate someone's help on this. Thank you.

EDIT : This is the complete cloudformation file, some of the parameters (memory, buildnumber, etc) are specified within the pipeline so that's the reason they don't need any values attributed to them within the template :

Description: "Generic Research Template for Application ECS Cluster with an ECS Service"
Parameters:
  Env:
    Description: the runtime environment
    Type: String
    AllowedValues:
      - dev
      - uat
      - prod
  ServiceName:
    Description: The service name
    Type: String
  BuildNumber:
    Description: The bitbucket build number
    Type: String
  AppCode:
    Description: The application's app code
    Type: String
  Subnets:
    Description: Choose which db subnets for the instance
    Type: List<AWS::EC2::Subnet::Id>
  ContainerPort:
    Description: The container port
    Type: String
    Default: 8080
  DesiredCount:
    Description: The number of desired tasks for this service
    Type: Number
    Default: 1
  ClusterLogGroup:
    Description: The cluster log group
    Type: String
  Cpu:
    Description: allocated cpu credits
    Type: Number
    Default: 1024
  Memory:
    Description: hard cap for memory
    Type: String
    Default: 2048
  ClusterArn:
    Description: The ECS Cluster ARN
    Type: String
  ExecRoleArn:
    Description: The ARN of the cluster execution role
    Type: String
  TaskRoleArn:
    Description: The ARN of the cluster task role
    Type: String
  ContainerSG:
    Description: The container security group
    Type: String
  ExcludeTaskDef:
    Description: Flag indiciating that the task definition resource should not be created as part of this stack
    Type: Number
    AllowedValues:
      - 0
      - 1
    Default: 0
Conditions:
  IncludeTaskDef: !Equals [!Ref ExcludeTaskDef, 0]
Resources:  
  ECSService:
    Type: AWS::ECS::Service
    Properties:
      ServiceName: !Sub ${Env}-${AppCode}-${ServiceName}-service
      Cluster: !Ref ClusterArn
      TaskDefinition: !Ref TaskDefinition
      DeploymentConfiguration:
        MinimumHealthyPercent: 0
        MaximumPercent: 100
      DesiredCount: !Ref DesiredCount
      LaunchType: FARGATE
      NetworkConfiguration:
        AwsvpcConfiguration:
          AssignPublicIp: DISABLED
          Subnets:
            - !Select [0, !Ref Subnets ]
            - !Select [1, !Ref Subnets ]
          SecurityGroups:
            - !Ref ContainerSG
  TaskDefinition:
    Type: AWS::ECS::TaskDefinition
    Condition: IncludeTaskDef
    Properties:
      Family: !Sub ${Env}-${AppCode}-${ServiceName}
      NetworkMode: awsvpc
      RequiresCompatibilities:
        - FARGATE
      Cpu: !Ref Cpu
      Memory: !Ref Memory
      ExecutionRoleArn: !Ref ExecRoleArn
      TaskRoleArn: !Ref TaskRoleArn
      ContainerDefinitions:
        - Name: !Sub ${Env}-${AppCode}-${ServiceName}
          Image: !Sub 558043318296.dkr.ecr.us-east-1.amazonaws.com/com.cambridge.gir/${AppCode}-${ServiceName}:${BuildNumber}
          Essential: True
          PortMappings:
            - ContainerPort: !Ref ContainerPort
          LogConfiguration:
            LogDriver: awslogs
            Options:
              awslogs-group: !Ref ClusterLogGroup
              awslogs-region: us-east-1
              awslogs-stream-prefix: !Ref ServiceName
          Environment:
            - Name: Environment
              Value: !Ref Env
            - Name: Timezone
              Value: "-Duser.timezone=America/New_York"
  ClusterKmsKey:
    Type: AWS::KMS::Key
    Properties:
      Description: "Encrypts secrets for apps in the cluster"
      KeyPolicy:
        Version: '2012-10-17'
        Id: !Sub ${Env}-${AppCode}-kms-key
        Statement:
          - Sid: 'Enable IAM User Permission'
            Effect: 'Allow'
            Principal:
              AWS: !Sub 'arn:aws:iam::${AWS::AccountId}:root'
            Action:
              - kms:*
            Resource: '*'
          - Sid: 'Allow ECS Tasks to use the key'
            Effect: 'Allow'
            Principal:
              Service: 'ecs-tasks.amazonaws.com'
            Action:
              - 'kms:GenerateDataKey'
              - 'kms:Encrypt'
              - 'kms:Decrypt'
            Resource: '*'
          - Sid: 'Allow SNS to use the key'
            Effect: 'Allow'
            Principal:
              Service: 'sns.amazonaws.com'
            Action:
              - 'kms:GenerateDataKey'
              - 'kms:Encrypt'
              - 'kms:Decrypt'
            Resource: '*'
          - Sid: 'Allow SQS to use the key'
            Effect: 'Allow'
            Principal:
              Service: 'sqs.amazonaws.com'
            Action:
              - 'kms:GenerateDataKey'
              - 'kms:Encrypt'
              - 'kms:Decrypt'
            Resource: '*'
          - Sid: 'Allow ES to use the key'
            Effect: 'Allow'
            Principal:
              Service: 'es.amazonaws.com'
            Action:
              - 'kms:GenerateDataKey'
              - 'kms:Encrypt'
              - 'kms:Decrypt'
            Resource: '*'
  EcsCluster:
    Type: AWS::ECS::Cluster
    Properties:
      ClusterName: !Sub ${Env}-${AppCode}-ecs-cluster
  LogGroup:
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupName: !Join [ '/', ['/aws', 'ecs', !Ref Env, !Ref AppCode]]
  ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       GroupDescription :  "ECS Containers Security Group"
       VpcId :  '{{resolve:ssm:/ca/config/network/vpc_id:1}}'
       GroupName :  !Sub   ${Env}-${ServiceName}-sg
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16
  ClusterExecutionRole:
    Type: AWS::IAM::Role
    Properties:
      RoleName: !Sub ${Env}-${AppCode}-execution-role
      AssumeRolePolicyDocument:
        Statement:
          - Effect: Allow
            Principal:
              Service: ecs-tasks.amazonaws.com
            Action: 'sts:AssumeRole'
      ManagedPolicyArns:
        - 'arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy'
        - 'arn:aws:iam::aws:policy/AmazonSSMFullAccess'
        - 'arn:aws:iam::aws:policy/SecretsManagerReadWrite'
      Policies:
        - PolicyName: !Sub ${Env}-${AppCode}-execution-role-policy
          PolicyDocument:
            Version: "2012-10-17"
            Statement:
              - Sid: AllowSecretsAccessForContainers
                Effect: Allow
                Action:
                  - 'kms:Decrypt'
                  - 'ssm:GetParameters'
                Resource:
                  - !Sub "arn:aws:ssm:*:*:parameter/${Env}/${AppCode}/*"
                  - !GetAtt ClusterKmsKey.Arn
              - Sid: AllowECRPull
                Effect: Allow
                Action:
                  - "ecr:GetAuthorizationToken"
                  - "ecr:BatchCheckLayerAvailability"
                  - "ecr:GetDownloadUrlForLayer"
                  - "ecr:BatchGetImage"
                Resource:
                  - "*"
  FargateTaskRole:
    Type: AWS::IAM::Role
    Properties:
      RoleName: !Sub ${Env}-${AppCode}-fargate-task-role
      AssumeRolePolicyDocument:
        Statement:
          - Effect: Allow
            Principal:
              Service: ecs-tasks.amazonaws.com
            Action: 'sts:AssumeRole'

ANSWER

Answered 2021-May-21 at 19:26

If it is all in one file, you don't need any parameters.

You can always go to the return section of all the resources in the CloudFormation documentation. In this case we can see that a LogGroup returns it's name when you use the Ref function. Sometimes you can use the Ref function, sometimes you need to use the Fn:GetAtt function if you want to get some more exotic properties of resources.

This cheat sheet is also really helpful to see when to use Ref or when to use GetAtt.

In your case you can for example just use !Ref LogGroup to get the name of your log group or !Ref ContainerSecurityGroup to get the name of the security group.

Source https://stackoverflow.com/questions/67642582

QUESTION

How do I properly use the VpcId Property inside Security Group?

Asked 2021-May-20 at 20:54

I have a cloudformation snippet that looks roughly like this :

ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       InstanceId: !Ref ContainerSG
       GroupDescription :  "ECS Containers Security Group"
       VpcId : 
         !Join :
                -  ""
                - -  "{{resolve:ssm:"
                  -  /
                  -  "ca"
                  -  /
                  -  "config"
                  -  /
                  -  "network"
                  -  /
                  -  "vpc_id:"
                  -  !Sub   "${ParamVersion}"
                  -  "}}"
       GroupName :  !Sub   ${Env}-${ServiceName}-sg
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16

But when I try to run this, I get the following error:

Template contains errors.: Template format error: [/Resources/ContainerSecurityGroup/Type/VpcId] map keys must be strings; received a map instead

Can anybody help me to resolve this one? Is there perhaps a workaround I have not considered? Would appreciate your help on this, thank you.

ANSWER

Answered 2021-May-20 at 20:54

Why are you even joining? Can't you just use:

ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       InstanceId: !Ref ContainerSG
       GroupDescription :  "ECS Containers Security Group"
       VpcId : !Sub '{{resolve:ssm:/ca/config/network/vpc_id:${ParamVersion}}}'
       GroupName :  !Sub   ${Env}-${ServiceName}-sg
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16

Source https://stackoverflow.com/questions/67609642

QUESTION

How do I properly format this YAML snippet?

Asked 2021-May-20 at 19:40

I have a cloudformation snippet that looks roughly like this :

  ContainerSecurityGroup:
    Type :  AWS::EC2::SecurityGroup
    Properties : 
       InstanceId: !Ref ContainerSG
       GroupDescription :  "ECS Containers Security Group"
       VpcId :  !Sub {{resolve:ssm:/ca/config/network/vpc_id:${ParamVersion}}}
       GroupName :  !Sub   ${Env}-${ServiceName}-sg
       SecurityGroupIngress :
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.49.63.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.93.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.97.0.0/16
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.128.0/21
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  10.50.144.0/24
        -  IpProtocol :  tcp
           FromPort :  8080
           ToPort :  8080
           CidrIp :  172.25.0.0/16

What am I doing wrong here? I get the following error:

Template contains errors.: Template format error: YAML not well-formed.

Can someone help me to resolve this one? Is there perhaps a workaround I have not considered?

ANSWER

Answered 2021-May-20 at 19:40

YAML requires consistent spacing for indention. Make sure you are use the same amount of spacing for each indent. The example you posted indents 2 spaces for some, 3 spaces for others. If you edit a YAML file in a modern IDE (i.e. VSCode), it should format and do the indention for you so you don't have the think about it.

Also, the VpcId line is not correct, the {{resolve:}} mechanism can't be combined with !Sub to parameterize the value presently, this has to be hardcoded. You may want to use the SSM Parameter types instead or just hardcode this.

ContainerSecurityGroup:
  Type: AWS::EC2::SecurityGroup
  Properties:
    InstanceId: !Ref ContainerSG
    GroupDescription: "ECS Containers Security Group"
    VpcId: {{resolve:ssm:/ca/config/network/vpc_id:1}}
    GroupName: !Sub ${Env}-${ServiceName}-sg
    SecurityGroupIngress:
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.49.63.0/24
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.93.0.0/16
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.97.0.0/16
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.50.128.0/21
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 10.50.144.0/24
      - IpProtocol: tcp
        FromPort: 8080
        ToPort: 8080
        CidrIp: 172.25.0.0/16

Source https://stackoverflow.com/questions/67626616

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ssm

You can download it from GitHub.
You can use ssm like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the ssm component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

DOWNLOAD this Library from

Reuse Trending Solutions

14 best Python Telegram Bot

21 best C# Game Development

Build AI Fake News Detector

Build Text Summarizer in Python

Getting Started with Web3

24 best Python Blockchain

26 best Python Face Recognition

Build Ludo Game in Python

Build Location Based AR App

Build AI Study Assistant Bot

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items

Find more libraries

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Save this library and start creating your kit

Explore Related Topics

Object-Relational Mapping

Share this Page

Reuse Utilities Kits

Build Text Summarizer in Python

Build AI Study Assistant Bot

Tetris Game

Open Source Intelligence

Ai Hulks App Kit

See all related Kits

Consider Popular Object-Relational Mapping Libraries

django

by django

mall

by macrozheng

typeorm

by typeorm

spring-boot-demo

by xkcoding

mybatis-3

by mybatis

See all Object-Relational Mapping Libraries

Try Top Libraries by liyifeng1994

seckill

by liyifeng1994 Java

webmagic-csdnblog

by liyifeng1994 Java

xfshxzs

by liyifeng1994 Java

PushDemo

by liyifeng1994 Java

bnuzitc

by liyifeng1994 HTML

See all Libraries by this author

Compare Object-Relational Mapping Libraries with Highest Support

django

by django

mongoengine

by MongoEngine

mybatis-3

by mybatis

querydsl

by querydsl

spring

by mybatis

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Highest Quality

spr-data

by Fruzenshtein

spring-data-demos

by gordonad

template-java-spring-hibernate

by heroku

osgi-starter

by seijoed

spring

by cr2121

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Highest Security

swing-spring-jpa-crud

by yaw

javafx-jpa-crud

by yaw

spring-data-demos

by gordonad

spring

by cr2121

spr-data

by Fruzenshtein

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Permissive License

ormlite-jdbc

by j256

weixin-mp-java

by grossopa

musicbrainz-data

by lastfm

SansOrm

by brettwooldridge

jpa-query-by-example

by jaxio

See all Object-Relational Mapping Libraries

Compare Object-Relational Mapping Libraries with Highest Reuse

phoenix-hibernate-dialect

by jruesga

springlets

by DISID

holon-datastore-jdbc

by holon-platform

karellen-kombu-ext

by karellen

autofactoryboy

by nickgashkov

See all Object-Relational Mapping Libraries

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items

Find more libraries

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Save this library and start creating your kit

© 2022 Open Weaver Inc.

© 2022 Open Weaver Inc.