ssm | Object-Relational Mapping library

aws session manager established communication with ec2 instance with SSM api (using websockets). The subnet your instance is in must have access to the internet, via NAT gateway for example (if it's in a private subnet) or you must create the following VPC endpoints:

• com.amazonaws.[region].ec2messages
• com.amazonaws.[region].ssmmessages

Name tag only:

You are missing the !Sub function for your {Environment} variable.

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.

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

   OR

2. 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

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

1. 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

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

you can try:

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.

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

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.