userguide | The oXygen XML userguide

Based on the comments.

The issue of being stuck at:

Install the CodeDeploy agent by following the steps in Install the CodeDeploy agent and using the Name=CodeDeployDemo instance tags.

was simply resolved by skipping this step. It is not needed, as OP uses UserData to setup CodeDeploy Agent.

I managed to solve my problem by not including project.sourceSets.main.runtimeClasspath and adding project.compileJava.classpath instead of project.sourceSets.main.compileClasspath.

Thus my build.gradle contained the following code instead of the first section of the question

The docs are pretty clear (emphasis added):

The Python types int, long, and float are not available for static typing and instead interpreted as C int, long, and float respectively, as statically typing variables with these Python types has zero advantages.

There are a number of concrete C APIs associated with stuff like list, tuple, etc., where static typing provides a meaningful benefit, allowing Cython to save time by compiling code that works with them on a more intrusive level (directly accessing the underlying array for list and tuple for example). For Python 3's int (and Python 2's long), that advantage largely doesn't exist; at best Cython could skip a tiny amount of type-checking work, in exchange for needing to reproduce all the rest of the code involved in the operations without those prechecks (Python 2's int is a C long under the hood, so you may as well declare it as such and benefit from using the raw C value directly). And it's quite a lot of code, given the complexities of working with arbitrary precision integers, and entirely unnecessary. If your values are small enough, you can use them as C types, but for anything larger, the cost of specializing for them would be greater than the gains.

In short: Declare it as nothing, or object if you want to be explicit. There's no benefit to be had from what you're trying to do, and you can't do it in any event.

aws cloudformation deregister-type --arn

https://docs.aws.amazon.com/cli/latest/reference/cloudformation/deregister-type.html

https://github.com/aws-cloudformation/cloudformation-cli/issues/401

This is what is tried and my error page also works.

• Created a bucket, changed permission to make it public.

• under permission -> block public access turn it off , and
  attached a policy bucket policy to grant public read access to your bucket. When you grant public read access, anyone on the internet can access your bucket.

with my user ubuntu access, I cannot create a folder without sudo

Unclear how you added your ubuntu user, but running mkdir -p /home/ubuntu as ec2-user wouldn't be correct.

You can fix the permissions with these commands, but you might want to re-visit the useradd command options

S3 Object Lambda is using the AWS Lambda service. AWS Lambda does only support the following runtimes "natively":

• Go
• .NET Core
• Ruby
• Java
• Python
• NodeJS

C++ is support through "custom" runtimes or through Docker containers. Usually, the AWS documentation only covers the "natively" supported runtimes and even then not all (as you noticed). Mostly they have examples for the most popular ones.

So what you need to look for are C++ Lambda examples, examples using the C++ AWS SDK and reference documentation.

Using the reference documentation and the Java/Python/NodeJS examples, it should be easy to write a C++ version.

For example:

1. Introducing the C++ Lambda Runtime (Blog Post)
2. C++ AWS SDK Page
3. API Reference for WriteGetObjectResponseRequest

JetBrains copied org.jetbrains.trove4j:trove4j:20160824 to Maven Central, which resolves this error. 🎉

If you use additional dependencies that have not yet migrated to Maven Central, you should reach out directly to them.

Update: "We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages." source

Update: Google is working on a fix for build tools 4.2 and maybe 4.1 as well. source

Update: You could try a dependency resolve rule.

The top-level dependency, com.android.tools.build:gradle, started using a newer version of trove4j in 7.0.0-alpha01. (7.0.0-alpha12 is currently the latest.)

Dependency chain: com.android.tools.build:gradle:7.0.0-alpha01 -> com.android.tools.build:builder:7.0.0-alpha01 -> com.android.tools:sdk-common:27.3.0-alpha01 -> org.jetbrains.intellij.deps:trove4j:1.0.20181211

However, this version is still in alpha and requires Android Studio 4.3+, which isn't even in Beta yet.

I have filed a bug with Google here: https://issuetracker.google.com/issues/179291081

ComputeEnvironment is Level 2 construct (high level) and as you pointed out it does not support Fargate. But if you go to Level 1 construct CfnComputeEnvironment you can do this.

The reason is that it directly maps to CloudFormation's AWS::Batch::ComputeEnvironment which you linked in your question.