AWS Elastic Search Upgrade 2.3 to 5.5 illegal_argument_exception - amazon-web-services

We recently upgraded from aws Elasticsearch service 2.3 to 5.5 and in the 5.5 version the pre-signed urls are not working (working for 2.3).
illegal_argument_exception is raised with the following message:
unrecognized parameters: [X-Amz-Algorithm], [X-Amz-Credential], [X-Amz-Date], [X-Amz-Expires], [X-Amz-Signature], [X-Amz-SignedHeaders].

Related

How to upgrade SQLite in AWS MWAA Airflow?

I am using yfinance library to get some values like market_cap.
Code:-
import yfinance as yf
com = yf.Ticker('1140.SR')
print(com.fast_info['market_cap'])
I've updated the library to latest version i.e. 0.2.9 locally and on AWS MWAA Apache Airflow.
Locally, I'm able to run the code.
But on Amazon MWAA Airflow, I'm getting an error 'near "without": syntax error'.
Based on my searching, I believe, that the issue is because of a lower version of SQLite. One person was able to resolve the issue by upgrading SQLite version - https://github.com/ranaroussi/yfinance/issues/1372
Locally, here is the configuration:-
Python version - 3.10.8
yfinance - 0.2.9
SQLite3 - 3.37.2
and my Amazon MWAA Airflow configuration is:-
Python version - 3.10.8 (main, Jan 17 2023, 22:57:31) [GCC 7.3.1 20180712 (Red Hat 7.3.1-15)]
yfinance - 0.2.9
SQLite3 - 3.7.17
SQLite is not a python library version, but it’s the a system-level application that needs to be upgraded manually.
I'm able to do locally, but how do I upgrade SQLite to >3.34.x version on Amazon MWAA?
Can anyone help me?
Tried upgrading SQLITE version with requirements file. It didn't work.
apache-airflow-providers-sqlite==3.3.1

403 error when importing a new JSS app to Sitecore 10.2

When trying to import a newly generated JSS application into Sitecore, the jss deploy app --includeContent --includeDictionary returns the following error:
Unexpected response from import service:
Status message: Forbidden
Status: 403
Version info:
Sitecore version 10.02
JSS Version: 19.0
For jss setup, I specify the Sitecore instance as NOT accessible via a network share.
It may be issue due to JSS version, i also had jss deploy issue, details are: https://rinkusitecore.wordpress.com/2021/03/20/app-deploy-issueforeach-import-for-sitecore-jss-using-sitecore-9-3/
It seems for sitecore 10.0, need jss version 15, checkout: https://dev.sitecore.net/Downloads/Sitecore_JavaScript_Services.aspx
So try to create your app based on jss version 10 like jss create react -b release/15.0.0
But In your title you mentioned sitecore 10.2, in that case JSS version is correct (https://dev.sitecore.net/Downloads/~/link.aspx?_id=B5D60A30ADD1495C9B011E793AF6884F&_z=z)
So confirm it first.

ElasticBeanstalk and CodegeIgniter

I'm trying to get a code igniter (PHP) site working on Elasticbeanstalk using apache. When i run it php 5.6(EB stack), everything works fine, but when using Php 7.4, i get the following error:
/var/www/html/.htaccess: <IfModule not allowed here
I also tried using .ebextensions to override the Allowoverrride All but using that php code is displayed in browser rather executing it.
My EB Stack is :- PHP 7.4 running on 64bit Amazon Linux 2/3.1.0
Note: When i am running the same code in php 5.6 in elastic beanstalk it's working fine
7.4 will definitely be supported, and I would assume on release. No release date specified - but not long!

Django 2.2 AWS Elastic Beanstalk Deployment not working

I read some reviews in AWS forums they said some people Django 2.2 and python 3.6 possible to AWS deployment but in this mean while most of the people said 2.1 only work not 2.2. so i want some clarification about which Django version should i use to AWS. i already test 2.2 it is not working state but 2.1 fine.
The aws documentation:
Deploying a Django application to Elastic Beanstalk
Indicates Django 2.1.1. This could explain why you found tat 2.2 is not working, but 2.1 is.

Getting Exception on using AWS S3 sdk with openstack to get all buckets/containers

I am getting Exception on using AWS S3 SDK with OpenStack to get all buckets/containers.
Expected Behavior
I should be able get list of buckets from OpenStack using aws s3 sdk using .net Core as it is working fine in dotnet 4.72 framework.
Current Behavior
I'm getting exception while fetching list of buckets from OpenStack using S3 sdk.
AWS s3 sdk is working fine with .net 4.72 frameworks
Possible Solution
Is there any incompatibility between dotnet core and openstack ?
Steps to Reproduce (for bugs)
Create a simple dotnet core application and try to fetch list of buckets using AWS s3 credentials.
Context
dotnet 4.72 was working fine but now after migrating to dotnet core it is not working.
Your Environment
AWSSDK.Core version used: 3.3.100
Service assembly and version used:
Operating System and version: Windows 10
Visual Studio version: VS 2015
Targeted .NET platform: dotnet core
.NET Core Info
.NET Core version used for development: dotnet core 2.1
I got the following response using GitHub ticket :
https://github.com/aws/aws-sdk-net/issues/1246
Hi. We do not make any guarantees on how the SDK behaves with non-S3 service.
Please re-open the issue if you can reproduce the problem against S3.